monitoring

LowVirtAPICount

Meaning

This alert fires when only one available virt-api pod is detected during a 60-minute period, although at least two nodes are available for scheduling.

Impact

An API call outage might occur during node eviction because the virt-api pod becomes a single point of failure.

Diagnosis

  1. Set the NAMESPACE environment variable:

    $ export NAMESPACE="$(kubectl get kubevirt -A -o custom-columns="":.metadata.namespace)"
    
  2. Check the number of available virt-api pods:

    $ kubectl get deployment -n $NAMESPACE virt-api -o jsonpath='{.status.readyReplicas}'
    
  3. Check the status of the virt-api deployment for error conditions:

    $ kubectl -n $NAMESPACE get deploy virt-api -o yaml
    
  4. Check the nodes for issues such as nodes in a NotReady state:

    $ kubectl get nodes
    

Mitigation

Try to identify the root cause and to resolve the issue.

If you cannot resolve the issue, see the following resources: