is it possible 502 raise sometimes, during node evict/drain.

[johnzheng1975]

Which component are you using?:
autoscaler

What version of the component are you using?:
cluster-autoscaler:v1.29.0

Component version:

What k8s version are you using (kubectl version)?:

kubectl version Output

$ kubectl version

What environment is this in?:

aws alb, eks

What did you expect to happen?:
no 502

What happened instead?:
502 raise sometimes.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

is it possible 502 raise sometimes, during node evict/drain.
After you drain node successfully, this ec2 is not k8 node anymore, however, then api will still be forwarded from aws alb until the node is terminated. 502 may raise since the api cannot be forwarded to k8s service.
Is this possible during this time period?
Thanks.

[Shubham82]

/area provider/aws
/area cluster-autoscaler

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten