1
00:00:04,680 --> 00:00:05,190
Great.

2
00:00:05,220 --> 00:00:09,490
Now let's try to connect to one of the ports, for instance, this one.

3
00:00:09,510 --> 00:00:11,190
Let's grab its IP address.

4
00:00:11,190 --> 00:00:17,580
And before we already tried to connect to one of the ports from our local computer and again, our local

5
00:00:17,580 --> 00:00:21,250
computer is external relative to Kubernetes cluster.

6
00:00:21,270 --> 00:00:23,160
It is very, very important.

7
00:00:23,910 --> 00:00:27,200
Let's try to connect to this IP address, see URL and paste.

8
00:00:27,220 --> 00:00:30,420
IP address and connection is not successful.

9
00:00:30,780 --> 00:00:37,710
Let's now go inside of the node mini cube node and try to connect to this port, any of those ports

10
00:00:37,710 --> 00:00:39,600
from inside of the node.

11
00:00:39,810 --> 00:00:44,310
And it will mean that we are trying to connect to the port inside of the cluster.

12
00:00:45,210 --> 00:00:54,210
Let's S-H again to our mini cube node as a sage docker add and this IP address.

13
00:00:55,940 --> 00:00:58,760
In your case, the sap is of course different.

14
00:00:58,850 --> 00:01:00,740
Password is TSI user.

15
00:01:02,050 --> 00:01:07,900
And now here, let's see your URL and enter IP address of one of the ports.

16
00:01:07,930 --> 00:01:09,820
Any port works here.

17
00:01:10,000 --> 00:01:11,620
So let's see your URL.

18
00:01:11,620 --> 00:01:15,820
And I was able to connect to specific port by its IP address.

19
00:01:16,360 --> 00:01:19,630
Let's try to connect to another port with another IP.

20
00:01:19,720 --> 00:01:22,390
For instance, let's try 0.3.

21
00:01:22,420 --> 00:01:24,710
I'm not sure whether I have such port running.

22
00:01:24,730 --> 00:01:25,780
Yes, I have.

23
00:01:25,840 --> 00:01:33,640
And I also got response from such port with such IP address that now I'm located inside of the node

24
00:01:33,730 --> 00:01:41,320
and I am able to connect to ports which are running on this specific node using IP addresses of those

25
00:01:41,320 --> 00:01:41,860
ports.

26
00:01:42,280 --> 00:01:47,380
Let's exit from this node and again, let's list ports along with IP addresses.

27
00:01:47,380 --> 00:01:52,240
So I was able to connect to this port and this port from the node.

28
00:01:53,110 --> 00:02:01,120
But of course such IP addresses are assigned to both dynamically when new posts are created and you

29
00:02:01,120 --> 00:02:06,970
should not rely on IP addresses of the ports if you would like to connect to a specific port.

30
00:02:07,840 --> 00:02:14,500
Therefore, it's not convenient to utilize such IP addresses and you should utilize some sort of other

31
00:02:14,500 --> 00:02:22,840
IP addresses which are managed by Kubernetes and which allow you to connect to any of the ports inside

32
00:02:22,840 --> 00:02:23,830
of the deployment.

