Skip to content

Kubernetes Operator Troubleshooting

For the shared debugging workflow, start with Debugging and Troubleshooting. It explains Debug Events, instance debug, and the relationship between workflow state and live resource state.

Operator Troubleshooting Checklist

Use omnistrate-ctl instance debug <instance-id> to open the Operator resource and work through the following:

  1. Review application logs from the operator-managed workload.
  2. Confirm deployment API parameters resolved to the expected custom-resource inputs.
  3. Inspect Operator CRD outputs and exported deployment output parameters.
  4. Check workflow events to separate Omnistrate orchestration errors from operator reconciliation errors.
  5. Use the Metrics tab or omnistrate-ctl instance dashboard <instance-id> to verify dashboard access when metrics are enabled.
  6. Use Deployment Cell Access to inspect the custom resource, operator logs, events, and status conditions directly.

The shared Operator Troubleshooting Checklist contains the same operational checks alongside the Compose, Helm, and Terraform checklists.

Workflow and Resource Failures

Check the operator’s status fields and the successCondition and failureCondition expressions used by the workflow. If readiness stalls or an output is not resolved, confirm that the operator writes the referenced status path and that the workflow targets the intended namespace and resource name.