After attending Kubecon last week, I came away with a few thoughts on how the Spinnaker community might engage the Kubernetes community to drive adoption. I’m interested in hearing other’s thoughts on this.
One of the biggest themes I saw over and over again was around CD and how to effectively deliver Kubernetes application to production. I kept saying in my head “just use Spinnaker”, but it was obvious that it wasn’t a widely known solution. I had the chance to attend a sig-apps meeting where multiple people asked things like “what’s the best way to deploy” and “how can I run database migrations as part of my deployment pipeline”. All of these are problems that Spinnaker is positioned to solve, but the knowledge isn’t out there.
Some potential things we could do as a community to drive adoption might be:
-
attend
sig-appsmeetings and have a presence in some part of the community. Spinnaker, while being multi-cloud, is still a great application within the Kubernetes ecosystem and I think it would be great to spread the word. For me, I think I will start attending these meetings to see a) there the community is headed and b) what the community wants out a tool in this space. -
More documentation around what it means to deploy to Kubernetes with Spinnaker. This could come in the form of blog posts, videos, code labs. Spinnaker solves the CD problem in a unique way, but I think a big hurdle is just knowing how to use it to achieve the goal.
If anyone has anymore thoughts about what we could do to engage the Kubernetes community, lets hear them!