Jan Broer 2a91bcf147 Support for claiming existing certificate + Store certificate in Volume
* Adds a new required "certificate name" parameter (backward
compatible): When there is an existing certificate by that name it will
be overwritten with a renewed certificate
* fullchain.pem and privatekey.pem are now stored in a Volume under /etc/letsencrypt/production/certificates/. This is until we find a better way to share the private key with other services.
2016-03-31 17:34:19 +02:00
2016-03-30 18:11:29 +02:00
2016-03-12 21:08:57 +01:00
2016-03-12 21:08:57 +01:00
2016-03-29 21:43:57 +02:00
2016-03-12 21:08:57 +01:00
2016-03-12 21:08:57 +01:00
2016-03-12 21:08:57 +01:00
2016-03-12 21:08:57 +01:00

Rancher + Let's Encrypt = Awesome Sauce

Let's Encrypt Certificate Manager for Rancher

Circle CI

A Rancher service that obtains free SSL/TLS certificates from the Let's Encrypt CA, adds them to Rancher's certificate store and manages renewal and propagation of updated certificates to load balancers.

Requirements

  • Rancher Server >= v0.63.0
  • Existing account with one of the supported DNS providers (currently CloudFlare, DigitalOcean and AWS Route53).

How to use

This application is distributed via the Rancher Community Catalog.

Enable the Community Catalog under Admin => Settings in the Rancher UI. Then find the Let's Encrypt template in the Catalog section of the UI and follow the instructions.

Building the image

make build && make image

Todo

  • Add unit/integration tests
  • Support additional DNS providers

Contributions

PR's welcome!

S
Description
🐮 Rancher service that obtains and manages free SSL certificates from the Let's Encrypt CA
Readme 3.4 MiB
Languages
Go 89.6%
Makefile 5.5%
Shell 3.3%
Dockerfile 1.6%