Building the Next Gen GitOps-based Platform
summary
A platform built around ConfigHub SaaS centralizes configuration as a queryable data store, not text, and proves it by preventing a real Grafana ConfigMap bug that broke 30 instances across 6 environments caused by a stray space. It validates and mutates YAML before cluster apply, exposes a CLI/UI and SDK, and syncs to clusters via a Flux Bridge using Flux 2.7 external artifacts CRD. Each running component maps to a one-to-one config unit with live-state refresh and local PVC-backed durability.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:44Configuration hell journey
- 5:20Config sprawl and risks
- 7:08Configuration as data
- 13:11Config Hub demo
- 18:27Flux and Flux Bridge
- 23:08Key benefits and takeaways
- 24:57Resources and getting started
- 25:21Q&A
related talks
29mThe Evolution of GitOps in Platform Engineering
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
28mManaging GitOps as a Platform Service
42mHow to build, deploys and maintains a globally distributed modern platform
24mHosting Applications in the Real World
35mPanel: GitOps User Stories
38mEnd User Panel: GITOPS in the Enterprise -Real World Experiences