Cloud Providers Overview
In Spinnaker, providers are integrations to the Cloud platforms you deploy your applications to.
This section describes how to install and set up Spinnaker.
Halyard was previously mentioned on this page, and is deprecated in favor of native installation using kustomize or similar 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.
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
Kustomize or kubectl with kustomize integrated
You can also install on a single local machine , or for Spinnaker development , making sure you have the 4 cores and 16GB in each case.
Installing a complete Spinnaker involves these steps:
It is HIGHLY recommended to at LEAST setup authentication for spinnaker!
In Spinnaker, providers are integrations to the Cloud platforms you deploy your applications to.
Based on your use case, choose how you want to install Spinnaker.
Spinnaker requires an external storage provider for persisting your Application settings and configured Pipelines.
After you finish configuring Spinnaker, deploy it and connect to the Deck, the Spinnaker UI.
Commonly Asked Questions
Size your Spinnaker services to meet your usage requirements.
Spinnaker configuration is a multipart process, including configuring Cloud providers as deployment targets and external storage for metadata persistence.
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/