-
Notifications
You must be signed in to change notification settings - Fork 64
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
[#837] Documentation and test for setting PriorityClassName #838
Conversation
Looks like the tests don't currently run b/c of this issue kubernetes-sigs/controller-runtime#2720 |
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.
@kevinfrommelt thanks for your PR but you could already customize the priorityClassName and other podSpec fields by using a strategic merge patch, for further details see https://github.com/artemiscloud/activemq-artemis-operator/issues/837#issuecomment-2016538868
After #758 new fields to customize the resource managed by the operator are added only for use cases in which a strategic merge patch doesn't work or would be too much complex.
You could change your PR to add a doc and a test to set the priorityClassName
by using a strategic merge patch if that works for your use case.
@brusdev Thanks for the info. I'll update the PR to just include docs and tests like you suggested. |
c43f09d
to
210788e
Compare
210788e
to
625078b
Compare
@brusdev This is ready for review |
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.
@kevinfrommelt great work!!!
@kevinfrommelt thanks for your contribution and for investigating the CI error, I fixed it in #839 |
^