Install and Configure Spinnaker
This section describes how to install and set up Spinnaker so that it can be configured for use in production. If you just want to evaluate Spinnaker without much work, one of the options in Quickstart might be a better choice.
What you’ll need
A machine on which to install Halyard
This can be a local machine or VM (Ubuntu 18.04 or higher, Debian 10 or higher), or it can be a Docker container. Make sure it has at least 12GB of memory.
A Kubernetes cluster on which to install Spinnaker itself
We recommend at least 4 cores and 16GB of RAM available in the cluster.
Installing a complete Spinnaker involves these steps:
- Install Halyard
- Choose a cloud provider
- Choose an environment
- Choose a storage service
- Deploy Spinnaker
- Back up your config
- Configure everything else (which includes a lot of stuff you need before you can use Spinnaker in production)
- Productionize Spinnaker (which mainly helps you configure Spinnaker to scale for production)
And then what?
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.
Create a backup of your Halyard config so that you can redeploy Spinnaker any time with the same configurations.
Common questions about Halyard.
Spinnaker configuration is a multipart process, including configuring Cloud providers as deployment targets and external storage for metadata persistence.
Upgrading Spinnaker is a two step process. First, select the target version. Then, apply your change.