Member-only story
Building a CI/CD System for Private GKE Clusters with Google Cloud Deploy

Originally published on priyathgregory.dev.
A robust Continuous Integration and Continuous Delivery (CICD) pipeline plays a crucial role in any development ecosystem, introducing dependability, efficiency, and adaptability to your integration and delivery workflows.
As part of our company’s ongoing re-architectural efforts, we recently engineered a CICD pipeline tailored to seamlessly support the deployment of Google Kubernetes Engine (GKE) workloads. The system was designed with the following criteria in mind:
- Separate build and deployment steps
- A single control point to manage the release lifecycle
- Support workload deployment into private GKE clusters across different GCP projects. (eg: staging & production)
- Environment promotion and rollback support for releases.
- Observability
A high-level visualisation of the final architecture is shown below

The Build Step