Node components (kubelet, kube-proxy, container runtime) in Kubernetes - Mini Project: Build & Apply

Understanding Kubernetes Node Components

📖 Scenario: You are learning how Kubernetes manages the worker nodes in a cluster. Each node runs several important components that help run and manage containers.These components are kubelet, kube-proxy, and the container runtime. Understanding their roles helps you troubleshoot and maintain your cluster.

🎯 Goal: Build a simple YAML configuration that lists the three main node components with their descriptions. Then, add a status field to each component. Finally, print the final list showing each component and its status.

📋 What You'll Learn

Create a dictionary named node_components with keys kubelet, kube-proxy, and container_runtime and their descriptions as values.

Add a new dictionary component_status with the status Running for each component.

Combine the descriptions and status into a new dictionary components_info where each component maps to a dictionary with description and status.

Print the components_info dictionary.

💡 Why This Matters

🌍 Real World

Kubernetes administrators need to understand node components to monitor and troubleshoot cluster nodes effectively.

💼 Career

Knowing how kubelet, kube-proxy, and container runtimes work is essential for roles like DevOps engineers and site reliability engineers managing Kubernetes clusters.

1

Create the initial node components dictionary

Create a dictionary called node_components with these exact entries: 'kubelet': 'Manages pods and containers on the node', 'kube-proxy': 'Maintains network rules on nodes', and 'container_runtime': 'Runs containers on the node'.

Kubernetes

# Create the node_components dictionary with exact keys and descriptions
# Your code here

Hint

Use a Python dictionary with the exact keys and string values given.

2

Add component status dictionary

Create a dictionary called component_status with the keys 'kubelet', 'kube-proxy', and 'container_runtime' all set to the string 'Running'.

Kubernetes

node_components = {
    'kubelet': 'Manages pods and containers on the node',
    'kube-proxy': 'Maintains network rules on nodes',
    'container_runtime': 'Runs containers on the node'
}
# Create the component_status dictionary with all statuses set to 'Running'
# Your code here

Hint

Create a dictionary with the same keys as node_components and set all values to 'Running'.

3

Combine descriptions and status into one dictionary

Create a new dictionary called components_info where each key is a component name from node_components. Each value should be a dictionary with keys 'description' and 'status' holding the corresponding values from node_components and component_status. Use a for loop with variables component and description to iterate over node_components.items().

Kubernetes

node_components = {
    'kubelet': 'Manages pods and containers on the node',
    'kube-proxy': 'Maintains network rules on nodes',
    'container_runtime': 'Runs containers on the node'
}

component_status = {
    'kubelet': 'Running',
    'kube-proxy': 'Running',
    'container_runtime': 'Running'
}

# Create components_info dictionary combining description and status
# Your code here

Hint

Use a for loop to build a new dictionary combining both dictionaries' values.

4

Print the combined components information

Write a print statement to display the components_info dictionary.

Kubernetes

node_components = {
    'kubelet': 'Manages pods and containers on the node',
    'kube-proxy': 'Maintains network rules on nodes',
    'container_runtime': 'Runs containers on the node'
}

component_status = {
    'kubelet': 'Running',
    'kube-proxy': 'Running',
    'container_runtime': 'Running'
}

components_info = {}
for component, description in node_components.items():
    components_info[component] = {
        'description': description,
        'status': component_status[component]
    }

# Print the components_info dictionary
# Your code here

Hint

Use print(components_info) to show the final dictionary.

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