Pangea cluster pods (authn, embargo, gateway) never reach running state

Per Pangea docs: a stuck install is usually a failed job - find it with kubectl get job and delete it.

Context: Problem: After install, no pangea-cluster pods are running. Diagnose: kubectl get pods -n [namespace] to confirm, then kubectl get job -n [namespace] to find the failed install job. Delete the failed job (kubectl delete job pangea-cluster-authn-[id] -n [namespace]) so it can be recreated cleanly.

Matched source

Source: Source: https://pangea.cloud/docs/deployment-models/private-cloud/troubleshooting Original query: "Pangea cluster pods (authn, embargo, gateway) never reach running state" Key terms: authn, cluster, embargo, gateway, never, pangea, pods, reach, running, state

Source: Problem: After install, no pangea-cluster pods are running. Diagnose: kubectl get pods -n [namespace] to confirm, then kubectl get job -n [namespace] to find the failed install job. Delete the failed job (kubectl delete job pangea-cluster-authn-[id] -n [namespace]) so it can be recreated cleanly.

Verified resolution: Per Pangea docs: a stuck install is usually a failed job - find it with kubectl get job and delete it.

Source URL: https://pangea.cloud/docs/deployment-models/private-cloud/troubleshooting