Now that we’ve picked a Deployment Environment, configured Persistent Storage, and enabled a Cloud Provider we’re ready to pick a version of Spinnaker and deploy it. First, list the available versions:
hal version list
You can follow the links to their changelogs to see what features each version
has included since the last release. Once you’ve picked a version (e.g.
VERSION=1.0.0), you can set it with
hal config version edit --version $VERSION
And finally, deploy Spinnaker with the following command:
hal deploy apply
Note: If you’re deploying to your local machine, that command may need to
be run with
Connect to the Spinnaker UI
If you have not enabled any sort of authentication, Spinnaker will not be publicly reachable by default. In this case, you will need to run the following command to reach the UI on localhost:9000:
hal deploy connect
If you want to make Spinnaker publicly reachable without running that command, please read the Halyard FAQ.
If this command fails, and it’s the first time you’ve run this command please
reach out to us on Slack.
If you’ve had a successful deployment, you can run
hal deploy diff to see what
changes you’ve made that may be causing problems. At any point you can rerun
hal deploy apply with any changes you’ve made to retry the deployment.
If you want to change Spinnaker versions using Halyard, you can read about supported versions like so:
hal version list
And pick a new version like so:
hal config version edit --version $VERSION # this will update Spinnaker hal deploy apply
Now that Spinnaker is deployed and capable managing your cloud provider, you can either visit the Guides pages to learn how to use Spinnaker, or continue with additional configuration, such as your image bakery.
You might also want to back up your configuration.