 Okay, in this video we are going to start configuring our consolidated logging, so Elasticsearch is the database that is going to be holding our consolidated logged data. On line 8 we can see that we have the Docker Compose configuration for Elasticsearch. Pretty straightforward, we have one environment property we need to set that is a Discovery Type single node, and then we need to expose port 9200, so let's toggle over to the command line and we will start working on that. So to set this up I'm going to use CUBE control, I'm going to create a deployment, call it Elasticsearch, and that image is going to equal, I'm just going to copy that, that's quite a bit to type out, and here we want to set up the drive run, client, and then minus O for YAML output, so that creates the YAML file, I'm going to toggle back over to Entology, and we want to set up a property, environment property of Discovery Type, I'm going to copy that on over, and here under resources we want to say ENV, remember this is going to be a list, name, so that Discovery Type, value, and you can see that we have single dash node, so that sets up Elasticsearch, so let's come back to the command line, and we can do Elasticsearch deployment, and that is going to create the Elasticsearch deployment, so a pod and container will be created for that inside of Dockers, and now what we want to do is go ahead and set up the service for that, so CUBE control, service, and this would be a cluster IP, because we don't need access from the outside, Elasticsearch, and TCP we're going to expose 9,200, drive run equals client, and we'll redirect this to Elasticsearch YAML file, that's created, and then let's go ahead and apply that, and that is created, and coming up we can see that we have a lot more stuff running under our pods, we can see that Elasticsearch is up and running, and we have an Elasticsearch cluster IP, port 9,200 is exposed, so exactly what we want, so let's come back over to IntelliJ, you can see that we added in the Elasticsearch deployment, and we did have to edit this file to add the ENV property, name, Discovery Type, value of single node, the Elasticsearch service, this was generated purely from the Kubernetes command line, and there's no editing required to this file, we just do CUBE control apply to create the services previously shown in the video.