Helm upgrade --install isn't picking up new changes
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm using the command below in my build CI such that the deployments to helm happen on each build. However, I'm noticing that the changes aren't being deployed.
helm upgrade --install --force
--namespace=default
--values=kubernetes/values.yaml
--set image.tag=latest
--set service.name=my-service
--set image.pullPolicy=Always
myService kubernetes/myservice
Do I need to tag the image each time? Does helm not do the install if the same version exists?
kubernetes-helm edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
add a comment |
I'm using the command below in my build CI such that the deployments to helm happen on each build. However, I'm noticing that the changes aren't being deployed.
helm upgrade --install --force
--namespace=default
--values=kubernetes/values.yaml
--set image.tag=latest
--set service.name=my-service
--set image.pullPolicy=Always
myService kubernetes/myservice
Do I need to tag the image each time? Does helm not do the install if the same version exists?
kubernetes-helm edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
add a comment |
I'm using the command below in my build CI such that the deployments to helm happen on each build. However, I'm noticing that the changes aren't being deployed.
helm upgrade --install --force
--namespace=default
--values=kubernetes/values.yaml
--set image.tag=latest
--set service.name=my-service
--set image.pullPolicy=Always
myService kubernetes/myservice
Do I need to tag the image each time? Does helm not do the install if the same version exists?
kubernetes-helm edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
I'm using the command below in my build CI such that the deployments to helm happen on each build. However, I'm noticing that the changes aren't being deployed.
helm upgrade --install --force
--namespace=default
--values=kubernetes/values.yaml
--set image.tag=latest
--set service.name=my-service
--set image.pullPolicy=Always
myService kubernetes/myservice
Do I need to tag the image each time? Does helm not do the install if the same version exists?
kubernetes-helm kubernetes-helm edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
edited Nov 28 '18 at 2:02
Hovercraft Full Of Eels
263k20213319
263k20213319
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
asked Nov 23 '18 at 17:21
AnthonyAnthony
10.3k2294191
10.3k2294191
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Yes, you need to tag each build rather than use 'latest'. Helm does a diff between the template evaluated from your parameters and the currently deployed one. Since both are 'latest' it sees no change and doesn't apply any upgrade (unless something else changed). This is why the helm best practices guide advises that "container image should use a fixed tag or the SHA of the image". (See also https://docs.helm.sh/chart_best_practices/ and Helm upgrade doesn't pull new container )
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
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%2f53450759%2fhelm-upgrade-install-isnt-picking-up-new-changes%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
Yes, you need to tag each build rather than use 'latest'. Helm does a diff between the template evaluated from your parameters and the currently deployed one. Since both are 'latest' it sees no change and doesn't apply any upgrade (unless something else changed). This is why the helm best practices guide advises that "container image should use a fixed tag or the SHA of the image". (See also https://docs.helm.sh/chart_best_practices/ and Helm upgrade doesn't pull new container )
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
add a comment |
Yes, you need to tag each build rather than use 'latest'. Helm does a diff between the template evaluated from your parameters and the currently deployed one. Since both are 'latest' it sees no change and doesn't apply any upgrade (unless something else changed). This is why the helm best practices guide advises that "container image should use a fixed tag or the SHA of the image". (See also https://docs.helm.sh/chart_best_practices/ and Helm upgrade doesn't pull new container )
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
add a comment |
Yes, you need to tag each build rather than use 'latest'. Helm does a diff between the template evaluated from your parameters and the currently deployed one. Since both are 'latest' it sees no change and doesn't apply any upgrade (unless something else changed). This is why the helm best practices guide advises that "container image should use a fixed tag or the SHA of the image". (See also https://docs.helm.sh/chart_best_practices/ and Helm upgrade doesn't pull new container )
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
Yes, you need to tag each build rather than use 'latest'. Helm does a diff between the template evaluated from your parameters and the currently deployed one. Since both are 'latest' it sees no change and doesn't apply any upgrade (unless something else changed). This is why the helm best practices guide advises that "container image should use a fixed tag or the SHA of the image". (See also https://docs.helm.sh/chart_best_practices/ and Helm upgrade doesn't pull new container )
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
answered Nov 23 '18 at 19:00
Ryan DawsonRyan Dawson
4,9423428
4,9423428
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
add a comment |
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
I suspect it would also force an image pull if you added the '--recreate-pods' flag.
– Ryan Dawson
Nov 24 '18 at 14:13
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
When they say "SHA of the image" Do they mean a git SHA?
– Anthony
Nov 25 '18 at 11:37
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
I think it means the docker image sha256 code - stackoverflow.com/questions/32046334/…
– Ryan Dawson
Nov 25 '18 at 14:31
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%2f53450759%2fhelm-upgrade-install-isnt-picking-up-new-changes%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
