1
00:00:01,120 --> 00:00:06,540
In the last section we put together our deployment file for the multi server set of pods and we made

2
00:00:06,540 --> 00:00:13,410
sure that we specify that port 5000 should be accessible on the image that gets created inside of each

3
00:00:13,410 --> 00:00:14,720
of those pods.

4
00:00:14,790 --> 00:00:19,500
So we're now going to create a second configuration file that's going to serve as what's going to create

5
00:00:19,530 --> 00:00:22,540
and maintain the cluster IP service.

6
00:00:22,710 --> 00:00:27,990
So I'm going to again flip back over to my code editor and inside of my Kades directory I'm going to

7
00:00:27,990 --> 00:00:37,750
put together a new file that I will call server cluster IP service that yemo all right and I'm going

8
00:00:37,750 --> 00:00:41,260
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

9
00:00:41,260 --> 00:00:42,370
so you can see the whole thing.

10
00:00:42,440 --> 00:00:46,270
But you can actually see the whole name right here on the tab inside of my code editor just in case

11
00:00:46,270 --> 00:00:49,640
you want to reference the exact name that I'm using.

12
00:00:49,640 --> 00:00:49,880
All right.

13
00:00:49,880 --> 00:00:56,510
So inside of here we're going to put together another config file for a service of type cluster IP.

14
00:00:56,510 --> 00:01:02,000
This is again going to be just about identical to the previous cluster IP service we put together.

15
00:01:02,030 --> 00:01:05,680
But let's go through typing it all out again just to kind of commit this stuff to memory.

16
00:01:05,720 --> 00:01:07,370
It'll be pretty quick.

17
00:01:07,370 --> 00:01:15,220
So I'm going to provide an API version of V-1 or provide a kind of service or meta data we're going

18
00:01:15,220 --> 00:01:18,240
to specify the name of this service or this object.

19
00:01:18,400 --> 00:01:26,800
And I'm going to use a name of server cluster IP service like the name we will provide a spec that's

20
00:01:26,800 --> 00:01:31,360
going to customize exactly how this server behaves or see how the service behaves.

21
00:01:31,360 --> 00:01:38,080
So we're going to specify a type of service of cluster IP and then we need to provide a selector that's

22
00:01:38,080 --> 00:01:42,980
going to tell the service exactly what set of pods it's supposed to provide access to.

23
00:01:43,030 --> 00:01:47,140
And so of course the cluster IP that we're putting together right now is supposed to provide access

24
00:01:47,140 --> 00:01:54,440
to all the multi server pods in just the last section when we put together the server deployment file.

25
00:01:54,510 --> 00:02:02,050
We had assigned each of those pods a label of component server and so inside of our server cluster IP

26
00:02:02,050 --> 00:02:09,040
service we're going to want to specify a selector of component server Tobacco-Free Here I'll provide

27
00:02:09,040 --> 00:02:13,750
a selector of component server.

28
00:02:13,950 --> 00:02:16,180
And then finally very similar to what we did last time.

29
00:02:16,200 --> 00:02:21,510
We're going to make sure that we specify the ports that the service is going to kind of mitigate control

30
00:02:21,510 --> 00:02:23,220
over or men control over.

31
00:02:23,220 --> 00:02:26,230
So just as before we're going to just send everything through.

32
00:02:26,340 --> 00:02:31,500
And as a reminder the multis server image listens for traffic on port five thousand.

33
00:02:31,770 --> 00:02:42,900
So we're going to provide our ports with a port of 5000 and a target port of 5000 as well just as we

34
00:02:42,900 --> 00:02:46,350
did inside of our previous service OK.

35
00:02:46,360 --> 00:02:47,100
So that's it.

36
00:02:47,140 --> 00:02:48,000
That's all we have to do.

37
00:02:48,000 --> 00:02:53,160
To put together our cluster IPs service that's going to govern or manage access to our running express

38
00:02:53,170 --> 00:02:54,090
API.

39
00:02:54,400 --> 00:02:56,410
So let's take a quick pause right here.

40
00:02:56,410 --> 00:03:02,830
I want to address one little side topic and then we'll continue with a couple more config files or the

41
00:03:02,920 --> 00:03:05,570
rest of all the objects inside of our application.

42
00:03:05,650 --> 00:03:07,450
So quick pause and I'll see you in just a minute.
