Spinnaker Feature – Management Flexibility: Cluster Management and Deployment Management

Apr 20, 2017 by Armory

Spinnaker ships with two core features: cluster management and deployment management. These features are easily reviewed through Armory’s Lighthouse feature.

Cluster Management – Managing your Clusters and regions can get out of hand as you scale – therefore Spinnaker strives to simplify it with an interactive and intuitive UI. Through this Spinnaker UI you can also manage the Security Group and Load Balancers associated with the respective Server Groups through Spinnaker.

<img src=”https://d1ax1i5f2y3x71.cloudfront.net/items/1u2q3W3U3v3t1J0x3o1S/Image 2017-03-24 at 3.05.04 PM.png“)

  • Cluster – A logical or customized grouping of Server Groups
  • Server Group – A collection of Virtual Machines (VM) running instances of images
  • Security Group – Generally a firewall that determines network traffic access. Can be set to desired specifications through Spinnaker
  • Load Balancer – Balances traffic among Server Group instances

Deployment Management – Deployments can take many manual steps that are hard to script and track. Spinnaker allows for precise orchestration of the Stages and Pipelines containing them to get your desired execution.

  • Stage – A Stage is an action within a Pipeline; successive completion of Stages leads to the eventual execution of a Pipeline.
  • Pipeline – A logical series of actions called Stages for deployments, where parameters are passed within each Pipeline from Stage to Stage. Pipelines can be configured to start manually or automatically triggered as well as send notifications and self-diagnosis to external channels such as SMS, Slack, email, etc.

Lighthouse – Spinnaker is for managing Clusters and Deployments, but Spinnaker itself should also be easy to manage. Lighthouse is a lightweight service for managing Spinnaker specific to Armory’s distribution of Enterprise Spinnaker.

  • Monitors Spinnaker services for health and failures of your deployed clusters
  • Monitors Orca on its own instance for termination when no jobs are running
  • Enables easy upgrades for Spinnaker (Spinnaker is an amalgamation of multiple services for which the user would have to manually update)
  • Bootstraps Spinnaker with pipelines that can be used in integration testing
  • Aggregates Spinnaker’s metrics for displaying onto a dashboard
This post is part of a series of posts that describe features in Spinnaker. You can find
all of the related posts here.

Learn More

Share this post:

Recently Published Posts

Navigating AWS Deployment Targets with Armory

Jan 20, 2023

Many organizations look to Amazon Web Services (AWS) to host and deploy their applications in the cloud. However, they’re finding that their deployment tooling, often built as an extension of their legacy continuous integration (CI), is one of the main impediments to adopting cloud services.  Custom-scripted production pipelines built with in-house tooling need to be […]

Read more

Release Roundup – January 2023

Jan 11, 2023

Get the latest product news on Continuous Deployment-as-a-Service and the most recent release for Continuous Deployment Self Hosted, 2.28.2. Welcome to 2023!  Just like every organization, Armory is looking for ways to improve our practices and deliver more value (and faster!) to you, our customers. That’s why our engineering team is working to deliver features, […]

Read more

Learn Continuous Deployment with Armory and Wilco

Jan 6, 2023

Armory is excited to announce we have launched an interactive, narrative-driven developer experience that teaches continuous deployment concepts. And now you can try it out for yourself! Wilco, also known as the “flight simulator” for software developers, allows companies to create engaging interactive developer challenges (called quests) that enable developers to acquire and practice skills […]

Read more