Set empty CPU limits when possible #22198
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
kind/enhancement
A feature request - must adhere to the feature request template.
severity/P1
Has a major impact to usage or development of the system.
team/A
This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Milestone
Is your enhancement related to a problem? Please describe
If a container reach a CPU limit it gets throttled (paused for a few ms). A container that get throttled performs poorly and can have side effects that are hard to associate with throttling.
In other words when setting CPU limits the application may behave in a weird way and users can lose hours figuring out why.
LimitRanges are used in Kubernetes clusters to set default request/limit for compute resources in a namespace and automatically inject them to Containers at runtime. If a default CPU limit is set in the Che namespace or in the workspaces namespaces, then we have to specify the CPU limits to avoid that an arbitrary limit gets set. But otherwise we don't have to.
Describe the solution you'd like
If there is no LimitRange or there is one but it doesn't specify the default CPU Limit in one of the following namespaces:
The text was updated successfully, but these errors were encountered: