How can I get to work on Kubernetes when using nginx-ingress and cert-manager?

Posted February 25, 2020 13.8k views
NginxLoad BalancingKubernetes

I have a deployment running inside my k8s cluster that uses, but external WebSocket traffic doesn’t seem to be getting to it.

I’m using nginx ingress controller with cert-manager, which works fine for normal HTTPS traffic. With this setup, SSL termination is with nginx and the certificates live in the cluster.

I’ve seen in the docs and elsewhere that I need to switch the load balancer protocol to HTTP instead of TCP to get WebSockets to work. However, doing that breaks SSL for me. This is because the DigitalOcean load balancer has two options:

  1. SSL Termination at the load balancer - this would require managing my domain and SSL certs through DigitalOcean and abandoning cert-manager which I don’t want to do
  2. SSL Passthrough - this passes the encrypted data straight to the droplet, which is also not what I want to do (I think??)

Is there a way to continue to use nginx ingress controller and cert manager with WebSockets?

1 comment
  • I am likewise having serious issues. I can’t find any official documentation on how to deal with this scenario, but it seems like a pretty common situation. I know that “me too!” comments aren’t overly helpful, but I’m hoping that more activity may garner a response from DO.

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
4 answers

Did you ever get a resolution to this, I am stuck with exactly the same issue.

I got this working in the end, terminating the SSL at nginx (passthrough on the load balancer) and allowing it to reverse-proxy the data to the apps with sticky sessions. For anyone else stuck on this, here are my manifests - hope they help:


kind: Service
apiVersion: v1
  name: ingress-nginx
  namespace: ingress-nginx
    # See "" "" "http" "true" "cookies" "jammydodger" "60"
  labels: ingress-nginx ingress-nginx
  externalTrafficPolicy: Local
  type: LoadBalancer
  selector: ingress-nginx ingress-nginx
    - name: http
      port: 80
      protocol: TCP
      targetPort: http
    - name: https
      port: 443
      protocol: TCP
      targetPort: https



# Define Ingress for the service
apiVersion: extensions/v1beta1
kind: Ingress
  name: testing-ingress
  annotations: "nginx" "letsencrypt-prod" /$2 # Lets us rewrite to "3600" "3600" "cookie" "route" "sha1" "172800" "172800"

  - hosts:
    secretName: testing-ingress-tls
  - host:
      - path: /v0(/|$)(.*)
          serviceName: platform-app-service
          servicePort: 80
  - host:
      - path: /
          serviceName: frontend-app-service
          servicePort: 80