Propagate taint errors for Queue Processor events - #1285
Open
enumura1 wants to merge 2 commits into
Open
Conversation
enumura1
marked this pull request as ready for review
August 15, 2026 08:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
Fixes #1284
Description of changes:
Return errors from Queue Processor pre-drain tasks when adding a taint fails.
Previously, taint errors were logged but treated as successful, allowing
node draining and SQS message deletion to continue.
Add tests for taint failures in ASG lifecycle, Rebalance Recommendation,
and Scheduled change events.
How you tested your changes:
pkg/monitor/sqseventandpkg/interruptionevent/draincordonvisibility timeout
Environment (Linux / Windows): Amazon Linux 2023 / Linux amd64
Kubernetes Version: EKS 1.34