VM only: This codelab requires you have a VM (for example, on AWS or GCP) on which to run it.
To walk you through some of the basics with Spinnaker, you’re going to set up a Spinnaker pipeline that bakes a virtual machine (VM) image containing redis, then deploys that image to a test cluster.
Note here that the us-east-1a availability zone is currently full, so it will need to be deselected in the corresponding ‘region’ checkbox list for each of these steps.
If you don’t already have a running Spinnaker instance, you’ll need to set one up before you continue. A demo installation should be sufficient for this codelab, but you can also follow the full setup guide to try out Spinnaker with a full installation.
Once you have deployed Spinnaker, navigate to localhost:9000 to start this codelab.
examplefor the Name field and your email address for the Owner Email field.
Next, you’ll create a firewall that specifies traffic rules for the cluster. You’ll configure the rules to allow all incoming traffic on port 80, for clusters associated with this firewall.
testfor the Detail (optional) field and
Test environmentfor the Description field.
0.0.0.0/0value for the Source Range field.
TCPvalue for the Protocol field. Change Start Port and End Port to
Next, you’ll create a load balancer in Spinnaker.
testfor the Stack field.
Your final task is to set up a Spinnaker pipeline. Let’s name it
Bake & Deploy to Test. The pipeline will produce an image
redis-server package and then deploy
it. In this tutorial, you’ll trigger the pipeline manually.
To create the pipeline:
Bake & Deploy to Testfor the Pipeline Name.
You’re now going to create the first stage of the pipeline. It will build an image from an existing redis-server package.
redis-serverfor the Package field.
You’re now going to set up the second stage of the pipeline. It takes the image constructed in the Bake stage and deploys it into a test environment.
Next, In the Configure Deployment Cluster window, input “test” for the Stack field.
example-test. Click the Next button.
example-test (example-test). Click the Next button.
2for the Number of Instances field, then click the Add button.
Now, watch Spinnaker in action. A MANUAL START section will appear, and will show progress as the pipeline executes. At any point during pipeline execution, click on the horizontal bar to see detailed status for any of the stages in the pipeline.
Feel free to navigate around the Spinnaker menus, create new pipelines, clusters, server groups, load balancers, and firewalls, etc. and see what happens.
When you’re ready to stop, don’t forget to cleanup your resources. An easy way to do this is to visit the pipelines, clusters, load balancers, and firewalls pages, click on the ones created and select the appropriate Delete command from the Actions pulldown on the right.