This alert fires when one or more virt-api pods are running, but not
all of them have been in a Ready state for the last 10 minutes.
The virt-api serves the KubeVirt API. The deployment typically runs two
replicas for high-availability.
Reduced capacity or redundancy for the KubeVirt API. If the condition
persists, it can lead to the NoReadyVirtAPI alert and API unavailability.
Set the NAMESPACE environment variable:
$ export NAMESPACE="$(kubectl get kubevirt -A -o jsonpath='{.items[].metadata.namespace}')"
Check the status of the virt-api pods:
$ kubectl -n $NAMESPACE get pods -l kubevirt.io=virt-api
Check the virt-api deployment and its events:
$ kubectl -n $NAMESPACE describe deploy virt-api
Check pod readiness and conditions for non-ready pods:
$ kubectl -n $NAMESPACE get pods -l kubevirt.io=virt-api -o wide
$ kubectl -n $NAMESPACE describe pod -l kubevirt.io=virt-api
If pods are in CrashLoopBackOff or to inspect runtime failures, check
virt-api pod logs and look for errors:
$ kubectl -n $NAMESPACE logs -l kubevirt.io=virt-api
Check for node issues, such as a NotReady state:
$ kubectl get nodes
Identify why some virt-api pods are not ready (e.g. failed readiness probe,
resource pressure, image pull issues) and resolve the underlying cause.
If you cannot resolve the issue, see the following resources: