Continuous Delivery Pipelines with Spinnaker and Google Kubernetes Engine

This tutorial shows you how to create a continuous delivery pipeline using Google Kubernetes Engine (GKE), Cloud Source Repositories, Cloud Build, and Spinnaker for GCP. After you create a sample app, you configure these services to automatically build, test, and deploy it. When you modify the app code, the changes trigger the continuous delivery pipeline to automatically rebuild, retest, and redeploy the new version.

Pipeline architecture

The following diagram illustrates the architecture of the continuous delivery pipeline.

Architecture of pipeline for developers and users.

To continuously deliver app updates to your users, you need an automated process that reliably builds, tests, and updates your software. Code changes should automatically flow through a pipeline that includes artifact creation, unit testing, functional testing, and production rollout. In some cases, you want a code update to apply to only a subset of your users, so that it is exercised realistically before you push it to your entire user base. If one of these canary releases proves unsatisfactory, your automated procedure must be able to quickly roll back the software changes.

With GKE and Spinnaker, you can create a robust continuous delivery flow that helps to ensure your software is shipped as quickly as it is developed and validated. Although rapid iteration is your end goal, you must first ensure that each app revision passes through a series of automated validations before becoming a candidate for production rollout. When a given change has been vetted through automation, you can also validate the app manually and conduct further prerelease testing.

After your team decides the app is ready for production, one of your team members can approve it for production deployment.

App delivery pipeline

In this tutorial, you build the continuous delivery pipeline shown in the following diagram.

Architecture of the app delivery pipeline.

The high-level steps of this pipeline are as follows:

  1. A developer changes code and pushes it to a repository.

  2. Cloud Build detects the changes, builds the Docker image, tests the image, and pushes the image to Spinnaker.

  3. Spinnaker detects the image, deploys image to Canary, and tests the Canary deployment. After a manual approval, Spinnaker deploys the image to production.


  • Set up your environment by launching Cloud Shell and deploying Spinnaker for GCP.
  • Create a GKE cluster to deploy the sample application to.
  • Download a sample app, create a Git repository, and upload it to a Cloud Source Repositories.
  • Build your Docker image.
  • Create triggers to create Docker images when your app changes.
  • Configure a Spinnaker pipeline to reliably and continuously deploy your app to GKE.
  • Deploy a code change, triggering the pipeline, and watch it roll out to production.


This tutorial uses billable components of Google Cloud Platform (GCP), including:

  • GKE
  • Cloud Load Balancing
  • Cloud Build
  • Cloud Source Repositories
  • Container Registry

Use the Pricing Calculator to generate a cost estimate based on your projected usage.

New GCP users might be eligible for a free trial.

Before you begin

  1. Sign in to your Google Account.

    If you don't already have one, sign up for a new account.

  2. Select or create a GCP project.

    Go to the project selector page

  3. Verifica che la fatturazione sia attivata per il tuo progetto.

    scopri come attivare la fatturazione

  4. Enable the GKE, Cloud Build, and Cloud Source Repositories APIs.

    Enable the APIs

Set up your environment

In this section, you configure the infrastructure required to complete the tutorial.

Deploy Spinnaker for GCP using Cloud Shell

Run all the terminal commands in this tutorial from Cloud Shell.

With Spinnaker for GCP, you can set up and manage Spinnaker in a production-ready configuration, optimized for GCP. Spinnaker for GCP sets up resources (GKE, Cloud Memorystore, Cloud Storage buckets and service accounts), integrates Spinnaker with related services such as Cloud Build, and provides a Cloud Shell-based management environment for your Spinnaker installations, with helpers and common tools such as spin and hal.

  1. Open Spinnaker for GCP in Cloud Shell. This clones the Spinnaker for GCP repository into your Cloud Shell environment and launches the detailed installation instructions.


  2. Install Spinnaker for GCP.

    PROJECT_ID=${DEVSHELL_PROJECT_ID} ~/spinnaker-for-gcp/scripts/install/
  1. Restart Cloud Shell to load new environment settings.

    Cloud Shell restart menu option.

  2. Connect to Spinnaker.

  3. In Cloud Shell, click the Web Preview icon and select Preview on port 8080.

    Cloud Shell Restart Option in Menu

Create a GKE for application deployments

A common pattern is to have a GKE cluster used for builds, deployments, and so on, and then other GKE clusters for running applications. In this section you create another GKE cluster, app-cluster, to deploy the sample application to.

  1. In Cloud Shell, create a new GKE cluster:

    gcloud config set compute/zone $REGION
    gcloud container clusters create app-cluster \
  2. Add the new GKE cluster to Spinnaker. The default values should be correct.


    Example output and values:

    Please enter the context you wish to use to manage your GKE resources: gke_spinnaker-246920_us-west1-b_app-cluster
    Please enter the id of the project within which the referenced cluster lives: spinnaker-246920
    Please enter a name for the new Spinnaker account: app-cluster-acct

  3. Change the kubernetes context back to your Spinnaker cluster:

    kubectl config use-context gke_${DEVSHELL_PROJECT_ID}_${REGION}_spinnaker-1
  4. Push and apply the configuration changes to Spinnaker:


Building the Docker image

In this section, you configure Cloud Build to detect changes to your app source code, build a Docker image, and then push it to Container Registry.

Create your source code repository

  1. In Cloud Shell, download the sample source code:

    cd ~
  2. Unpack the source code:

    tar xzfv sample-app-v2.tgz
  3. Change directories to the source code:

    cd sample-app
  4. Set the username and email address for your Git commits in this repository. Replace [EMAIL_ADDRESS] with your Git email address, and replace [USERNAME] with your Git username.

    git config --global "[EMAIL_ADDRESS]"
    git config --global "[USERNAME]"
  5. Make the initial commit to your source code repository:

    git init
    git add .
    git commit -m "Initial commit"
  6. Create a repository to host your code:

    gcloud source repos create sample-app
    git config credential.helper
  7. Add your newly created repository as remote:

    export PROJECT=$(gcloud info --format='value(config.project)')
    git remote add origin$PROJECT/r/sample-app
  8. Push your code to the new repository's master branch:

    git push origin master
  9. Check that you can see your source code in the console:


Configure your build triggers

The following diagram illustrates the trigger that you build in this section.

Spinnaker workflow

You configure Cloud Build to build and push your Docker images every time you push Git tags to your source repository. Cloud Build automatically checks out your source code, builds the Docker image from the Dockerfile in your repository, and pushes that image to Container Registry.

  1. In the GCP Console, in the Cloud Build section, click Build Triggers.


  2. Select Cloud Source Repository and click Continue.

  3. Select your newly created sample-app repository from the list, and click Continue.

  4. Set the following trigger settings:

    • Name: sample-app-tags
    • Trigger type: Tag
    • Tag (regex): v.*
    • Build configuration: cloudbuild.yaml
    • cloudbuild.yaml location: cloudbuild.yaml
  5. Click Create trigger.

    Trigger settings when you create a trigger.

From now on, whenever you push a Git tag prefixed with the letter "v" to your source code repository, Cloud Build automatically builds and pushes your app as a Docker image to Container Registry.

Prepare your Kubernetes Manifests for use in Spinnaker

Spinnaker needs access to your Kubernetes manifests in order to deploy them to your clusters. This section creates a Cloud Storage bucket that will be populated with your manifests during the CI process in Cloud Build. After your manifests are in Cloud Storage, Spinnaker can download and apply them during your pipeline's execution.

  1. Create the bucket.

    export PROJECT=$(gcloud info --format='value(config.project)')
    gsutil mb gs://$PROJECT-kubernetes-manifests
  2. Enable versioning on the bucket so that you have a history of your manifests.

    gsutil versioning set on gs://$PROJECT-kubernetes-manifests
  3. Set the correct GCP project ID in your Kubernetes deployment manifests:

    sed -i s/PROJECT/$PROJECT/g k8s/deployments/*
  4. Commit the changes to the repository:

    git commit -a -m "Set project ID"

Configuring your deployment pipelines

Now that your images are building automatically, you need to deploy them to the Kubernetes cluster.

The following diagram illustrates the deployment pipeline steps.

Configure deployment pipeline.

You deploy to a scaled-down environment for integration testing. After the integration tests pass, you must manually approve the changes to deploy the code to production services.

Create the deployment pipeline

  1. Use spin to create an app in Spinnaker.

    spin application save --application-name sample \
                          --owner-email \
                          --cloud-providers kubernetes \
                          --gate-endpoint http://localhost:8080/gate

Next, you create the continuous delivery pipeline. In this tutorial, the pipeline is configured to detect when a Docker image with a tag prefixed with "v" has arrived in your Container Registry.

  1. In a new tab of Cloud Shell, run the following command in the source code directory to upload an example pipeline to your Spinnaker instance:

    export PROJECT=$(gcloud info --format='value(config.project)')
    sed s/PROJECT/$PROJECT/g spinnaker/pipeline-deploy.json > pipeline.json
    spin pipeline save --gate-endpoint http://localhost:8080/gate -f pipeline.json

Build your image

Push your first image using the following steps:

  1. Go to your source code folder in Cloud Shell.
  2. Create a Git tag:

    git tag v1.0.0
  3. Push the tag:

    git push --tags
  4. In Cloud Build, click Build History to check that the build has been triggered. If not, verify the trigger was configured properly in the previous section.


    build history

View your pipeline execution

The configuration you just created uses notifications of newly tagged images being pushed to trigger a Spinnaker pipeline. In a previous step, you pushed a tag to the Cloud Source Repositories which triggered Cloud Build to build and push your image to Container Registry. You can now check on the pipeline that was triggered.

  1. Return to the Pipelines page by clicking Pipelines.

  2. Click Details to see more information about the pipeline's progress. This section shows the status of the deployment pipeline and its steps. Steps in blue are currently running, green ones have completed successfully, and red ones have failed. Click a stage to see details about it.

    After 3 to 5 minutes the integration test phase completes and the pipeline requires manual approval to continue the deployment.

  3. Hold the pointer over Push to production, and then click Continue.

    Your rollout continues to the production frontend and backend deployments. It completes after a few minutes.

  4. To view the app, select Infrastructure > Load Balancers in the top of the Spinnaker UI.

    Infrastructure drop-down list with Load Balancers selected.

  5. Scroll down the list of load balancers and click Default, under sample-frontend-production.

    Default load balancer.

  6. Scroll down the details pane on the right and copy your app's IP address by clicking the clipboard button on the Ingress IP. The ingress IP link from the Spinnaker UI uses HTTPS by default, but the application is configured to use HTTP.

    Details pane with your app's IP address.

  7. Paste the address into your browser to view the production version of the app.

    Production version of the app.

    You have now manually triggered the pipeline to build, test, and deploy your app.

Triggering your pipeline from code changes

In this section, you test the pipeline end to end by making a code change, pushing a Git tag, and watching the pipeline run in response. By pushing a Git tag that starts with "v", you trigger Cloud Build to build a new Docker image and push it to Container Registry. Spinnaker detects that the new image tag begins with "v" and triggers a pipeline to deploy the image to canaries, run tests, and roll out the same image to all pods in the deployment.

  1. Change the color of the app from orange to blue:

    cd ~/sample-app
    sed -i 's/orange/blue/g' cmd/gke-info/common-service.go
  2. Tag your change and push it to the source code repository:

    git commit -a -m "Change color to blue"
    git tag v1.0.1
    git push --tags
  3. See the new build appear in the Cloud Build Build History.

  4. Click Pipelines to watch the pipeline start to deploy the image.

  5. Observe the canary deployments. When the deployment is paused, waiting to roll out to production, start refreshing the tab that contains your app. Four of your backends are running the previous version of your app, while only one backend is running the canary. You should see the new, blue version of your app appear about every tenth time you refresh.

  6. After testing completes, return to the Spinnaker tab and approve the deployment.

  7. When the pipeline completes, your app looks like the following screenshot. The Version field now reads v1.0.1.

    Production version of the updated app.

    You have now successfully rolled out your app to your entire production environment!

  8. Optionally, you can roll back this change by reverting your previous commit. Rolling back adds a new tag (v1.0.2), and pushes the tag back through the same pipeline you used to deploy v1.0.1:

    git revert v1.0.1
    git tag v1.0.2
    git push --tags

Cleaning up

To avoid incurring charges to your Google Cloud Platform account for the resources used in this tutorial:

1. Delete Spinnaker for GCP:

<pre class="lang-sh devsite-click-to-copy">
cd ~
  1. Delete the GKE cluster:

    gcloud container clusters delete app-cluster --zone=us-west1-b
  2. Delete the repository:

    gcloud source repos delete sample-app
  3. Delete the bucket:

    export PROJECT=$(gcloud info --format='value(config.project)')
    export BUCKET=$PROJECT-spinnaker-config
    gsutil -m rm -r gs://$BUCKET
  4. Delete your container images:

    export PROJECT=$(gcloud info --format='value(config.project)')
    gcloud container images delete$PROJECT/sample-app:v1.0.0
    gcloud container images delete$PROJECT/sample-app:v1.0.1
  5. If you created v1.0.2 in the optional rollback step above, delete that container image:

    gcloud container images delete$PROJECT/sample-app:v1.0.2

What's next

Hai trovato utile questa pagina? Facci sapere cosa ne pensi:

Invia feedback per...