Ethan Rogers, resident Spinnaker expert, gives an quick overview of Spinnaker and explains why this tool is invaluable to your workflow.
A Trascript of this video is available below:
Ethan: What is up guys I am Ethan your Spinnaker expert. Thanks for joining us for the first video of our Spinnaker training series. We will be teaching you how to use spinnaker to get most out of your application and infrastructure deployments. Today we will be talking about Spinnaker and what it is and what sets it apart from other continuous deployment platforms on the market.
Spinnaker is a multi-cloud continuous delivery platform. It is kind of a mouthful so we are going to impact that a little bit. What that means is that Spinnaker can deploy to any cloud provider that you are using. Whether that's AWS, Google Cloud or Kubernnates and it can be used to automate your delivery to all your environments that you use throughout the software development life cycle from test, to stage, to production.
You can see Spinnaker as like a single pane of glass providing important insight into your application health that really helps drive our deployment and scaling decisions that you are going to make throughout the applications life. Spinnaker does this by abstracting away some of the common cloud infrastructure that you can find throughout this cloud providers such as load balancers, security groups and server groups. Now, server groups are just in abstraction on top of your application running in one of these cloud providers. So in AWS, that would be an auto scale group made up of EC2 instances.
In Kubernetes there would be a deployment or replica set made up of pods. One of the greatest things though that Spinnaker provides is this robust pipeline framework that you can use to build out any deployment workflow that you want. So the way this works is that you can compose a series of stages that represent various steps throughout your deployment pipeline. So let us say you have pushed code to Github, the next thing you want to do is have Jenkins build your artefact and then you can have Spinnaker pick up when Jenkins builds that artefact, bake it into an AMI and then deploy the AMI into AWS.
Now, all of these stages have been battle tested and really built out so that your applications stays available and that some of the biggest companies today are already using Spinnaker to do this. So, this training series is really to give you an in-depth understanding of Spinnaker. Throughout we will be reviewing all the different aspects that make the platform what it is. We will be looking at how to deploy applications and infrastructure with Spinnaker and utilize all of these best practices to manage their life cycle throughout the process and lifetime of your application. If at any point you have any ideas for ways to make Spinnaker better be sure to reach out to Armory at: go.armory.io/ideas. The Armory team would really love to hear your feedback and really wants to make Spinnaker better for you. I hope this series really helps you just build out your understanding of Spinnaker and really help you feel comfortable within the platform so that you can continue bringing business value to your organization.
Thanks for watching.