Skip to main content

Troubleshooting a Helm deployment

Written by Aron Day

If an install or upgrade does not become ready, check the Helm release and the pods it created. These commands assume the 3b release in the 3b namespace:

helm -n 3b status 3b
kubectl -n 3b get pods
kubectl -n 3b get jobs
kubectl -n 3b get events --sort-by=.lastTimestamp

For a pod that is restarting or stuck, check its events and previous logs. Replace <pod-name> with the name from get pods:

kubectl -n 3b describe pod <pod-name>
kubectl -n 3b logs <pod-name> --all-containers --previous --tail=100

If the pod has not restarted, remove --previous. Check the Helm installation guide for the cluster requirements. If you need help, send Tines support the release status, pod events, and relevant logs. Redact secrets before sharing them.

Did this answer your question?