Policies > LimitRange Example not Correct..!! about website HOT 7 CLOSED

Hi @faizan35,
The example described in the documentation is correct.
The max value defined in the LimitRange is the maximum permissible value. However in case the Pod's container does not define a resource limit, the default CPU limit of 500m that is defined in the LimitRange will be applied (not the max value).

As the requested CPU of 700m is greater than the default limit of 500m, Kubernetes throws an error.

If you explicitly define CPU limit as 700m, the Pod will be created.

apiVersion: v1
kind: Pod
metadata:
  name: example-conflict-with-limitrange-cpu
spec:
  containers:
    - name: demo
      image: registry.k8s.io/pause:2.0
      resources:
        limits:
          cpu: 700m
        requests:
          cpu: 700m

Note that if you explicitly define a CPU limit > 1, then Kubernetes will throw an error as the LimitRange defines the maximum permissible value as 1.

Hope this helps in clearing the doubt.

from website.

@adityasamant25 thank you for clearing my doubt.

from website.

@faizan35 If your doubt is resolved, please mark the issue as closed.

from website.

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from website.

Page related to issue: https://kubernetes.io/docs/concepts/policy/limit-range/
/language en

from website.

/kind support

from website.

@faizan35 Happy to help!
If your doubt is resolved, please mark the issue as closed.

from website.