Want to extend GitOps to Infrastructure and Workloads? Here's how.
summary
Most teams keep Kubernetes GitOps in Argo/Flux while infrastructure and serverless remain in brittle CI pipelines; PipeCD claims to close that gap by treating Terraform, GCP Cloud Run, AWS ECS and Azure Functions as first‑class targets. It runs a piped stateless agent in each environment, reports to a control plane dashboard, and encodes pipelines like 10% canary then approval or a Terraform plan → apply flow. V1 adds plugin binaries (OpenTofu and community plugins exist) and basic drift, rollbacks, and progressive delivery.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:23What is GitOps
- 3:31Why GitOps emerged
- 5:57Gap in GitOps tools
- 7:41Extending GitOps beyond Kubernetes
- 8:24PipeCD for multi-platform GitOps
- 10:29PipeCD architecture
- 12:56PipeCD plugins and future
- 14:21Call to action
- 15:24Closing remarks & Q&A
related talks
05mProject Lightning Talk: GitOps Without Boundaries: Deploy to Infrastructur...
17mUsing GitOps for Both Infrastructure and Applications
26mGitOps Lifecycle Management
06mGitOps - At a Glance
48mThe State of GitOps in 2021
30mOur Journey in Integrating GitOps Tools Into Delivery Pipelines
40mHow GitOps Changes Everything in CI/CD
33mGitOps Pipelines: Everything Everywhere All at Once