Resource validation webhook
v0.4.0 release, we have now added a ‘validating webhook’ for our API resources. This will help prevent invalid configurations being submitted to the API server.
This feature is disabled by default.
Information on enabling the new webhook component can be found in the Resource Validation Webhook document.
New Certificate options
A number of new fields have been added to the Certificate resource type:
keyAlgorithm- support alternative private key algorithms (e.g. RSA or ECDSA) for generated certificates.
keySize- allow specifying an alternative key bit size
isCA- allows generating certificates with the ‘signing’ usage set
organization- allows specifying values for the ‘O’ field of Certificates (for supported providers)
New fields like this make cert-manager more useful for applications beyond just securing Ingress, as well as allowing users to continue meeting their security requirements for X.509 certificates.
New ACME DNS providers
This release includes two new DNS provides for the ACME Issuer:
- RFC2136 These additions should help more users begin using cert-manager with their chosen DNS provider, without having to delegate to an alternate provider that is supported
renew-before-expiry-durationoption to configure how long before expiration a certificate should be attempted to be renewed (#801,
- Add validation webhooks for API types (#478,
- Add extended issuer specific validation to certificates at runtime (#761,
- Adds new fields:
CertificateSpecto allow specifying algorithm (RSA, ECDSA) and key size to use when generating TLS keys (#722,
isCAfield to Certificates (#658,
- Add “organization” field to certificate objects (#838,
- Don’t bundle the CA certificate when using the self signed issuer (#811,
- Fix issue that could cause Certificates to fail renewal (#800,
- Add ACMEDNS as a DNS01 provider (#787,
- Fix panic from
acmedns.goconstructor failure (#858,
- Fix CloudFlare provider failing on cleanup if no record is found (#849,
- Fixed Route53 cleanup errors for already deleted records. (#746,
- Add support for delegating DNS01 challenges using CNAME records. (#670,
- Fix a race that could cause ACME orders to fail despite them being in a ‘valid’ state (#764,
- Fix cleanup of Google Cloud DNS hosted zone for DNS01 challenge records (#754,
- Fix issue causing existing Ingresses to not be cleaned up properly after HTTP01 challenges in some cases (#831,
- Allow metadata server authentication for Google Cloud DNS (#664,
- Add RFC2136 DNS Provider (#661,