You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
@oliviassss how does adding prestop will help here because alb controller pods deletes the target group immediately after deregisration of the instances.
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.
Expected outcome
A concise description of what you expected to happen.
Environment
Additional Context:
The text was updated successfully, but these errors were encountered: