Node components (kubelet, kube-proxy, container runtime) in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the role of the kubelet in a Kubernetes node?

The kubelet is an agent that runs on each node. It makes sure containers are running in pods as expected by communicating with the Kubernetes control plane.

beginner

What does the kube-proxy component do in a Kubernetes node?

Kube-proxy manages network rules on nodes. It helps route traffic to the right pods, enabling communication inside the cluster and with external clients.

beginner

Explain the purpose of the container runtime on a Kubernetes node.

The container runtime is software that runs containers. It downloads container images, starts and stops containers, and manages their lifecycle on the node.

intermediate

How do kubelet and container runtime work together on a node?

Kubelet tells the container runtime which containers to run based on pod specs. The container runtime then runs those containers and reports status back to kubelet.

intermediate

Why is kube-proxy important for service discovery in Kubernetes?

Kube-proxy sets up network rules that forward requests to the correct pod IPs. This allows services to find and communicate with pods without knowing their exact locations.

Which component on a Kubernetes node is responsible for running containers?

A Kubelet

B Container runtime

C Kube-proxy

D API server

The container runtime runs containers by managing their lifecycle on the node.

What does the kubelet do on a Kubernetes node?

A Manages network traffic

B Runs containers directly

C Ensures pods are running as expected

D Schedules pods to nodes

Kubelet ensures pods and their containers are running as defined by the control plane.

Which component helps route network traffic to the correct pod in Kubernetes?

A Kube-proxy

B Container runtime

C Kubelet

D Scheduler

Kube-proxy manages network rules to route traffic to pods.

How does the kubelet communicate with the container runtime?

A It sends pod specs to the container runtime to run containers

B It manages network rules for the container runtime

C It schedules pods to nodes

D It stores container images

Kubelet instructs the container runtime which containers to run based on pod specifications.

Which of these is NOT a function of kube-proxy?

A Load balancing network traffic

B Routing traffic to pods

C Managing network rules

D Running containers

Running containers is the job of the container runtime, not kube-proxy.

Describe the main functions of the kubelet, kube-proxy, and container runtime on a Kubernetes node.

Think about what each component does to keep the node working properly.

Explain how kubelet and container runtime interact to run pods on a node.

Focus on the communication flow between kubelet and container runtime.

Practice

1. Which Kubernetes node component is responsible for making sure containers start and keep running on a node?

easy

A. kube-proxy

B. kubelet

C. container runtime

D. etcd

Solution

1. Step 1: Understand the role of kubelet

   kubelet runs on each node and ensures containers are started and stay running as requested by the control plane.

2. Step 2: Differentiate from other components

   kube-proxy manages network traffic, container runtime runs containers, and etcd stores cluster data.

3. Final Answer:

   kubelet -> Option B

4. Quick Check:

   Container management = kubelet [OK]

Hint: kubelet manages containers on nodes, not networking or storage [OK]

Common Mistakes:

• Confusing kubelet with kube-proxy
• Thinking container runtime manages container lifecycle
• Selecting etcd which is for cluster data storage

2. Which of the following is the correct command to check the status of the kubelet service on a Linux node?

easy

A. systemctl status kube-proxy

B. docker ps | grep kubelet

C. systemctl status kubelet

D. kubectl get pods kubelet

Solution

1. Step 1: Identify the service name for kubelet

   The kubelet runs as a system service named 'kubelet' on Linux nodes.

2. Step 2: Use systemctl to check service status

   The command 'systemctl status kubelet' shows the running status of the kubelet service.

3. Final Answer:

   systemctl status kubelet -> Option C

4. Quick Check:

   Check kubelet service = systemctl status kubelet [OK]

Hint: Use systemctl with 'kubelet' to check its status [OK]

Common Mistakes:

• Checking kube-proxy instead of kubelet
• Using kubectl which manages cluster, not node services
• Searching for kubelet in docker containers

3. Given the following command output snippet from a node, which component is responsible for managing network rules to allow pod communication?

NAME       STATUS   ROLES    AGE   VERSION
node-1     Ready    <none>   10d   v1.26.0

Active connections:
- kubelet running
- kube-proxy running
- container runtime running

medium

A. kube-proxy

B. container runtime

C. kubelet

D. etcd

Solution

1. Step 1: Identify the role of kube-proxy

   kube-proxy manages network rules and traffic routing inside the cluster to enable pod communication.

2. Step 2: Differentiate from other components

   kubelet manages containers, container runtime runs containers, and etcd stores cluster data.

3. Final Answer:

   kube-proxy -> Option A

4. Quick Check:

   Network management = kube-proxy [OK]

Hint: Network rules inside cluster are handled by kube-proxy [OK]

Common Mistakes:

• Confusing kubelet with network management
• Thinking container runtime manages networking
• Selecting etcd which is unrelated to node networking

4. You notice pods on a node are not receiving network traffic correctly. You check and find kube-proxy is not running. Which command would you use to restart kube-proxy on a systemd-based node?

medium

A. systemctl restart kube-proxy

B. kubectl restart kube-proxy

C. systemctl restart kubelet

D. docker restart kube-proxy

Solution

1. Step 1: Identify the correct service to restart

   Since kube-proxy manages network traffic and is not running, restarting kube-proxy service is needed.

2. Step 2: Use systemctl to restart kube-proxy

   On systemd-based systems, 'systemctl restart kube-proxy' restarts the kube-proxy service properly.

3. Final Answer:

   systemctl restart kube-proxy -> Option A

4. Quick Check:

   Restart kube-proxy with systemctl restart kube-proxy [OK]

Hint: Restart kube-proxy service with systemctl to fix network issues [OK]

Common Mistakes:

• Restarting kubelet instead of kube-proxy
• Using kubectl which cannot restart node services
• Trying to restart kube-proxy as a docker container

5. A Kubernetes node uses containerd as its container runtime. You want to verify that the container runtime is running correctly and can start containers. Which sequence of commands would you use to check containerd status and list running containers?

hard

A. docker ps && crictl status

B. systemctl status kubelet && docker ps

C. kubectl get pods && systemctl status containerd

D. systemctl status containerd && crictl ps

Solution

1. Step 1: Check containerd service status

   Use 'systemctl status containerd' to verify the container runtime service is active and running.

2. Step 2: List running containers with crictl

   Since containerd uses CRI, 'crictl ps' lists running containers managed by containerd.

3. Final Answer:

   systemctl status containerd && crictl ps -> Option D

4. Quick Check:

   Check containerd and containers with systemctl and crictl [OK]

Hint: Use systemctl for service and crictl for container runtime containers [OK]

Common Mistakes:

• Using docker commands when containerd is runtime
• Checking kubelet status instead of container runtime
• Mixing kubectl pod commands with container runtime checks