Verify node is present and reported for all AZs. #2776
Merged
Conversation
This file contains 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
jdn5126
approved these changes
Feb 1, 2024
jdn5126
force-pushed
the
assert_node_presence
branch
from
47e5897 to
8a04248
Compare
|
/lgtm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
During an LSE; a node in the AZ was not returned by API Server. The tests scheduled the pods in rest of the nodes, and continued with exercise.
It is desirable to ensure that nodes are across AZs; and fail if the node in any AZ is not getting reported or taking workload.
This test ensures coverage that node is present across the supported AZ.
Using a test instead of #2768