-
Book Overview & Buying
-
Table Of Contents
The Platform Engineer's Handbook
By :
Figure 8.1 illustrates the layered architecture of CI/CD as a platform service. The platform team owns the reusable building blocks at the bottom, which compose into templates in the middle layer. Development teams consume templates provided by the platform team, and the resulting artifacts are delivered via GitOps to the platform runtime.
This diagram shows the three-layer ownership model for CI/CD as a platform service. The platform team maintains reusable tasks (build, scan, test) that feed into pipeline templates (backend, frontend, ML) in the middle layer. Stream-aligned teams (A, B, C) consume these templates, and all artifacts flow through policy gates and GitOps delivery via Flux CD and Argo Rollouts to the Kubernetes cluster with its observability stack. The key takeaway here is the clear separation: the platform team owns the building blocks, teams own their pipeline configurations, and GitOps owns the delivery path.

Figure 8.1 - CI/CD...