This lab provides practice scenarios to help prepare you for the Certified Kubernetes Application Developer (CKAD) exam. You will be presented with tasks to complete, as well as server(s) and/or an existing Kubernetes cluster to complete them in. You will need to use your knowledge of Kubernetes to successfully complete the provided tasks, much like you would on the real CKAD exam. Good luck!
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Create a Blue/Green Setup for an Existing Deployment
Create a blue/green Deployment setup for the existing
web-frontend
Deployment in thebluegreen
Namespace.You can find a Deployment manifest for
web-frontend
on the CLI server at/home/cloud_user/bluegreen/web-frontend.yml
. Feel free to copy this manifest in order to create your green Deployment.Give the green Deployment the name
web-frontend-green
and set theenv
label togreen
in the Pod template.Once you have created the green Deployment and verified that it is working, modify the
web-frontend-svc
Service so that it points only to the new green Deployment’s Pods. This is a NodePort Service, and you can test it by reaching out to port30081
on any of the cluster nodes, for example:curl k8s-control:30081
.- Create a Canary Setup for an Existing Deployment
Create a canary Deployment setup for the existing
auth
Deployment in thecanary
Namespace.There is a manifest file for the existing Deployment at
/home/cloud_user/canary/auth.yml
. You can copy this file to create your canary Deployment.Give the canary Deployment the name
auth-canary
, and set theenv
label in the Pod template tocanary
.There is a Service called
auth-svc
, also in thecanary
Namespace. Modify this Service to direct traffic to both the main and canary Deployments. Configure your setup so that there will be4
total replicas, including both the main Deployment and the canary Deployment, and so that approximately25%
of traffic will go to the canary Pod(s). Note that you may need to modify the original main Deployment in order to accomplish this.The Service is a NodePort Service, and you can test it by reaching out to port
30082
on any of the cluster nodes, for example:curl k8s-control:30082
.