-
Task
-
Resolution: Done
-
Major
-
AMQ 7.5.0.GA, AMQ 7.4.1.GA, AMQ 7.6.0.GA
-
None
At present, when the AMQ 7 stateful set is created by the broker operator on OpenShift, it does not provide any mechanism to customize the OpenShift resource limits (CPU, memory, etc). There ideally needs to be some entry in the AMQ 7 custom resource description to provide this customization.
- causes
-
ENTMQBR-4137 Broker pod fails to spawn when memory limit is applied in yaml
- Closed
- is blocked by
-
ENTMQBR-3338 Provide a mechanism to change stateful set resource limits via operator in AMQ 7 on OCP
- Closed