-
Notifications
You must be signed in to change notification settings - Fork 92
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
feat: allow migrate from HelmChart v1beta1 to v1beta2 if Helm --take-ownership is set #5046
Conversation
This needs to be merged alongside updating Helm to either use the version with |
I've updated the PR with fetching from Helm PR that supports |
edda4b7
to
c0daf44
Compare
c0daf44
to
2ebd087
Compare
Many thanks @sgalsaleh! I have made the requested changes accordingly and notice the Melange and Apko actions completed successfully. Please let me know how it goes. |
Now that the change is merged in Helm, we can use the 'main' branch rather than the PR branch |
Helm |
apologies @sgalsaleh could you help me approve the change again? I removed the |
ce8f18f
to
bd8fc5b
Compare
This reverts commit a1a42cf.
b6b04d4
to
6c4bc70
Compare
Update: The new |
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.
needs update now that Helm got released.
Hi @sgalsaleh @laverya, I have removed the Helm PR setup due to Could you help me with the final approval? Cheers, |
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 update. Needs KOTS team to review.
Product question: should we add the flag automatically for a more seamless migration? |
@xavpaice signed CLA |
How would we detect this? And can we deterministically detect it, or could the vendor intend something else. I always like making things easier, but if this migration is being heavily moderated by Replicated (like we're helping vendors make these changes and whatnot), then the steps are pretty clear and the risk of doing it automatically might not be necessary. So I could go either way depending on whether we think that's really necessary. |
What this PR does / why we need it:
We currently don't allow migration from existing Helm installation of
v1beta1
withuseHelmInstall: false
to Helmv1beta2
.As Helm CLI will soon support
--take-ownership
flag, this will be possible.This PR allows the application pull for Helm chart with same name in
v1beta2
, as long as there is--take-ownership
flag in Helm additional upgrade flags.Demo: https://www.loom.com/share/db17e620509843d884fbcf98605daaed?t=281
If no
--take-ownership
flag, pull will fail during update checksWhich issue(s) this PR fixes:
Story: sc-117029
Does this PR require a test?
NONE
Does this PR require a release note?
We will need a release note later when upstream Helm CLI supports
--take-ownership
flag.Does this PR require documentation?
Current docs will have to be updated after the change is merged and upstream Helm CLI supports
--take-ownership
flag