Releases: cert-manager/cert-manager
Releases · cert-manager/cert-manager
v0.1.1
Overview
This release fixes some issues with the ACME implementation when using the GCLB ingress controller. Previously, cert-manager might have passed the HTTP01 self check before the new path had propagated to all of Google's edge locations.
This release also fixes a race in the HTTP01 challenge solver.
Changelog since v0.1.0
v0.1.0
This is the first release of cert-manager. It is currently still not in a production ready state, and features are subject to change.
Notable features:
- Automated certificate renewal
- ACME DNS-01 challenge mechanism
- CloudDNS
- Route53
- Cloudflare
- ACME HTTP-01 challenge mechanism
- Should be compatible with all ingress controllers following ingress spec (GCE & nginx tested)
- Simple CA based issuance
- Create an Issuer that references a Secret resource containing a signing keypair, and issue/renew certificates from that.
- Cluster-wide issuers (aka ClusterIssuer)
- Backed by CRDs
- Events logged to the Kubernetes API
- Status block utilised to store additional state about resources
Please check the README for a quick-start guide.
We really value any feedback and contributions to the project. If you'd like to get involved, please open some issues, comment or pick something up and get started!