In the last section we put together our deployment file for the multi server set of pods and we made
sure that we specify that port 5000 should be accessible on the image that gets created inside of each
of those pods.
So we're now going to create a second configuration file that's going to serve as what's going to create
and maintain the cluster IP service.
So I'm going to again flip back over to my code editor and inside of my Kades directory I'm going to
put together a new file that I will call server cluster IP service that yemo all right and I'm going
to say I don't need to or is going to say I was going to type out the name of the file right here just
so you can see the whole thing.
But you can actually see the whole name right here on the tab inside of my code editor just in case
you want to reference the exact name that I'm using.
All right.
So inside of here we're going to put together another config file for a service of type cluster IP.
This is again going to be just about identical to the previous cluster IP service we put together.
But let's go through typing it all out again just to kind of commit this stuff to memory.
It'll be pretty quick.
So I'm going to provide an API version of V-1 or provide a kind of service or meta data we're going
to specify the name of this service or this object.
And I'm going to use a name of server cluster IP service like the name we will provide a spec that's
going to customize exactly how this server behaves or see how the service behaves.
So we're going to specify a type of service of cluster IP and then we need to provide a selector that's
going to tell the service exactly what set of pods it's supposed to provide access to.
And so of course the cluster IP that we're putting together right now is supposed to provide access
to all the multi server pods in just the last section when we put together the server deployment file.
We had assigned each of those pods a label of component server and so inside of our server cluster IP
service we're going to want to specify a selector of component server Tobacco-Free Here I'll provide
a selector of component server.
And then finally very similar to what we did last time.
We're going to make sure that we specify the ports that the service is going to kind of mitigate control
over or men control over.
So just as before we're going to just send everything through.
And as a reminder the multis server image listens for traffic on port five thousand.
So we're going to provide our ports with a port of 5000 and a target port of 5000 as well just as we
did inside of our previous service OK.
So that's it.
That's all we have to do.
To put together our cluster IPs service that's going to govern or manage access to our running express
API.
So let's take a quick pause right here.
I want to address one little side topic and then we'll continue with a couple more config files or the
rest of all the objects inside of our application.
So quick pause and I'll see you in just a minute.