Armory uses K3 to simplify CD Spinnaker installations
Armory today launched an Armory Minnaker offering that uses a lightweight instance of Kubernetes combined with operator software to simplify the deployment of its distribution of the open source Spinnaker Continuous Delivery (CD) platform.
Chad Tripod, Field Technical Director for Data and Cloud at Armory, says one of the main challenges organizations face with Spinnaker is that it is complex to configure and deploy. Operators, a way to configure Kubernetes clusters originally developed by CoreOS, are extensible, however. By creating an Armory Operator to deploy Spinnaker on an open source K3s instance of Kubernetes, Armory reduces installation complexity to the point where the CD platform can now be installed in less than 10 minutes, Tripod explains.
Kubernetes’ K3 instances provide a lighter subset of container orchestration platform functionality that is starting to be more widely used since the project was donated to the Cloud Native Computing Foundation (CNCF), which oversees the development of Kubernetes, by Rancher Labs, which has since been acquired by SUSE.
Originally developed by Netflix, Spinnaker is now under development under the auspices of the Continuous Delivery (CD) Foundation, which, like the CNCF, is also a branch of the Linux Foundation. Armory proposes to deploy a Spinnaker CD platform independent of a Continuous Integration (CI) platform which can be used to automate deployments of the two emerging, container-based microservices as well as architecture-based applications. traditional monolithic.
Integrated CI / CD platform vendors have advocated for years for tight integration of DevOps workflows. However, most DevOps teams haven’t been able to fully automate app delivery, as each platform an app is deployed on tends to be unique. As a result, DevOps teams end up writing additional custom scripts to deploy applications that then need to be maintained.
In theory, the rise of Kubernetes presents an opportunity to standardize on Kubernetes clusters that all have a common application programming interface (API). However, there are many extensions and add-ons for Kubernetes platforms that over time conspire to make every environment somewhat unique.
Spinnaker was specifically created by Netflix’s in-house DevOps team to address this complexity using a CD platform based on a microservices architecture. Armory was created specifically to organize a distribution of Spinnaker that would be easier for corporate IT organizations to consume and create GitOps workflows. These workflows allow a platform to automatically pull artifacts directly from Git repositories, rather than waiting for a DevOps team to use a CI / CD platform to push code to a target platform.
It is still early days for the adoption of Spinnaker in the company. There are now several platforms that, to varying degrees, allow software development teams to implement GitOps best practices. However, as Spinnaker continues to evolve, many other organizations should be able to more easily automate continuous delivery. The issue they will have to resolve, however, is the extent to which they may need a separate, dedicated CD platform instead of trying to continue to depend on an integrated CI / CD platform.