Cancel context kueue - No mutex/locks #8
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
…to streamline REST mapping checks
ChristianZaccaria
force-pushed
the
cancel-context-kueue
branch
from
264ebd0
to
564fb0f
Compare
ChristianZaccaria
force-pushed
the
cancel-context-kueue
branch
from
564fb0f
to
1d9c7b7
Compare
ChristianZaccaria
changed the title
ChristianZaccaria
force-pushed
the
main
branch
2 times, most recently
from
7e3ed90
to
a768127
Compare
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.
Tests are passing.
The use of mutexes/locks is not required here.
The context is cancelled once a newly available Framework is found, causing the Kueue pod to restart.
This is a more robust solution as all processes start from a fresh state, which would start the controllers and webhooks of the newly added CRDs.