You are viewing version 2.23 of the documentation, which is no longer maintained. For up-to-date documentation, see the latest version.

Armory Admin

Administer an Armory deployment that is installed in your environment.

Creating and Adding a Kubernetes Account to Spinnaker as a Deployment Target

Administration on AWS

Administer an Armory deployment on AWS infrastructure

Authentication and Authorization

Bake and Share AMIs Across Accounts

Configuring Kayenta for Automated Canary Deployments

Configuring Clouddriver to use a Relational Database Management System

Configuring Dynamic Kubernetes Accounts With Vault

Configuring Gate and Deck to Run on the Same Hostname

Simplify DNS and Ingress management by deploying Gate and Deck to the same host.

Configuring GitHub OAuth for Spinnaker

Configuring mTLS for Spinnaker Services

This guide describes how to enable mutual TLS (mTLS) between Spinnaker services and is building on top of how to enable TLS. Adding mTLS provides additional security for your Spinnaker services since only validated clients can interact with services when mTLS is enabled.

Configuring Auth for Spinnaker Using Okta SAML

Spinnaker supports using Okta for authentication and authorization.

Configuring Orca to use a Relational Database Management System

Configuring Slack Notifications

Configuring Support Diagnostics for the Armory Platform

Configuring the Armory Splunk App for Spinnaker™

The Armory Splunk App for Spinnaker brings all the SDLC information your organization has into a digestible and familiar format, Splunk dashboards.

Configuring TLS for Spinnaker Services

Spinnaker services communicate with each other and can exchange potentially sensitive data. Enabling TLS between services ensures that this data is encrypted and that a service will only communicate with another service that has a valid certificate.

Connecting Docker Registries

Connecting Spinnaker to GitHub as an Artifact Source

Connecting Spinnaker to Jenkins

To use Jenkins in Spinnaker, configure access to your Jenkins instance.

Connecting to Travis

Creating Kubernetes Service Accounts and Kubeconfigs

To use Kubernetes with Spinnaker, configure


Enabling Pipelines as Code

Pipelines as Code allows you to create and maintain pipeline templates in source control.

Enabling Policy Engine

Enabling the Terraform Integration Stage

Exposing the Spinnaker API Endpoint

Generating Certificates

If you do not have existing certificates to use for securing your Spinnaker environment, create them.

Armory-extended Halyard Reference

Command reference with examples and Operator equivalents

Integrating ServiceNow with Spinnaker

Integrating a Sumo Logic Dashboard

Monitoring Spinnaker with Prometheus

Monitoring Spinnaker using Prometheus and Grafana

Rate Limiting the Spinnaker API

By default Spinnaker, queries (polls) the entire state of cloud resources managed by Spinnaker every 30 seconds through the Clouddriver service.

Restrict Application Creation

Configure Fiat, the Spinnaker microservice responsible for authorization (authz), to control which users can create applications by using the prefix parameter.

Spinnaker GitOps with Halyard

You can manage your Halyard configs as part of a GitOps workflow by storing it in source control.

Working with Secrets

Armory supports several secret stores. Use them to keep your secrets secure and not commit plain text secrets to your configs.

Last modified October 9, 2020: docs(order): clean up the order (#249) (48ec05a)