Playstation's Code Deployment to Kubernetes Flow with Spinnaker, Helm & AWS
summary
PlayStation runs a CI/CD flow from GitHub commits to AWS EKS: GitHub webhooks kick Jenkins pipelines that build and push uniquely tagged Docker images to ECR, ECR triggers start Spinnaker pipelines, Spinnaker uses Helm 3 bake manifest to render charts with environment-specific values, pauses for manual judgment before applying, and deploys to targeted EKS clusters. Key actionable tip: leave the chart’s image tag empty so Spinnaker injects the triggered tag at bake time.
AI-written summary · about
chapters (13)
- 0:00Introduction to talk
- 0:44Challenges in Kubernetes deployment
- 2:10Flow overview from code to deploy
- 3:36GitHub webhook and Jenkins CI
- 5:25Docker image push to registry
- 6:30Spinnaker pipeline configuration
- 7:35Bake manifest with Helm 3
- 9:23Override values per environment
- 10:05Manual judgment in pipeline
- 11:09Deploy manifest to Kubernetes
- 12:37Handling unique image tags in Helm
- 14:24Full pipeline walkthrough
- 16:51Summary and Q&A
related talks
01h 04mOpening Keynote [Full]
50mSpinnaker get control over your deployements
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
29mGetting Started with the Spinnaker Operator and Amazon EKS
52mContinuous Deployment to the Cloud using Spinnaker
45mGetting Started with Spinnaker (part 1)
30mSpinception: Deploying Spinnaker with Spinnaker
48mContinuous Delivery with Spinnaker