Fix node tainting when using UseProviderId with SQS monitors #1203
+52
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Fixes node tainting failures when
UseProviderIdis enabled and Kubernetes node names differ from AWS PrivateDnsNames (e.g., clusters using instance IDs as node names).PreDrainTask functions in SQS event handlers used
interruptionEvent.NodeName(AWS PrivateDnsName) directly, causing tainting to fail when the Kubernetes node name didn't match. Drain/cordon operations worked because they resolved the correct node name via provider ID lookupExample Failure
How you tested your changes:
Environment Linux:
Kubernetes Version: v1.31.5
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.