Practices for Applications Migration to Spinnaker
summary
Spinnaker becomes the central orchestrator that replaces or wraps legacy deploys: Jenkins job pass-through for SSH or artifactory-based VM installs, Kubernetes run job containers acting as bastions to execute scripted sequences, and migration patterns that either convert Jenkins→Spinnaker for cloud-native apps or pack UrbanCode/PL/ shell scripts into a single container stage. Secrets and roles map to Spinnaker accounts/namespaces. Canary analysis runs against Datadog/Prometheus metrics for single-VM rollouts. Several customers convert orchestration tools and gain visible, auditable pipelines.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:15Why Spinnaker?
- 2:41Migration Considerations
- 3:47Continuous Delivery
- 5:47Spinnaker Workflow
- 6:58Spinnaker Extension
- 8:43Jenkins Support
- 9:28Jenkins Pipeline Integration
- 10:49Common Pipeline Workflow
- 13:07UrbanCode Conversion
- 15:24Converted Pipeline
- 16:38Custom Stage Configuration
- 17:50Canary And Rollback
- 20:55Automated Reports
related talks
50mSpinnaker get control over your deployements
21mMigrate Legacy Deployment Orchestration to Spinnaker
19mSpinnaker @ Upside: Getting Started, Establishing Culture & Deploying Microservices with Confidence
31mHow Spinnaker is Shaping Delivery Excellence at SAP
25mEnabling Diverse Application Use Cases using Spinnaker
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
30mSpinception: Deploying Spinnaker with Spinnaker
53mContinuous Deployment with Spinnaker — Automate All Your Deployments!