 Okay, in this video we want to go ahead and set up the beer service in Kubernetes and you can see up on the screen I do have the beer service on the Docker compose and in this case you can see that our setup is very similar to inventory except we have one additional property we need to set and that is for the inventory service host there on line 68. So let's go ahead and start creating that. I'm going to toggle over to the command line to use kubectl to create the initial yaml file. The first thing we want to do is this command kubectl create deployment and we'll call it beer service and that's going to be the name of the service it's going to come from the image and this is going to be pulling from Docker hub so I have these images up in Docker hub for your use and this is going to be a drive run equals client we want the yaml output we're going to redirect the output to the file beer service deployment yaml and let's come back over to Entology and we'll go ahead and edit that file and in this file we want to set up the environment properties and I'm going to pause the video and set those up and do a code review. So I've resumed the video and you can see up on the screen starting at line 25 this is where I'm defining the environment parameters and name value pairs and everything looks pretty much the same. So you look at the Docker compose so we have the property name and the value and we have six of them and you can see here that we have six of them and again here we are setting up the inventory service so remember the inventory service that is going to match the service name and then that becomes effectively the host and the IP is resolved within a Kubernetes context so that is exactly what we want for this deployment. I'm going to come back over to the command line and we'll go ahead and apply that. Beer service deployment see that one was created now let's go ahead and create the service component for that so create service cluster IP it's going to be beer service and the service is going to be exposed in port 8080 and also we need the drive run flag to output YAML and we'll redirect that to beer service YAML technically I guess finally naming convention we should do beer service service but I think beer service YAML is perfectly fine for our purposes and go ahead and apply that minus F and that's beer service YAML and let's see here I made a mistake on that beer service YAML rather than YML just for consistency and do beer service YAML so that looks a little bit better and then let's go ahead and do a cube control get off and now we can see that we have the beer service pod running you can't quite see that scroll up a little bit so we can see that's the top pod running then we also have the service running and we can see the various deployment so everything is up and it appears to be working properly so let's go ahead and clear that I'm going to toggle back over to IntelliJ again what we did in this video as we created two files beer service deployment and beer service YAML the beer service deployment is mimicking what we'd set up for the Docker compose as far as setting up the necessary environment properties to override and set things up for the spring boot context and then the beer service YAML exposes that service as a service within Kubernetes context