1
00:00:04,680 --> 00:00:11,670
And such a resolution of the service name to IP address is performed by internal service of the Kubernetes,

2
00:00:11,670 --> 00:00:13,320
which is called DNS.

3
00:00:13,650 --> 00:00:15,970
And we could actually verify that quickly.

4
00:00:15,990 --> 00:00:23,070
Let's go to the terminal, for example, here, and that we could still get a list of the ports, get

5
00:00:23,070 --> 00:00:31,320
ports, and now we could take any of the ports and execute the any commands inside of the running container

6
00:00:31,320 --> 00:00:35,020
inside of the port using cube ctrl exec command.

7
00:00:35,040 --> 00:00:38,400
This command is very similar to Docker Exec Command.

8
00:00:38,700 --> 00:00:45,840
Let's now take the name of any port which belongs to K as web to engine deployment.

9
00:00:45,870 --> 00:00:47,220
Let me copy this name.

10
00:00:47,220 --> 00:00:54,510
In your case, names will be completely different and let me clear our terminal here and enter k exec.

11
00:00:54,540 --> 00:00:56,340
Here will be name of the port.

12
00:00:56,370 --> 00:00:58,140
Next will be two dashes.

13
00:00:58,680 --> 00:01:04,470
And afterwards let's type and s look up and things like that.

14
00:01:04,830 --> 00:01:06,000
Let's press enter.

15
00:01:06,450 --> 00:01:08,610
And I got following response.

16
00:01:09,210 --> 00:01:10,350
What does it mean?

17
00:01:10,440 --> 00:01:19,560
Using this command, we tried to resolve engine x name from inside of the container, which belongs

18
00:01:19,560 --> 00:01:20,580
to this port.

19
00:01:21,180 --> 00:01:23,730
And such resolution was successful.

20
00:01:24,210 --> 00:01:32,700
And this IP address which I got from the DNS server when I made request and let's look up in Genesis.

21
00:01:33,270 --> 00:01:35,790
But where does this IP come from?

22
00:01:36,420 --> 00:01:39,780
Let's write K get as we see.

23
00:01:41,010 --> 00:01:47,340
And here I get such IP and notice that this IP is the same as this one.

24
00:01:48,200 --> 00:01:50,030
And that's what I told you.

25
00:01:51,030 --> 00:01:59,220
Now Kubernetes is able to resolve name of the service to corresponding cluster IP.

26
00:01:59,610 --> 00:02:01,590
And that's what we see here.

27
00:02:01,800 --> 00:02:09,389
And we performed resolution inside of the port, which belongs to our deployment and other service.

28
00:02:11,940 --> 00:02:16,830
And of course, I could execute a similarly command in one of the ports.

29
00:02:16,830 --> 00:02:28,470
For example, I could type here, we get this queue or desk and here type HTTP and gen x and this will

30
00:02:28,470 --> 00:02:35,220
actually connect to an index server and retrieve from it root web page.

31
00:02:35,460 --> 00:02:36,360
Let's try it.

32
00:02:37,560 --> 00:02:42,720
And I successfully received a response from one of the engine exports.

33
00:02:43,350 --> 00:02:45,360
And here was again, web page.