-
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
cert-manager could not find resources after upgrade #1134
Comments
I've seen this reported in a few places, and it's due to a bug in Helm's handling of the My current plan is to remove the Removing the annotation will also cause users upgrading from v0.5 to receive an The other option would be to remove the CRDs from that chart altogether, and ship a simple YAML manifest containing CRDs only and require users This is a really messy situation and I've been deliberating a while over the best way to handle this, burning the least number of users. Thanks for opening an issue to track it, & I'm keen to hear any thoughts/ideas you may have on this (as we can't release 0.6 without a resolution!) |
I ran into the same issue. To fix, I recreate everything? |
@sww314 yes, I stored all issuers and certifiates to yaml, deleted cert-manager using helm, then installed new version and restored issuers and certificates using |
I've opened #1138 to attempt to resolve this - we now require the CRD to be manually installed as part of the installation (with |
I just upgraded from v0.4.1 to v0.6.0 and somehow had to re-apply the CRDs after
|
bah, I missed this part in the manual, my bad: Upgrading from older versions using Helm |
Describe the bug:
After upgrading cert-manager using helm, cert-manager is not able to find any custom resources:
can't list or create issuer, clusterissuer, certificate.
cert-manager produces a lot of similar logs messages:
Expected behaviour:
cert-manager is able to list or create custom resources
Steps to reproduce the bug:
cert-manager-v0.4.0-dev.3
viahelm install
cert-manager-v0.5.2
viahelm upgrade
Anything else we need to know?:
All existing issuers and certificates was disappeared.
Environment details::
0.4.0-dev.3
to0.5.2
/kind bug
The text was updated successfully, but these errors were encountered: