-
Notifications
You must be signed in to change notification settings - Fork 1
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
Automate ssl certificate generation using certbot on HAProxy for wildcard certs #5
Comments
Alternativelly we could use Caddy web server with a shared storage, for example using Redis. |
The Kubernetes ingress for DEV environment was configured to use cert manager. We still need to issue an wildcard certificate on HAProxy when any service is down. |
We just need to do this on HAProxy for wildcard certificates, when the backends are down. |
Automate ssl certificate generation using ACME/certbot on HAProxy for wildcard certs. #5
Implemented. To clean old certificate files, we need to run manually the follow script: cd /nau/ops/nau-balancer
find /nau/ops/nau-balancer/certs/ -type f -mtime +15 -exec rm {} \; |
In future we need to execute the acme playbook regularly. |
Configured Jenkins jobs. |
Done! |
Jobs running on Jenkins! |
Previous work:
We already have a PROC for SSL certificate generation using Let's Encrypt.
Motivation:
Currently we are using on nau.edu.pt certificates issued by Sectigo, from the RCTSaai community.
But it was decided from the major players, like Google that manages Chrome and the major Certificate entities, to reduce the max time of certificates ssl validation to 90 days.
We need to automate the SSl certificate generation using CertBot, because the Sectigo Certificate authority supports ACME protocol.
We already have been done a POC prof of concept to use the lets encrypt certificates.
This was implemented directly on HAProxy.
On the move to Kubernetes we should the cert-manager, but instead of using the Lets Encrypt servers, we should use the Sectigo servers.
https://share.fccn.pt/sites/rctscertificados/ACME/acme_internal_fccn/#page-toc-10
https://forms.office.com/pages/responsepage.aspx?id=0aBHeQvToEyYmDfUhhxlnO_mc0SdF0JIt4x7BHMOCmJUNFFWMVFHTVpFMFlWR0RaWTVSVkdGM0RNTS4u
https://share.fccn.pt/sites/rctscertificados/ManualUtilizador/#page-toc-3
During the internal FCCN event "Cartas na Mesa" the Emanuel Massano told me that Felipe Santana from ASR already have done that.
I've talked with Filipe Santana from ASR department, he has told that he is emitting the certificates directy using Traefik and not using cert-manager.
The text was updated successfully, but these errors were encountered: