This alert fires when no virt-api pod in a Ready state has been detected
for 10 minutes.
The virt-api serves the KubeVirt API.
Without a ready virt-api, API requests for virtual machines
and other KubeVirt resources cannot be served.
KubeVirt API is effectively unavailable. Users and controllers cannot perform API operations such as creating, updating, or deleting virtual machine instances (VMIs) or other KubeVirt resources.
Set the NAMESPACE environment variable:
$ export NAMESPACE="$(kubectl get kubevirt -A -o custom-columns="":.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 events:
$ kubectl -n $NAMESPACE describe deploy virt-api
Review logs of any virt-api pod that is running but not ready:
$ kubectl -n $NAMESPACE logs <virt-api-pod-name> --previous
$ kubectl -n $NAMESPACE logs <virt-api-pod-name>
Check for node issues:
$ kubectl get nodes
Identify the root cause (e.g. all replicas crashing, readiness probe failures,
node or resource issues) and restore at least one ready virt-api pod.
If you cannot resolve the issue, see the following resources: