LimitRange sets resource usage limits for each kind of resource in a Namespace.

APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

LimitRangeSpec defines a min/max usage limit for resources that match on kind.

LimitRangeItem defines a min/max usage limit for any resource that matches on kind.

Limits is the list of LimitRangeItem objects that are enforced.

Spec defines the limits enforced. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

It's a good practice to set CPU and Memory requests for each pod. You can use a LimitRange to enforce a minimum CPU and Memory request on all pods in a namespace that do not specify a CPU request.

A basic LimitRange to enforce use of CPU and Memory requests

1. A basic LimitRange to enforce use of CPU and Memory requests

You may want to have constraints around CPU and Memory limits of your pods, in this example the LimitRange has a default, max and min values for CPU and Memory. These values apply to limits only, not requests

v1 · Namespaced Resource

LimitRange

Looking for some examples?

Other useful resources

Tired of using Kubectl? 😓