-
Notifications
You must be signed in to change notification settings - Fork 37
feat: Add priorityClassName to deployment #192
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
feat: Add priorityClassName to deployment #192
Conversation
Also i've noticed that this would not add a priorityClassName to the DaemonSet pods, i'll be happy to help implement this feature if it's something that could be useful |
Co-authored-by: Anatolii Bazko <abazko@redhat.com>
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.
Sounds good. Thank you for conrtibution.
Please update README.md as wel..
@tolusha I updated the readme |
Build 3.20 :: imagepuller_3.x/150: Console, Changes, Git Data |
Build 3.20 :: sync-to-downstream_3.x/8771: Console, Changes, Git Data |
Build 3.20 :: get-sources-rhpkg-container-build_3.x/8889: imagepuller : 3.x :: Failed in 66700746 : BREW:BUILD/STATUS:UNKNOWN |
Hello everyone !
I've read the Opensource guide on how to make contribution and felt that a Pull Request was the correct way to implement this as an Issue was maybe a bit too much, i hope i did things correctly.
I'm opening a PR to add a feature to the deployment :
This feature adds the following
Let me know if this is the correct way to do so.