Workshop: Extending Spinnaker via Custom Jobs
summary
Explains extending Spinnaker by running Kubernetes jobs via the built-in run job stage to run a Maven container, write artifacts to a shared NFS workspace, build and push images with kaniko to Docker Hub using the commit SHA as the image tag, and expose values with spinnaker_property_commitId for downstream stages. Notes converting the flow into a registered custom stage requires editing Orca local and restarting, and warns to handle job cleanup and Kubernetes secrets for registry or Git credentials.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:47Use cases where this is useful
- 26:51Passing values for downstream processing
- 32:19Custom Job Stage
- 39:26Other considerations
related talks
32mMaking Spinnaker Your Own
01h 54mFirst-time Spinnaker Contributors Workshop
22mPractices for Applications Migration to Spinnaker
50mSpinnaker get control over your deployements
17mIntroduction to Spinnaker on Kubernetes
24mUsing Jenkins and Spinnaker to Supercharge Your Deployment Pipelines
43mSpinnaker Plugins: Extending...
45mGetting Started with Spinnaker (part 1)