spot-termination-exporter: Add priority class name spot termination exporter #1091
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.
What's in this PR?
This pull request allows users to set priorityClassName to spot-termination-exporter pods. It also fixes a couple of other minor issues in the helm chart itself.
Why?
There are cases were having spot-termination-exporter pods being able to schedule on every node is critical for the monitoring of the cluster. As such, we should be using priorities in that case to make sure that the DS always take precedence against other lower priority workloads.
Additional context
A couple of other fixes related to helm lint and also to the Chart itself.
Checklist