-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
Minimal footprint RHOSAK Hybrid
-
False
-
None
-
False
-
No
-
To Do
-
MGDSRVS-145 - RHOSAK Enterprise Plan: RHOSAK on customer-owned OSD/ROSA/ARO
-
50% To Do, 25% In Progress, 25% Done
-
---
-
---
-
-
Currently, the resource requirements for the RHOSAK components is high when it is installed in the hybrid cloud. Plus, in the future, there is a need to install minimal components that satisfy RHOC installation on a separate cluster but do not consume any RHOSAK components where the customer knows there are not going to be any Kafka instances.
Need to investigate
- How to reduce the number of operator replicas, which will be worked under MGDSTRM-11134, but won't use HPA
MGDSTRM-11100 - How to reduce the strimzi resources, which is primarily discussed under
MGDSTRM-9976- has three possible outcomes:- Simply reduce the cpu request
- Use VPA MGDSTRM-11132
- Use FSO based logic to manipulate the resources, in the same way as MGDSTRM-11134
- Possibility to not instantiate any ingress controllers until the very first Kafka instance is deployed: MGDSTRM-11101
- Or Remove ingress controller to favor load balancers as cost semantics may have changed
- The last time this was looked into the conclusion was to eventually use the gateway api: https://docs.google.com/document/d/1gnsgfZVD_31ZG1eCYXpf0nSwYhBqVGQDebqjTQHetQs/edit# That recommendation will likely still stand as long as we need to account for developer / trial with a single mechanism.
- depends on
-
MGDSTRM-9976 Rationalize strimzi resources
- Closed
- is related to
-
MGDSTRM-11072 Investigate and document the resource requirements for RHOSAK/RHOC services
- New
-
MGDSTRM-10055 Use LoadBalancer Services for RHOSAK enterprise brokers
- Closed
-
MGDSTRM-11055 Understand the minimum requirements for the default machine pool
- Closed