Why Kubernetes networking matters - See It in Action

Why Kubernetes Networking Matters

📖 Scenario: You are working in a team that manages applications running on Kubernetes clusters. To keep the applications running smoothly, you need to understand how networking works inside Kubernetes. This helps you ensure that different parts of your application can talk to each other and to the outside world.

🎯 Goal: Learn the basics of Kubernetes networking by creating a simple data structure that represents pods and their IP addresses, then configure a network policy to allow traffic only between certain pods, and finally display which pods can communicate with each other.

📋 What You'll Learn

Create a dictionary representing pods with their IP addresses

Add a list of allowed pod names to simulate a network policy

Write code to find which pods can communicate based on the policy

Print the communication pairs

💡 Why This Matters

🌍 Real World

Kubernetes networking is essential to control traffic flow between application parts, improving security and reliability.

💼 Career

Understanding Kubernetes networking helps DevOps engineers configure clusters correctly and troubleshoot connectivity issues.

1

Create a dictionary of pods with IP addresses

Create a dictionary called pods with these exact entries: 'frontend': '10.0.0.1', 'backend': '10.0.0.2', 'database': '10.0.0.3'

Kubernetes

# Create the pods dictionary with pod names and their IP addresses
# Your code here

Need a hint?

Think of pods as a phone book where each pod name has its phone number (IP address).

2

Add a list of allowed pods for network policy

Create a list called allowed_pods containing the pod names 'frontend' and 'backend' to simulate a network policy allowing communication only between these pods

Kubernetes

pods = {'frontend': '10.0.0.1', 'backend': '10.0.0.2', 'database': '10.0.0.3'}
# Create the allowed_pods list with 'frontend' and 'backend'
# Your code here

Need a hint?

This list acts like a guest list for who can talk to each other.

3

Find which pods can communicate based on the policy

Create a list called allowed_communications that contains tuples of pod pairs (source, destination) where both pods are in allowed_pods. Use a for loop with variables src and dst to iterate over allowed_pods twice and include pairs where src != dst

Kubernetes

pods = {'frontend': '10.0.0.1', 'backend': '10.0.0.2', 'database': '10.0.0.3'}
allowed_pods = ['frontend', 'backend']
# Create allowed_communications list with tuples of (src, dst) where both are in allowed_pods and src != dst
# Your code here

Need a hint?

Think of this as making pairs of friends who can call each other, but not themselves.

4

Print the allowed pod communications

Write a print statement to display the allowed_communications list

Kubernetes

pods = {'frontend': '10.0.0.1', 'backend': '10.0.0.2', 'database': '10.0.0.3'}
allowed_pods = ['frontend', 'backend']
allowed_communications = []
for src in allowed_pods:
    for dst in allowed_pods:
        if src != dst:
            allowed_communications.append((src, dst))
# Print the allowed_communications list
# Your code here

Need a hint?

This shows which pods can talk to each other according to the network policy.