Learn what Spinnaker does when it deploys to Kubernetes targets and then add a Kubernetes Service Account to Spinnaker.
This section contains guides for administering a Spinnaker or Armory deployment on AWS infrastructure.
Configure a Spinnaker Manual Judgment pipeline stage to propagate authentication.
Configure Spinnaker to share an Amazon Machine Image (AMI) when Spinnaker and the deployment target share the same AWS account.
Learn how to configure Kayenta when Spinnaker has been installed using the Armory Operator.
Configure Spinnaker’s Clouddriver service to use MySQL or AWS Aurora.
Use Spinnaker’s External Account Configuration feature to manage Kubernetes accounts.
Simplify DNS and Ingress management by deploying Gate and Deck to the same host.
Configure GitHub and Spinnaker to use GitHub as an OAuth2 authenticator.
This guide describes how to enable mutual TLS (mTLS) between Spinnaker services. Adding mTLS provides additional security for your Spinnaker services since only validated clients can interact with services when mTLS is enabled.
Configure Okta for authentication and authorization in Spinnaker.
Configure Spinnaker’s Orca service to use an RDMS to store its pipeline execution.
Learn how to configure Spinnaker to send Slack notifications.
Enable Armory Diagnostics so that Armory’s Support team can better troubleshoot any issues you encounter.
Learn how to configure the Armory Splunk application so you can display your SDLC data in 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.
Learn how to configure Spinnaker to access a Docker registry.
Configure Spinnaker to access a GitHub repo as a source of artifacts.
Use Halyard or the Armory Operator to configure Spinnaker to access to your Jenkins instance.
Use Halyard to configure Spinnaker to access to your Travic CI instance.
Manually create a Kubernetes Service Account to use with Spinnaker.
Configure your infrastructure so users can access your Spinnaker instance.
Learn how to configure Spinnaker to use pipeline templates stored in source control.
Enable the Policy Engine and configure an OPA server. When enabled, the Policy Engine can perform save time or runtime validation on your Spinnaker pipelines.
Learn how to configure the Terraform Integration and an artifact provider to support either GitHub or BitBucket.
Set up x509 certificate authentication to expose Spinnaker API endpoints when you have third-party authentication configured.
Use OpenSSL to generate certificates for Spinnaker.
Armory-extended Halyard command reference with examples and Operator equivalents
Create ServiceNow integrations through a generic webhook stage or a custom webhook stage.
Learn how to integrate a Sumo Logic Dashboard using Halyard or the Armory Operator.
Monitor Spinnaker using Prometheus and Grafana.
Configure Spinnaker to avoid cloud providers such as AWS, GCP, and Azure from throttling your Spinnaker traffic.
Configure Fiat, the Spinnaker microservice responsible for authorization (authz), to control which users can create applications by using the
Create a workflow to store Spinnaker configuration files in GitOps and automate deployment.
This section contains guides for using secrets stored outside of Spinnaker in products such as Hashicorp Vault, Google Cloud Storage, AWS S3, and the AWS Secrets Manager.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.