fix: reallowing nodeclaim zones to fix node/nodeclaim creations for workloads with zone affinity constraints #340
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
…orkloads with zone affinity constraints
Pull Request Test Coverage Report for Build 9039702148Details
💛 - Coveralls |
tallaxes
approved these changes
May 11, 2024
tallaxes
added
area/provisioning
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.
Fixes #339
Description
See the issue.
This change should not undo the continuous drift issue that #274 fixes, as adding zones requirements is still prohibited on the nodepool CRD, which is the (intentionally) user-facing interface.
Current drift logic also "ignore" requirements that exist in NodeClaims, but not NodePools.
How was this change tested?
Does this change impact docs?
Release Note