-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Remote helm charts should not be upgraded by default #3274
Remote helm charts should not be upgraded by default #3274
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
Codecov Report
|
@googlebot I signed it! |
pkg/skaffold/deploy/helm.go
Outdated
@@ -204,6 +204,9 @@ func (h *HelmDeployer) deployRelease(ctx context.Context, out io.Writer, r lates | |||
if !isInstalled { | |||
args = append(args, "install", "--name", releaseName) | |||
args = append(args, h.Flags.Install...) | |||
} else if !h.shouldUpgradeOnChange(r) { | |||
logrus.Infof("Release %s already installed...\n", releaseName) |
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.
Do you think we should handle and log remote separately?
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.
Sorry not sure exactly what you mean. I am open to anything just needed the main feature of not upgrading remote charts.
Do you want more logging to indicate why the chart wasn't upgraded?
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.
Sorry, I missed this :-( Yes, more logging: since we're changing behaviour, it would be worth including why and what can be done.
@dahovey the CLA bot doesn't have a record for you. Could you please try again? |
@googlebot I signed it! |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
@briandealwis Could you clarify what you mean by 'handle' remote separately? |
@briandealwis could you please take another look? |
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.
A little more logging, otherwise LGTM.
pkg/skaffold/deploy/helm.go
Outdated
@@ -204,6 +204,9 @@ func (h *HelmDeployer) deployRelease(ctx context.Context, out io.Writer, r lates | |||
if !isInstalled { | |||
args = append(args, "install", "--name", releaseName) | |||
args = append(args, h.Flags.Install...) | |||
} else if !h.shouldUpgradeOnChange(r) { | |||
logrus.Infof("Release %s already installed...\n", releaseName) |
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.
Sorry, I missed this :-( Yes, more logging: since we're changing behaviour, it would be worth including why and what can be done.
I think I need some help with this. On my first attempt with this feature the schema had already been updated, but now when I tried to run I did add more logging when |
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.
Sorry @dahovey for the delay. If you merge with HEAD and resolve the conflict, your PR should be much smaller now.
@dahovey sorry this kinda fizzled out, that's on us. would you mind quickly rebasing and regenerating the schema docs so that they're updating the correct version? let me know if you need any help with that. |
@dahovey is there anything I can do to assist to get this ready to merge? |
@dahovey this just needs a rebase and I'll merge it |
…o dahovey/upgradeOnChange
Hi all, I apologize for the delay. I got a whole lot of failures running |
@dahovey sorry to hear you ran into issues with the tests. I see a few things looking at the failures in travis:
we run |
@dahovey - need any help getting this PR pushed through? |
…o dahovey/upgradeOnChange
@tstromberg @nkubala Could one of you please help resolve this error? It is received when running
|
I bumped schema version to Before the tests were refactored I believe I had it setup correctly to test that Thanks for your patience. |
@dahovey that error you were getting comes from the unfortunately this keeps falling behind on our release cadence so the schema version needs to keep getting bumped, but I'll do everything I can to make sure this gets merged in the next week and a half before our next release. would you mind doing one last rebase? |
We just merged the version bump to v2beta5. |
@briandealwis @nkubala Thanks for your patience. This has been a learning experience. Hope everything looks better. I still couldn't resolve the licensing error. I ran which for |
Thanks @dahovey! |
yes! awesome to see this one finally go in! thanks @dahovey for all your patience here, I think we've also learned a thing or two about staying on top of our reviews to make sure things don't fall behind because of us. hopefully your next contribution is a lot less painful 😁 |
Fixes #2245.
Description
Adds config to HelmRelease
upgradeOnChange
.User facing changes
Remote helm charts will NOT be upgraded by default.
Before
Remote helm charts would always be upgraded on local file changes.
After
By default, remote helm charts will not be upgraded on local file changes. User will need to add
upgradeOnChange: true
to any remote charts that need to be upgraded on changes.Next PRs.
n/a
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Reviewer Notes
Release Notes