Configure Default CPU Requests and Limits for a Namespace

    You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

    To check the version, enter .

    Create a namespace

    Create a namespace so that the resources you create in this exercise are isolated from the rest of your cluster.

    Here’s the configuration file for a LimitRange object. The configuration specifies a default CPU request and a default CPU limit.

    admin/resource/cpu-defaults.yaml 

    1. apiVersion: v1
    2. kind: LimitRange
    3. metadata:
    4.   name: cpu-limit-range
    5. spec:
    6.   limits:
    7.   - default:
    8.       cpu: 1
    9.     defaultRequest:
    10.       cpu: 0.5
    11.     type: Container

    Create the LimitRange in the default-cpu-example namespace:

    1. kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults.yaml --namespace=default-cpu-example

    Now if a Container is created in the default-cpu-example namespace, and the Container does not specify its own values for CPU request and CPU limit, the Container is given a default CPU request of 0.5 and a default CPU limit of 1.

    Here’s the configuration file for a Pod that has one Container. The Container does not specify a CPU request and limit.

    Configure Default CPU Requests and Limits for a Namespace - 图2

    1. apiVersion: v1
    2. kind: Pod
    3. metadata:
    4. spec:
    5.   containers:
    6.   - name: default-cpu-demo-ctr

    Create the Pod.

    1. kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults-pod.yaml --namespace=default-cpu-example

    The output shows that the Pod’s Container has a CPU request of 500 millicpus and a CPU limit of 1 cpu. These are the default values specified by the LimitRange.

    1. containers:
    2. - image: nginx
    3.   imagePullPolicy: Always
    4.   name: default-cpu-demo-ctr
    5.   resources:
    6.     limits:
    7.       cpu: "1"
    8.     requests:
    9.       cpu: 500m

    What if you specify a Container’s limit, but not its request?

    Here’s the configuration file for a Pod that has one Container. The Container specifies a CPU limit, but not a request:

    1. apiVersion: v1
    2. kind: Pod
    3. metadata:
    4.   name: default-cpu-demo-2
    5. spec:
    6.   containers:
    7.   - name: default-cpu-demo-2-ctr
    8.     image: nginx
    9.     resources:
    11.         cpu: "1"

    Create the Pod:

    1. kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults-pod-2.yaml --namespace=default-cpu-example

    View the Pod specification:

    1. kubectl get pod default-cpu-demo-2 --output=yaml --namespace=default-cpu-example

    The output shows that the Container’s CPU request is set to match its CPU limit. Notice that the Container was not assigned the default CPU request value of 0.5 cpu.

    Here’s the configuration file for a Pod that has one Container. The Container specifies a CPU request, but not a limit:

    admin/resource/cpu-defaults-pod-3.yaml Configure Default CPU Requests and Limits for a Namespace - 图4

    1. kind: Pod
    2. metadata:
    3.   name: default-cpu-demo-3
    4. spec:
    5.   containers:
    6.   - name: default-cpu-demo-3-ctr
    7.     image: nginx
    8.     resources:
    9.       requests:
    10.         cpu: "0.75"

    Create the Pod:

    1. kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults-pod-3.yaml --namespace=default-cpu-example

    View the Pod specification:

    1. kubectl get pod default-cpu-demo-3 --output=yaml --namespace=default-cpu-example
    1. resources:
    2.   limits:
    3.     cpu: "1"
    5.     cpu: 750m

    Motivation for default CPU limits and requests

    If your namespace has a resource quota, it is helpful to have a default value in place for CPU limit. Here are two of the restrictions that a resource quota imposes on a namespace:

    • Every Container that runs in the namespace must have its own CPU limit.
    • The total amount of CPU used by all Containers in the namespace must not exceed a specified limit.

    If a Container does not specify its own CPU limit, it is given the default limit, and then it can be allowed to run in a namespace that is restricted by a quota.

    Delete your namespace:

    What’s next

    For app developers