# 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. # Live on railiance01 since 2026-09-21 (ADMINISTER @ realm:kubernetes/railiance01, # activation=APPROVED by the founder). 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 -n --type strategic --patch-file # 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: 50m --- # 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: 30m --- # 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: 30m --- # 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: 30m --- # 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: 30m --- # 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: 50m