Lab
A Cloud Guru

Move Kubernetes Pods to a Secured Runtime Sandbox

Runtime sandboxes are a powerful tool for secure container isolation in Kubernetes. In this lab, you will work to implement a runtime sandbox and run containers within it.

Try for free Contact sales

Path Info

Level

Advanced

Duration

30m

Published

May 19, 2021

Challenge

Install gVisor and Create a containerd Sandbox Configuration

Install gVisor on both the control plane node and the worker node.

Create a containerd runtime configuration called runsc on both servers as well.
Challenge

Create a RuntimeClass for the Sandbox

Create a RuntimeClass called runsc-sandbox. Configure it to use the runsc containerd configuration.
Challenge

Move All Pods in the questionablesoft Namespace to the New Runtime Sandbox

Move all Pods in the questionablesoft namespace to the new runtime sandbox. You will need to delete and re-create the Pods to accomplish this. For convenience, you can find manifest files for these Pods in /home/cloud_user.

Note: If you wish to compare the sandboxed Pods to a non-sandboxed Pod, there is a non-sandboxed Pod called securicorp-api in the default namespace.

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.