You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
Letsencrypt has launched the support for wildcard certificate from january 4,2018 with a new v2 api end point. Help us to understand on how to create a single wild card certificate using kube lego.
The text was updated successfully, but these errors were encountered:
Hi there - Letsencrypt currently does not support ACMEv2 in production. A staging test endpoint was added on January 4th, with the production release cited for 27th Feb: https://letsencrypt.org/2017/06/14/acme-v2-api.html
As discussed in #304, we won't be adding support for this to kube-lego, not least because this project is now deprecated in favour of cert-manager, but also because wildcards are only available with DNS based validation, which kube-lego has never supported.
Hi,
Letsencrypt has launched the support for wildcard certificate from january 4,2018 with a new v2 api end point. Help us to understand on how to create a single wild card certificate using kube lego.
The text was updated successfully, but these errors were encountered: