1

00:00:00,560 --> 00:00:07,400

This is the solution video for the servers, Networking Lab. So the first question we have to identify



2

00:00:07,400 --> 00:00:10,980

the network range of the nodes which are part of this cluster.



3

00:00:11,930 --> 00:00:17,300

So in the terminal, let's run Kubek to get nodes or wide.



4

00:00:18,340 --> 00:00:25,510

This will give us the IP address of both the north, so we have two nodes, Masra, another one, and



5

00:00:25,510 --> 00:00:30,870

the internal IP address starts with one seventy to 17, zero twenty four and twenty seven.



6

00:00:31,330 --> 00:00:38,170

So let us look at the side range for this network, which makes use of industry, as we saw in one of



7

00:00:38,170 --> 00:00:41,270

the labs earlier, for a node to note communication.



8

00:00:41,620 --> 00:00:44,530

And here we can see that it's using 16.



9

00:00:45,470 --> 00:00:54,710

And it begins with 172 dots, 17, not zero, so most appropriate answer here is 117 to dot 17 or zero



10

00:00:54,710 --> 00:00:58,940

zero, which is the exact network, and slash 16 as the Seiter.



11

00:01:00,220 --> 00:01:04,730

What is the range of IP address configured for ports on this cluster?



12

00:01:05,410 --> 00:01:09,510

So this is specifically for the port, not the nodes itself.



13

00:01:14,520 --> 00:01:19,980

So to take this, we can we can see the configuration of the IV plug in port.



14

00:01:24,420 --> 00:01:28,080

So I'm going to run Cube CTL log's.



15

00:01:32,990 --> 00:01:40,700

For the evening at port and inside, we have a container called Veve, so if we open up the logs for



16

00:01:40,710 --> 00:01:45,600

this, we should see the IP allocation range somewhere here.



17

00:01:45,620 --> 00:01:48,800

So if you scroll to the very top, you see that epilog range.



18

00:01:49,730 --> 00:01:51,050

Is set to.



19

00:01:53,620 --> 00:01:56,920

Then today, 2.0 slashed 12.



20

00:01:58,150 --> 00:01:59,500

So that's one way of doing it.



21

00:01:59,530 --> 00:02:05,180

We can also look up at the configuration for we've but in this case, this is the most appropriate answer.



22

00:02:05,590 --> 00:02:06,590

So we'll go with that.



23

00:02:07,060 --> 00:02:10,790

What is the IP range configured for these services within the cluster?



24

00:02:10,810 --> 00:02:12,700

So in this case, we are looking at services.



25

00:02:12,700 --> 00:02:14,820

We have already checked node and ports.



26

00:02:15,640 --> 00:02:17,850

So let's look at services for this.



27

00:02:17,860 --> 00:02:24,680

Another easy way to do it is to check the address range, which is configured and like API server.



28

00:02:24,700 --> 00:02:30,810

So I'm going to open up this definition file for Kuepper Server using Viator.



29

00:02:31,210 --> 00:02:37,540

And if you scroll all the way to the bottom or in the command section, we should see the service address



30

00:02:37,540 --> 00:02:37,940

range.



31

00:02:38,650 --> 00:02:44,470

So here these service cluster IP range is standard 96 dot zero zero, slash 12.



32

00:02:45,910 --> 00:02:46,960

So let's let that.



33

00:02:50,130 --> 00:02:56,190

How many proxy ports are deployed in this cluster, so the proxy is typically Iran as a demon's head



34

00:02:56,190 --> 00:02:56,660

as well.



35

00:03:06,220 --> 00:03:08,890

So you can see that we have two parts running.



36

00:03:11,390 --> 00:03:15,080

What type of proxy is proxy configured to use?



37

00:03:15,830 --> 00:03:21,590

We know that by default it makes use of IP table genes, but we can validate that.



38

00:03:25,200 --> 00:03:26,970

Again, let's look at the logs.



39

00:03:28,830 --> 00:03:34,000

RFQ proxy, so let's select one of the pods here so we'll make use of the common cube CTO.



40

00:03:34,980 --> 00:03:39,780

Nash and cube system logs and the Q proxy part.



41

00:03:42,860 --> 00:03:47,980

So if you see the first line, it is assuming IAPT was proxy, so that's our answer.



42

00:03:52,420 --> 00:03:58,150

And for the last question, we have to answer this, how does the scoop, when it is close to ensure



43

00:03:58,150 --> 00:04:01,430

that a proxy pot runs on all nodes in the cluster?



44

00:04:01,450 --> 00:04:08,290

So we already discussed that Q proxy Iran as a demon said, but we can validate that on the terminal



45

00:04:08,290 --> 00:04:13,360

by Iran and Cuba, still get assets in the system namespace.



46

00:04:18,130 --> 00:04:24,550

And here we can see that your proxy is in the list and it does not require us to decide parts of it



47

00:04:24,550 --> 00:04:26,200

to our current and to already.



48

00:04:27,560 --> 00:04:30,830

So the answer is using a demon set.



49

00:04:31,490 --> 00:04:32,820

So that was the last question.



50

00:04:32,840 --> 00:04:35,160

Thank you for joining me in this video.



51

00:04:35,180 --> 00:04:36,200

Also in the next one.