-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Delay between target removal in the TargetGroup and POD removal causing 502 error #3430
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Would recommend closing this issue as duplicate of #2366 |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Describe the bug
I'm using HPA, and when the scalingdown is done, randomly the clients that consume the ALB receive a 502 error.
After much testing, I discovered that there is a delay between removing the POD (removing the internal IP) and removing the destination, within the TargetGroup, causing the ALB to still send traffic to a pod/port/ip that does not exist more. Even using a delay when closing the POD, this does not solve the problem.
I found some documentation and reports searching on the internet, but it actually seems to solve the problem.
Is there anything that helps me solve this problem?
Environment
The text was updated successfully, but these errors were encountered: