You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Bhavin Gandhi c3310bb724 fix(pkg/kube): statefulSetReady: handle partition cases correctly ... The partition value can be greater than number of replicas, in that case no pods are rolled out. The expectedReplicas becomes a negative number. https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions In the cases where the update does not change anything in the pod template, the updatedReplicas value from StatefulSet status remains unchanged. Such updates can still set some partition value, and UpdatedReplicas is always greater than expectedReplicas. Basically, the StatefulSet is ready / rolled-out. In both the above scenarios, providing `--wait` flag causes it to timeout waiting indefinitely. Because updatedReplicas can never be negative, or be equal to the expectedReplicas for the second case. This commit handles both the scenarios by checking if UpdatedReplicas is smaller than expectedReplicas. If it is, then the StatefulSet is not ready yet. Based on the code from kubectl rollout: a450ebd59c/pkg/polymorphichelpers/rollout_status.go (L138-L141) Closes #8674 Signed-off-by: Bhavin Gandhi <bhavin7392@gmail.com>		5 years ago
..
action	…
chart	…
chartutil	…
cli	…
downloader	…
engine	…
gates	…
getter	…
helmpath	…
kube	fix(pkg/kube): statefulSetReady: handle partition cases correctly	5 years ago
lint	…
plugin	…
postrender	…
provenance	…
release	…
releaseutil	…
repo	…
storage	…
strvals	…
time	…