Continuous Delivery Pipelines with Spinnaker and Kubernetes Engine
Quest: Deploy and Manage Cloud Environments with Google Cloud
Objectives
Set up your environment by launching Google Cloud Shell, creating a Kubernetes Engine cluster, and configuring your identity and user management scheme.
Download a sample application, create a Git repository then upload it to a Google Cloud Source Repository.
Deploy Spinnaker to Kubernetes Engine using Helm.
Build your Docker image.
Create triggers to create Docker images when your application changes.
Configure a Spinnaker pipeline to reliably and continuously deploy your application to Kubernetes Engine.
Deploy a code change, triggering the pipeline, and watch it roll out to production.
Pipeline architecture
To continuously deliver application 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.
My LinkedIn: / jeet-patel-b7a90316a