-
Notifications
You must be signed in to change notification settings - Fork 375
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
Move from let's encrypt v1 API to v2; kube-lego to cert-manager #1448
Labels
Comments
This was referenced Mar 2, 2022
This was referenced Apr 11, 2022
This was referenced Aug 5, 2022
This was referenced Sep 22, 2022
This was referenced Sep 29, 2022
This was referenced Apr 24, 2023
This was referenced Aug 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
We have moved to v2 and kube-lego's successor, cert-manager, before things start breaking in each cluster
alfajores
alfajoresstaging
baklavastaging
pilot
pilotstaging
integration
celo-networks-dev
Current Behavior
We currently use the v1 API of let's encrypt with kube-lego, but this has been deprecated.
The text was updated successfully, but these errors were encountered: