-
Bug
-
Resolution: Done
-
Undefined
-
None
-
1.7.0
-
None
-
Serverless Sprint 184, Serverless Sprint 185
Having a LimitRange defined in a namespace
apiVersion: "v1" kind: "LimitRange" metadata: name: "core-resource-limits" spec: limits: - type: "Pod" max: cpu: "2" memory: "1Gi" min: cpu: "200m" memory: "6Mi" - type: "Container" max: cpu: "2" memory: "1Gi" min: cpu: "100m" memory: "4Mi" default: cpu: "300m" memory: "200Mi" defaultRequest: cpu: "200m" memory: "100Mi" maxLimitRequestRatio: cpu: "10"
It is possible to create a pod without specifying resource requests there
apiVersion: v1
kind: Pod
metadata:
name: helloworld-go
labels:
app: helloworld-go
spec:
containers:
- image: gcr.io/knative-samples/helloworld-go
name: helloworld-go
env:
- name: TARGET
value: "Go Sample v1"
but the same deployed as a ksvc doesn't work:
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
name: helloworld-go
spec:
template:
spec:
containers:
- image: gcr.io/knative-samples/helloworld-go
env:
- name: TARGET
value: "Go Sample v1"
Will not be deployed with errors:
1s Warning FailedCreate replicaset/helloworld-go-xx9rh-deployment-745cd6876f (combined from similar events): Error creating: pods "helloworld-go-xx9rh-deployment-745cd6876f-kpbmx" is forbidden: [minimum cpu usage per Container is 100m, but request is 25m, cpu max limit to request ratio per Container is 10, but provided ratio is 12.000000]
- causes
-
SRVKS-574 [DOC] Add queue-proxy's default CPU request issue to known issues
- Closed