📘 Kubernetes LimitRange Deep Dive¶

🌟 Introduction¶

LimitRange is a Kubernetes resource that sets default, minimum, and maximum resource constraints for containers and pods within a namespace. While [ResourceQuota](01-resource-quota-guide.md) enforces aggregate resource usage limits, LimitRange controls the per-container/pod resource policies.

They complement each other in a cluster’s resource policy setup.

🧠 Key Purpose of LimitRange¶

🧪 Example: Full YAML with Descriptive Comments¶

apiVersion: v1
kind: LimitRange
metadata:
  name: resource-limits
  namespace: dev
spec:
  limits:
    - type: Container       # Applies to individual containers (not whole pods)
      max:                  # Upper bound for requests and limits
        cpu: "1"            # Container can't request more than 1 CPU core
        memory: "1Gi"       # Container can't use more than 1Gi of memory
      min:                  # Lower bound for requests and limits
        cpu: "100m"         # At least 100 millicores must be requested
        memory: "128Mi"     # At least 128Mi memory must be requested
      default:              # this section defines default limits
        cpu: "500m"         # If not set in Pod spec, this value is used (Default resource.limit.cpu)
        memory: "512Mi"
      defaultRequest:       # this section defines default requests
        cpu: "200m"         # Default resource.request.cpu
        memory: "256Mi"
      maxLimitRequestRatio:
        cpu: "4"            # Limits can’t be more than 4x requests for CPU

🎯 Use Case Breakdown¶

🔹 1. Pod without Resource Requests or Limits¶

containers:
  - name: test
    image: nginx

resources:
  requests:
    cpu: 200m       # From defaultRequest
    memory: 256Mi
  limits:
    cpu: 500m       # From default
    memory: 512Mi

🔹 2. Pod Specifies Less Than min¶

resources:
  requests:
    cpu: 50m
    memory: 64Mi

🔹 3. Pod Exceeds max¶

resources:
  limits:
    cpu: 2

🔹 4. Pod Violates maxLimitRequestRatio¶

resources:
  requests:
    cpu: 100m
  limits:
    cpu: 1

🧩 Relationship Between LimitRange and ResourceQuota¶

Example Conflict Scenario:¶

• ResourceQuota allows total cpu: 2
• A user tries to create 3 pods with limit cpu: 1 (total = 3)
• ❌ Fails due to quota, even if LimitRange individually allows it

🔧 CLI Flags vs YAML for LimitRange¶

There is no direct kubectl create limitrange command with full feature flags like --hard in ResourceQuota. You need to apply YAML manifest.

⚖️ CPU & Memory Units Reference¶

CPU¶

• 1 = 1 core
• 500m = 0.5 cores
• 100m = 0.1 cores

Memory¶

• Mi = Mebibytes (base-2) → 1Mi = 1,048,576 bytes
• Gi = Gibibytes → 1Gi = 1024Mi

✅ Best Practices¶

• Set reasonable defaultRequest to guarantee scheduler efficiency.
• Use LimitRange to avoid resource hogs and noisy neighbors.
• Combine LimitRange with ResourceQuota to ensure predictable namespace limits.
• Document both resource policies clearly for development teams.

📎 Bonus: Pod Spec Validation Summary¶

Further Reading¶

• Limit Range and Pod Sheduling
• Limit Range and Resource Quota Demo
• Limit Range and Resource Quota Together in Kubernetes