Hello, does anyone use AWS NLB or ALB to loadbalan...
# general
r
Hello, does anyone use AWS NLB or ALB to loadbalance the Rancher instance? I'm having an issue with the latest version of Rancher + ingress-nginx - did anything change perhaps? This is the config I'm using for the ingress:
Copy code
controller:
  kind: "DaemonSet"
  ingressClassResource:
    name: nginx
    enabled: true
    default: true
  service:
    targetPorts:
      http: http
      https: http
    annotations:
      <http://service.beta.kubernetes.io/aws-load-balancer-backend-protocol|service.beta.kubernetes.io/aws-load-balancer-backend-protocol>: tcp
      <http://service.beta.kubernetes.io/aws-load-balancer-proxy-protocol|service.beta.kubernetes.io/aws-load-balancer-proxy-protocol>: "*"
      <http://service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout|service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout>: '7200'
      <http://service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled|service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled>: 'true'
      <http://service.beta.kubernetes.io/aws-load-balancer-ssl-cert|service.beta.kubernetes.io/aws-load-balancer-ssl-cert>: arn:aws:acm:eu-west-2:XXXX
      <http://service.beta.kubernetes.io/aws-load-balancer-ssl-ports|service.beta.kubernetes.io/aws-load-balancer-ssl-ports>: https
      <http://service.beta.kubernetes.io/aws-load-balancer-type|service.beta.kubernetes.io/aws-load-balancer-type>: "external"
      <http://service.beta.kubernetes.io/aws-load-balancer-subnets|service.beta.kubernetes.io/aws-load-balancer-subnets>: "subnet-XX,subnet-XX,subnet-XX"
      <http://service.beta.kubernetes.io/aws-load-balancer-eip-allocations|service.beta.kubernetes.io/aws-load-balancer-eip-allocations>: "eipallocXX,eipalloc-XX,eipalloc-XX"
      <http://service.beta.kubernetes.io/aws-load-balancer-scheme|service.beta.kubernetes.io/aws-load-balancer-scheme>: "internet-facing"
      <http://service.beta.kubernetes.io/aws-load-balancer-nlb-target-type|service.beta.kubernetes.io/aws-load-balancer-nlb-target-type>: instance
      <http://service.beta.kubernetes.io/aws-load-balancer-healthcheck-protocol|service.beta.kubernetes.io/aws-load-balancer-healthcheck-protocol>: TCP
      <http://service.beta.kubernetes.io/aws-load-balancer-name|service.beta.kubernetes.io/aws-load-balancer-name>: "lXXs-rancher-nginx-lb"
      <http://service.beta.kubernetes.io/aws-load-balancer-security-groups|service.beta.kubernetes.io/aws-load-balancer-security-groups>: "sg-XXX"
  extraArgs:
    ingress-class: ingress-nginx   
  metrics:
    enabled: true
    service:
      annotations:
        <http://prometheus.io/port|prometheus.io/port>: "10254"
        <http://prometheus.io/scrape|prometheus.io/scrape>: "true"
then running:
helm install ingress-nginx ingress-nginx/ingress-nginx --set-string controller.service.externalTrafficPolicy=Local --set-string controller.service.type=LoadBalancer --set controller.publishService.enabled=true --set serviceAccount.create=true --set rbac.create=true --set-string controller.config.server-tokens=false --set-string controller.config.use-proxy-protocol=true --set-string controller.config.compute-full-forwarded-for=true --set-string controller.config.use-forwarded-headers=true --set controller.metrics.enabled=true --set controller.autoscaling.maxReplicas=3 --set controller.autoscaling.minReplicas=2 --set controller.autoscaling.enabled=true --namespace ingress-nginx --create-namespace -f ingress_nginx_values.yaml
The NLB healthcheck is remaining Unhealthy