Deploying Spring Boot apps with Spinnaker.
summary
Hands-on demo deploys a Spring Boot petclinic built by Jenkins, packaged as an RPM-packaged Spring Boot service, uploaded to an S3 yum repo, then baked into AMIs via Rosco/Packer bake and deployed to AWS auto-scaling groups with blue/green and rollback support. Terraform provisions load balancers, Halyard stores Spinnaker config as code, and Kubernetes flow uses Docker/Helm on minikube. Deployment latency is about ten minutes; team deploys ~10 staging runs/day and one production run. Drawbacks: heavyweight (~8–12 GB), steep setup and troubleshooting.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:26Philosophy and constraints
- 3:55Why choose Spinnaker
- 7:24Deployment demo: VM based
- 15:15Advanced Spinnaker features
- 23:00Rollbacks and environment
- 27:18Spinnaker internals
- 33:13Kubernetes integration
- 38:27Best practices and summary
- 42:25Conclusion and Q&A
related talks
32mContinuous Software Delivery using Jenkins, Spinnaker and Terraform...
36mSpinnaker - Land of a 1000 Builds
48mContinuous Delivery with Spinnaker
52mContinuous Deployment to the Cloud using Spinnaker
31mContinuous Software Delivery Using Spinnaker and Jenkins in Cloud
30mSpinception: Deploying Spinnaker with Spinnaker
19mSpinnaker @ Upside: Getting Started, Establishing Culture & Deploying Microservices with Confidence
18mOvercoming the challenges of using Spinnaker as a multi-tenant CD service
