railiance-cluster/install/knative/overlays/serving-core/cpu-requests.patch.yaml
codex 3b18b84997
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Render rail-knative's HPA caps and 10m CPU requests in the Knative installer (RCLUSTER-WP-0020).
Follow rail-knative 76cb9c7 (RAIL-KNATIVE-WP-0003): overlays set 10m CPU
requests for the six substrate containers and add hpa-caps.patch.yaml
(maxReplicas activator 3, webhook 2, 3scale-kourier-gateway 3); verify.sh
checks both; tests/test_knative_render.py checks overlays, verify.sh, the
rail-knative declaration and the render. Not applied. Adds the receiving
task for wave-2 railiance-cluster allocation (CUST-WP-0071, RESOURCE-WP-0008).

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:43:27 +02:00

67 lines
1.5 KiB
YAML

# CPU requests declared by rail-knative (substrate/v1.22.0/cpu-requests.patch.yaml),
# the documents of that file that target serving-core.yaml. Only CPU requests are set;
# memory requests and all limits stay upstream. First set live on railiance01
# 2026-09-21 (ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED by
# the founder); trimmed to 10m each by RAIL-KNATIVE-WP-0003 (2026-10-21).
# Keep in step with rail-knative: tests/test_knative_render.py
# fails if the two declarations disagree.
---
# 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