arrow_back

Deploy to Kubernetes in Google Cloud: Challenge Lab

Join Sign in

Deploy to Kubernetes in Google Cloud: Challenge Lab

1 hour 30 minutes 7 Credits

GSP318

Google Cloud self-paced labs logo

Introduction

In a challenge lab you’re given a scenario and a set of tasks. Instead of following step-by-step instructions, you will use the skills learned from the labs in the quest to figure out how to complete the tasks on your own! An automated scoring system (shown on this page) will provide feedback on whether you have completed your tasks correctly.

When you take a challenge lab, you will not be taught new Google Cloud concepts. You are expected to extend your learned skills, like changing default values and reading and researching error messages to fix your own mistakes.

To score 100% you must successfully complete all tasks within the time period!

This lab is recommended for students who have enrolled in the Deploy to Kubernetes in Google Cloud quest. Are you ready for the challenge?

Setup

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources will be made available to you.

This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

  • Access to a standard internet browser (Chrome browser recommended).
Note: Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.
  • Time to complete the lab---remember, once you start, you cannot pause a lab.
Note: If you already have your own personal Google Cloud account or project, do not use it for this lab to avoid extra charges to your account.

Challenge scenario

You have just completed training on containers and their creation and management and now you need to demonstrate to the Jooli Inc. development team your new skills. You have to help with some of their initial work on a new project around an application environment utilizing Kubernetes. Some of the work was already done for you, but other parts require your expert skills.

You are expected to create container images, store the images in a repository, and configure a Jenkins CI/CD pipeline to automate the build for the product. Your know that Kurt, your supervisor, will ask you to complete these tasks:

  • Create a Docker image and store the Dockerfile.
  • Test the created Docker image.
  • Push the Docker image into the Container Repository.
  • Use the image to create and expose a deployment in Kubernetes
  • Update the image and push a change to the deployment.
  • Create a pipeline in Jenkins to deploy a new version of your image when the source code changes.

Some Jooli Inc. standards you should follow:

  • Create all resources in the us-east1 region and us-east1-b zone, unless otherwise directed.

  • Use the project VPCs.

  • Naming is normally team-resource, e.g. an instance could be named kraken-webserver1.

  • Allocate cost effective resource sizes. Projects are monitored and excessive resource use will result in the containing project's termination (and possibly yours), so beware. This is the guidance the monitoring team is willing to share: unless directed, use n1-standard-1.

Your challenge

As soon as you sit down at your desk and open your new laptop you receive the following request to complete these tasks. Good luck!

Task 1. Create a Docker image and store the Dockerfile

  1. Open Cloud Shell and run source <(gsutil cat gs://cloud-training/gsp318/marking/setup_marking_v2.sh). This command will install marking scripts you can use to help check your progress.

  2. Use Cloud Shell to clone the valkyrie-app source code repository (it is in your project).

The app source code is in valkyrie-app/source.

  1. Create valkyrie-app/Dockerfile and add the configuration below:

FROM golang:1.10 WORKDIR /go/src/app COPY source . RUN go install -v ENTRYPOINT ["app","-single=true","-port=8080"]
  1. Use valkyrie-app/Dockerfile to create a Docker image called with the tag .

  2. Once you have created the Docker image, and before clicking Check my progress, run step1_v2.sh to perform the local check of your work.

After you get a successful response from the local marking you can check your progress.

Click Check my progress to verify the objective. Create a Docker image and store the Dockerfile

Task 2. Test the created Docker image

  1. Launch a container using the image :
  • You need to map the host’s port 8080 to port 8080 on the container.
  • Add & to the end of the command to cause the container to run in the background.

When your container is running you will see the page by Web Preview.

  1. Once you have your container running, and before clicking Check my progress, run step2_v2.sh to perform the local check of your work. After you get a successful response from the local marking you can check your progress.

Click Check my progress to verify the objective. Test the created Docker image

Task 3. Push the Docker image in the Container Repository

  1. Push the Docker image into the Container Registry.

  2. Make sure you re-tag the container to .

Click Check my progress to verify the objective. Push the Docker image in the Google Container Repository

Task 4. Create and expose a deployment in Kubernetes

Kurt created the deployment.yaml and service.yaml to deploy your new container image to a Kubernetes cluster (called valkyrie-dev). The two files are in valkyrie-app/k8s.

  1. Remember you need to get the Kubernetes credentials before you deploy the image onto the Kubernetes cluster.

  2. Before you create the deployments make sure you check the deployment.yaml and service.yaml files. Kurt thinks they need some values set (he thinks he left some placeholder values).

  3. You can check the load balancer once it’s available.

Click Check my progress to verify the objective. Create and expose a deployment in Kubernetes

Task 5. Update the deployment with a new version of valkyrie-app

  1. Before deploying the new code, increase the replicas from 1 to to ensure you don't cause an outage.

Click Check my progress to verify the objective. Increase the replicas from 1 to

Kurt made changes to the source code (he put the changes in a branch called kurt-dev).

  1. You need to merge kurt-dev into master (you should use git merge origin/kurt-dev).

  2. Build the new code as version of valkyrie-app, push the updated image to the Container Repository, and then redeploy to the valkyrie-dev cluster. You will know you have the new version because the titles for the cards will be green.

Click Check my progress to verify the objective. Update the deployment with a new version of valkyrie-app

Task 6. Create a pipeline in Jenkins to deploy your app

This process of building the container and pushing to the container repository can be automated using Jenkins. There is a Jenkins deployment in your valkyrie-dev cluster - connect to Jenkins and configure a job to build when you push a change to the source code.

  1. Remember with Jenkins:
  • Get the password with printf $(kubectl get secret cd-jenkins -o jsonpath="{.data.jenkins-admin-password}" | base64 --decode);echo.

  • Connect to the Jenkins console using the commands below (but make sure you don't have a running container docker ps; if you do, kill it):

export POD_NAME=$(kubectl get pods --namespace default -l "app.kubernetes.io/component=jenkins-master" -l "app.kubernetes.io/instance=cd" -o jsonpath="{.items[0].metadata.name}") kubectl port-forward $POD_NAME 8080:8080 >> /dev/null &
  • Setup your credentials to use Google Service Account from metadata.

  • Configure Jenkins Cloud for Kubernetes

  • Create a pipeline job that points to your */master branch on your source code.

  1. Make two changes to your files before you commit and build:

  • Edit valkyrie-app/Jenkinsfile and change YOUR_PROJECT to your actual project id.

  • Edit valkyrie-app/source/html.go and change the two occurrences of green to orange.

  1. Use git to:
  • Add all the changes then commit those changes to the master branch.
  • Push the changes back to the repository.

When you are ready, manually trigger a build (the initial build will take some time, so just monitor the process). The build will replace the running containers with containers with different tags; you will see orange colored headings.

Click Check my progress to verify the objective. Create a pipeline in Jenkins to deploy your app

Congratulations!

Deploy to Kubernetes Skill badge

Earn your next skill badge

This self-paced lab is part of the Deploy to Kubernetes in Google Cloud skill badge quest. Completing this skill badge quest earns you the badge above, to recognize your achievement. Share your badge on your resume and social platforms, and announce your accomplishment using #GoogleCloudBadge.

This skill badge quest is part of Google's Cloud Hybrid and Multi-Cloud Cloud Architect learning path. If you have already completed the other skill badge quests in this learning path, search the Google Cloud Skills Boost catalog for 20+ other skill badge quests in which you can enroll.

Google Cloud training and certification

...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.

Manual Last Updated September 19, 2022

Lab Last Tested September 19, 2022

Copyright 2022 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.