Configuration Injection via Git
summary
Shows a concrete pattern to inject a Git-stored BOM into a Spinnaker pipeline and use it to drive deployments: fetch bom.yaml from Git via a configured Spinnaker artifact account, run a Kubernetes job using the spinnaker Run Job stage to call Clouddriver fetch via artifact account, emit JSON to pipeline output, then conditionally deploy services. Demo deploys nginx (image bumped to 1.17) while skipping postgres, passes the exact BOM/version on to production, and succeeds end-to-end.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 2:48GitOps style operations explained
- 7:52Spinnaker integration with Git
- 11:31Live demo setup
- 13:44Injecting config via run job
- 18:21Downstream deployment process
- 21:10Triggering and validating changes
- 26:07Recap and key takeaways
related talks
31mManaged Releases with Spinnaker
32mMaking Spinnaker Your Own
50mSpinnaker get control over your deployements
48mContinuous Delivery with Spinnaker
45mGetting Started with Spinnaker (part 1)
31mHow Spinnaker is Shaping Delivery Excellence at SAP
08mAutomated & Immutable Spinnaker Deployments with Security...
22mPractices for Applications Migration to Spinnaker