Break the silo: How we built a decentralized control plane for service orchestration
summary
Julius Baer builds a decentralized control plane that exposes a single public API (composite CRs) on a Crossplane + Kubernetes commander which delegates work to independent unit clusters via the Kubernetes provider. Teams author compositions in Go, store manifests in Git and use GitOps via Flux; units run their own Crossplane/providers and own lifecycle. The system runs in production, solves a unified service catalog but creates real challenges in onboarding, version skew and cross-unit data contracts. commander delegates to unit clusters
AI-written summary · about
chapters (9)
- 0:00Decentralized control plane intro
- 3:03Traditional portal problems
- 6:33Platform orchestration intro
- 10:49Fleet Commander internals
- 13:38Kubernetes operators basics
- 17:56Fleet Commander for teams
- 21:47Fleet Commander workflow
- 25:19Decentralized orchestration challenges
- 30:45Q&A
related talks
41mBreak the silo: How we built a decentralized control plane for service orchestration
37mPlatformOps with Crossplane
36mCrossplane Intro And Deep Dive - The Cloud Native Control Plane Framework
31mLearnings From Providing A Platform API With Kubernetes And Crossplane
27mKubernetes as a Universal Infrastructure Control Plane
31mCrossplane Intro and Deep Dive - The Cloud Native Control Plane Framework
24mBeyond Infra/Service Provision: The Crossplane Essentials and Adoption
31mThe Crossplane Experience