Support of priorityClassName (without overriding entire statefulSet.spec.template.spec.containers field) #1388
Closed
jimmyjamesbaldwin
started this conversation in
General
Replies: 1 comment 2 replies
-
Hi @jimmyjamesbaldwin, there's no need to provide the entire
You can see the production example as a reference: |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
We are deploying a rabbitmq cluster using the cluster-operator and want to ensure it has high priority for scheduling within the cluster using a PriorityClass. As per #892, it's possible to override the
spec.override.statefulSet.spec.template.spec.priorityClassName
field, but Kubernetes does not allow for patching of this value without overriding the entirespec.override.statefulSet.spec.template.spec.containers
which is managed by the operator and contains a lot of configuration which I'm hesitant to replicate.Is there a way to configure the StatefulSet pods to have a PriorityClass set without overriding the entire
.spec.containers
field?I'm using the following CRD:
but as can be seen when running Terraform to apply the changes, Kubernetes can't patch this field without providing the whole
.spec.containers
:Thanks!
Beta Was this translation helpful? Give feedback.
All reactions