How to control speed of RollingUpdate
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
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
add a comment |
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
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
add a comment |
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
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
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 '18 at 16:10
sthompssthomps
1,53932241
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
asked Nov 19 '18 at 16:10
sthompssthomps
1,53932241
1,53932241
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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 '18 at 7:06
RicoRico
27.3k94865
Oh,maxUnavailableandmaxSurgeare 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 '18 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 at 17:36
Hm, also wasn't sure ifminReadySecondscould be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 '18 at 17:39
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 '18 at 7:06
RicoRico
27.3k94865
Oh,maxUnavailableandmaxSurgeare 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 '18 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 at 17:36
Hm, also wasn't sure ifminReadySecondscould be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 '18 at 17:39
add a comment |
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 '18 at 7:06
RicoRico
27.3k94865
Oh,maxUnavailableandmaxSurgeare 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 '18 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 at 17:36
Hm, also wasn't sure ifminReadySecondscould be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 '18 at 17:39
add a comment |
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 '18 at 7:06
RicoRico
27.3k94865
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 '18 at 7:06
RicoRico
27.3k94865
answered Nov 20 '18 at 7:06
RicoRico
27.3k94865
answered Nov 20 '18 at 7:06
RicoRico
27.3k94865
answered Nov 20 '18 at 7:06
RicoRico
27.3k94865
27.3k94865
Oh,maxUnavailableandmaxSurgeare 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 '18 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 at 17:36
Hm, also wasn't sure ifminReadySecondscould be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 '18 at 17:39
add a comment |
Oh,maxUnavailableandmaxSurgeare 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 '18 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 at 17:36
Hm, also wasn't sure ifminReadySecondscould be used for this purpose. But in any case, might be more of a hack than your canary suggestion.
– sthomps
Nov 20 '18 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 '18 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 '18 at 17:31
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 at 17:36
gotcha, wasn't really sure if you meant that. Thx!
– Rico
Nov 20 '18 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 '18 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 '18 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.
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
