Version 1.7

This is one of the biggest releases of the Let's Encrypt controller so far!
The single most notable change is that the controller has been rewritten (or
rather "refactored") as a Kotlin application instead of the previous
"Spooky Java"-stack, but there are several other enhancements and fixes as
well.

Simply deploy the controller manifest to your cluster to get started.

---

Features:

• The controller has been re-written in Kotlin! Detailed information can be found
  in pull request #57 and issue #54
• Support for split-brain Route53 setups has been added by ignoring private zones
  during zone selection (see #61 and #64, thanks @itomaldonado!)
• The controller will now re-provision certificates if domains are removed from
  a certificate request.

Fixes and chores:

• All outdated dependencies have been bumped. Note: This has the minor effect
  that the created Secret-object no longer contains a field with only the
  intermediate certificates (previously the chain field).
  Due to changes in the acme4j library, both the chain and fullchain fields now
  contain a full certificate chain. The chain field will be deprecated in a future
  version.
• The MIT-license has been re-added to the project (thanks @ensonic for pointing it out!).
  All trees in this repository that do not have a LICENSE file can be assumed to be
  MIT-licensed, too.
• The build system used by this project is now Gradle, but this has no user-visible
  changes.

As always there have been some minor refactorings and fixes along the way.

Release version 1.6

Features:

• Existing domain authorizations will be re-used within the period that they are valid. For small changes to domain lists this results in huge speed improvements and higher reliability.
• TXT records will be removed again after challenges have been completed to avoid having "zombie"-records hanging around

Fixes:

• An issue was fixed that could result in unstructured log messages being printed when running on GCP
• The default wait time before validating challenges with Google Cloud DNS has been increased to avoid a persistent issue with DNS-consistency (#14)

In addition some maintenance work has been performed on the codebase (style fixes and dependency bumps).

Release version 1.5

Features:

• Structured JSON log output
• Configurable log levels

Fixes:

• Fixed a potential stack overflow by using a ScheduledEexecutorService for
  scheduling.

Release version 1.4

Features:

• Configurable secret file names (thanks @ahume)
  Configurable secret file names can be used to, for example, support
  Kubernetes Ingress controllers with TLS by specifying the expected
  file names.

Fixes:

• Fixes an issue that prevented secret annotations from being updated
  correctly if the requested certificates for a service were changed.

Release version 1.3.1

• Fixes a bug that could cause SAN certificate retrievals using AWS Route53 to fail.

Release version 1.3

• Support for multiple domains in a single certificate! (SAN)

  Simply write an array of domains in the request annotation and the
  controller will fetch a single certificate that is valid for all of
  them.
  See the README for usage information.

• Better reconciliation!

  The controller will now check that secrets actually contain the
  requested certificates, and not just that a secret with a matching
  name is present.

• Various other smaller fixes & improvements.

  Check out the milestone for detailed information:
  https://github.com/tazjin/kubernetes-letsencrypt/milestone/4?closed=1

Release version 1.2

• Full-chain certificate file in the secret
• Source annotations for ACME CA on secrets
• Various minor improvements

Release version 1.1

This is the second release of the Letsencrypt Controller.

New features and fixes:

• Support for Google Cloud DNS
• Automatic cloud platform detection
• Support for multiple namespaces
• Support for certificate renewal
• Many smaller fixes

Take a look at the release milestone for more detailed information:
https://github.com/tazjin/kubernetes-letsencrypt/milestone/1?closed=1

Release version 1.0

Initial release of the Letsencrypt controller.

Features:

• Retrieve certificates with DNS challenges using AWS Route53
• Publish certificates as secrets
• Reconcile on launch and watch new service updates

Many important features are still missing. Keep an eye on the issues
list.