-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Helm2 to Helm3 migration #2451
Comments
@AlexShemeshWix There is not much that jetstack can do to fix this, as any changes to the charts will cause the same error. Kube limits specific fields as immutable. I found a workaround which is to manually edit the 3 deployments generated |
Yes thats what i ended up doing. Not very efficient |
True, but this is not really a bug in Helm or the Chart. |
I ran into the same issue, it seems like if we migrate an existing release and there is a selector/label set to |
The right solution to this would be to not use
labels that target this release. |
I have written a few simple string replacement commands to fix this issue. Hope this helps.
|
We have removed this label now as part of our selector, so this shouldn't come up again. As noted before, we sadly can't do anything to help those on older versions trying to upgrade. |
Describe the bug:
Migrating cert-manager helm chart from helm2 to helm3 is not working.
Expected behaviour:
There are no differences except for "app.kubernetes.io/managed-by":"Helm" and it should upgrade without problem
Steps to reproduce the bug:
Ive installed version v0.12.0 of cert-manager helm chart with helm2
Ive migrated helm releases using
helm3 2to3 convert
command.When i run helm3 upgrade i have following error message
Anything else we need to know?:
i can destroy converted release and redeploy it from helm3 and it will work ok.
Environment details::
kube v1.15.6
helm2 v2.16.1
helm3 v3.0.0
cert-manager v0.12.0
/kind bug
The text was updated successfully, but these errors were encountered: