-
Task
-
Resolution: Done
-
Major
-
None
-
5
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
RHOAM Sprint 49, RHOAM Sprint 50, RHOAM Sprint 51
What
Update the APIManger CRD to include fields for adding HPA to
- ApicastProductionSpec
- BackendListenerSpec
- BackendWorkerSpec
Set default values based off the findings in https://issues.redhat.com/browse/THREESCALE-10499
- New APIMAnager CRD field of object type: spec.backend.ListenerSpec.hpa.
spec: backend: listenerSpec: hpa: name: test enabled: bool minPods: W maxPods: X cpuPercent: Y memoryValue: Z
- New APIMAnager CRD field of object type: spec.backend.workerSpec.hpa.
spec: backend: workerSpec: hpa: name: test enabled: bool minPods: W maxPods: X cpuPercent: Y memoryValue: Z
- New APIMAnager CRD field of object type: spec.apicast.productionSpec.hpa.
spec: apicast: productionSpec: hpa: name: test enabled: bool minPods: W maxPods: X cpuPercent: Y memoryValue: Z
And if this value is set in the CR create resource HPA objects for the following list, based on the values passed in in the APIManager
- apicast-production
- backend- listener
- backend-worker
Once these are set unless there is a change to the values in the APIManager CR the HPA objects will be left to the values set in the HPA objects.
https://docs.google.com/document/d/1BQ3VyCB42dtwn8ZHLhqXQ4_gcZML8Fz5CpBWfPwU8L8/edit?usp=sharing
- blocks
-
THREESCALE-10563 Investigate a pattern for adding warning messages to a status block on a custom resource
- Closed
-
THREESCALE-10499 Set default request for apicast and backend components for HPA
- Closed
- clones
-
THREESCALE-10499 Set default request for apicast and backend components for HPA
- Closed
- links to
-
RHEA-2024:129555 Release of 3scale-operator 0.12.1mas for RHOAM - Containers