Choose your Environment
Based on your use case, choose how you want to install Spinnaker.
A kubernetes cluster
This can be any of the supported vendor solutions (AKS/EKS/GKE/etc.) or an on-premise kubernetes cluster. Make sure it has at least 18GB of memory and 6 cores. Spinnaker uses memory depending upon configuration and the number of “accounts” registered with spinnaker
kubectl with kustomize integrated
Kubernetes native configuration management Kustomize
Installing a complete Spinnaker involves these steps:
It is HIGHLY recommended to at LEAST setup authentication for spinnaker!
hal is deprecated.
Halyard was previously mentioned on this page, and is deprecated in favor of native installation using kustomize native configurations.
References to halyard are being steadily removed from the project. An example script is available to export a halyard or operator deployed spinnaker into kustomize style deployment.
Based on your use case, choose how you want to install Spinnaker.
After you finish configuring Spinnaker, deploy it and connect to the Spinnaker UI (Deck).
In Spinnaker, providers are integrations to the Cloud platforms you deploy your applications to.
Spinnaker requires an external storage provider for persisting your Application settings and configured Pipelines.
Spinnaker configuration is a multipart process, including configuring Cloud providers as deployment targets and external storage for metadata persistence.
Commonly Asked Questions
Learn how to migrate to Kustomize Deployment automatically. Mirrored from the armory docs https://docs.armory.io/continuous-deployment/spinnaker-user-guides/armory-operator-to-kustomize-migration/
Size your Spinnaker services to meet your usage requirements.