Description of problem: When I edit resource limits. Any values within the limit ranges seem to be accepted for cpu/memory request and limit. Ideally I would only be able to see and set the memory limit. But the current behavior creates a couple of problems: 1) As a user, I can easily change values that make it difficult to understand where I am going over quota by changing only CPU or memory 2) The cluster won't be fully scheduled because memory and cpu aren't guaranteed to be proportional Version-Release number of selected component (if applicable): Starter tier How reproducible: Steps to Reproduce: 1. Deploy something (Ex: ruby) 2. Edit the resource limits and only change the memory or CPU 3. Actual results: The change is accepted Expected results: ClusterResourceOverride should adjust all the values based on memory limit Ideally only memory limit would be settable. Additional info: https://docs.openshift.org/latest/admin_guide/overcommit.html#configuring-masters-for-overcommitment
Dan, can you explain more detailed what you expect from this feature?