Allow specification of priorityClassName for speaker and controller #1099
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.
When installing using the plain manifests you can add a
priorityClassName
to the speaker and controller pods via a kustomization, but there's currently no way to do the same when installing via helm. This PR adds the necessary snippets to the helm templates to inject these settings via e.g.--set speaker.priorityClassName=system-node-critical
, and the equivalent forcontroller
.Fixed #995