Question

LoadBalancers, Kubernetes and LetsEncrypt Wildcards

Hey all,

Does anyone know of a timeline for DO to implement issuing wildcard SSL certificates on LoadBalancers e.g. *.example.com

Running a Kubernetes cluster with Nginx ingress on DO would be perfect if we could issue a wildcard certificate on the load balancers so routes like my-app-staging.example.com and my-app.example.com have valid SSL certificates.

Thanks,

Aaron


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I’d like to also request this. Using ingress-nginx or Traefik certainly works with Let’s Encrypt on DO k8s, but terminating TLS within the cluster adds a solid ~50ms of latency. Terminating TLS at the load balancer results in a 50ms performance improvement.

Why isn’t this implemented yet ?!

I wonder why there’s no more support for this. Naturally, this can be achieved by doing TLS on the cluster, but that means it’s just yet something else to worry about and manage.