Supercharge Backstage: Self-Service GitOps Staging Environments wi...
summary
Self-service platform glues Backstage to GitOps: a developer clicks (or pushes a branch) and a vCluster + FluxCD pipeline creates an isolated, production-like namespace in under two minutes versus ~45 minutes for an EKS Terraform flow. Implementation uses FluxCD, copier templating, kubevela and Carpenter autoscaling; deletion happens automatically when branches close (helm hooks and cleanup logic handle lingering LB/RDS). Proven at ~100+ host clusters and teams reporting up to ~2,000 ephemeral vClusters on one host, with clear developer productivity and cost reduction.
AI-written summary · about
chapters (10)
- 0:00Self-service GitOps staging
- 3:12Shared env pain points
- 6:45Dynamic staging solution
- 8:09Tool stack & architecture
- 13:45Live demo: env creation
- 21:23Real-world impact & benefits
- 23:50Challenges & solutions
- 24:33Platform design lessons
- 25:37Key takeaways
- 27:29Q&A
related talks
22mStreamlining Cloud-Native Development with OpenShift and Backstage
35mBackstage: Restoring Order To Your Chaos
14mFrom the Ranch(er) to the Dev: A Case Study About Simplifying K8s Cluster Setup Wit...
27mIntroduction to Backstage
28mBuilding Open Developer Platforms with Backstage
15mGitOps in the Real World: Opportunities for Developer Experience Improvement
31mWhen GitOps Meets UX
31mImplementing Preview Environments with GitOps in Kubernetes