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
Currently our CSI Pod cant be scheduled in certain scenarios, because of lacking resources on the cluster. However if the customer uses a deployment mode, which relies on the CSI Driver Pod to be there and handle volumes, it then leads to the situation that every pod gets the CSI Volume added by the webhook, but the CSI Pod can not handle those requests because he is simply not there. In consequence the application pod, which gets the CSI Volume cannot start and will fail.
Therefor I added a new priorityClass, which is set to a high priority by default, in order to make sure our CSI Pods can be scheduled
How can this be tested?
Checklist