Troubleshooting

Restart Loop

If you find that your pods go from the ContainerCreating to Running status but then restart and never get to the READY 1/1 STATUS Running, try disabling the probes. For some reason, the probes aren't able to detect that your pod is running and so kubernetes restarts your pod.

# values.yaml
...
probes:
  liveness:
    enabled: false
  readiness:
    enabled: false
...

502 Bad Gateway

If you receive a 502 Bad Gateway error when trying to view the ingress webpage, this is most likely due to the fact that your pod hasn't finished starting. Some images can be quite large so downloading them can take a while.

# Check the status of your pod.
$ kubectl get pods -n chartnamespace

CrashLoopBackOff

Often times the CrashLoopBackOff error is generated because the chart image is not compatible with the cluster architecture.

Check the pod logs.

$ kubectl logs pod/chartname-7bd595bf64-nj6vg

Check the events.

$ kubectl get events -n chartnamespace

Missing Common

If you're working locally within the repository and you get the following error:

# From within the chart directory
$ helm install my-chart .
Error: found in Chart.yaml, but missing in charts/ directory: common

You need to first update the common dependency.

# From within the chart directory
$ helm update dependency
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "nicholaswilde" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading common from repo https://nicholaswilde.github.io/helm-charts/
Deleting outdated charts

See Testing