 Okay in this video what we want to do is deploy our REST brewery. So previously in a course I showed you how to take this spring boot application and build a Docker image of that. So now what we want to do is we want to take this and this is published up to Docker Hub so you'll be able to access this pretty easily. If you don't want to go through the time to generate your own image so you can go ahead and utilize this and follow it directly along with what I'm doing in the course here. So this is a simple REST application I will leave in the course resources up here SFGBearworks brewery API so we have a basic CRUD application that's the spring boot application that we are going to deploy to Kubernetes so this is a nice little application for us to work with. So I'm going to toggle over to the command line now and we'll take a closer look at those. So I'm in the command line and what we can do is we can do kubectl get all and we can see we've got our cluster is up nothing is running right now so that that's exactly where we want to be. I'm going to go ahead and clear this and what we can do is we can also use kube control to actually create the deployment YAML so there's quite a bit to it and we are going to accept some defaults and have the tool generate the YAML file for us so I'm going to say kubectl create a deployment we are going to call this KBE REST that is the name of the application we are deploying and then image going to be spring framework guru slash so that's the name of my github repository and this is going to be KBE REST brewery like so that's the name of the image up inside a Docker hub now we're going to say do a command called drive run and I used to just be this there's a recent change where you have to say client and what this does is it tells it to run locally we're only going to run the command we're not actually doing the deployment because we want to generate the actual YAML for it and we're going to do a redirect to a file and let's call this deployment YAML like so and we hit enter runs pretty quick and we'd see that I do have a deployment YAML file that has been generated so if I come in and view that I'm using a little vim now we can see this is a YAML that was generated by kubectl quite a bit here but we're saying that we want one replica so we'll have one of these running and then down here the containers we can see that that is the image that we specified so we did not specify a tag so by default it's going to grab this latest tag from the the repository so pretty simple at this time we're not going to dive too deep into the actual options inside the YAML this is kind of the default that has been generated but this is the YAML specification that tells kubernetes how to or what to deploy so I don't need to write I'm just going to do a quit clear this now to actually get this to run we need to do kubectl apply so this is a generic man to apply and I'm saying minus f and I want to take that YAML file that we just generated so we'll go ahead and deploy that and we can see here that I get that was created so now if I was clear and do and we can see that a pod has been created so right at the top there we see pod kbe rest it's got a number and that the status is running so nothing else has really changed we have a deployment of kbe rest we say 101 is ready up to date one available desired current so we only told it to create one so we're only using one instance in our little single mode cluster so nothing too exciting going on here except for that we do have this running and if I do docker ps we can see here from docker that that container is actually running now so that is up and running currently not exposed to anything but it is up and running in a kubernetes context