1
00:00:04,470 --> 00:00:11,370
In Kubernetes, you have to create so called services if you would like to connect to specific deployments

2
00:00:11,370 --> 00:00:18,690
using specific IP addresses and there are different options available, you could create so called cluster

3
00:00:18,690 --> 00:00:26,130
IP, and such a IP address will be created and assigned to specific deployment and you will be able

4
00:00:26,130 --> 00:00:33,060
to connect to this specific deployment only inside of the cluster using this virtual IP address.

5
00:00:33,450 --> 00:00:40,530
And Kubernetes will distribute load across different ports which are assigned to specific deployment.

6
00:00:41,130 --> 00:00:46,830
But please note that such IP address will be just a single IP address for entire deployment.

7
00:00:47,890 --> 00:00:53,440
And of course it is much more convenient to use such a IP address than specific IP addresses of the

8
00:00:53,440 --> 00:00:55,210
ports as we just tried.

9
00:00:55,960 --> 00:01:04,360
Also, there was an option to create external IP addresses to open deployment to outside world, and

10
00:01:04,360 --> 00:01:14,490
it is possible to expose specific deployment to the IP address of the node or use a load balancer or

11
00:01:14,500 --> 00:01:17,100
kept it inside of the Kubernetes cluster.

12
00:01:17,110 --> 00:01:22,510
It is possible to have multiple nodes and ports could be distributed across different nodes.

13
00:01:23,020 --> 00:01:29,860
Therefore, the most common solution is to have a load balancer IP address, which will be just single

14
00:01:29,860 --> 00:01:33,400
for entire Kubernetes cluster for specific deployment.

15
00:01:33,610 --> 00:01:40,330
And you will be able to connect to your deployment no matter where our ports are created using just

16
00:01:40,330 --> 00:01:42,370
a single external IP address.

17
00:01:42,700 --> 00:01:49,360
But such load balancer IP addresses are usually assigned by specific cloud provider like Amazon Web

18
00:01:49,360 --> 00:01:56,020
Services or Google Cloud, and such assignments are managed by Cloud Controller Manager.

19
00:01:56,020 --> 00:01:58,840
It is service which is running on the master node.