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
kube-lego can only respond to challenges using the HTTP-01 challenge, and only works for Ingress objects.
kube-cert-manager is a lot more flexible. It:
Supports the other two challenge types (SNI-TLS-01, DNS-01)
Uses xenolf/lego to support a ton of DNS providers
Supports certificates as ThirdParty resources, meaning I can use kube-cert-manager to request TLS certificates for anything, like my IRC bouncer, for example
kube-lego:
Ends up re-implementing a subset of ACME (instead of using xenolf/lego)
A comparison with https://github.com/jetstack/kube-lego would be helpful. AFAICT, both projects have the same goal?
The text was updated successfully, but these errors were encountered: