Nov 7, 2019 by Rosalind Benoit
Having recently joined the Spinnaker community, I’m taking the time to understand how this promising project has evolved from a Netflix-internal tool called Asgard to the leader in the continuous delivery platform space. IMHO (as a super-biased Linux nerd), Spinnaker’s ubiquity has the open source software community to thank. When it comes to enabling fast, safe, repeatable deployments, and blazing a path to cloud native continuous delivery at enterprises, open source is simply the most viable and sustainable option. The adage that “the only thing constant is change” dictates an approach to maintaining a platform which embraces the ecosystem’s evolution; from updates to cloud provider offerings to an ever-growing list of integrations, we need a platform that leverages open source’s power to keep up with the pace, share wins, and have fun doing it!
Armory understands this, and is thus a leader in the Spinnaker open source community. We have become one of the top contributors to the project’s code and documentation. Some of Armory’s key open source stats:
We dedicate time each day to actively supporting the community in Spinnaker Slack by answering questions and building a knowledge base – please join us! We have also committed to co-leading a number of key SIGs (Special Interest Groups):
These are open groups which welcome anyone in the community to join, participate, and ask questions. Stop in from anywhere to join Armory in getting engaged with the community and helping guide the future of the project. Armory also organizes Spinnaker meetups across the country, has developed the leading training and educational program for Spinnaker, and has published more than a dozen free ebooks and whitepapers about how to achieve success with Spinnaker.
Beyond community development, Armory is a top-5 contributor to OSS Spinnaker, and has contributed many of the key features since the project was open sourced in late 2015. Diving right into an OSS community like Spinnaker can be daunting, so many of Armory’s contributions focus on paving the way for others to adopt and use Spinnaker to transform software delivery at their organizations.
Some of my favorite of Armory’s Spinnaker contributions include the Plugins Framework, which allows users to add functionality at boot/runtime without the need to manage the lifecycle of building, testing, and distributing an extension. Another, the Spinnaker Operator, allows administrators to manage Spinnaker with
kubectl, or other Kubernetes tools that they’re comfortable with. Finally, the Terraform Provider provides the capability to manage Spinnaker applications and pipelines using Hashicorp’s Terraform, another ubiquitous tool in the cloud native universe enabled by immutable infrastructure.
Here’s a more complete list of Armory’s key feature contributions:
Click here for details on Armory’s 600+ merged PRs.
Armory has invested heavily in making Spinnaker the most usable, extensible, and powerful continuous delivery platform on the planet. We invite you to join us in contributing to the project that will change software delivery forever!
Multi-target deployments can feel tedious as you deploy the same code over and over to multiple clouds and environments — and none of them in the same way. With an automatic multi-target deployment tool, on the other hand, you do the work once and deliver your code everywhere it needs to be. Armory provides an […]
Read more →
KubeCon+CloudNativeCon EU is one of the world’s largest tech conferences. Here, users, developers, and companies who have and intend to adopt the Cloud Native standard of running applications with Kubernetes in their organizations come together for 5 days. From May 16-20, 2022, tech enthusiasts will congregate both virtually and in person in Valencia, Spain to […]
Read more →
Deciding how frequently to release a product is an interesting challenge faced by many companies. There are definite pros and cons related to adjusting your release cadence that have to be evaluated on an individual basis. Faster release cycles in theory might sound good, but of course, there can be tradeoffs. Looking at historical release […]
Read more →