cert-manager v0.3.2 released containing critical fix for Let's Encrypt

[james.m...@jetstack.io]

We have just tagged and released cert-manager v0.3.2, which contains a critical fix for the ACME Issuer implementation.

Full details taken from the release page:

---

This is a bugfix release containing a critical patch for the ACME Issuer type.

Let's Encrypt recently made a change to their API to bring it in-line with the latest ACME draft spec, which has caused cert-manager to fail to obtain Certificates in some cases. More information can be found on the Let's Encrypt forum.

It is advised that all users of v0.3.x upgrade to this release immediately, as without the changes include in this release, certificate renewal will not be successful.

As this is a patch release, there have been no breaking changes. Please do not hesitate to upgrade your deployments!

Changelog since v0.3.1

* ACME: Handle the new Let's Encrypt 'Ready' state for orders (#698, @edevil)

* Fix panic when a Certificate specifies a DNS01 provider that is not present on the Issuer resource (#708, @munnerz)

* Fix bug that could cause changes to Ingress resources when using ingress-shim to not be properly propagated to their respective Certificate resources (#686, @kragniz)

---

The official Helm chart in kubernetes/charts has been updated to default to this release. It is advised that all users upgrade immediately.