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

TL;DR

Delete the failed job (kubectl delete job pangea-cluster-authn-[id] -n [namespace]) so it can be recreated cleanly. Per Pangea docs: a stuck install is usually a failed job - find it with kubectl get job and delete it.

Steps

1. Delete the failed job (kubectl delete job pangea-cluster-authn-[id] -n [namespace]) so it can be recreated cleanly.
2. Per Pangea docs: a stuck install is usually a failed job - find it with kubectl get job and delete it.

When to use

Use this skill when you run into "Pangea cluster pods (authn, embargo, gateway) never reach running state".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

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