1

00:00:00,420 --> 00:00:05,080

In the solution we do we will further explore networking that we've CNI.



2

00:00:05,730 --> 00:00:09,380

So the first question, we have to identify the number of nodes in this cluster.



3

00:00:09,390 --> 00:00:11,460

So let's try and get nodes.



4

00:00:14,090 --> 00:00:17,550

And here we can see that, including master, there are three volcanoes.



5

00:00:17,570 --> 00:00:19,640

So the answer is for.



6

00:00:22,040 --> 00:00:24,380

What is the networking solution using the cluster?



7

00:00:27,970 --> 00:00:33,310

So let's run CD, slash EDC and I.



8

00:00:34,350 --> 00:00:41,140

And Matadi and here will look at the configuration and the name of the configuration as standards,



9

00:00:41,170 --> 00:00:46,470

we've got Consulars, which is the configuration of files for Veev Cianni.



10

00:00:48,340 --> 00:00:50,500

So our answer is we've.



11

00:00:53,130 --> 00:00:55,870

How many agents officers are deployed in the cluster?



12

00:00:55,890 --> 00:01:00,750

So this is run as a demon set, so it should be running on all for naught, but let's inspect that anyway.



13

00:01:00,750 --> 00:01:02,880

So I'm going to run, keep still, get parts.



14

00:01:02,880 --> 00:01:06,600

Duchaine keep system and grip for leave.



15

00:01:07,200 --> 00:01:11,140

But I'm also using natural light so that it brings the new names and the IP address.



16

00:01:11,160 --> 00:01:17,250

So here we have four parts for weave and they're running on all all nodes.



17

00:01:17,250 --> 00:01:20,520

Master nodes are one of the two and three.



18

00:01:21,930 --> 00:01:22,680

Answers for.



19

00:01:24,300 --> 00:01:29,550

On this note, our David Pierce president, so we already saw that it is running on every note.



20

00:01:30,910 --> 00:01:37,420

Identify the name of the bridge network or interface created by Veev on each node so we can inspect



21

00:01:37,420 --> 00:01:40,390

this on the Mustonen by running if confect.



22

00:01:42,430 --> 00:01:49,210

So I'm going to try and avoid conflict and look for a weave, an interface created by V4, which should



23

00:01:49,210 --> 00:01:51,080

also be typically the same name.



24

00:01:51,100 --> 00:01:55,600

So if you scroll to the bottom here, you'll see the interface by the name of VIF.



25

00:01:58,900 --> 00:02:01,900

What is the IP address range configured by Veve?



26

00:02:03,410 --> 00:02:08,030

So there are, again, different ways to do this, we can look at the configuration file used by the



27

00:02:08,030 --> 00:02:09,260

V4, Demon said.



28

00:02:11,040 --> 00:02:18,290

But we can also look at the IP address, which is used by the bridge, our interface, and here at a



29

00:02:18,300 --> 00:02:20,280

standard 30 2.0 dot one.



30

00:02:23,150 --> 00:02:29,220

I went to an IP address of which will show me the exact same output, but just for the Web interface.



31

00:02:29,240 --> 00:02:33,140

So at a standard 32 zero dot one 12.



32

00:02:35,770 --> 00:02:40,200

So here we do not have any answer which matches that exact range except 14..



33

00:02:40,240 --> 00:02:41,590

Excellent, excellent Ekso.



34

00:02:41,620 --> 00:02:43,260

We are going to select that as our answer.



35

00:02:45,610 --> 00:02:49,570

What is the default gateway configured on Paul's schedule on those little three?



36

00:02:50,560 --> 00:02:56,770

So for this to work, we'll have to schedule a part specifically on the workload, not zero three,



37

00:02:57,520 --> 00:03:01,960

and to do this, we will first create a YAML definition file using ducktail children.



38

00:03:01,970 --> 00:03:05,020

And I'm going to use the Xbox as an example part here.



39

00:03:05,950 --> 00:03:10,390

So let's use Bazzy Box with the same image name.



40

00:03:11,400 --> 00:03:18,240

And let's add a command so that the container or the pod sleeps for a thousand seconds, so we are going



41

00:03:18,240 --> 00:03:25,470

to add sleep one thousand and then we'll use that as a dry run as equal to client and actual YAML file



42

00:03:25,980 --> 00:03:26,580

YAML.



43

00:03:27,510 --> 00:03:32,280

To redirect the definition to a file called Baudot YAML.



44

00:03:33,690 --> 00:03:42,090

So now let's edit this YAML file and we'll add a note name here so that it is specifically scheduled



45

00:03:42,090 --> 00:03:43,500

on neutral three.



46

00:03:46,550 --> 00:03:49,310

And once that is done, going to save an exit.



47

00:03:51,400 --> 00:03:57,910

And we can run Cube still applied f baudot yaml to create that pod.



48

00:03:59,290 --> 00:04:03,820

Now, once the pot is running, we can use your exec to.



49

00:04:05,050 --> 00:04:12,340

Get into the pot and we'll use Shell such as Basche or as Etch the Shell.



50

00:04:14,460 --> 00:04:19,410

And then we will run, so in this case, Bashar is not available, so let's run as Etch and said.



51

00:04:19,410 --> 00:04:28,320

So once we are inside a container running on the port, we can run IP space are to get the IP wrote



52

00:04:28,350 --> 00:04:29,550

of this port.



53

00:04:29,550 --> 00:04:37,310

And here we can see that the default is where 10 dot 38, not 0.01, and it's using the zero interface.



54

00:04:37,320 --> 00:04:42,540

So that should be our answer and not thirty a node 2.0.



55

00:04:43,740 --> 00:04:44,910

That was the last question.



56

00:04:45,540 --> 00:04:49,050

Thank you for joining me and the solution we do, we'll see in the next one.