WEBVTT 00:01.170 --> 00:02.050 Okay. 00:02.060 --> 00:02.869 In this lab, 00:02.880 --> 00:06.510 we will be installing Weave Net POD networking solution to the cluster 00:06.520 --> 00:09.170 so let us first inspect the setup. 00:10.290 --> 00:12.050 We've deployed an application called app. 00:12.139 --> 00:13.720 Let's check that out. 00:15.472 --> 00:17.410 Kubectl get PODs. 00:18.500 --> 00:21.968 We have app and the status is container creating. 00:23.960 --> 00:25.560 What is the state of the POD? 00:25.648 --> 00:27.136 It's not running. 00:28.040 --> 00:30.840 Still in a container creating state so it's not running. 00:33.840 --> 00:35.470 Inspect why the POD is not running. 00:35.559 --> 00:39.590 Let's do a kubectl describe POD app. 00:41.240 --> 00:47.500 We see that it's failed to create a POD sandbox and network for POD, 00:47.510 --> 00:49.560 network plugins, cni failed to set up POD. 00:50.040 --> 00:52.490 Basically, it looks like there's a network issue. 00:53.530 --> 00:56.520 The network plugin cni failed to teardown POD network. 00:57.920 --> 01:00.720 It's not because it's faulty start, wrong image, or node failed, 01:00.760 --> 01:03.470 it's because there's no network configured. 01:07.440 --> 01:10.670 Let's deploy a view net networking solution to the cluster. 01:12.350 --> 01:13.460 Let's do that now. 01:15.136 --> 01:17.504 I remember to replace the default IP address 01:18.110 --> 01:23.936 and subnet of Weave Net to 10.50.0.0/16. 01:24.670 --> 01:27.360 Let's look at the Weave Net installation guide. 01:27.480 --> 01:29.600 We're going to go to the Weave works 01:30.576 --> 01:31.730 installation documentation, 01:31.750 --> 01:36.540 and then we're going to use the installation guide here. 01:38.270 --> 01:44.860 Basically, it's just the command that can help us install weave works. 01:51.920 --> 01:53.260 Let's do that right now. 01:56.090 --> 01:58.950 Now, one of the things that's mentioned here 01:58.960 --> 02:03.632 is to use the IP range 10.50.0.0/16. 02:04.109 --> 02:06.059 If you look at the solution given here, 02:07.100 --> 02:10.870 we'll see that the reason that we're asking that to be done 02:10.880 --> 02:14.780 is because the Weave Net default subnet 02:14.800 --> 02:23.060 that it uses for the POD network is 10.32.0.0/12, and that will overlap 02:23.070 --> 02:26.760 with the cluster IP range that's configured. 02:28.220 --> 02:29.850 What we're going to do is we're going to specify 02:29.860 --> 02:32.570 this IP allocation range, 02:32.580 --> 02:33.889 which is a new range. 02:34.800 --> 02:38.192 You have to add that at the end of this command like this. 02:38.496 --> 02:41.870 We're going to copy this. 02:41.900 --> 02:42.900 Paste it right here. 02:45.240 --> 02:47.150 We're running the same kubectl apply command, 02:47.632 --> 02:51.080 but at the end, we're appending this IP allocation range. 02:52.980 --> 02:53.980 Let's give that a shot. 02:55.610 --> 03:01.472 Now, let's check the status of the weave POD. 03:05.360 --> 03:07.410 We see that the Weave Net POD is running. 03:08.290 --> 03:14.000 Let's check the status of the app POD and the app POD is now running as well. 03:17.690 --> 03:17.920 Okay. 03:17.930 --> 03:18.930 That's successful. 03:19.320 --> 03:25.920 This was a lab to just demonstrate the installation of a network solution 03:26.730 --> 03:30.380 and that happens to be Weave in this case and because we've talked about weave, 03:30.460 --> 03:31.810 but this could be anything. 03:32.540 --> 03:34.090 From an exam perspective, 03:34.170 --> 03:37.480 you don't really have to worry about going to the Weave documentation pages 03:37.490 --> 03:40.190 because as part of the exam, 03:40.200 --> 03:43.920 you're not allowed to go outside of the Kubernetes documentation pages, 03:44.170 --> 03:47.520 so you can safely assume that it's going to be something 03:47.530 --> 03:50.304 that's within the Kubernetes documentation pages.