What tools in GCP can help us achieve this

In this lesson, we’ll map our CI/CD requirements to Google Cloud Platform (GCP) services. If you’d prefer to explore on your own first, try searching for terms like “GCP CI/CD pipeline” or “Cloud Build alternatives in GCP.”

Step 1: Select the Right GCP Services

Within GCP, the two core services for building, storing, and deploying containerized applications are:

Service	Purpose	Key Features
Cloud Build	Continuous Integration & Delivery	Builds Docker images, runs tests, and deploys
Artifact Registry	Managed container and artifact repository	Stores Docker images, Helm charts, and binaries

Note

Cloud Build integrates directly with Cloud Source Repositories, GitHub, and Bitbucket. You can trigger builds automatically on code pushes or pull requests.

Step 2: Visualize the CI/CD Pipeline

Below is a high-level diagram showing how Cloud Build and Artifact Registry work together in a typical pipeline:

The image lists two Google Cloud Platform services: Cloud Build and GCP Artifact Registry, each with an icon and numbered labels.

Step 3: CI/CD Workflow Breakdown

Build & Push
- A Cloud Build trigger fires on commits to your GitHub or Cloud Source Repository.
- Cloud Build executes a build config (cloudbuild.yaml), packages your application into a Docker image, and pushes it to Artifact Registry.
Deploy to GKE
- A second Cloud Build trigger detects the new image in Artifact Registry.
- Cloud Build pulls the image and applies Kubernetes manifests (or Helm chart) to your Google Kubernetes Engine (GKE) cluster.

Warning

Ensure that the Cloud Build service account has the artifactregistry.writer and GKE permissions before running pipelines.

Next Steps

Now that we’ve covered the CI/CD services in GCP:

We’ll create the cloudbuild.yaml configuration.
We’ll set up GitHub triggers and IAM roles.
We’ll define Kubernetes deployment manifests or Helm charts.

Stay tuned for the detailed configuration guide!

References

Watch Video

Watch video content