GSP393

Overview

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 course 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 enrolled in the Implement CI/CD Pipelines on Google Cloud course. Are you ready for the challenge?

Topics tested

• Using Cloud Build and Artifact Registry for containers.
• Setting up Cloud Deploy pipelines using Skaffold.
• Deploying to multiple environments with promotion approvals.
• Rolling back deployments.

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 are made available to you.

This hands-on lab lets you do the lab activities in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials 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).

• Time to complete the lab—remember, once you start, you cannot pause a lab.

You must wait for the lab to provision before making any changes to the environment! The pre-configured parts of the environment that you need to work with will be available to you as soon as the lab indicates it is ready.

Challenge Scenario

You have started a new role as a Cloud Engineer for Jooli Inc. New management has decided to modernize and believe it's best to completely replace their legacy systems with managed infrastructure and automated integration and delivery pipelines. They have tasked you with finding and testing the best tools and services to achieve this.

By the end of the day, management would like to see a proof of concept that can address all of the following:

• Container images stored in a secure and reliable registry.
• Automatic container image scanning with detailed reports on security vulnerabilities.
• A test web application running on managed infrastructure.
• A CI/CD pipeline defined as code in order to eliminate manual errors.
• A reliable, easy, and quick way to deploy code and promote to a production-like environment or rollback if necessary.

You're expected to help manage the Cloud infrastructure and deployment tools at Jooli. Common tasks include provisioning resources for projects and implementing new products and services to ensure Jooli Inc. is modernizing effectively and following best practices.

You are expected to have the skills and knowledge for these tasks, so step-by-step guides won't be provided.

Some Jooli Inc. standards you should follow:

• Create all resources in the region, unless otherwise directed.
• Use the project default VPC.
• 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 the default machine types.

Your challenge

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

1. PRE-WORK - Enable APIs, Create GKE clusters and create an docker repository in Artifact Registry.
2. Clone source code, build image, and push to artifact registry.
3. Create delivery pipeline, targets, and release.
4. Rebuild and push image, tag with latest.
5. Create new release with latest version.
6. Promote the latest release to second cluster.
7. Rollback changes to second cluster, modify, and re-release.

Task 1. Prework - Set up environment, enable APIs and create clusters

1. Set up environment variables for your Project ID (this is important as it is used in several of the configuration files below). You can use the commands below:

2. Enable the following services in your Google Cloud project using the following commands:

• container.googleapis.com
• clouddeploy.googleapis.com
• artifactregistry.googleapis.com
• cloudbuild.googleapis.com

3. Enable permissions for both Kubernetes and Cloud Deploy using the following commands:

4. Create an Artifact Repository

Create a repository for storing your Docker containers.

Name the repository: cicd-challenge

5. Create the Google Kubernetes Engine clusters

Create two GKE clusters for Staging and Production named cd-staging and cd-production. Clusters should be single zone and single node.

Task 2. Build the images and upload to the repository

1. Clone the repository for the lab into your home directory using the commands below:

2. Create the skaffold.yaml configuration using the command below:

The web directory now contains the skaffold.yaml configuration file, which provides instructions for Skaffold to build a container image for your application.

3. Run the skaffold command to build the application and deploy the container image to the Artifact Registry repository previously created:

HINT: use the full path to the repository you created earlier

Task 3. Create the Delivery Pipeline

Run the following commands to copy the pipeline template file:

1. Create the delivery-pipeline resource using the delivery-pipeline.yaml file:

2. Set the deployment region using the deploy/region configuration parameter.
3. Apply the pipeline configuration you created above using thef gcloud beta deploy command
4. Verify the delivery pipeline was created using the command below:

Configure the deployment targets

Two delivery pipeline targets will be created - one for each of the GKE clusters.

Ensure that the clusters are ready

The two GKE clusters should now be running but it's useful to verify this.

• Get the status of the clusters:

All clusters should be in the RUNNING state, as indicated in the output below. If they are not yet marked as RUNNING, retry the command above until their status has changed to RUNNING.

Create a context for each cluster

• Use the commands below to get the credentials for each cluster and create an easy-to-use kubectl context for referencing the clusters later:

Create a namespace in each cluster

• Use the commands below to create a Kubernetes namespace (web-app) in each of the clusters:

Create the delivery pipeline targets

1. Create a target definition file for each of the targets using the commands below (no changes needed):

2. Apply the target files to Cloud Deploy.

The targets are described in a yaml file. Each target configures the relevant cluster information for the target.

Display the details for the staging target:

Task 4. Create a Release

1. Create a release using the gcloud beta deploy releases command and the skaffold and artifacts.json files you created earlier.

• Name the release web-app-001 and use the delivery-pipeline web-app.

HINT: your source directory should be web/

• Verify that your application has been deployed to the staging environment (cd-staging) via the command below or in the console.

Task 5. Promote your application to production

• Promote your application from the Staging (cd-staging) environment to the Production (cd-production) environment.

HINT: Don't forget to approve the deployment!

Task 6. Make a change to the application and redeploy it

1. Using the editor, open the cloud-deploy-tutorials/tutorials/base/web/leeroy-app/ directory and modify the app.go file. Change line 24 to say: fmt.Fprintf(w, "leeroooooy app v2!!\n")
2. Build the application and push to the Artifact Registry.
3. Create a new release on your pipeline you created earlier. Name the release web-app-002
4. Verify the new version has been deployed to the staging environment.

Task 7. Rollback The Change

Oh No! Your QA Engineers have found a bug in your release to staging so you will need to rollback to the previous version.

1. Use Cloud Deploy to rollback to the original version of the application - web-app-001
2. Verify that the original version is running.

Congratulations!

In this lab, you have successfully set up a CI/CD pipeline using Google Cloud Deploy and Artifact Registry. You've created a proof of concept that addressed all of management's requirements. Jooli Inc. is now well on their way towards achieving higher ROI with the benefits of application modernization!

Earn your next skill badge

This lab is part of the Implement CI/CD Pipelines on Google Cloud course. Completing this skill badge course 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 course is part of Google Cloud’s DevSecOps Learning Path. Continue your learning journey here DevSecOps Learning Path!

Next Steps / Learn More

• Google Kubernetes Engine: Types of Clusters
• Container analysis and vulnerability scanning
• Integrating Google Cloud Deploy with other systems

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 March 4, 2024

Lab Last Tested August 28, 2023

Copyright 2025 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.