How to control speed of RollingUpdate
up vote
1
down vote
favorite
I have a deployment configured in yml using RollingUpdate:
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 0
maxSurge: 10%
I'd like to be able to slow down the deployment to give a longer window in which I can pause and possibly rollback.
Is there a way to configure this?
kubernetes
add a comment |
up vote
1
down vote
favorite
I have a deployment configured in yml using RollingUpdate:
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 0
maxSurge: 10%
I'd like to be able to slow down the deployment to give a longer window in which I can pause and possibly rollback.
Is there a way to configure this?
kubernetes
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a deployment configured in yml using RollingUpdate:
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 0
maxSurge: 10%
I'd like to be able to slow down the deployment to give a longer window in which I can pause and possibly rollback.
Is there a way to configure this?
kubernetes
I have a deployment configured in yml using RollingUpdate:
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 0
maxSurge: 10%
I'd like to be able to slow down the deployment to give a longer window in which I can pause and possibly rollback.
Is there a way to configure this?
kubernetes
kubernetes
asked Nov 19 at 16:10
sthomps
1,50432139
1,50432139
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Kubernetes doesn't really have a way of controlling this (the speed of the rolling updates). maxUnavailable: 0, maxSurge: 10%
seems like a step gap hack.
If you are concerned about your update being ready and having the ability to rollback, you should consider creating a canary Deployment. In other words, another Deployment with a small number of replicas, that you can delete if something goes wrong.
Another alternative is looking at a Service-Mesh like Istio that allows you to do Canary Deployments.
Oh,maxUnavailable
andmaxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.
– sthomps
Nov 20 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
Hm, also wasn't sure ifminReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 at 17:39
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Kubernetes doesn't really have a way of controlling this (the speed of the rolling updates). maxUnavailable: 0, maxSurge: 10%
seems like a step gap hack.
If you are concerned about your update being ready and having the ability to rollback, you should consider creating a canary Deployment. In other words, another Deployment with a small number of replicas, that you can delete if something goes wrong.
Another alternative is looking at a Service-Mesh like Istio that allows you to do Canary Deployments.
Oh,maxUnavailable
andmaxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.
– sthomps
Nov 20 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
Hm, also wasn't sure ifminReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 at 17:39
add a comment |
up vote
2
down vote
accepted
Kubernetes doesn't really have a way of controlling this (the speed of the rolling updates). maxUnavailable: 0, maxSurge: 10%
seems like a step gap hack.
If you are concerned about your update being ready and having the ability to rollback, you should consider creating a canary Deployment. In other words, another Deployment with a small number of replicas, that you can delete if something goes wrong.
Another alternative is looking at a Service-Mesh like Istio that allows you to do Canary Deployments.
Oh,maxUnavailable
andmaxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.
– sthomps
Nov 20 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
Hm, also wasn't sure ifminReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 at 17:39
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Kubernetes doesn't really have a way of controlling this (the speed of the rolling updates). maxUnavailable: 0, maxSurge: 10%
seems like a step gap hack.
If you are concerned about your update being ready and having the ability to rollback, you should consider creating a canary Deployment. In other words, another Deployment with a small number of replicas, that you can delete if something goes wrong.
Another alternative is looking at a Service-Mesh like Istio that allows you to do Canary Deployments.
Kubernetes doesn't really have a way of controlling this (the speed of the rolling updates). maxUnavailable: 0, maxSurge: 10%
seems like a step gap hack.
If you are concerned about your update being ready and having the ability to rollback, you should consider creating a canary Deployment. In other words, another Deployment with a small number of replicas, that you can delete if something goes wrong.
Another alternative is looking at a Service-Mesh like Istio that allows you to do Canary Deployments.
answered Nov 20 at 7:06
Rico
25.1k94864
25.1k94864
Oh,maxUnavailable
andmaxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.
– sthomps
Nov 20 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
Hm, also wasn't sure ifminReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 at 17:39
add a comment |
Oh,maxUnavailable
andmaxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.
– sthomps
Nov 20 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
Hm, also wasn't sure ifminReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 at 17:39
Oh,
maxUnavailable
and maxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.– sthomps
Nov 20 at 17:31
Oh,
maxUnavailable
and maxSurge
are just my current RollingDeploy config. Didn't mean to suggest I was using those to control the speed. Figured I'd just paste my current RollingDeploy config incase I'm missing something. Canary sounds like a good step for now.– sthomps
Nov 20 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 at 17:36
Hm, also wasn't sure if
minReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.– sthomps
Nov 20 at 17:39
Hm, also wasn't sure if
minReadySeconds
could be used for this purpose. But in any case, might be more of a hack than your canary suggestion.– sthomps
Nov 20 at 17:39
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378626%2fhow-to-control-speed-of-rollingupdate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown