Open RomanOrlovskiy opened 1 year ago
We have seen this startup failure too. But only momentarily. It made no sense since "we did not change anything (tm)".
It later turned out that this happened because one of our apiservices became unavailable (in our case linkerd-tap
because the pods ran into an issue). You can check with kubectl get apiservices.apiregistration.k8s.io
. This did not affect any other workload on the cluster. I honestly do not understand why it causes secret-generator to hang. It definitely should not cause that.
Ideas?
We looked some more into this issue. Seems to be a bug in the (old) version of operator-sdk. Guess an update would fix that.
Is there a workaround for this issue?
Workaround: Fix all of your webhooks ;-). This only happens when other webhooks are broken for us.
Describe the bug The pod is not able to start up during the initial deployment using the latest v3.4.0 helm chart. Is it possible this is related to the Kubernetes version?
Those are the only logs available in pods:
To Reproduce Just a basic installation using helm.
values.yaml:
Environment: