-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Installation without webhook not working #2015
Comments
interestingly I attempted to downgrade to 0.5.2 again and still see the same issue. Fairly certain everything v0.9.1 related is gone. |
Any update on this issue? Facing a similar problem. |
To my part I test the 0.9.1 without webhook it failed but 0.8.1 works |
We've had the same issue when upgrading from 0.6.x to 0.9.1 and got around it by manually removing the MutatingWebhookConfiguration from the admission controller:
After that I ran into the problem that the ingress-shim flags in the Helm chart are seemingly not supported anymore ( |
Yep, it looks like you've not properly cleaned up the webhook resources you created when you first tried to install with the webhook enabled. I'm going to close this as it isn't really a bug, rather a misconfiguration caused by a borked upgrade/downgrade 😄 |
I attempted to install cert-manager without webhooks as outlined here on GKE with Kubernetes 1.13: https://docs.cert-manager.io/en/latest/getting-started/webhook.html. Unfortunately by installing kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v0.9.1/cert-manager-no-webhook.yaml.
we get:
In the past we had version 0.5.2 installed. First we tried to setup with webhooks. But this resulted in similar errors already during installation. webhook itself did subsequently not start because of missing TLS certificates. The namespace was properly labeled to disable validation.
I would have expected this error to disappear when not using webhooks.
potentially it would be worthwhile to minimize dependencies of that webhook, make sure it is always running even in case of glitch somewhere else.
The text was updated successfully, but these errors were encountered: