-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate the use of Let's encrypt #13411
Comments
@tnozicka FYI (I think you was building something related) |
@ctron Take a look at https://github.com/tnozicka/openshift-acme |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
@enj Any updates on this matter? 😇 |
/assign @tnozicka Now has its trello card https://trello.com/c/nmh6J8ly/1140-adopt-openshift-acme |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
@marziman thx.
I'd like us to be able to provide certificates for masters and for the router. Also for the purposes of multitenancy we need to have internal rate limits. |
about openshift-acme, it is working great for routes, not sure how to configure it for console as well, any ideas? |
https://github.com/tnozicka/openshift-acme works great! It would just be cool to have this work with the click of a "Get Certificate!" button built into OpenShift, just to save a long night of reading up and searching to understand what to look for and ultimately find this... 😃 |
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
Current Result
Not supported
Expected Result
Out of the box support for Let's encrypt.
The text was updated successfully, but these errors were encountered: