Spinnaker: The Best Way to Deploy to Kubernetes
Sep 24, 2019 by Stu Posluns
Many companies making the move to containers and implementing Kubernetes for container orchestration come to the realization that, while Kubernetes is powerful and does a lot out-of-the-box, it doesn’t do everything. Without either outside tooling or custom scripts, they can’t automate the deployment process and move to a mature continuous deployment model.
We’re a bit biased, but we think the best way to solve this dilemma is by using Spinnaker to deploy to Kubernetes. In fact, we wrote an ebook about why Spinnaker is the best way to manage deployments to Kubernetes. Here’s a summary.
Spinnaker Makes Business Sense
Companies use Kubernetes because:
- They don’t want to get locked in to a proprietary container orchestration solution
- They don’t want to spend the resources to build their own orchestration platform
- They don’t get any competitive advantage from having their own, proprietary orchestration solution
- They want the best container orchestration platform available.
If you use the same logic to decide on a continuous delivery tool, you’ll land on Spinnaker. Like Kubernetes, it’s open source, helps facilitate a multicloud strategy, and is much less complicated than building your own tool. Most companies won’t get any competitive advantage from reinventing the wheel and building their own continuous delivery solution, and are better off focusing their engineering resources on projects that build value for the company.
Most importantly, Spinnaker is the best tool available for managing continuous delivery. Using Spinnaker is the rational choice for most companies that use Kubernetes.
Tight Technical Integration
Spinnaker and Kubernetes are both open source projects, but many of the core contributors work at the same companies—Google and Netflix. The two projects have a tight, fully-mature integration from a technical perspective, with Spinnaker giving you an easy way to manage resource mapping, manifest versioning, and templating for Kubernetes in a way that isn’t possible with Kubernetes alone.
Using Spinnaker and Kubernetes together lets you take full advantage of what both technologies have to offer. Spinnaker makes Kubernetes easier to adopt and easier to manage in an enterprise setting by providing the advanced deployment capabilities and easy rollbacks needed to ensure errors don’t make it into production.. and if they do, recovery is easy and fast.
Want to learn more about why Spinnaker is the best way to deploy to Kubernetes? Read the ebook.
Want to learn more about how Armory can help you get Spinnaker up-and-running faster, and provide the support enterprises rely on? Schedule a demo today.
Recently Published Posts
A day in the life of a TAM
I’ve been asked what a Technical Account Manager (TAM) does so I wanted to take the opportunity to illustrate it by walking through a standard day in the life. Before we can look at what a day in a life of a TAM is, I should provide some background in what is a TAM and […]
Read more →
Nikema’s Spinnaker Summit 2021 Recap
My Second Spinnaker Summit is in the Books! Last week I attended and spoke at my second Spinnaker Summit. Like last year’s summit, it was fully virtual. This time Spinnaker Summit was co-located with cdCon and took place on the Hopin platform. Last year, I spoke on a panel about Black professionals a few months […]
Read more →
Announcing General Availability of Armory Policy Engine Plugin
Armory Policy Engine provides support for automating policy compliance with Spinnaker. Policy Engine Plugin is the latest version of Policy Engine and adds support for both advanced role-based access control (RBAC) use-cases and open source Spinnaker. The release of Policy Engine Plugin comes with new documentation, including a library of example policies from across Armory’s […]
Read more →