1
00:00:05,130 --> 00:00:07,890
So let's also check ports.

2
00:00:07,980 --> 00:00:09,540
K get ports.

3
00:00:11,150 --> 00:00:14,390
Some of the boats are running and one is still pending.

4
00:00:14,390 --> 00:00:22,970
And now we are able to test our setup and try to connect from web application, from Web deployment

5
00:00:22,970 --> 00:00:24,590
to engine deployment.

6
00:00:25,160 --> 00:00:32,840
Let's open connection to our Web service deployment because we used here a load balancer type for this

7
00:00:32,840 --> 00:00:39,800
service and we could utilize this port here and IP address of the Kubernetes node.

8
00:00:40,280 --> 00:00:47,720
We kept that in order to quickly get a URL for specific deployment using mini cube, you could enter

9
00:00:47,720 --> 00:00:56,540
command, mini cube service and here we'll be name of the service k8s web two and Genesis.

10
00:01:00,380 --> 00:01:08,660
Web browser page was opened and we got response from one of the posts which belongs to k8s web to engine

11
00:01:08,870 --> 00:01:09,890
deployment.

12
00:01:10,130 --> 00:01:14,000
And here was name of the corresponding replica set.

13
00:01:15,350 --> 00:01:16,000
All right.

14
00:01:16,010 --> 00:01:19,250
We just triggered a connection to route URL.

15
00:01:19,520 --> 00:01:22,140
Let's go back quickly to our application.

16
00:01:22,160 --> 00:01:30,310
Let me hide this terminal here and let's go to this new application and open index, both file and request

17
00:01:30,320 --> 00:01:38,510
that here we have two endpoints root endpoint and slash and endpoint, which will essentially send request

18
00:01:38,510 --> 00:01:47,540
to engineers your well, this one and return back to the client proxy response from our other server.

19
00:01:47,780 --> 00:01:54,740
This server is external relative to this server where we are running this web application.

20
00:01:54,740 --> 00:01:58,580
We just received this string from the server.

21
00:01:58,610 --> 00:02:01,520
Let's not try to connect to an endpoint.

22
00:02:01,910 --> 00:02:04,700
Let's go back to web browser and add here.

23
00:02:06,330 --> 00:02:07,470
Slash and J.

24
00:02:07,480 --> 00:02:07,980
Nicks.

25
00:02:09,080 --> 00:02:10,100
Press enter.

26
00:02:10,100 --> 00:02:12,800
And what I got, I got.

27
00:02:12,830 --> 00:02:14,510
Welcome to N Jennings.

28
00:02:15,530 --> 00:02:25,340
It means that the response from the Phoenix Sarah was broadcast successfully inside of the server,

29
00:02:25,340 --> 00:02:27,560
which belongs to our web deployment.

30
00:02:28,990 --> 00:02:34,930
And we were able in such a way to connect from one deployment to another deployment.

31
00:02:36,110 --> 00:02:38,450
By the name of another service.

32
00:02:38,450 --> 00:02:44,150
So NCLEX here is the name of another service as we specified here.

33
00:02:44,780 --> 00:02:48,230
And such service has no cluster IP.

34
00:02:49,790 --> 00:02:51,680
They get, as we see.

35
00:02:53,030 --> 00:02:57,290
So here is cluster IP for angelic service.

36
00:02:58,080 --> 00:03:04,260
And we were able to connect to another deployment by name of the service.

37
00:03:05,340 --> 00:03:10,110
That's how you could very easily connect different deployments together.