Proposal: A new ‘Deploy Kubernetes Resources’ stage in Spinnaker pipelines
We’d like to get feedback from Kubernetes users interested in using Spinnaker in more sophisticated ways. Here’s a quick video outlining a problem we’re hearing from Kubernetes users, and proposed solution below:
The problem: Today, you can use Spinnaker to deploy images. However, other resource types (secrets, config maps, persistent volumes, etc.) are not natively supported within Spinnaker. This means that Kubernetes users accustomed to using kubectl find Spinnaker pipelines limiting because other resources have to be provisioned outside of Spinnaker.
Kuberentes has manifest files (which usually live in source control). How can Spinnaker use pipeline orchestration to deploy Kubernetes entities from Spinnaker pipelines?
Our Proposed Solution: We’ve mocked up a new “Deploy Kubernetes Resource” stage within Spinnaker to create a generic way to deploy more Kubernetes entities, which we show in the video above. Specifically:
- New drop-down “stage” in Spinnaker pipelines called “Deploy Kubernetes Resources”
- Ingests a Manifest from source control with filepath to repository
- Allows for variable substitutions
- Uses Spinnaker’s expression language to fill in variables from the Kubernetes Manifest yaml.
Before we actually create this stage, we’d like to find a few customers that want to test it. Please contact us below or email [email protected] if you’re interested.
Here are a few screenshots of Andrew’s “Deploy Kubernetes Resource” Stage mockup from the video: