Bug Fix - Replacing scan order from PV to PVC while counting on K8s native node annotations #52
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
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.
This PR introduce an update for the way that the controller is filtering the needed PVC objects to be deleted.
In the current method, we are looping over the list of PVs while checking the NodeAffinity query to identify PVs that got allocated on the faulty node. This method does not provide the algorithm a definite way on the decision wether the PV is attached to the faulty node or not (due to query variance).
In this PR, the algorithm will be changed to be:
pvc.spec.volumeNamewas indeed configured to use thelocalstorage pluginThis PR closes Bug - #48