-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Provide ability to adjust compute resource limit/requests for the DataScienceCluster ModelRegistry Operator
2. What is the nature and description of the request?
Users want a way to adjust compute resource limit/requests of the DataScienceCluster ModelRegistry Operator pod in RHOAI based on the expected load. Ideally this configuration would be accessible in such a way that it could be defined via automation through CI/CD by specifying memory/cpu parameters.
User would like a way to override default memory value, to adjust it based on the load. It would be good to align with the same approach as used for other components under RHOAI Operator
3. Why does the customer need this? (List the business requirements here)
This operator does not provide users a way to inject customized numbers for resource limits/requests. Users do not have access to codebase to adjust code users can defind resource limits/requests. Since the operator does not currently provide a configuration mechanism for resource limits, users must use a post-deployment patch to adjust memory allocation (https://access.redhat.com/solutions/7116942).
4. List any affected packages or components.
DataScienceCluster ModelRegistry Operator
model-registry-operator-controller-manager