Spinnaker 1.0: The continuous delivery platform for cloud used at Netflix and Waze
© Shutterstock / Rawpixel.com
It’s not a “buy one, get one for free” type of situation but with the release of Spinnaker 1.0, Google is also announcing the launch of a new CLI tool, halyard, that helps admins more easily install, configure and upgrade a production-ready instance of Spinnaker. What is Spinnaker and why should you care? Let’s find out.
Spinnaker, an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence has hit a new milestone: the release of 1.0.
Netflix open-sourced it in November 2015. “To create a truly extensible multi-cloud platform, the Spinnaker team partnered with Google, Microsoft and Pivotal to deliver out-of-the-box cluster management and deployment,” the company wrote in a blog post announcing the platform’s availability. “Spinnaker facilitates the creation of pipelines that represent a delivery process that can begin with the creation of some deployable asset (such as an machine image, Jar file, or Docker image) and end with a deployment.”
Spinnaker can be installed locally, on-prem, or in the cloud, running either on a virtual machine (VM) or Kubernetes, Google’s Christopher Sanson wrote in a blog post announcing Spinnaker 1.0. The platform streamlines the deployment process by decoupling your release pipeline from your target cloud provider, which can reduce the complexity of moving from one platform to another or deploying the same application to multiple clouds, he added.
Spinnaker has built-in support for Google Compute Engine, Google Container Engine, Google App Engine, AWS EC2, Microsoft Azure, Kubernetes, and OpenStack. Oracle Bare Metal and DC/OS are coming soon.
SEE ALSO: Netflix — “Moving to the cloud is hard”
Spinnaker in a nutshell
Spinnaker integrates seamlessly with your existing continuous integration (CI) workflows, Sanson wrote. You can trigger pipelines from git, Jenkins, Travis CI, Docker registries, on a cron-like schedule, or even other pipelines.
“Out-of-the-box, Spinnaker supports sophisticated deployment strategies like release canaries, multiple staging environments, red/black (a.k.a. blue/green) deployments, traffic splitting and easy rollbacks. This is enabled in part by Spinnaker’s use of immutable infrastructure in the cloud, where changes to your application trigger a redeployment of your entire server fleet. With Spinnaker, you simply choose the deployment strategy you want to use for each environment, e.g. red/black for staging, rolling red/black for production, and it orchestrates the dozens of steps necessary under-the-hood. You don’t have to write your own deployment tool or maintain a complex web of Jenkins scripts to have enterprise-grade rollouts.”
Spinnaker 1.0 comes bearing gifts
In addition to Spinnaker 1.0, the companies are also launching a new CLI tool, halyard, that helps admins more easily install, configure and upgrade a production-ready instance of Spinnaker. Previously, admins had to manage each of the microservices that make up Spinnaker individually but starting with 1.0, all new Spinnaker releases are individually versioned and follow semantic versioning. With halyard, upgrading to the latest Spinnaker release is as simple as running a CLI command.
If you want to find out how Spinnaker helps developers at Waze focus on developing business logic, rather than becoming experts on each cloud platform, check out this blog post.
For more info on this continuous delivery platform, visit the new Spinnaker website.