Air France–KLM’s GitOps Takeoff: Real Stories From the Flig...
summary
Air France–KLM replaces gated centralized ops with a GitOps foundation that bootstraps Flux CD into clusters, uses pipelines to keep standardization, and applies infra changes with Terraform. The biggest barrier is cultural trust, not tech; the team proves value by rolling GitOps into a new implementation, connecting an ops repo to add-on teams so Security/Network/Observability own their configs while preserving ITIL auditability and compliance, dramatically reducing cross-team release overhead.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:06GitOps challenges in airline
- 3:18Kubernetes platform evolution
- 4:44Pipeline standardization & compliance
- 6:08Config updates before Flux CD
- 7:13Flux CD simplified config
- 8:41Old vs new GitOps workflows
- 9:25Building trust for GitOps
- 10:50Flux CD setup details
- 11:37Future GitOps plans
related talks
35mPanel: GitOps User Stories
26mGitOps Lifecycle Management
30mDevOps: Supporting aircraft from hanger to take-off
27mFrom “No Time For GitOps” To Enterprise Adoption: Selling Flux The Human Way
26mKeynote Session: GitOps as an Evolution of Kubernetes
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
29mWe Have Always Done It This Way! Now Let’s Try Something Completely Different
06mFrom Policy to Production: Flux and GitOps as Governance Control...