keycloak/keycloak-operator

Support priorityClassName

maxime1907 opened this issue · 1 comments

maxime1907 commented

Description

Support priorityClassName in the keycloak CR for deployment and reconciliation

Discussion

No response

Motivation

If a Pod cannot be scheduled, the scheduler tries to preempt (evict) lower priority Pods to make scheduling of the pending Pod possible.

So if we add support for it, eviction in kubernetes cluster will work as expected and keycloak will stop behing evicted by higher priority pods.

Details

Add it as an experimental feature spec in the keycloak CR like it was done for serviceAccountName

stianst commented

Thanks (again) for reporting this issue. Keycloak 19 was the last version that included this legacy Operator, and with the release of Keycloak 20 the Operator reached EOL and this repository will be archived, please see our blog post on this topic. If this issue is still valid for the Realm Operator, please re-open it there. Thanks for your understanding. And be sure to check out our new Operator!