From Click To Chaos: Linking Argo Workflows and Backstage for Automate...
summary
Neo4j links Argo Workflows to Backstage scaffolder so a single portal click spawns reusable Argo workflow templates across more than 1,000 Kubernetes clusters; a lightweight Go microservice accepts a JSON payload, picks the target cluster from the Bolt URI and creates the workflow via the Argo SDK, while a custom TypeScript scaffolder action in Backstage sends the request and streams logs back to the UI. Implementation runs in isolated dev (“moon”) environments today, lets non‑Kubernetes engineers trigger chaos and integration tests, and is planned to expand into controlled production fire drills.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 1:47What Neo4j is and its use cases
- 3:11Chaos testing in dev
- 5:58Argo Workflows for chaos
- 8:44Microservice to trigger workflows
- 10:30Backstage chaos integration
- 12:37Backstage scaffolder
- 14:02Custom Backstage actions
- 15:26Future chaos plans
- 16:51Automated fire drills
related talks
27mLeveraging Argo Workflows To Move, Migrate and Manage All of Your Workflows
20mDemystifying Argo Workflows: An Architectural Deep Dive
22mLeveraging Argo WorkflowTemplates Within a Data Platform
52mCloud-Native Kubernetes Workflows on AKS with Argo
25mOne Engine To Rule Them All: Unifying Cloud Workloads With Argo Workflows
22mCross Cluster Execution of Argo Workflows
36mArgo Workflows: Intro, Update and Deep Dive
36mAutomating Cloud-native Spark Jobs with Argo Workflows