While Onload Operator configures KMM, it does not report on, or otherwise repeat, logs, and statuses produced by KMM. The following commands are a summary of KMM 1.1 troubleshooting commands:
- Expect
Runningpods and no messages about in-cluster build failures:onload_cr_name=onload kubectl describe ds -l kmm.node.kubernetes.io/module.name=${onload_cr_name}-module kubectl describe ds -l kmm.node.kubernetes.io/module.name=${onload_cr_name}-sfcmod kubectl logs -l kmm.node.kubernetes.io/module.name=${onload_cr_name}-module kubectl logs -l kmm.node.kubernetes.io/module.name=${onload_cr_name}-sfcmod - Expect reconciler loop to have
succeeded:
kubectl logs -n openshift-kmm deployment/kmm-operator-controller-manager --tail 200 -f
Refer to KMM documentation for further expected deployment state details and OpenShift-specific troubleshooting advice.