Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon
Labs

Working with Kubernetes NetworkPolicies

By default, Kubernetes pods have unrestricted network access both inside and outside the cluster. However, it is often desirable to restrict network access to and from pods, particularly for security reasons. Kubernetes NetworkPolicies provide a flexible way to implement these networking restrictions, giving you control over all of the network traffic involving your pods. In this lab, walk through NetworkPolicies concepts, and examine some existing policies to determine how we can properly apply them to a pod.

Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Intermediate
Duration
Clock icon 1h 0m
Published
Clock icon Mar 31, 2019

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Provide the `web-gateway` Pod with Network Access to the Pods Associated with the `inventory-svc` Service

    First, get a list of existing NetworkPolicies:

    kubectl get networkpolicy
    

    Examine inventory-policy more closely:

    kubectl describe networkpolicy inventory-policy
    

    Note that the policy selects pods with the label app: inventory, and provides incoming and outgoing network access to all pods with the label inventory-access: true.

    Modify the web-gateway pod with kubectl edit pod web-gateway.

    Add the inventory-access: "true" label to the pod under metdadata.labels.

    ...
    metdadata:
      labels:
        inventory-access: "true"
    ...
    

    Test access to the inventory-svc like so:

    kubectl exec web-gateway -- curl -m 3 inventory-svc
    
  2. Challenge

    Provide the `web-gateway` Pod with Network Access to the Pods Associated with the `customer-data-svc` Service

    Examine customer-data-policy more closely:

    kubectl describe networkpolicy customer-data-policy
    

    Note that the policy selects pods with the label app: customer-data, and provides incoming and outgoing network access to all pods with the label customer-data-access: true.

    Modify the web-gateway pod with kubectl edit pod web-gateway.

    Add the customer-data-access: "true" label to the pod under metadadata.labels:

    ...
    metdadata:
      labels:
        inventory-access: "true"
        customer-data-access: "true"
    ...
    

    Test access to the customer-data-svc like so:

    kubectl exec web-gateway -- curl -m 3 customer-data-svc
    

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

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.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans