Add support for custom priorityClassName #117
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
yahel2410
force-pushed
the
feat/add-priorityclassname
branch
from
0aef721
to
5e7206c
Compare
alexrashed
approved these changes
Mar 26, 2024
There was a problem hiding this comment.
Hey @yahel2410! Thanks a lot for the contribution! I tested it locally and it works like a charm! I'll go ahead and directly merge the PR and create a release. 🚀 💯
|
@alexrashed awesome 😃 |
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.
Motivation
Added support for custom priorityClassName. For cases when Localstack needs to be prioritized / de-prioritized over other pods
Changes
Added support for custom priorityClassName
Testing
Added a test value for common built-in priorityClassName