pod eviction prioritization for datapower

Hi,
We are implementing pod eviction prioritization in our OpenShift environment to protect critical workloads during node resource pressure. We created a PriorityClass named high-priority with a value of 100000. We are able to configure this PriorityClass for other workloads by specifying priorityClassName in their pod templates.

However, when we attempt to add priorityClassName: high-priority to the DataPowerService custom resource YAML, the configuration is rejected with a validation error. The DataPowerService CR specification does not appear to expose a supported field for configuring the pod PriorityClass.

Steps we performed:
1.Created the Kubernetes PriorityClass high-priority with value 100000.
2.Attempted to configure priorityClassName: high-priority in the DataPowerService CR YAML.
3.The configuration was rejected during validation.
4. We Manually patched the generated StatefulSet pod template using the following command:
oc patch sts dpgateway-dev -n cp4i-dev --type=merge --patch='{"spec":{"template":{"spec":{"priorityClassName":"high-priority"}}}}'
It worked, but it is reverting back after every change or pod restart.

Assistance requested:

1.Please confirm whether configuring priorityClassName for DataPower Gateway pods is supported by DataPower Operator.

2.If supported, please provide the correct CR field and YAML syntax.

3.If the field is not exposed in the CR, please advise on the supported configuration or workaround.

Our objective is to configure pod priority through a supported and persistent mechanism, rather than relying on manual patches to operator-managed resources.