1
00:00:02,220 --> 00:00:05,390
And that is it for this module.

2
00:00:05,390 --> 00:00:07,939
We had a look at all the important scenarios

3
00:00:07,939 --> 00:00:11,030
when it comes to containers and pods interacting

4
00:00:11,030 --> 00:00:13,590
with the Java and the outside world.

5
00:00:13,590 --> 00:00:17,000
We had a look at pod internal communication

6
00:00:17,000 --> 00:00:18,550
through local host.

7
00:00:18,550 --> 00:00:22,300
This special address which you can use if two containers

8
00:00:22,300 --> 00:00:26,040
are running in the same pod and one container wants to send

9
00:00:26,040 --> 00:00:28,053
a request to the other container.

10
00:00:29,210 --> 00:00:32,479
We had a look at outside world communication

11
00:00:32,479 --> 00:00:34,130
with type load balancer.

12
00:00:34,130 --> 00:00:37,770
So, by creating such a service of type load balancer.

13
00:00:37,770 --> 00:00:40,450
We had another look at services in general

14
00:00:40,450 --> 00:00:45,450
but we also had a look at cluster internal communication.

15
00:00:45,720 --> 00:00:48,480
When we want to ensure that we actually

16
00:00:48,480 --> 00:00:51,580
have multiple pods talk to each other

17
00:00:51,580 --> 00:00:54,500
and maybe some pod is also only reachable

18
00:00:54,500 --> 00:00:56,310
from inside the cluster.

19
00:00:56,310 --> 00:00:58,540
We learned that we can achieve this

20
00:00:58,540 --> 00:01:01,360
by creating a service of type cluster IP

21
00:01:01,360 --> 00:01:04,470
which also has some automatic load balancing built in

22
00:01:04,470 --> 00:01:08,270
as I mentioned and TB10 can either look up

23
00:01:08,270 --> 00:01:11,680
the IP address manually

24
00:01:11,680 --> 00:01:14,310
or that we use this automatically generated

25
00:01:14,310 --> 00:01:17,190
cluster internal domain name

26
00:01:17,190 --> 00:01:18,712
or that we use the automatically generated

27
00:01:18,712 --> 00:01:23,712
environment variables which Kubernetes gives us.

28
00:01:24,550 --> 00:01:27,630
And this allows us to really enable exactly

29
00:01:27,630 --> 00:01:30,320
the setup and the communication we need

30
00:01:30,320 --> 00:01:33,140
in our deployed application.

31
00:01:33,140 --> 00:01:36,930
We can lock down what we wanna lock down

32
00:01:36,930 --> 00:01:40,600
and for example, ensure that the Auth API

33
00:01:40,600 --> 00:01:43,270
simply can't be reached from outside

34
00:01:43,270 --> 00:01:46,950
and we can still implement all the communication we need

35
00:01:46,950 --> 00:01:50,733
with all the tools I showed you throughout this module.