Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Target group deletion causing inflight request 503's #3739

Open
Harif-Rahman opened this issue Jun 11, 2024 · 3 comments
Open

Target group deletion causing inflight request 503's #3739

Harif-Rahman opened this issue Jun 11, 2024 · 3 comments

Comments

@Harif-Rahman
Copy link

Harif-Rahman commented Jun 11, 2024

Describe the bug
In the Ingress configuration, we are redirecting the rules to a new target group or service, and there are no existing rules directing traffic to the old target group or service. However, the target group is being deleted hastily without taking into account the deregistration delay, leading to in-flight requests resulting in 503 errors.
Any idea how to handle this ?

Steps to reproduce
Logs
Deletion of target group logs - 2024-06-11 8:57:06 UTC

{"level":"info","ts":1718096226.6557481,"logger":"controllers.ingress","msg":"deleted targetGroup","arn":"arn:aws:elasticloadbalancing:us-east-1:123:targetgroup/k8s-fcjava-javaapii-79a6c094bb/9cac3a3ffc19a38f"}

below is the 503 access logs from lb.

2024-06-11 8:57:06 arn:aws:elasticloadbalancing:us-east-1:123:targetgroup/k8s-fcjava-javaapii-79a6c094bb/9cac3a3ffc19a38f 22
2024-06-11 8:57:07 arn:aws:elasticloadbalancing:us-east-1:123:targetgroup/k8s-fcjava-javaapii-79a6c094bb/9cac3a3ffc19a38f 112
2024-06-11 8:57:08 arn:aws:elasticloadbalancing:us-east-1:123:targetgroup/k8s-fcjava-javaapii-79a6c094bb/9cac3a3ffc19a38f 125
2024-06-11 8:57:09 arn:aws:elasticloadbalancing:us-east-1:123:targetgroup/k8s-fcjava-javaapii-79a6c094bb/9cac3a3ffc19a38f 85
2024-06-11 8:57:10 arn:aws:elasticloadbalancing:us-east-1:123:targetgroup/k8s-fcjava-javaapii-79a6c094bb/9cac3a3ffc19a38f 115

Expected outcome
A concise description of what you expected to happen.

Environment

  • AWS Load Balancer controller version - v2.4.5
  • Kubernetes version - v1.24
  • Using EKS (yes/no),yes - v1.24

Additional Context:

@oliviassss
Copy link
Collaborator

@Harif-Rahman, can you check if adding a sleep as preStop would mitigate your issue, see more details in:
#2366

@aravindsagar
Copy link

Hi, this seems like a bug with target group deletion. We're trying to reproduce the issue and will work on a fix after that.

@Harif-Rahman
Copy link
Author

@oliviassss how does adding prestop will help here because alb controller pods deletes the target group immediately after deregisration of the instances.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants