-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helm: update updateStrategy #2351
Conversation
/retest ci/centos/upgrade-tests-rbd |
/retest ci/centos/mini-e2e-helm/k8s-1.19 |
Both jobs failed with #2264 |
@@ -11,6 +11,11 @@ metadata: | |||
heritage: {{ .Release.Service }} | |||
spec: | |||
replicas: {{ .Values.provisioner.replicaCount }} | |||
strategy: | |||
type: {{ .Values.provisioner.strategy.type }} | |||
rollingUpdate: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should only be included when Values.provisioner.strategy.type == RollingUpdate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, need an if check here to check the strategy.type == RollingUpdate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion! Added the check.
dc30211
to
af98211
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue exists only for deployment, not for daemonset pods? can you please send a separate PR daemonset if it's required?
@@ -11,6 +11,11 @@ metadata: | |||
heritage: {{ .Release.Service }} | |||
spec: | |||
replicas: {{ .Values.provisioner.replicaCount }} | |||
strategy: | |||
type: {{ .Values.provisioner.strategy.type }} | |||
rollingUpdate: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, need an if check here to check the strategy.type == RollingUpdate
af98211
to
0aad55b
Compare
|
/retest ci/centos/upgrade-tests-rbd |
LGTM. However will wait for review from @nixpanic as he was already reviewing it |
/retest ci/centos/mini-e2e-helm/k8s-1.19 |
/retest ci/centos/mini-e2e-helm/k8s-1.21 |
Failed with #2264 |
/retest ci/centos/mini-e2e/k8s-1.21 |
Failed with #2362 |
/retest ci/centos/mini-e2e-helm/k8s-1.21 |
Failed with #2264 |
/retest ci/centos/mini-e2e-helm/k8s-1.20 |
/retest ci/centos/mini-e2e/k8s-1.20 |
1 similar comment
/retest ci/centos/mini-e2e/k8s-1.20 |
Update ceph-csi-rbd.provisioner updatestrategy to allow maxUnavailable pods at a time to be 50% Signed-off-by: Yug Gupta <yuggupta27@gmail.com>
Update ceph-csi-cephfs.provisioner updatestrategy to allow maxUnavailable pods at a time to be 50% Signed-off-by: Yug Gupta <yuggupta27@gmail.com>
Update the provisioner and nodeplugin updatestrategy
to allow maxUnavailable and maxSurge
pods at a time to be 50%
Fixes: #2335
Signed-off-by: Yug Gupta yuggupta27@gmail.com
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)
/retest all
: run this in case the CentOS CI failed to start/report any testprogress or results