I appear to also be getting this. It appears that the nodes aren’t being rotated via round robin anywhere nearly as often as they should be. Subsequent requests should be split evenly across each Node backend, but it appears they’re not being frequently.

Edit: It appears for the port you have to use the HTTP port type. Using TCP doesn’t make it work, however HTTP reliabably forwards across node backends. I edited that in the Digital Ocean console and suddenly it all started to work.

We have similar problem on the recently created environment - all traffic is redirected to the single pod all the time no meter what load we have. However, service discovers pods successfully and if one of the pods fails traffic got redirected to other pod.

Has anyone solved this problem ?

Here is our setup:

Service (Also tried to create with type: Loadbalancer) :

apiVersion: v1
kind: Service
metadata:
  name: api
spec:
  selector:
    app: api
  ports:
    - port: 80
      targetPort: 8080

Ingress:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-ingress
  namespace: default
  annotations:
    kubernetes.io/tls-acme: "true"
    kubernetes.io/ingress.class: "nginx"
    certmanager.k8s.io/acme-http01-edit-in-place: "true"
    certmanager.k8s.io/cluster-issuer: "letsencrypt"
    certmanager.k8s.io/acme-challenge-type: "http01"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/secure-backends: "true"
    nginx.ingress.kubernetes.io/websocket-services: "<Service name>"
    nginx.org/websocket-services: "notifications-service"
    nginx.ingress.kubernetes.io/upstream-hash-by: "$arg_token"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"
spec:
  tls:
  - hosts:
    - <HOST>
    secretName: letsencrypt-prod-cert
  rules:
  - host: <HOST>
    http:
      paths:
      - path: /
        backend:
          serviceName: api
          servicePort: 80

Kube-proxy configured to use iptables