1
00:00:00,450 --> 00:00:05,960
Hello and welcome to this lecture and this lecture we discussed about IP address management.

2
00:00:06,270 --> 00:00:09,420
So how does IP address management work and cobra.

3
00:00:09,420 --> 00:00:15,160
Notice this section does not concern the IP address assigned to the nodes in the network.

4
00:00:15,240 --> 00:00:20,210
We can manage that on your own or with your own external Pam solutions.

5
00:00:20,250 --> 00:00:26,970
What this section covers is however the word tool brutes networks and the nodes assigned an IP subnet.

6
00:00:27,150 --> 00:00:29,930
And how are the parts assigned an IP.

7
00:00:29,980 --> 00:00:37,290
Where is this information stored and who is responsible for ensuring there are no duplicate IP is assigned.

8
00:00:37,290 --> 00:00:39,010
Let's start with The Who.

9
00:00:39,150 --> 00:00:45,930
Let's ask CNI as they're the ones who define the standards CNI says it is the responsibility of the

10
00:00:45,930 --> 00:00:52,800
CNI plug in the network solution provider to take care of assigning IP to the containers.

11
00:00:52,800 --> 00:00:55,170
Remember the basic plugin we built earlier.

12
00:00:55,320 --> 00:00:59,670
We actually took care of assigning IP addresses within this plugin.

13
00:00:59,670 --> 00:01:03,640
There was a section for assigning IP to the container network namespace.

14
00:01:03,750 --> 00:01:09,090
But how do we manage these APIs competent is doesn't care how we do it.

15
00:01:09,090 --> 00:01:15,540
We just need to do it by making sure we don't assign any duplicate APIs and manage it properly.

16
00:01:15,540 --> 00: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

17
00:01:21,240 --> 00:01:24,270
our script to manage this file properly.

18
00:01:24,270 --> 00:01:31,200
This file would be placed on each host and manages the APIs of parts on those notes instead of coding

19
00:01:31,200 --> 00:01:38,310
that ourselves in our script CNI comes with two built in plugins to which you can outsource this task

20
00:01:38,340 --> 00:01:39,230
to.

21
00:01:39,230 --> 00:01:44,890
In this case the plugin that implements the approach that we followed for managing the IP addresses

22
00:01:44,940 --> 00:01:53,160
locally on each host is the host local plugin but is still our responsibility to invoke that plugin

23
00:01:53,220 --> 00:01:59,160
in our script or we can make our script dynamic to support different kinds of plugins.

24
00:01:59,220 --> 00:02:06,480
The CNI configuration file has a section called APM in which we can specify the type of plug in to be

25
00:02:06,480 --> 00:02:10,200
used the subnet and route to be used.

26
00:02:10,200 --> 00:02:15,750
This details can be read from our script to invoke the appropriate plugin instead of hard coding it

27
00:02:15,750 --> 00:02:21,750
to use hosted local every time different network solution providers does it differently.

28
00:02:21,750 --> 00:02:25,110
Let's see how we works managers IP addresses.

29
00:02:25,110 --> 00:02:30,500
In fact you have seen some of the APIs assigned by Reef in the previous practice test.

30
00:02:30,580 --> 00:02:38,290
We've by default allocates the appearance tender to 0 0 0 slash twelve for the entire network.

31
00:02:38,370 --> 00:02:47,110
That gives the network IP from range tender 32 of 0 1 to 10 not 47 not 255 but 254.

32
00:02:47,190 --> 00:02:52,160
That's about a million APIs that you can use for part on the network from this range.

33
00:02:52,230 --> 00:02:59,100
The peers decide to split the IP addresses equally between them and assigns one portion to each node

34
00:02:59,850 --> 00:03:00,750
pods created.

35
00:03:00,750 --> 00:03:03,840
On this note we'll have is in this range.

36
00:03:03,840 --> 00:03:09,840
Of course these ranges are configurable with additional options past while deploying the weave plug

37
00:03:09,840 --> 00:03:11,230
into a cluster.

38
00:03:11,490 --> 00:03:13,490
Well for this lecture.

39
00:03:13,500 --> 00:03:20,700
Head over to the practice test and explore a pan in the weave CNI plugin.
