Hello everyone, I have recently set up Rancher v2....
# general
b
Hello everyone, I have recently set up Rancher v2.13.1 on EKS and I am encountering an issue when adding a downstream cluster. Environment • Rancher v2.13.1 running on EKS • Rancher is exposed through NGINX Ingress Controller • NGINX Ingress is fronted by an AWS NLB Issue description When I add another EKS cluster to Rancher and apply the agent manifest generated by Rancher on the downstream cluster, the Rancher agent initially connects to the Rancher server but disconnects after approximately 10 seconds. • On the Rancher agent logs, the agent appears to connect successfully. • However, on the Rancher server logs, the agent is reported as not connected, with messages indicating that the tunnel is disconnected. • As a result, the downstream cluster never becomes active in Rancher. Additional information I have attached the following logs for reference: • Rancher server logs • Rancher agent logs • NGINX Ingress Controller logs I would appreciate any help reviewing this setup and identifying the root cause of the agent disconnection issue. Thank you very much for your support Besides, below is my current helm value setup for rancher and nginx ingress controller. 1. Rancher helm value:
Copy code
hostname: rancher.int.xxx.org
      auditLog:
        enabled: true
        level: 2
        destination: hostPath
        hostpath: /var/log/rancher/audit/
        maxAge: 7
        maxBackup: 7
        maxSize: 200
      ingress:
        ingressClassName: "nginxi"
        # pathType: Prefix
        extraAnnotations:
          kubernetes.io/ingress.class: nginxi
          cert-manager.io/cluster-issuer: letsencrypt-ops-shared
        tls:
          source: secret
          secretName: tls-rancher-ingress
      replicas: 1
      debug: true
2. Nginx ingress helm value
Copy code
controller:
  replicaCount: 1
  ingressClassResource: 
    name: nginxi

  config:
    use-http2: "false"
    ssl-protocols: "TLSv1.2 TLSv1.3"
    use-proxy-protocol: "false"
    use-forwarded-headers: "true"
    compute-full-forwarded-for: "true"
    forwarded-for-header: "forwarded-for-header"
    # compression js, css, json
    use-gzip: "true"
    gzip-level: "6"
    gzip-types: "application/json application/x-javascript text/css text/javascript"

  service:
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-name: ops-shared-nginxi-ingress
      service.beta.kubernetes.io/aws-load-balancer-scheme: "internal"
      service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "TCP"
      service.beta.kubernetes.io/aws-load-balancer-attributes: load_balancing.cross_zone.enabled=true
      service.beta.kubernetes.io/aws-load-balancer-target-group-attributes: preserve_client_ip.enabled=true
    type: LoadBalancer
i just added other cluster in ap-east-1 similar, same region with Rancher server. But it still fail with same error. Below is the server log. Do you mind to help me take a look>