GitOps for Istio - Manage Istio Config like Code
summary
Claim that Istio configuration is treated as code with Git as the single source of truth and an in-cluster operator enforcing desired state, using Terraform/Ansible/Kubernetes YAML stored in Git and reconciled by Weave Flux operator. Demo shows a canary flow where commits update virtualservice weights, the operator auto-commits image bumps (example v0.3.1) and routes partial traffic, and Prometheus metrics gate rollouts via Prometheus metrics gating so teams move from weekly deploys to 30–50 updates per day and recover clusters in minutes.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:31Example: Qordoba
- 10:12Structure of a GitOps repository
- 10:57Summary: 3 core principles of GitOps
- 12:15Summary: 3 benefits of GtOps
- 17:42Many sets of configuration across teams
- 24:58Config Workflows need automation
- 29:45Istio Canary Deployment: CD Overview
related talks
27mSecure Multicluster Istio Configuration Using GitOps...
47mGitOps - Using Git as your source of truth for build, deploy and observability
26mGitOps Lifecycle Management
35mGitOps - Operations by Pull Request
43mConfiguration as Data, GitOps and Multi Cluster The Key to Successful Servic
34mGitOps: Git Based Application Deployment Patterns for Kubernetes
45mGitops: The Kubernetes way
07mIntroduction to GitOps