{"id":20699,"date":"2025-01-23T13:15:06","date_gmt":"2025-01-23T13:15:06","guid":{"rendered":"http:\/\/www.devopsschool.com\/blog\/?p=20699"},"modified":"2025-01-23T13:16:13","modified_gmt":"2025-01-23T13:16:13","slug":"kubernetes-resourcequota-limitrange-example-programs","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/kubernetes-resourcequota-limitrange-example-programs\/","title":{"rendered":"Kubernetes ResourceQuota & LimitRange Example Programs"},"content":{"rendered":"\n

Kubernetes ResourceQuota and LimitRange are two important mechanisms for managing resource allocation and usage within a Kubernetes cluster.<\/p>\n\n\n\n

Here’s a comparison of ResourceQuota and LimitRange features and use cases in a tabular format:<\/p>\n\n\n\n

Feature<\/th>ResourceQuota<\/th>LimitRange<\/th><\/tr><\/thead>
Scope<\/td>Namespace-wide<\/td>Individual pods and containers<\/td><\/tr>
Purpose<\/td>Limit aggregate resource consumption<\/td>Set constraints on individual resources<\/td><\/tr>
Resource Types<\/td>CPU, memory, storage, object counts<\/td>CPU, memory<\/td><\/tr>
Default Values<\/td>Does not set defaults<\/td>Can set default requests and limits<\/td><\/tr>
Enforcement Level<\/td>Across all pods in a namespace<\/td>Per pod or container<\/td><\/tr>
Ratio Enforcement<\/td>No<\/td>Can enforce request-to-limit ratio<\/td><\/tr>
Object Creation<\/td>Can limit number of objects by type<\/td>N\/A<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Use Case<\/th>ResourceQuota<\/th>LimitRange<\/th><\/tr><\/thead>
Prevent resource overuse by a team<\/td>\u2713<\/td><\/td><\/tr>
Ensure fair resource distribution<\/td>\u2713<\/td><\/td><\/tr>
Set default resource requests\/limits<\/td><\/td>\u2713<\/td><\/tr>
Prevent creation of pods without limits<\/td><\/td>\u2713<\/td><\/tr>
Limit storage consumption<\/td>\u2713<\/td><\/td><\/tr>
Control number of objects (e.g., services, ConfigMaps)<\/td>\u2713<\/td><\/td><\/tr>
Enforce minimum resource requirements<\/td><\/td>\u2713<\/td><\/tr>
Prevent excessive resource allocation to single pod<\/td><\/td>\u2713<\/td><\/tr>
Maintain consistent request-to-limit ratios<\/td><\/td>\u2713<\/td><\/tr>
Isolate resources between different environments (dev\/prod)<\/td>\u2713<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This comparison highlights the complementary nature of ResourceQuota and LimitRange in managing Kubernetes cluster resources effectively.<\/p>\n\n\n\n

ResourceQuota<\/h2>\n\n\n\n

ResourceQuota is used to limit the aggregate resource consumption per namespace. It can restrict:<\/p>\n\n\n\n

    \n
  • Total compute resources (CPU and memory) that can be requested<\/li>\n\n\n\n
  • Number of objects that can be created by type (e.g., pods, services)<\/li>\n\n\n\n
  • Total storage resources that can be consumed<\/li>\n<\/ul>\n\n\n\n

    Key features:<\/p>\n\n\n\n

      \n
    • Applied at the namespace level<\/li>\n\n\n\n
    • Limits the sum of resources across all pods in a namespace<\/li>\n\n\n\n
    • Enforces constraints on both resource requests and limits<\/li>\n<\/ul>\n\n\n\n

      Example ResourceQuota:<\/p>\n\n\n

      apiVersion<\/span>: v1<\/span>\nkind<\/span>: ResourceQuota<\/span>\nmetadata<\/span>:\n  name<\/span>: compute-resources<\/span>\nspec<\/span>:\n  hard<\/span>:\n    requests<\/span>.cpu<\/span>: \"2\"\n    requests<\/span>.memory<\/span>: 1Gi<\/span>\n    limits<\/span>.cpu<\/span>: \"4\"\n    limits<\/span>.memory<\/span>: 2Gi<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      LimitRange<\/h2>\n\n\n\n
      LimitRange sets constraints on individual pods and containers within a namespace. It can:<\/p>\n\n\n\n
        \n
      • Enforce minimum and maximum compute resources per pod or container<\/li>\n\n\n\n
      • Set default request\/limit values for containers<\/li>\n\n\n\n
      • Enforce a ratio between request and limit for a resource<\/li>\n<\/ul>\n\n\n\n
        Key features:<\/p>\n\n\n\n
          \n
        • Applied at the pod and container level within a namespace<\/li>\n\n\n\n
        • Sets default values for resource requests and limits<\/li>\n\n\n\n
        • Can prevent the creation of pods that don’t meet the specified constraints<\/li>\n<\/ul>\n\n\n\n
          Example LimitRange:<\/p>\n\n\n
          apiVersion: v1\nkind<\/span>: LimitRange\nmetadata<\/span>:\n  name: limit-mem-cpu-per-container\nspec<\/span>:\n  limits:\n  - default<\/span>:\n      cpu: 500<\/span>m\n      memory<\/span>: 512<\/span>Mi\n    defaultRequest<\/span>:\n      cpu: 200<\/span>m\n      memory<\/span>: 256<\/span>Mi\n    type<\/span>: Container<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
          Use Cases<\/h2>\n\n\n\n
            \n
          • ResourceQuota: Useful for enforcing overall resource constraints in a shared cluster environment, preventing one team or application from consuming all available resources.<\/li>\n\n\n\n
          • LimitRange: Helpful for setting reasonable defaults and preventing the creation of pods with excessive resource requirements or no specified limits.<\/li>\n<\/ul>\n\n\n\n
            By using both ResourceQuota and LimitRange together, cluster administrators can effectively manage resource allocation and ensure fair usage across different teams and applications within a Kubernetes cluster.<\/p>\n\n\n\n
            <\/p>\n\n\n
            apiVersion: v1\nkind<\/span>: Namespace\nmetadata<\/span>:\n  name: myspace\n---\napiVersion: v1\nkind<\/span>: ResourceQuota\nmetadata<\/span>:\n  name: compute-quota\n  namespace<\/span>: myspace\nspec<\/span>:\n  hard:\n    requests.cpu: \"1\"<\/span>\n    requests.memory: 1<\/span>Gi\n    limits.cpu: \"2\"<\/span>\n    limits.memory: 2<\/span>Gi\n---\napiVersion: v1\nkind<\/span>: ResourceQuota\nmetadata<\/span>:\n  name: object-quota\n  namespace<\/span>: myspace\nspec<\/span>:\n  hard:\n    configmaps: \"10\"<\/span>\n    persistentvolumeclaims<\/span>: \"4\"<\/span>\n    replicationcontrollers<\/span>: \"20\"<\/span>\n    secrets<\/span>: \"10\"<\/span>\n    services<\/span>: \"10\"<\/span>\n    services.loadbalancers: \"2\"<\/span>\n\n\n\napiVersion<\/span>: extensions\/v1beta1\nkind<\/span>: Deployment\nmetadata<\/span>:\n  name: helloworld-deployment\n  namespace<\/span>: myspace\nspec<\/span>:\n  replicas: 3<\/span>\n  template<\/span>:\n    metadata:\n      labels:\n        app: helloworld\n    spec<\/span>:\n      containers:\n      - name: k8s-demo\n        image<\/span>: wardviaene\/k8s-demo\n        ports<\/span>:\n        - name: nodejs-port\n          containerPort<\/span>: 3000<\/span>\n        resources<\/span>:\n          requests:\n            cpu: 200<\/span>m\n            memory<\/span>: 0.5<\/span>Gi\n          limits<\/span>:\n            cpu: 400<\/span>m\n            memory<\/span>: 1<\/span>Gi\n\n\napiVersion<\/span>: v1\nkind<\/span>: LimitRange\nmetadata<\/span>:\n  name: limits\n  namespace<\/span>: myspace\nspec<\/span>:\n  limits:\n  - default<\/span>:\n      cpu: 200<\/span>m\n      memory<\/span>: 512<\/span>Mi\n    defaultRequest<\/span>:\n      cpu: 100<\/span>m\n      memory<\/span>: 256<\/span>Mi\n    type<\/span>: Container<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n