rail-knative/substrate/v1.22.0/cpu-requests.patch.yaml
tegwick 76cb9c7ad9 RAIL-KNATIVE-WP-0003: cap Knative HPAs for one node, trim substrate CPU requests to 60m
Declare maxReplicas activator 20->3, webhook 5->2, 3scale-kourier-gateway
10->3 and 10m CPU requests for all six substrate containers (220m->60m),
per the resource-control node budget of 2026-10-21 (CUST-WP-0071,
RESOURCE-WP-0008). Read-only BEFORE evidence under
docs/evidence/2026-10-21-hpa-caps-before/. Not applied; railiance-cluster
overlays must follow (handoff in T02).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 8340@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-21 08:40:35 +02:00

103 lines
2.5 KiB
YAML

# Declared CPU requests for the Knative Serving + Kourier v1.22.0 substrate.
# Strategic-merge patches over the upstream release manifests (serving-core.yaml,
# kourier.yaml), checksum-pinned in railiance-cluster/install/knative/release-lock.env.
# Only CPU requests are set; memory requests and all limits stay upstream.
# First set live on railiance01 2026-09-21 (220m total; ADMINISTER @
# realm:kubernetes/railiance01, activation=APPROVED by the founder). Trimmed to
# 10m each (60m total) by RAIL-KNATIVE-WP-0003 per the resource-control node
# budget of 2026-10-21 (7d p95 <= 7.2m per workload). Re-applying upstream
# without these patches restores the upstream values noted per document and
# re-exhausts the node.
# Apply after each upstream apply, e.g. for each document:
# kubectl patch deployment <name> -n <ns> --type strategic --patch-file <doc>
# or list this file under `patches:` in a kustomization over the staged assets.
---
# upstream v1.22.0 request: 300m
apiVersion: apps/v1
kind: Deployment
metadata:
name: activator
namespace: knative-serving
spec:
template:
spec:
containers:
- name: activator
resources:
requests:
cpu: 10m
---
# upstream v1.22.0 request: 100m
apiVersion: apps/v1
kind: Deployment
metadata:
name: autoscaler
namespace: knative-serving
spec:
template:
spec:
containers:
- name: autoscaler
resources:
requests:
cpu: 10m
---
# upstream v1.22.0 request: 100m
apiVersion: apps/v1
kind: Deployment
metadata:
name: controller
namespace: knative-serving
spec:
template:
spec:
containers:
- name: controller
resources:
requests:
cpu: 10m
---
# upstream v1.22.0 request: 100m
apiVersion: apps/v1
kind: Deployment
metadata:
name: webhook
namespace: knative-serving
spec:
template:
spec:
containers:
- name: webhook
resources:
requests:
cpu: 10m
---
# upstream v1.22.0 request: 200m
apiVersion: apps/v1
kind: Deployment
metadata:
name: net-kourier-controller
namespace: knative-serving
spec:
template:
spec:
containers:
- name: controller
resources:
requests:
cpu: 10m
---
# upstream v1.22.0 request: 200m
apiVersion: apps/v1
kind: Deployment
metadata:
name: 3scale-kourier-gateway
namespace: kourier-system
spec:
template:
spec:
containers:
- name: kourier-gateway
resources:
requests:
cpu: 10m