Limit ranges for defaults in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a LimitRange in Kubernetes?

A LimitRange is a Kubernetes resource that sets default resource limits and requests for containers in a namespace. It helps control how much CPU and memory each container can use.

beginner

How does a LimitRange set default resource limits?

A LimitRange can specify default CPU and memory limits and requests. If a container does not specify these, Kubernetes applies the defaults from the LimitRange automatically.

intermediate

What happens if a container requests resources outside the LimitRange?

If a container requests resources less than the minimum or more than the maximum defined in the LimitRange, Kubernetes rejects the pod creation with an error.

intermediate

Example YAML snippet to set default CPU and memory limits using LimitRange?

apiVersion: v1 kind: LimitRange metadata: name: default-limits spec: limits: - default: cpu: 500m memory: 256Mi defaultRequest: cpu: 250m memory: 128Mi type: Container

beginner

Why use LimitRanges for defaults in a Kubernetes namespace?

LimitRanges help ensure fair resource use, prevent resource starvation, and avoid unexpected high resource consumption by setting sensible defaults and limits for containers.

What does a LimitRange resource in Kubernetes do?

A Sets default and max resource limits for containers in a namespace

B Manages network policies for pods

C Schedules pods to nodes

D Stores container images

LimitRange sets default and maximum CPU and memory limits for containers in a namespace.

If a container does not specify resource requests, what happens when a LimitRange with defaults exists?

A The container runs without any resource limits

B The pod is rejected

C Kubernetes applies the default resource requests and limits from the LimitRange

D The pod is scheduled to a random node

Kubernetes uses the default resource requests and limits defined in the LimitRange if the container does not specify them.

What happens if a container requests more CPU than the maximum in the LimitRange?

A Kubernetes ignores the request and schedules the pod

B The pod is scheduled but marked as pending

C The container is throttled after starting

D Pod creation is rejected with an error

Kubernetes rejects pod creation if resource requests exceed the maximum defined in the LimitRange.

Which type field is used in LimitRange to set defaults for containers?

A Pod

B Container

C Node

D Namespace

The type 'Container' is used in LimitRange to define default resource limits and requests for containers.

Why is it important to set default resource limits in Kubernetes?

A To prevent resource overuse and ensure fair sharing

B To speed up pod scheduling

C To increase network bandwidth

D To store logs efficiently

Setting default resource limits prevents resource overuse and helps ensure fair resource sharing among containers.

Explain what a LimitRange is and how it helps manage resources in a Kubernetes namespace.

Think about how Kubernetes controls CPU and memory usage for containers.

Describe what happens when a container's resource requests do not match the limits set by a LimitRange.

Consider Kubernetes behavior when resource requests are outside allowed ranges.