flywithu/community-catalog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updates rancher-letsencrypt to v0.2.7

Browse Source 
* New DNS providers: Dyn, DNSimple
* Support for claiming existing Rancher certificate by name
* Handle API connection errors on container start
This commit is contained in:
Jan Broer
2016-03-31 03:55:58 +02:00
committed by JanB
parent a45179fa86
commit 222fad83bd
4 changed files with 159 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
templates/letsencrypt/1/README.md
+17
View File
@@ -0,0 +1,17 @@
# Let's Encrypt Certificate Manager
### About
The Let's Encrypt Certificate Manager obtains a free (SAN) SSL Certificate from the [Let's Encrypt CA](https://letsencrypt.org/) and adds it to Rancher's certificate store. Once the certificate is created it is scheduled for auto-renewal 14-days before expiration. The renewed certificate is propagated to all applicable load balancer services.
### Usage
1. Accept the terms of service.
2. Select the API version to use. The Sandbox API should be used for testing purposes.
3. Fill in your email address.
4. Enter the name for storing the certificate in Rancher. If you specify the name of an existing resource it will be overwritten with a renewed certificate.
4. Enter one or more domain names. The first domain will be used as the Common Name property of the certificate.
5. Select the DNS provider that manages the zone enclosing the given domain names.
5. Fill in the required credentials for the provider. AWS Route 53 requires IAM permissions as specified [here](https://github.com/janeczku/rancher-letsencrypt#aws-route-53).
If you want your certificate to be automatically renewed leave the service running. Otherwise you may remove the service once the certificate has appeared in Rancher's certificate store.
### Suggestions & issue reports
Please submit suggestions or any issues you find to the [rancher-letsencrypt](https://github.com/janeczku/rancher-letsencrypt) GitHub repo.