Closed ChaitDevOps closed 1 month ago
I had the same problem. I got Rancher working when I deleted path "/" check condition from AWS ALB listener rules and also needed to set "path: /" parameter empty at aws-rancher ingress rules. This problem seems appear from Rancher version 2.7.5 and up.
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.
Hello,
I'm trying to launch Rancher with the AWS LB controller and i'm getting health checks failed for the ingress. Can someone please look at my set up and let me know if something that's obvious?
EKS cluster version: 1.28 EndPointAcces: Public and Private Nodegroup: Private Subnet Security Group ALB-Ingress allows Inbound & Outbound traffic from 0.0.0.0/0 on port 80 and 443. Outbound rule allows traffic to the security group created for the EKS nodegroup. I updated the rancher service to a NodePort. Error message for healthcheck failed "request timed out"