WEBVTT 00:00.450 --> 00:05.960 Hello and welcome to this lecture and this lecture we discussed about IP address management. 00:06.270 --> 00:09.420 So how does IP address management work and cobra. 00:09.420 --> 00:15.160 Notice this section does not concern the IP address assigned to the nodes in the network. 00:15.240 --> 00:20.210 We can manage that on your own or with your own external Pam solutions. 00:20.250 --> 00:26.970 What this section covers is however the word tool brutes networks and the nodes assigned an IP subnet. 00:27.150 --> 00:29.930 And how are the parts assigned an IP. 00:29.980 --> 00:37.290 Where is this information stored and who is responsible for ensuring there are no duplicate IP is assigned. 00:37.290 --> 00:39.010 Let's start with The Who. 00:39.150 --> 00:45.930 Let's ask CNI as they're the ones who define the standards CNI says it is the responsibility of the 00:45.930 --> 00:52.800 CNI plug in the network solution provider to take care of assigning IP to the containers. 00:52.800 --> 00:55.170 Remember the basic plugin we built earlier. 00:55.320 --> 00:59.670 We actually took care of assigning IP addresses within this plugin. 00:59.670 --> 01:03.640 There was a section for assigning IP to the container network namespace. 01:03.750 --> 01:09.090 But how do we manage these APIs competent is doesn't care how we do it. 01:09.090 --> 01:15.540 We just need to do it by making sure we don't assign any duplicate APIs and manage it properly. 01:15.540 --> 01:21.240 An easy way to do it is to store the list of APIs in a file and make sure we have necessary code in 01:21.240 --> 01:24.270 our script to manage this file properly. 01:24.270 --> 01:31.200 This file would be placed on each host and manages the APIs of parts on those notes instead of coding 01:31.200 --> 01:38.310 that ourselves in our script CNI comes with two built in plugins to which you can outsource this task 01:38.340 --> 01:39.230 to. 01:39.230 --> 01:44.890 In this case the plugin that implements the approach that we followed for managing the IP addresses 01:44.940 --> 01:53.160 locally on each host is the host local plugin but is still our responsibility to invoke that plugin 01:53.220 --> 01:59.160 in our script or we can make our script dynamic to support different kinds of plugins. 01:59.220 --> 02:06.480 The CNI configuration file has a section called APM in which we can specify the type of plug in to be 02:06.480 --> 02:10.200 used the subnet and route to be used. 02:10.200 --> 02:15.750 This details can be read from our script to invoke the appropriate plugin instead of hard coding it 02:15.750 --> 02:21.750 to use hosted local every time different network solution providers does it differently. 02:21.750 --> 02:25.110 Let's see how we works managers IP addresses. 02:25.110 --> 02:30.500 In fact you have seen some of the APIs assigned by Reef in the previous practice test. 02:30.580 --> 02:38.290 We've by default allocates the appearance tender to 0 0 0 slash twelve for the entire network. 02:38.370 --> 02:47.110 That gives the network IP from range tender 32 of 0 1 to 10 not 47 not 255 but 254. 02:47.190 --> 02:52.160 That's about a million APIs that you can use for part on the network from this range. 02:52.230 --> 02:59.100 The peers decide to split the IP addresses equally between them and assigns one portion to each node 02:59.850 --> 03:00.750 pods created. 03:00.750 --> 03:03.840 On this note we'll have is in this range. 03:03.840 --> 03:09.840 Of course these ranges are configurable with additional options past while deploying the weave plug 03:09.840 --> 03:11.230 into a cluster. 03:11.490 --> 03:13.490 Well for this lecture. 03:13.500 --> 03:20.700 Head over to the practice test and explore a pan in the weave CNI plugin.