Make "no CPU limits set" warning in save dialog configurable or remove it

[carrielevy]

What product would you like to leave feedback for?

Console

What Console version are you using?

v14.5.5

Description

The save configuration dialog currently surfaces a "no CPU limits set" warning for any service without a CPU limit configured. We are requesting that this warning either be made configurable (so platform administrators can disable it) or removed entirely.

We intentionally do not set CPU limits on our microservices, and the "no CPU limits set" warning that fires in the save dialog is creating noise for our engineers on every single save. We'd like to understand if this warning can be turned off, and if not, we'd like to make the case that it should be.

A bit of background on why we don't set CPU limits, this isn't a misconfiguration. Our DevOps engineers made a deliberate decision to omit them based on how Kubernetes actually handles CPU enforcement. The official Kubernetes docs actually call this out directly. Containers are explicitly permitted to exceed their request when node capacity allows. Requests handle scheduling. Limits just throttle.

Our questions:

1. Is there a way to disable or configure this warning today at the project or console level?
2. If not, can that be added? We should be able to opt out of warnings that don't apply to our setup.
3. Longer term, is this something the Mia team would consider revisiting given where the Kubernetes community has landed on this?

Thank you!