Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

Support for Letsencrypt wildcard certificate #318

Closed
nagarjunac opened this issue Feb 12, 2018 · 1 comment
Closed

Support for Letsencrypt wildcard certificate #318

nagarjunac opened this issue Feb 12, 2018 · 1 comment

Comments

@nagarjunac
Copy link

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.

@munnerz
Copy link
Contributor

munnerz commented Feb 12, 2018

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.

There is a PR on cert-manager to add support for wildcard certificates: cert-manager/cert-manager#309

Once the production endpoint is live, we will be merging that shortly afterwards.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants