Remove all CPU limits cluster-wide to eliminate CFS throttling

CPU limits cause CFS throttling even when nodes have idle capacity.
Move to a request-only CPU model: keep CPU requests for scheduling
fairness but remove all CPU limits. Memory limits stay (incompressible).

Changes across 108 files:
- Kyverno LimitRange policy: remove cpu from default/max in all 6 tiers
- Kyverno ResourceQuota policy: remove limits.cpu from all 5 tiers
- Custom ResourceQuotas: remove limits.cpu from 8 namespace quotas
- Custom LimitRanges: remove cpu from default/max (nextcloud, onlyoffice)
- RBAC module: remove cpu_limits variable and quota reference
- Freedify factory: remove cpu_limit variable and limits reference
- 86 deployment files: remove cpu from all limits blocks
- 6 Helm values files: remove cpu under limits sections
This commit is contained in:
Viktor Barzin 2026-03-14 08:51:45 +00:00
parent 120f83ce93
commit b00f810d3d
108 changed files with 609 additions and 435 deletions

View file

@ -104,7 +104,6 @@ collabora:
resources:
limits:
cpu: "2"
memory: 1Gi
requests:
cpu: 50m

View file

@ -42,7 +42,6 @@ resource "kubernetes_resource_quota" "nextcloud" {
hard = {
"requests.cpu" = "4"
"requests.memory" = "8Gi"
"limits.cpu" = "32"
"limits.memory" = "16Gi"
pods = "10"
}
@ -58,7 +57,6 @@ resource "kubernetes_limit_range" "nextcloud" {
limit {
type = "Container"
default = {
cpu = "250m"
memory = "256Mi"
}
default_request = {
@ -66,7 +64,6 @@ resource "kubernetes_limit_range" "nextcloud" {
memory = "64Mi"
}
max = {
cpu = "16"
memory = "8Gi"
}
}