All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
- Set the ENTRYPOINT instead of the CMD #117
- Fix suppressed error while ACME client creation #155
- Fix the order of namespace/name in the secret names #141
- fix logic typo #110
- Add support for pprof #139
- Update godeps and k8s method signatures #48
- Upgrade docker golang to v1.8 #127
- Add support for running multiple instance of kube-lego in the cluster #105
- Add ability to customize ingress class #101
- Change docker image from scratch to alpine #87
- Add ability to only monitor a single namespace #123
View all the changes
- Workaround for GLBC health check detection bug
- Raise resync period to 60 seconds
- Use correct minimum validity config (used the
LEGO_CHECK_INTERVAL
before)
- Replace lego with the acme library
- Increase tests coverage and automation
- Improved log output, no secrets default log level is debug
- Upgrade dependencies
- Upgrade to go 1.7.3
- Possibility to change api server url [Pavel Sorejs]
- Better error output for failing validations
- Fix problems with updating ingress objects
- Fix version output of kube-lego
- Fix image version in the docs
- Support for GCE load balancer ingress controller
- E2E automation scripts for GCE/NGINX ingress controllers on GKE
- Support for ingress-class annotations to distinguish between GCE/NGINX ingress
- Abstracted the ingress controller specific code into separate packages
- Deployment of kube-lego uses readiness checks
- Handle failed certificate request without exiting kube-lego
- Check for expired certificates periodically (default config every 8 hours)
- Use upstream nginx-ingress-controller (from k8s-contrib)
- Fix bug for empty kube-lego ingress resource
- E2E test for receiving a cert from Let's Encrypt Staging
- Updating docs/examples to use latest nginx-ingress release
- Documentation
- Versioned docker images
- Jenkins builds using pipelines/workflow plugin
- Recognizes the need of a new certificate (domain name missing, certificate expired, certificate unparseable)
- Obtains certificates per TLS object in ingress resources and stores it in Kubernetes secrets using
HTTP-01
challenge - Creates a user account (incl. private key) for Let's Encrypt and stores it in Kubernetes secrets
- Watches changes of ingress resources and reevaluate certificates
- Configures endpoints for
HTTP-01
challenge in a separate ingress resource