Monitor Calico Network Operator Status

Use the following procedure to monitor the health of the components managed by the Tigera Operator. For an overview of the operator model, see Calico Network Operator Overview (Tigera Operator).

Procedure

1. Use tigerastatus to check overall component status. All components should report AVAILABLE=True, PROGRESSING=False, and DEGRADED=False.

   ~(keystone_admin)]$ kubectl get tigerastatus
   NAME         AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
   calico       True        False         False      ...     All objects available
   gatewayapi   True        False         False      ...     All objects available
   ippools      True        False         False      ...     All objects available
   

2. Check the operator logs. Review the most recent entries to confirm the operator is reconciling without errors.

   The Tigera Operator logs record reconciliation activity and any errors encountered while managing the Calico resources.

   ~(keystone_admin)]$ kubectl logs -n tigera-operator deployment/tigera-operator --tail=50
   

3. Check the Installation CR status conditions. Inspect these conditions to confirm the Calico deployment is fully reconciled and ready.

   The Installation CR reports the operator’s reconciliation state through its status conditions.

   ~(keystone_admin)]$ kubectl get installation default -o jsonpath='{.status.conditions}' | python3 -m json.tool
   

4. Check the Calico system pods. Confirm each pod reports READY and a Running status.

   The calico-system namespace hosts the core Calico networking pods (calico-node, calico-typha, and calico-kube-controllers).

   ~(keystone_admin)]$ kubectl get pods -n calico-system
   NAME                                       READY   STATUS    RESTARTS   AGE
   calico-kube-controllers-xxxxx              1/1     Running   0          ...
   calico-node-xxxxx                          1/1     Running   0          ...
   calico-typha-xxxxx                         1/1     Running   0          ...