Please refer to the following commands to perform a health check or investigation into the Rok Operator.
1. Check the status of the Rok Operator StatefulSet:
$ kubectl get statefulset -n rok-system rok-operator -o wide
2. Check the status of the Rok Operator Pod:
$ kubectl get pods -n rok-system rok-operator-0 -o wide
3. Inspect the events on the Rok Operator StatefulSet:
$ kubectl describe statefulset -n rok-system rok-operator
4. Inspect the events of the Rok Operator Pod:
$ kubectl describe pod -n rok-system rok-operator-0
5. Inspect the logs of the Rok Operator Pod:
$ kubectl logs -n rok-system rok-operator-0 -f
After successful deployment, and under normal operation, the Rok Operator Pod should emit log messages similar to the following ones:
2022-03-09T16:48:13.588481+0000 rok-operator pid=9/tid=9/pytid=139658617316048
clusterdriver:898 [INFO] [rokcluster=rok/rok] Health: OK, Phase: Running
2022-03-09T16:48:15.278882+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:203 [INFO] [rokcluster=rok/rok] Cluster is up-to-date with desired version
2022-03-09T16:48:15.279140+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:757 [INFO] [rokcluster=rok/rok] Syncing secondary resources
2022-03-09T16:48:16.435956+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:740 [INFO] [rokcluster=rok/rok] Synced secondary resources
2022-03-09T16:48:16.436172+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:761 [INFO] [rokcluster=rok/rok] Managing cluster members
2022-03-09T16:48:16.513664+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:605 [INFO] [rokcluster=rok/rok] Current and expected members match,
no need to scale the cluster
2022-03-09T16:48:16.513936+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:764 [INFO] [rokcluster=rok/rok] Syncing cluster configuration
2022-03-09T16:48:16.549701+0000 rok-operator pid=9/tid=9/pytid=139658617317328
reconcile:688 [INFO] [rokcluster=rok/rok] Successfully synced cluster configuration,
no changes were detected
Useful links
Comments
0 comments
Article is closed for comments.