Skip to main content
Version: v0.24 Stable

Limit Range

You can create a LimitRange policy to constrain virtual cluster resource allocation. vCluster creates the LimitRange on the host in the same namespace as vCluster itself. LimitRange only applies to synced resources, such as pods.

Example​

If you would normally deploy the following LimitRange:

apiVersion: v1
kind: LimitRange
metadata:
  name: vcluster-limit-range
spec:
  limits:
  - default:
      memory: 512Mi
      cpu: "1"
    defaultRequest:
      memory: 128Mi
      cpu: 100m
    type: Container

Instead configure the LimitRange in your vcluster.yaml config file like this:

policies:
  limitRange:
    enabled: true
    default:
    memory: 512Mi
    cpu: "1"
  defaultRequest:
    memory: 128Mi
    cpu: 100m

Config reference​

limitRange required object pro​

LimitRange specifies limit range options.

enabled required string|boolean auto pro​

Enabled defines if the limit range should be deployed by vCluster. "auto" means that if resourceQuota is enabled, the limitRange will be enabled as well.

default required object map[cpu:1 ephemeral-storage:8Gi memory:512Mi] pro​

Default are the default limits for the limit range

defaultRequest required object map[cpu:100m ephemeral-storage:3Gi memory:128Mi] pro​

DefaultRequest are the default request options for the limit range

max required object {} pro​

Max are the max limits for the limit range

min required object {} pro​

Min are the min limits for the limit range

annotations required object {} pro​

Annotations are extra annotations for this resource.

labels required object {} pro​

Labels are extra labels for this resource.