You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we use a load balancer to forward traffic to our Nginx Ingress Controller, which has a LetsEncrypt certificate for handling SSL. The LetsEncrypt certificate is managed by Kubernetes. Instead, we could have Nginx run without SSL at all, and install a LetsEncrypt cert on the load balancer directly. We could then change the LB from a TCP route to an HTTP2 (HTTPS) route. This would save SSL processing on the Ingress Controller.
The text was updated successfully, but these errors were encountered:
Right now we use a load balancer to forward traffic to our Nginx Ingress Controller, which has a LetsEncrypt certificate for handling SSL. The LetsEncrypt certificate is managed by Kubernetes. Instead, we could have Nginx run without SSL at all, and install a LetsEncrypt cert on the load balancer directly. We could then change the LB from a TCP route to an HTTP2 (HTTPS) route. This would save SSL processing on the Ingress Controller.
The text was updated successfully, but these errors were encountered: