k8s-helm-troubleshooting
Helm troubleshooting
Find out why a Helm release fails or is stuck, and propose a fix. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
Helm keeps every release in a Secret (type helm.sh/release.v1, named
sh.helm.release.v1.<release>.v<revision>), with its values, which often hold
passwords. helm status, helm history, helm list and helm get all read those
Secrets, and you never read Secrets. So you investigate the release's objects with
kubectl, and you give the helm commands to the user to run and paste back. They are
under "Proposed fix" only because they read Secrets, not because they change anything;
say so when you hand them over. Never ask for helm get values output without warning
that values can contain passwords the user should remove first.
The commands use placeholders: my-app (the release), my-namespace (its namespace)
and my-app-podinfo (an object of the release). Replace them with the real names.