-
Enhancement
-
Resolution: Done
-
Major
-
None
-
2
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
https://github.com/3scale/3scale-operator/pull/808, https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1372, https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1379, https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1380
-
-
-
RHOAM Sprint 39, RHOAM Sprint 40, API CCS Sprint 43 (3Scale), API CCS Sprint 44 (3Scale) 2
WHAT
There are use cases where a 3scale Operator consumer would want to set the pod priority for the various components installed by 3scale. This is currently not provided via the APIManager CR, and the deployment configs must be updated manually for this which would cause a subsequent pod rollout.
This can be however managed and defined via the APIManager CR.
HOW
Potentially an optional pod priority field in the various subcomponent fields of the APIManager CRD that the reconciler will add to the pod template of the respective component
DONE
- Pod priority for 3scale components can be defined via the APIManager CR
- blocks
-
MGDAPI-5030 Consume 3scale build and update RHOAM 3scale reconcile logic
- Closed
- links to
- mentioned on