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.
Companies use Kubernetes because:
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.
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.
Introducing Quick Spin One of the most common challenges that organizations face when implementing a continuous deployment strategy is the time and focus that it takes to set up the tools and processes. But a secure, flexible, resilient and scalable solution is available right now. Want to see if it’s the right tool for your […]
Read more →
Spinnaker is the most powerful continuous delivery tool on the market. DevOps engineers and developers recognize this power and are looking to use Spinnaker as a foundational tool in their Continuous Integration and Continuous Delivery (CI/CD) process for hybrid and multi-cloud deployments. Such a powerful, expansive open source tool needs expertise within your organization to […]
Read more →
Today, Armory is excited to announce the availability of the GitHub Action for Armory Continuous Deployment-as-a-Service. GitHub is where developers shape the future of software. After a developer writes and tests their code in GitHub, it must be deployed. Armory’s GitHub Action for Continuous Deployment-as-a-Service extends the best-in-class deployment capabilities to Kubernetes. CD-as-a-Service enables declarative […]
Read more →