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