Automated Deployment Pipeline for Google Container Registry (GCR)
Question
Your application images are built and pushed to Google Container Registry (GCR)
You want to build an automated pipeline that deploys the application when the image is updated while minimizing the development effort.
What should you do?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D.
To build an automated pipeline that deploys an application when the image is updated while minimizing the development effort, there are different options that can be used in Google Cloud Platform (GCP).
Option A: Use Cloud Build to trigger a Spinnaker pipeline. This option involves using Cloud Build to trigger a Spinnaker pipeline. Cloud Build is a GCP service that provides a fully-managed continuous integration and continuous delivery (CI/CD) platform. It automates the process of building, testing, and deploying applications. Spinnaker is an open-source, multi-cloud continuous delivery platform that enables users to deploy applications to various targets, including Kubernetes clusters, virtual machines, and serverless platforms.
To use this option, a Cloud Build trigger is set up to monitor changes to the application image in GCR. Once a change is detected, Cloud Build triggers a Spinnaker pipeline to deploy the new image. This option is a good choice for teams that are already using Spinnaker for their deployments, as it leverages existing infrastructure and does not require additional setup.
Option B: Use Cloud Pub/Sub to trigger a Spinnaker pipeline. This option involves using Cloud Pub/Sub to trigger a Spinnaker pipeline. Cloud Pub/Sub is a fully-managed messaging service that enables users to send and receive messages between independent applications. It decouples components of a distributed system, making it easier to build and scale applications.
To use this option, a Cloud Pub/Sub topic is created to receive notifications when a new image is pushed to GCR. A Spinnaker pipeline is then triggered to deploy the new image. This option provides more flexibility than Option A, as it can be used with different CI/CD tools, not just Cloud Build.
Option C: Use a custom builder in Cloud Build to trigger a Jenkins pipeline. This option involves using a custom builder in Cloud Build to trigger a Jenkins pipeline. Jenkins is an open-source automation server that enables users to build, test, and deploy software. It provides hundreds of plugins to support building, deploying, and automating any project.
To use this option, a custom builder is created in Cloud Build to trigger a Jenkins pipeline. The custom builder listens for changes to the application image in GCR and triggers a Jenkins pipeline to deploy the new image. This option is a good choice for teams that are already using Jenkins for their deployments, as it leverages existing infrastructure and does not require additional setup.
Option D: Use Cloud Pub/Sub to trigger a custom deployment service running in Google Kubernetes Engine (GKE). This option involves using Cloud Pub/Sub to trigger a custom deployment service running in GKE. GKE is a fully-managed Kubernetes service that enables users to deploy, manage, and scale containerized applications.
To use this option, a Cloud Pub/Sub topic is created to receive notifications when a new image is pushed to GCR. A custom deployment service is then triggered in GKE to deploy the new image. This option provides more flexibility than Option A, as it can be used with different deployment tools, not just Spinnaker.
In summary, Option A and Option B are focused on using Spinnaker for deployment, while Option C and Option D are focused on using Jenkins and custom deployment services, respectively. The best option depends on the existing infrastructure and tools used by the team, as well as the desired level of flexibility and customization.
