Jan 7, 2017 by Ben Mappen
Have a question that’s not listed here? Email us at [email protected]
Armory recently released Armory Spinnaker v1.0. Here are some FAQs and answers about the release:
We support all US regions.
Spinnaker supports OAuth and SAML 2.0. We wrote a blog post on how to configure Github OAuth here.
Our installer can be run in development mode and HA mode. When run in HA mode, we expose monitoring endpoints that you can use to forward application and system logs to services like Splunk and SumoLogic. We also deploy Spinnaker behind an ASG so that it will auto-heal itself just in case it goes down.
No, Armory Spinnaker removes the dependency on Cassandra and replaces that data store with S3. S3 is easier to manage, more stable, and comes with global redundancy and versioning so that you have a historical record of what changes and by whom as you update your config files and pipelines.
If you used the existing AMI Quickstart installer, you’ll need to run an update because the AMI was created several months ago and it is about two hundred versions behind. This can be risky because there are no official Spinnaker releases today. Armory Spinnaker comes with stable releases and AWS integration tests so you can have confidence that when you update, it won’t break your system.
Armory Spinnaker stands up a Redis cluster that is configured to communicate with your Spinnaker instance. We place it in the correct subnet, ensure failovers are handled properly, and configure it with enough capacity to run on your physical infrastructure. If you already have a Redis cluster, it’s easy to point Spinnaker to use your cluster.
Spinnaker supports Kubernetes out of the box today. There are plans to add support for Mesos and ECS in 2017.
Yes, we can send you comprehensive a list of the IAM roles that you’ll need. Spinnaker requires Power User access and generally speaking, the person in your organization who is responsible for managing IAM roles is likely also the person who will need to install Spinnaker.
Yes, pipelines are represented in Spinnaker as JSON. If your goal is to maintain versioning, this can be done simply by enabling versioning on the S3 bucket that stores your pipeline configs. If your goal is to store pipeline configs in source control, we can help facilitate that. You’ll need to create the config files and store them in your repository. Then, whenever the config file changes, they will need to be POST-ed to the Spinnaker API.
Software deployment processes differ across organizations, teams, and applications. The most basic, and perhaps the riskiest, is the “big bang deployment.” This strategy updates all nodes within the target environment simultaneously with the new software version. This deployment strategy causes many issues, including potential downtime or other issues while the update is in progress. It […]
Read more →
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 →