debug-openshell-cluster

Diagnose an OpenShell cluster startup failure by running a diagnostic workflow that validates namespace presence, TLS secrets, k3s health, and pod readiness to identify the root cause and outline remediation steps.

An OpenShell cluster remains unhealthy due to missing TLS secrets, k3s failures, or unresolved pod readiness issues. A guided diagnostic workflow checks cluster state and health endpoints to identify and resolve these underlying operational problems.

Troubleshoot TLS and mTLS issues in an OpenShell Kubernetes deployment by validating TLS secrets and checking cluster health endpoints through a guided diagnostic workflow to ensure proper certificate configuration and restore secure communications.

Yes, you can use this diagnostic workflow for both local and remote OpenShell deployments. It captures actionable insights across environments by checking cluster state, Kubernetes readiness, and gateway start failures regardless of deployment location.

The best way to check Kubernetes readiness for OpenShell components is running an end-to-end diagnostic workflow that validates namespace presence, inspects pod readiness, and verifies health endpoints to ensure your deployment is fully operational.

For an OpenShell gateway start failure, check rollback readiness by validating TLS secrets, inspecting k3s health, and verifying pod readiness through a guided diagnostic workflow to restore cluster health and resolve the startup failure.