// the find
kelseyhightower/pipeline
A step by step guide on creating build and deployment pipelines for Kubernetes.
A step-by-step tutorial from Kelseyhightower showing how to wire up a multi-environment Kubernetes deployment pipeline using Google Cloud Container Builder and GitHub repos as environment manifests. Aimed at teams moving from ad-hoc kubectl applies to something reproducible across dev/staging/prod clusters. Pure documentation — no code, just markdown labs.
The multi-repo-per-environment model is a legitimate pattern for access control isolation — separating manifest repos means your CI service account for staging can't touch production. Kelseyhightower's tutorials are usually precise and avoid hand-waving the hard parts. The separation of application repo from manifest repos is a clean GitOps foundation that predates Flux/ArgoCD going mainstream.
Abandoned in 2019 and it shows: Cloud Container Builder is now Cloud Build, the API and trigger config have changed substantially, and the hub CLI tooling referenced is likely broken or deprecated. There's zero code to run — it's entirely prose and screenshots, so if any step is stale you're debugging Google docs instead of actual failures. No mention of secrets management, which is where every real pipeline actually bites you. If you're starting a GitOps pipeline today, Flux or ArgoCD with a maintained tutorial will get you further faster.