Closed lchdev closed 3 years ago
Hey @lchdev, the upstream helm chart now uses "Recreate" as deployment strategy which should result in upgraded deployments starting as expected.
I could successfully test this on a local cluster (using the upstream master
codebase) by running:
$ helm install kubernetes-secret-generator deploy/helm-chart/kubernetes-secret-generator/.
$ helm upgrade --install kubernetes-secret-generator deploy/helm-chart/kubernetes-secret-generator --set secretLength=50
$ kubectl get po
NAME READY STATUS RESTARTS AGE
kubernetes-secret-generator-84946bf455-q8wjn 1/1 Running 0 30s
The deployment strategy might also be set via helm install [...] --set deploymentStrategy="Recreate"
.
I hope this fixes your issue! If there's anything else we can help you with, please let us know.
Describe the bug Unable to perform a rolling upgrade: new pods are never marked ready because the liveness probe fails continuously.
To Reproduce
helm upgrade --install kubernetes-secret-generator mittwald/kubernetes-secret-generator --version 3.3.2
helm upgrade --install kubernetes-secret-generator mittwald/kubernetes-secret-generator --version 3.3.2 --set secretLength=50
The deployment will try to create a new pod, but the container will enter a crash loop and never become ready:
Container logs:
If I manually kill the old instance, the new pod is able to become the leader and to start successfully.