Integrate the use of Let's encrypt
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
Let's encrypt [1] provides a great way to get SSL certificates which are accepted by browsers.
When it comes to OpenShift there are two downsides using Let's encrypt. Certificates are only valid for 90 days and they don't offer wildcard certificates. So you either need one for each domain or your can use server aliases to include more.
However there is an API for automating this process [2], which could be included into OpenShift in order to automate this process out of the box.
Of course you can find some way to fiddle around with some shell scripts and the router templates to DIY, but it would be cool to have this support out of the box for front-facing HTTPS access.
[1] https://letsencrypt.org/
[2] https://ietf-wg-acme.github.io/acme/
Version
oc v1.4.1+3f9807a
kubernetes v1.4.0+776c994
features: Basic-Auth GSSAPI Kerberos SPNEGO
Steps To Reproduce
- Use OpenShift
- Create router
Current Result
Not supported
Expected Result
Out of the box support for Let's encrypt.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the router templates mentioned in the issue and the linked Let's Encrypt and ACME documentation. Determine the integration scope for automated certificate provisioning and define completion as out-of-the-box Let's Encrypt support for front-facing HTTPS access.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100