Using Kubernetes in Production? Try adding Spinnaker
In the process of onboarding multiple companies onto Spinnaker, we’ve found that those already evaluating or using Kubernetes are especially well positioned to take advantage of Spinnaker due to its immutable opinionated philosophy and ability to help migrate workloads over to Kubernetes from other environments.
Spinnaker is a great way for companies to abstract their deployment pipelines up one level to enable workloads to be deployed to multiple targets (including AWS EC2 (and soon ECS and Lambda), Kubernetes, Azure, OpenStack, DC/OS, and GCP), to make deployment pipelines more self-service and flexible for both application teams and infrastructure/automation/ops teams, and to help companies move workloads onto Kubernetes. In this video, Isaac the CTO of Armory describes the challenges of moving to Kubernetes inside a large company without Spinnaker:
And now with Barometer, Armory’s automated canary analysis solution (currently in alpha), application teams get an additional level of automation, speed and confidence with Spinnaker.
Armory is specifically looking for teams using Kubernetes to test Barometer on Spinnaker. Barometer will provide a level of automated canary analysis that’s not otherwise available, enabling confident, safe and rapid deployments to production, and allowing for less integration testing and manual judgement stages.
Want to install Spinnaker on Kubernetes?
While Armory supports Kubernetes as a deployment target, our installer currently only installs Spinnaker in AWS. If you’re interested in installing Spinnaker in Kubernetes, you can try using the open source installer, Halyard. We are evaluating providing commercial support for installing Spinnaker in Kubernetes; please contact us below if you’re interested in this.
Want to read more? You can find a number of other Kubernetes + Spinnaker posts here.