I used --wait option during helm upgrade but found while waiting for the deployment ready, once a failure return from k8s api happened, helm will exit immidiately.

Since a chart may contain various of resources, it is not so good to exit immidiately once a failure API calling happened while waiting for them to be ready

I think there should be some retrys while calling APIs since network APIs are designed to fail.

logs attached:

wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
wait.go:225: [debug] Deployment is not ready: core/cdf-apiserver. 0 out of 1 expected pods are ready
Error: etcdserver: leader changed
helm.go:94: [debug] etcdserver: leader changed

Output of helm version:
v3.3.0

Output of kubectl version:
v1.20.4

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
kubeadm