In docs, I fount this example configuration https://github.com/digitalocean/digitalocean-cloud-controller-manager/blob/master/docs/controllers/services/examples/http-nginx-with-redirect.yml for nginx load balancer on DO k8s.

Does this configuration provides SSL termination on load balancer by default?
If this part of config

    - name: https
      protocol: TCP
      port: 443
      targetPort: 80

proxies 443 client connections to 80 backend service, will it terminate ssl on the load balancer by default, without any additional configuration/work?

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.

Submit an Answer
2 answers

Hi there,

Yes, with that in place there would be no need to make any changes to the application itself.

One thing to keep in mind is that you need the following configuration so that you could specify the certificate that should be used:

    service.beta.kubernetes.io/do-loadbalancer-certificate-id: "your_certificate_id_here"


by Savic
Kubernetes Ingresses offer you a flexible way of routing traffic from beyond your cluster to internal Kubernetes Services. Helm https://helm.sh/ is a package manager for managing Kubernetes. In this guide, you'll set up the Kubernetes-maintained Nginx Ingress Controller using Helm. You'll then create an Ingress Resource to route traffic from your domains to example Hello World back-end services.