Continuous Delivery Pipelines with Spinnaker and Kubernetes Engine

“Continuous Delivery Pipelines with Spinnaker and Kubernetes Engine”

Pengantar

Lab praktis ini menunjukkan cara membuat pipeline continuous delivery menggunakan Google Kubernetes Engine, Google Cloud Source Repositories, Google Cloud Container Builder, dan Spinnaker. Setelah Anda membuat aplikasi sampel, Anda mengonfigurasi layanan ini untuk membangun, menguji, dan menerapkannya secara otomatis. Saat Anda mengubah kode aplikasi, perubahan tersebut memicu alur pengiriman berkelanjutan untuk secara otomatis membuat ulang, menguji ulang, dan menerapkan ulang versi baru.

Pipeline architecture

Application delivery pipeline

Praktikum

Task 1. Set up your environment

• Set the default compute zone:

gcloud config set compute/zone us-east1-d

• Create a Kubernetes Engine cluster using the Spinnaker tutorial sample application:

gcloud container clusters create spinnaker-tutorial \
    --machine-type=n1-standard-2

Configure identity and access management

• Create the service account:

gcloud iam service-accounts create spinnaker-account \
    --display-name spinnaker-account

• Store the service account email address and your current project ID in environment variables for use in later commands:

export SA_EMAIL=$(gcloud iam service-accounts list \
    --filter="displayName:spinnaker-account" \
    --format='value(email)')

export PROJECT=$(gcloud info --format='value(config.project)')

• Bind the storage.admin role to your service account:

gcloud projects add-iam-policy-binding $PROJECT \
    --role roles/storage.admin \
    --member serviceAccount:$SA_EMAIL

• Download the service account key. In a later step, you will install Spinnaker and upload this key to Kubernetes Engine:

gcloud iam service-accounts keys create spinnaker-sa.json \
     --iam-account $SA_EMAIL

Task 2. Set up Cloud Pub/Sub to trigger Spinnaker pipelines

• Create the Cloud Pub/Sub topic for notifications from Container Registry:

gcloud pubsub topics create projects/$PROJECT/topics/gcr

• Create a subscription that Spinnaker can read from to receive notifications of images being pushed:

gcloud pubsub subscriptions create gcr-triggers \
    --topic projects/${PROJECT}/topics/gcr

• Give Spinnaker’s service account permissions to read from the gcr-triggers subscription:

export SA_EMAIL=$(gcloud iam service-accounts list \
    --filter="displayName:spinnaker-account" \
    --format='value(email)')

gcloud beta pubsub subscriptions add-iam-policy-binding gcr-triggers \
    --role roles/pubsub.subscriber --member serviceAccount:$SA_EMAIL

Task 3. Deploying Spinnaker using Helm

Configure Helm

• Grant Helm the cluster-admin role in your cluster:

kubectl create clusterrolebinding user-admin-binding \
    --clusterrole=cluster-admin --user=$(gcloud config get-value account)

• Grant Spinnaker the cluster-admin role so it can deploy resources across all namespaces:

kubectl create clusterrolebinding --clusterrole=cluster-admin \
    --serviceaccount=default:default spinnaker-admin

• Add the stable charts deployments to Helm’s usable repositories (includes Spinnaker):

helm repo add stable https://charts.helm.sh/stable
helm repo update

Configure Spinnaker

• Still in Cloud Shell, create a bucket for Spinnaker to store its pipeline configuration:

export PROJECT=$(gcloud info \
    --format='value(config.project)')

export BUCKET=$PROJECT-spinnaker-config

gsutil mb -c regional -l us-east1 gs://$BUCKET

• Run the following command to create a spinnaker-config.yaml file, which describes how Helm should install Spinnaker:

export SA_JSON=$(cat spinnaker-sa.json)
export PROJECT=$(gcloud info --format='value(config.project)')
export BUCKET=$PROJECT-spinnaker-config
cat > spinnaker-config.yaml <<EOF
gcs:
  enabled: true
  bucket: $BUCKET
  project: $PROJECT
  jsonKey: '$SA_JSON'
dockerRegistries:
- name: gcr
  address: https://gcr.io
  username: _json_key
  password: '$SA_JSON'
  email: 1234@5678.com
# Disable minio as the default storage backend
minio:
  enabled: false
# Configure Spinnaker to enable GCP services
halyard:
  spinnakerVersion: 1.19.4
  image:
    repository: us-docker.pkg.dev/spinnaker-community/docker/halyard
    tag: 1.32.0
    pullSecrets: []
  additionalScripts:
    create: true
    data:
      enable_gcs_artifacts.sh: |-
        $HAL_COMMAND config artifact gcs account add gcs-$PROJECT --json-path /opt/gcs/key.json
        $HAL_COMMAND config artifact gcs enable
      enable_pubsub_triggers.sh: |-
        $HAL_COMMAND config pubsub google enable
        $HAL_COMMAND config pubsub google subscription add gcr-triggers \
          --subscription-name gcr-triggers \
          --json-path /opt/gcs/key.json \
          --project $PROJECT \
          --message-format GCR
EOF

Deploy the Spinnaker chart

• Use the Helm command-line interface to deploy the chart with your configuration set:

helm install -n default cd stable/spinnaker -f spinnaker-config.yaml \
           --version 2.0.0-rc9 --timeout 10m0s --wait

• After the command completes, run the following command to set up port forwarding to Spinnaker from Cloud Shell:

export DECK_POD=$(kubectl get pods --namespace default -l "cluster=spin-deck" \
    -o jsonpath="{.items[0].metadata.name}")

kubectl port-forward --namespace default $DECK_POD 8080:9000 >> /dev/null &

• To open the Spinnaker user interface, click the Web Preview icon at the top of the Cloud Shell window and select Preview on port 8080.

Task 4. Building the Docker image

Create your source code repository

• In Cloud Shell tab, download the sample application source code:

gsutil -m cp -r gs://spls/gsp114/sample-app.tar .

mkdir sample-app
tar xvf sample-app.tar -C ./sample-app

cd sample-app

git config --global user.email "$(gcloud config get-value core/account)"

git config --global user.name "[USERNAME]"

git init

git add .

git commit -m "Initial commit"

gcloud source repos create sample-app

git config credential.helper gcloud.sh

export PROJECT=$(gcloud info --format='value(config.project)')

git remote add origin https://source.developers.google.com/p/$PROJECT/r/sample-app

git push origin master

• Check that you can see your source code in the Console by clicking Navigation Menu > Source Repositories.
• Click sample-app.

Configure your build triggers

• In the Cloud Platform Console, click Navigation menu > Cloud Build > Triggers.
• Click Create trigger.
• Set the following trigger settings:

    Name: sample-app-tags

    Event: Push new tag

    Select your newly created sample-app repository.

    Tag: .*(any tag)

    Configuration: Cloud Build configuration file (yaml or json)

    Cloud Build configuration file location: /cloudbuild.yaml

• Click CREATE

Prepare your Kubernetes Manifests for use in Spinnaker

• Create the bucket:

export PROJECT=$(gcloud info --format='value(config.project)')

gsutil mb -l us-east1 gs://$PROJECT-kubernetes-manifests

• Enable versioning on the bucket so that you have a history of your manifests:

gsutil versioning set on gs://$PROJECT-kubernetes-manifests

• Set the correct project ID in your kubernetes deployment manifests:

sed -i s/PROJECT/$PROJECT/g k8s/deployments/*

• Commit the changes to the repository:

git commit -a -m "Set project ID"

Build your image

• In Cloud Shell, still in the sample-app directory, create a Git tag:

git tag v1.0.0

git push --tags

Task 5. Configuring your deployment pipelines

Install the spin CLI for managing Spinnaker

• Download the 1.14.0 version of spin:

curl -LO https://storage.googleapis.com/spinnaker-artifacts/spin/1.14.0/linux/amd64/spin

chmod +x spin

Create the deployment pipeline

• Use spin to create an app called sample in Spinnaker. Set the owner email address for the app in Spinnaker:

./spin application save --application-name sample \
                        --owner-email "$(gcloud config get-value core/account)" \
                        --cloud-providers kubernetes \
                        --gate-endpoint http://localhost:8080/gate

• From your sample-app source code directory, run the following command 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

Manually trigger and view your pipeline execution

• Switch to your browser tab displaying your Spinnaker UI.
• n the Spinnaker UI, click Applications at the top of the screen to see your list of managed applications.
• Click sample to view your application deployment.
• Click Pipelines at the top to view your applications pipeline status.
• Click Start Manual Execution, select Deploy in Select Pipeline, and then click Run to trigger the pipeline this first time.
• Click Execution Details to see more information about the pipeline’s progress.
• Click a stage to see details about it.
• Hover over the yellow “person” icon and click Continue.
• To view the app, at the top of the Spinnaker UI, select Infrastructure > Load Balancers.
• Scroll down the list of load balancers and click Default, under service sample-frontend-production. You will see details for your load balancer appear on the right side of the page. If you do not, you may need to refresh your browser.
• 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 may use HTTPS by default, while the application is configured to use HTTP.

• Paste the address into a new browser tab to view the application. You might see the canary version displayed, but if you refresh you will also see the production version.

Task 6. Triggering your pipeline from code changes

• From your sample-app directory, change the color of the app from orange to blue:

sed -i 's/orange/blue/g' cmd/gke-info/common-service.go

• 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

• In the Console, in Cloud Build > History, wait a couple of minutes for the new build to appear. You may need to refresh your page. Wait for the new build to complete, before going to the next step.
• Return to the Spinnaker UI and click Pipelines to watch the pipeline start to deploy the image. The automatically triggered pipeline will take a few minutes to appear. You may need to refresh your page.

Task 7. Observe the canary deployments

• When the deployment is paused, waiting to roll out to production, return to the web page displaying your running application and 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 fifth time you refresh.
• When the pipeline completes, your app looks like the following screenshot. Note that the color has changed to blue because of your code change, and that the Version field now reads canary.

• 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

• When the build and then the pipeline completes, verify the roll back by clicking Infrastructure > Load Balancers, then click the service sample-frontend-production Default and copy the Ingress IP address into a new tab.

Penutup

Sahabat Blog Learning & Doing demikianlah penjelasan mengenai Continuous Delivery Pipelines with Spinnaker and Kubernetes Engine. Semoga Bermanfaat . Sampai ketemu lagi di postingan berikut nya.