Comment 2 for bug 1898792

The interesting thing is that it looks like the pod in question exists:

dex-auth/0* terminated idle 10.1.80.20 5556/TCP unit stopped by the cloud
dex-auth/1 terminated failed 10.1.80.51 5556/TCP unit stopped by the cloud
dex-auth/2 error idle 10.1.80.52 5556/TCP hook failed: "start"

Here's what kubectl sees:

NAMESPACE NAME READY STATUS RESTARTS AGE
kubeflow dex-auth-6b568d4ddd-vh2qf 1/1 Running 0 37s
kubeflow dex-auth-844c5ffdb-bm4gv 0/1 Terminating 1 9m57s

I assume that `dex-auth-6b568d4ddd-vh2qf` == `dex-auth/2`, which doesn't explain why `dex-auth/2` has a failing start hook. Perhaps the error is being attributed to the wrong unit?