This article assumes you are new to Spinnaker. It contains basic information about what to do after Spinnaker is installed.
Before you get going…
Whether you’re an operator or admin installing or managing Spinnaker or an end user getting started using Spinnaker, here are some pointers to get you started.
Operators (managing Spinnaker)
If you want to install Spinnaker, instructions are here.
If you want to find out more about tuning and maintaining Spinnaker, here are some things to check out:
Users (deploying with Spinnaker)
If you just want to try out Spinnaker, here are some quickstarts.
If Spinnaker is already installed in your organization, and you want to practice it using some guided tutorials, here are some codelabs.
If you want a very basic overview of how to use Spinnaker, the high-level process is described below.
Using Spinnaker: the high-level process
Typically, you’ll have one application per microservice.
Note that your application configuration affects what you can do with Spinnaker—you can enable or disable some Spinnaker features.
Define the infrastructure the service will run on
You define infrastructure for each application. Your pipelines deploy services to the server groups you define.
Note: this step is not a prerequisite for creating pipelines. In fact, you can use pipelines to create infrastructure.
In fact, create all the pipelines you need to deploy the service or services covered by the application, in whatever ways you want to deploy.
Learn more here in the Managing pipelines guide.
Run your pipeline to deploy your service
You can run a pipeline manually, but most pipelines are triggered automatically.
For practice, and to see some sample deployment scenarios, check out our codelabs.