-
Notifications
You must be signed in to change notification settings - Fork 884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for priorityClassName #165
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bump |
Hey, thanks for the bump. Missed the notification for your previous comment. Rebased and added unit tests. |
Resolved new merge conflict, also bump @jasonodonnell. |
@bycEEE can you fix the new merge conflict and ping approvers again? Would love to see this get added and its so close! |
@InAnimaTe fixed! |
Awesome, you da man! @jasonodonnell I think this is ready to go in!! |
This reverts commit 2af6f9b.
I didn't notice that a colleague merged a similar feature implementing priorityClassName's on the pods, so this caused a collision. I reverted this merge, however, this feature has been implemented and merged. You can find this in the next vault-helm release. Thanks! |
* Add support for priorityClassName * Add unit tests * Remove comment * Update comment, accidentally deleted comment * Remove whitespace
No description provided.