Lock Down Inter-Pod Communication with NetworkPolicies

30 minutes
  • 2 Learning Objectives

About this Hands-on Lab

NetworkPolicies are a great way to control network communication within a Kubernetes cluster. In this lab, you will make a Kubernetes cluster more secure by using NetworkPolicies to restrict network traffic to only traffic that is actually needed by applications running in the cluster.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Block Incoming Traffic by Default for All Pods in the web-auth Namespace

Create a configuration that causes incoming traffic to all Pods in the web-auth namespace to be blocked by default.

Allow Traffic from the auth-client Pod to Reach the web-auth-server

Allow the auth-client Pod to reach web-auth-server. Both Pods are in the web-auth namespace. You can use existing labels to accomplish this.

  • auth-client needs to be able to reach web-auth-server on port 80.
  • Only Pods with the appropriate label should be able to access web-auth-server, even if they are in the web-auth namespace.
  • Pods outside the web-auth namespace should never be able to access web-auth-server, no matter what labels they have.

Additional Resources

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?