Removes registrar liveness-probe #1549
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
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.
Description
The liveness probe of the
registrarcontainer of the csi driver is unnecessary.This liveness probe was only needed for windows nodes on an certain kubernetes versions.
Furthermore there is an issue, that it can cause high CPU usage.
Also according to: kubernetes-csi/node-driver-registrar#244 the livenessprobe was only needed for windows nodes, which we are not supporting anyway.
How can this be tested?
Deploy the csi driver, check if it works as expected
Checklist