Troubleshooting

This section will contain assorted troubleshooting steps for common failure or misconfiguration scenarios.

My Pod won't start!

If you find that your pod will not start, first retrieve its status:

$ kubectl get pods
NAME                                                 READY   STATUS              RESTARTS   AGE
ignition-gateway-0                                   0/1     Init:0/1            0          2m47s

Here we see our pod stuck in Init:0/1 status. In order to find more information, use kubectl describe:

$ k describe pod/ignition-gateway-0
# ...
Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  3m47s                default-scheduler  0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
  Normal   Scheduled         3m46s                default-scheduler  Successfully assigned demo/ignition-gateway-0 to docker-desktop
  Warning  FailedMount       98s (x9 over 3m46s)  kubelet            MountVolume.SetUp failed for volume "gan-issuer-tls" : secret "my-external-issuer" not found

Here we can see that there is an issue mounting the Gateway Network Issuer secret. From here we can trouble shoot the configuration and upgrade the Helm release with a proposed fix.

tip

You may need to actually delete the Pod after you've updated the StatefulSet via a helm upgrade .... It will then be immediately recreated with the new specification.

My Pod won't start!​

My Pod won't start!