Lab
A Cloud Guru

Using Init Containers in Kubernetes

Init containers are a great way to customize container startup. This lab will allow you to test your knowledge of init containers by using them to solve problems in an existing Kubernetes cluster.

Try for free Contact sales

Path Info

Level

Intermediate

Duration

30m

Published

Sep 03, 2020

Challenge

Create a Sample Pod That Uses an Init Container to Delay Startup

You will find a simple pod descriptor on the control plane server at /home/cloud_user/pod.yml. Modify this pod descriptor to add an init container that will delay startup if shipping-svc cannot be located using nslookup. Then, create the pod.

Note: Please use BusyBox 1.27. Newer releases may encounter complications with nslookup.
Challenge

Test Your Setup by Creating the Service and Verifying the Pod Starts Up

Apply the deployment descriptor for the shipping-svc found at /home/cloud_user/shipping-svc.yml. Watch the status of your pod. If you set it up correctly, you should see the pod complete startup once the service becomes available.

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.