Closed mart3051 closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
I had similar issue.
In my case target group was all unhealthy, but health check traffic logs in pod were OK with 200.
Then the problem must have been about network acl.
After doing some research, I realized that I didn't add cluster security group to loadbalancer.
I added cluster security group to alb.ingress.kubernetes.io/security-groups
,
target group became healthy, and all worked!
I had same issue and by doing what @yoonkwon commented above solved my issue.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
@yoonkwon What security groups did you tag, and did you add this annotation to the ingress.yaml file? I've added them to mine deleted the pods and it still isn;t passing health checks
We have two VPCs in our system. There is a VPC peering in between them. We are also having two ingress controllers . Everything is ok with first ingress controller which is referencing subnets of same VPC where the EKS is placed.
For the 2nd ingress controller we are pointing to the 2nd VPC .
New Ingress is pointing to public subnets of 2nd VPC and ingress-class of second ingress controller.
Below is the the ingress controller yaml
ingress.yml
In logs we see the successful reconciliation message
The ALBs are also created but when we try to reach the application we receive 504 error.
We have tried increasing timeout but that has not helped either.
On some occasions deletion of ingress controller and ingress had helped but it seems to have no impact now.