Lab
A Cloud Guru

Assigning a Kubernetes Pod to a Specific Node

Kubernetes scheduling usually doesn't need much help in order to determine which node to run a pod on. However, you may occasionally wish to have a little more control. In this lab, you will be able to practice the process of ensuring a pod runs on a specific node.

Try for free Contact sales

Path Info

Level

Intermediate

Duration

30m

Published

Sep 03, 2020

Challenge

Configure the `auth-gateway` Pod to Only Run on `k8s-worker2`

Locate the auth-gateway pod in the beebox-auth namespace. Modify the pod, using a label and a nodeSelector constraint, so it will always be scheduled on k8s-worker2. You will need to delete and re-create the pod in order for these changes to take effect.

You can find a YAML descriptor for this pod at /home/cloud_user/auth-gateway.yml.
Challenge

Configure the `auth-data` Deployment's Replica Pods to Only Run on `k8s-worker2`

You will find the auth-data deployment in the beebox-auth namespace. Modify the deployment, using a nodeSelector constraint, so its replica pods will always run on k8s-worker2. These changes should take effect once you make this change via a rolling deployment.

You can find a YAML descriptor for this pod at /home/cloud_user/auth-data.yml.

Author

A Cloud Guru

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.