You are viewing version 2.23 of the documentation, which is no longer maintained. For up-to-date documentation, see the latest version.
Administer an Armory deployment on AWS infrastructure
Simplify DNS and Ingress management by deploying Gate and Deck to the same host.
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.
Spinnaker supports using Okta for authentication and authorization.
The Armory Splunk App for Spinnaker brings all the SDLC information your organization has into a digestible and familiar format, Splunk dashboards.
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.
To use Jenkins in Spinnaker, configure access to your Jenkins instance.
To use Kubernetes with Spinnaker, configure
Pipelines as Code allows you to create and maintain pipeline templates in source control.
If you do not have existing certificates to use for securing your Spinnaker environment, create them.
Command reference with examples and Operator equivalents
Monitoring Spinnaker using Prometheus and Grafana
By default Spinnaker, queries (polls) the entire state of cloud resources managed by Spinnaker every 30 seconds through the Clouddriver service.
Configure Fiat, the Spinnaker microservice responsible for authorization (authz), to control which users can create applications by using the
You can manage your Halyard configs as part of a GitOps workflow by storing it in source control.
Armory supports several secret stores. Use them to keep your secrets secure and not commit plain text secrets to your configs.