Demystifying Spinnaker VM Image Baking and Deployment
summary
Rosco microservice bakes VM images from Packer templates using builders (e.g., GCE, AWS) and provisioners (shell, Ansible), produces AMIs/snapshots, and can share images across accounts; Rosco caches base images (watch the 1,000-image cache limit) and will kill concurrent bakes that use the same base. Large or custom templates require Packer templates loaded via sidecar or image build container preload, use cloud‑config/user‑data for init, inspect Packer logs in the Rosco pod /tmp, and do not bake secrets.
AI-written summary · about
chapters (11)
- 0:00Introduction to VM baking
- 1:20Spinnaker and image baking
- 3:21Packer core components
- 5:54CI/CD pipeline integration
- 7:15Baking tips and best practices
- 10:09Handling multi-cloud environments
- 13:28Customizing Packer templates
- 16:58Deployment and configuration
- 21:21Advanced baking best practices
- 24:13Troubleshooting deployments
- 27:29Future contributions and Q&A
related talks
22mImage-Builder Deep Dive
49mBuild, provision & deploy in the Cloud with Packer, Ansible & Terraform
16mDelivering Golden AMIs with Spinnaker
48mDeploying Spring Boot apps with Spinnaker.
43mImmutable AWS Deployments with Packer and Jenkins
16mImplementing Custom Job Stages into Spinnaker with K8s
33mPacker: A Swiss Army Knife for Architectural Enablement
21mAutomate Customizing VM Images with Image Builder
