feat(helm): Allow Pod priorityClassName to be configured #890
Conversation
This file contains hidden or 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
…late run up to stackabletech/operator-templating@9937fb4 Reference-to: stackabletech/operator-templating@9937fb4 (This allows Pod `priorityClassName` to be configured in operators (excluding listener-operator and secret-operator). It requires a CHANGELOG entry before merging (see example in <stackabletech/operator-templating#551>).)
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Note
Autogenerated PR to update templated files since the last template run up to stackabletech/operator-templating@9937fb4.
priorityClassNameto be configured in operators (excluding listener-operator and secret-operator). It requires a CHANGELOG entry before merging (see example in stackabletech/operator-templating#551).Tip
Please update the change type as appropriate.
For example, if the change is breaking, add an
!after the change type:If you need to add subsequent commits to make the checks pass, change the type:
For more information, See Conventional Commits.