-
Enhancement
-
Resolution: Obsolete
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
No
-
---
-
---
-
MK - Sprint 227, MK - Sprint 228
The FSO responsible, or another component, could be for scaling up / down the strimzi operator deployments (or even setting the resources) based upon how many managedkafkas, if any, reference the given strimzi version.
This is especially needed for enterprise RHOSAK as the number of managed instances will be minimal.
As we move toward services sharing components, such as strimzi, we'll need any such mechanism to understand the full load of what is demanded - that could span a number of managed kafkas and connectors.
- is depended on by
-
MGDSTRM-11081 Minimal footprint RHOSAK Hybrid
- Backlog
- is related to
-
MGDSTRM-10045 Rationalise CPU utilisation in order to allow for strimzipodset enablement
- Closed
-
MGDSTRM-11132 Determine if VPA can be used for Strimzi operators
- New