Comparing Spinnaker and Kubernetes in this way is somewhat unfair to both projects. The scale, scope, and magnitude of these technologies are different, but parallels can still be drawn.<\/p>\n
Just like Kubernetes, Spinnaker<\/a> is a technology that is battle tested, with Netflix using Spinnaker internally for continuous delivery. Like Kubernetes, Spinnaker is backed by some of the biggest names in the industry, which helps breed confidence among users. Most importantly, though, both projects are open source, designed to build a diverse and inclusive ecosystem around them.<\/p>\n Continuous Delivery (CD) is a solved problem, but it has been a bit of a Frankenstein\u2019s monster, with companies trying to build their own creations by stitching parts together, along with Jenkins. \u201cWe tried to build a lot of custom continuous delivery tooling, but they all fell short of our expectation,\u201d said Brandon Leach, Sr. Manager of Platform Engineering at Lookout.<\/p>\n \u201cWe were using Jenkins along with tools like Rundeck, but both had their own set of problems. While Rundeck didn\u2019t have a first-class deployment tool, Jenkins was becoming a nightmare and we ended up moving to Gitlabs,\u201d said Gard Voigt Rimestad of Schibsted<\/a>, a major Norwegian media group.<\/p>\n Netflix created a more elegant way for continuous delivery called Asgard, open sourced in 2012, which was designed to run Netflix\u2019s own workload on AWS. Many companies were using Asgard, including Schibsted, and it was gaining momentum. But it was tied closely to the kind of workload Netflix was running with AWS. Bigger companies who liked Asgard forked it to run their own workloads. IBM forked it twice to make it work with Docker containers.<\/p>\n IBM\u2019s forking of Asgard was an eye-opening experience for Netflix. At that point, Netflix had started looking into containerized workloads, and IBM showed how it could be done with Asgard.<\/p>\n Google was also planning to fork Asgard to make it work on Google Compute Engine. By that time, Netflix had started working on the successor to Asgard, called Spinnaker. \u201cBefore Google could fork the project, we managed to convince Google to collaborate on Spinnaker instead of forking Asgard. Pivotal also joined in,\u201d said Andy Glover, shepherd of Spinnaker and Director of Delivery Engineering at Netflix. The rest is history.<\/p>\n There are many factors at play that contribute to the popularity and adoption of Spinnaker. First and foremost, it\u2019s a proven technology that\u2019s been used at Netflix. It instills confidence in users. \u201cSpinnaker is the way Netflix deploys its services. They do things at the scale we don\u2019t do in AWS. That was compelling,\u201d said Leach.<\/p>\n The second factor is the powerful community around Spinnaker that includes heavyweights like Microsoft, Google, and Netflix. \u201cThese companies have engineers on their staff that are dedicated to working on Spinnaker,\u201d added Leach.<\/p>\n In October 2018, the Spinnaker community organized its first official Spinnaker Summit<\/a> in Seattle. During the Summit, the community announced the governance structure for the project<\/a>.<\/p>\n \u201cInitially, there will be a steering committee and a technical oversight committee. At the moment Google and Netflix are steering the governance body, but we would like to see more diversity,\u201d said Steven Kim, Google\u2019s Software Engineering Manager who leads the Google team that works on Spinnaker. The broader community is organized around a set of special interest groups (SIGs) that enable users to focus on particular areas of interest.<\/p>\n \u201cThere are users who have deployed Spinnaker in their environment, but they are often intimidated by two big players like Google and Netflix. The governance structure will enable everyone to be able to have a voice in the community,\u201d said Kim.<\/p>\n At the moment, the project is being run by Google and Netflix, but eventually, it may be donated to an organization that has a better infrastructure for managing such projects. \u201cIt could be the OpenStack Foundation, CNCF, or the Apache Foundation,\u201d said Boris Renski, Co-founder and CMO of Mirantis.<\/p>\n I met with more than a dozen users at the Summit, and they were extremely bullish about Spinnaker. Companies are already using it in a way even Netflix didn\u2019t envision. Since continuous delivery is at the heart of multi-cloud strategy, Spinnaker is slowly but steadily starting to beat at the heart of many companies.<\/p>\n Spinnaker might not become as big as Kubernetes, due to its scope, but it\u2019s certainly becoming as important. Spinnaker has made some bold promises, and I am sure it will continue to deliver on them.<\/p>\nFrankenstein\u2019s Monster<\/h3>\n
Continuous popularity<\/h3>\n
Governance<\/h3>\n