Spinnaker as a Platform: Driving Cloud Adoption in Healthcare
summary
Healthcare org moves from a Windows .NET monolith and slow change control to an automated delivery platform using Spinnaker, GitLab CI, Terraform and GKE; teams build a delivery engineering layer with Spinnaker pipeline templates and a developer portal that generates repos, CI and CD. They run GitLab CI → Docker registry → Spinnaker flows, automate DNS/certs/secrets, use GKE canary with Istio and Kayenta/Prometheus dashboards, track approvals into Jira, migrate a major .NET app in three months, and successfully Canary the payment API.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 7:19Platform engineering challenges
- 13:15What is Spinnaker
- 16:40Spinnaker deployment strategies
- 21:37Kubernetes migration journey
- 25:06Developer experience with Spinnaker
- 28:35Key takeaways and future vision
related talks
31mHow Spinnaker is Shaping Delivery Excellence at SAP
43mAll Aboard: Transforming Software Delivery Using Spinnaker
18mOvercoming the challenges of using Spinnaker as a multi-tenant CD service
19m5 Reasons Spinnaker Aligns to FinServ Business Initiatives
52mContinuous Deployment to the Cloud using Spinnaker
36mSpinnaker - Land of a 1000 Builds
48mContinuous Delivery with Spinnaker
50mSpinnaker get control over your deployements
