WEBVTT Kind: captions Language: en 00:00:00.240 --> 00:00:03.830 align:start position:0% words<00:00:00.560> to<00:00:00.719> describe<00:00:01.599> setting<00:00:02.000> up<00:00:02.159> k3s 00:00:03.830 --> 00:00:03.840 align:start position:0% words to describe setting up k3s 00:00:03.840 --> 00:00:05.590 align:start position:0% words to describe setting up k3s this<00:00:04.080> is<00:00:04.240> hard 00:00:05.590 --> 00:00:05.600 align:start position:0% this is hard 00:00:05.600 --> 00:00:08.150 align:start position:0% this is hard this<00:00:05.839> is<00:00:06.000> so<00:00:06.319> difficult<00:00:06.799> to<00:00:06.960> set<00:00:07.200> up 00:00:08.150 --> 00:00:08.160 align:start position:0% this is so difficult to set up 00:00:08.160 --> 00:00:10.390 align:start position:0% this is so difficult to set up isn't<00:00:08.400> this<00:00:08.559> overkill 00:00:10.390 --> 00:00:10.400 align:start position:0% isn't this overkill 00:00:10.400 --> 00:00:13.270 align:start position:0% isn't this overkill what<00:00:10.559> is<00:00:10.719> the<00:00:10.800> load<00:00:11.040> balancer<00:00:11.519> again 00:00:13.270 --> 00:00:13.280 align:start position:0% what is the load balancer again 00:00:13.280 --> 00:00:16.390 align:start position:0% what is the load balancer again why<00:00:13.440> do<00:00:13.679> i<00:00:13.759> need<00:00:14.080> two<00:00:14.320> load<00:00:14.559> balancers 00:00:16.390 --> 00:00:16.400 align:start position:0% why do i need two load balancers 00:00:16.400 --> 00:00:18.230 align:start position:0% why do i need two load balancers should<00:00:16.560> i<00:00:16.720> use<00:00:16.880> that<00:00:17.039> cd 00:00:18.230 --> 00:00:18.240 align:start position:0% should i use that cd 00:00:18.240 --> 00:00:20.870 align:start position:0% should i use that cd so<00:00:18.480> wait<00:00:18.880> i<00:00:19.039> need<00:00:19.359> two<00:00:19.600> load<00:00:19.840> balancers<00:00:20.640> and 00:00:20.870 --> 00:00:20.880 align:start position:0% so wait i need two load balancers and 00:00:20.880 --> 00:00:22.870 align:start position:0% so wait i need two load balancers and keep<00:00:21.039> alive<00:00:21.439> d 00:00:22.870 --> 00:00:22.880 align:start position:0% keep alive d 00:00:22.880 --> 00:00:25.429 align:start position:0% keep alive d what<00:00:23.119> is<00:00:23.279> metal<00:00:23.600> lb<00:00:24.000> again 00:00:25.429 --> 00:00:25.439 align:start position:0% what is metal lb again 00:00:25.439 --> 00:00:27.670 align:start position:0% what is metal lb again have<00:00:25.599> you<00:00:25.680> heard<00:00:25.920> of<00:00:26.000> cubevip 00:00:27.670 --> 00:00:27.680 align:start position:0% have you heard of cubevip 00:00:27.680 --> 00:00:33.190 align:start position:0% have you heard of cubevip um<00:00:28.480> isn't<00:00:28.720> that<00:00:28.880> a<00:00:28.960> single<00:00:29.199> point<00:00:29.439> of<00:00:29.519> failure 00:00:33.190 --> 00:00:33.200 align:start position:0% 00:00:33.200 --> 00:00:34.389 align:start position:0% i<00:00:33.440> know 00:00:34.389 --> 00:00:34.399 align:start position:0% i know 00:00:34.399 --> 00:00:36.549 align:start position:0% i know i'll<00:00:34.719> automate<00:00:35.200> the<00:00:35.280> whole<00:00:35.520> thing 00:00:36.549 --> 00:00:36.559 align:start position:0% i'll automate the whole thing 00:00:36.559 --> 00:00:39.030 align:start position:0% i'll automate the whole thing today<00:00:36.960> we're<00:00:37.200> not<00:00:37.520> only<00:00:37.760> going<00:00:37.920> to<00:00:38.000> set<00:00:38.239> up<00:00:38.399> k3s 00:00:39.030 --> 00:00:39.040 align:start position:0% today we're not only going to set up k3s 00:00:39.040 --> 00:00:41.990 align:start position:0% today we're not only going to set up k3s with<00:00:39.280> ncd<00:00:39.920> and<00:00:40.160> ha<00:00:40.640> installation<00:00:41.440> with<00:00:41.760> cube 00:00:41.990 --> 00:00:42.000 align:start position:0% with ncd and ha installation with cube 00:00:42.000 --> 00:00:44.950 align:start position:0% with ncd and ha installation with cube vip<00:00:42.480> and<00:00:42.640> middle<00:00:42.960> of<00:00:43.120> b<00:00:43.600> but<00:00:43.840> we're<00:00:44.079> also<00:00:44.719> going 00:00:44.950 --> 00:00:44.960 align:start position:0% vip and middle of b but we're also going 00:00:44.960 --> 00:00:47.110 align:start position:0% vip and middle of b but we're also going to<00:00:45.120> automate<00:00:45.680> the<00:00:45.840> whole<00:00:46.079> entire<00:00:46.480> thing<00:00:46.960> so 00:00:47.110 --> 00:00:47.120 align:start position:0% to automate the whole entire thing so 00:00:47.120 --> 00:00:49.830 align:start position:0% to automate the whole entire thing so that<00:00:47.360> we<00:00:47.840> can't<00:00:48.160> really<00:00:48.640> mess<00:00:48.960> this<00:00:49.200> up<00:00:49.600> and<00:00:49.680> so 00:00:49.830 --> 00:00:49.840 align:start position:0% that we can't really mess this up and so 00:00:49.840 --> 00:00:51.350 align:start position:0% that we can't really mess this up and so we're<00:00:50.000> going<00:00:50.079> to<00:00:50.239> fully<00:00:50.640> automate<00:00:51.120> the 00:00:51.350 --> 00:00:51.360 align:start position:0% we're going to fully automate the 00:00:51.360 --> 00:00:53.990 align:start position:0% we're going to fully automate the installation<00:00:51.920> of<00:00:52.079> k3s<00:00:52.800> so<00:00:52.960> that<00:00:53.199> it's<00:00:53.360> 100 00:00:53.990 --> 00:00:54.000 align:start position:0% installation of k3s so that it's 100 00:00:54.000 --> 00:00:55.110 align:start position:0% installation of k3s so that it's 100 repeatable 00:00:55.110 --> 00:00:55.120 align:start position:0% repeatable 00:00:55.120 --> 00:00:57.350 align:start position:0% repeatable and<00:00:55.280> then<00:00:55.600> we're<00:00:55.760> gonna<00:00:56.239> tear<00:00:56.399> it<00:00:56.559> all<00:00:56.719> down<00:00:57.199> as 00:00:57.350 --> 00:00:57.360 align:start position:0% and then we're gonna tear it all down as 00:00:57.360 --> 00:00:59.750 align:start position:0% and then we're gonna tear it all down as if<00:00:57.520> it<00:00:57.600> never<00:00:57.840> happened<00:00:58.239> but<00:00:58.480> before<00:00:58.800> we<00:00:58.960> do<00:00:59.520> a 00:00:59.750 --> 00:00:59.760 align:start position:0% if it never happened but before we do a 00:00:59.760 --> 00:01:02.389 align:start position:0% if it never happened but before we do a huge<00:01:00.160> thanks<00:01:00.559> to<00:01:00.719> our<00:01:00.879> sponsor<00:01:01.520> microcenter 00:01:02.389 --> 00:01:02.399 align:start position:0% huge thanks to our sponsor microcenter 00:01:02.399 --> 00:01:04.149 align:start position:0% huge thanks to our sponsor microcenter if<00:01:02.559> you're<00:01:02.719> thinking<00:01:03.039> of<00:01:03.120> building<00:01:03.440> a<00:01:03.520> new<00:01:03.760> pc 00:01:04.149 --> 00:01:04.159 align:start position:0% if you're thinking of building a new pc 00:01:04.159 --> 00:01:05.350 align:start position:0% if you're thinking of building a new pc you<00:01:04.400> should<00:01:04.559> look<00:01:04.720> no<00:01:04.879> further<00:01:05.199> than 00:01:05.350 --> 00:01:05.360 align:start position:0% you should look no further than 00:01:05.360 --> 00:01:06.789 align:start position:0% you should look no further than microcenter<00:01:06.080> if<00:01:06.159> you've<00:01:06.320> never<00:01:06.560> been<00:01:06.720> to 00:01:06.789 --> 00:01:06.799 align:start position:0% microcenter if you've never been to 00:01:06.799 --> 00:01:08.630 align:start position:0% microcenter if you've never been to microcenter<00:01:07.520> you're<00:01:07.760> missing<00:01:08.080> out<00:01:08.320> on<00:01:08.400> seeing 00:01:08.630 --> 00:01:08.640 align:start position:0% microcenter you're missing out on seeing 00:01:08.640 --> 00:01:10.870 align:start position:0% microcenter you're missing out on seeing a<00:01:08.720> huge<00:01:09.040> selection<00:01:09.439> of<00:01:09.600> technology<00:01:10.240> in<00:01:10.320> person 00:01:10.870 --> 00:01:10.880 align:start position:0% a huge selection of technology in person 00:01:10.880 --> 00:01:12.710 align:start position:0% a huge selection of technology in person they've<00:01:11.119> got<00:01:11.360> everything<00:01:11.760> for<00:01:11.920> custom<00:01:12.320> pc 00:01:12.710 --> 00:01:12.720 align:start position:0% they've got everything for custom pc 00:01:12.720 --> 00:01:15.030 align:start position:0% they've got everything for custom pc builders<00:01:13.200> from<00:01:13.439> ssds<00:01:14.080> and<00:01:14.159> hard<00:01:14.400> drives<00:01:14.880> to 00:01:15.030 --> 00:01:15.040 align:start position:0% builders from ssds and hard drives to 00:01:15.040 --> 00:01:17.830 align:start position:0% builders from ssds and hard drives to power<00:01:15.360> supplies<00:01:16.240> to<00:01:16.400> memory<00:01:17.119> to<00:01:17.280> air<00:01:17.680> and 00:01:17.830 --> 00:01:17.840 align:start position:0% power supplies to memory to air and 00:01:17.840 --> 00:01:20.390 align:start position:0% power supplies to memory to air and water<00:01:18.159> cooling<00:01:18.720> to<00:01:18.880> motherboards<00:01:19.920> to<00:01:20.080> video 00:01:20.390 --> 00:01:20.400 align:start position:0% water cooling to motherboards to video 00:01:20.400 --> 00:01:23.429 align:start position:0% water cooling to motherboards to video cards<00:01:21.119> to<00:01:21.280> processors<00:01:22.240> and<00:01:22.479> more<00:01:22.880> microcenter 00:01:23.429 --> 00:01:23.439 align:start position:0% cards to processors and more microcenter 00:01:23.439 --> 00:01:25.030 align:start position:0% cards to processors and more microcenter is<00:01:23.600> your<00:01:23.759> one-stop<00:01:24.240> shop<00:01:24.479> to<00:01:24.640> totally 00:01:25.030 --> 00:01:25.040 align:start position:0% is your one-stop shop to totally 00:01:25.040 --> 00:01:27.109 align:start position:0% is your one-stop shop to totally customize<00:01:25.520> your<00:01:25.680> next<00:01:25.920> pc<00:01:26.320> build<00:01:26.799> and<00:01:26.960> don't 00:01:27.109 --> 00:01:27.119 align:start position:0% customize your next pc build and don't 00:01:27.119 --> 00:01:28.789 align:start position:0% customize your next pc build and don't worry<00:01:27.520> if<00:01:27.759> it's<00:01:27.840> your<00:01:28.000> first<00:01:28.240> time<00:01:28.400> building<00:01:28.720> a 00:01:28.789 --> 00:01:28.799 align:start position:0% worry if it's your first time building a 00:01:28.799 --> 00:01:30.789 align:start position:0% worry if it's your first time building a pc<00:01:29.280> they<00:01:29.520> have<00:01:29.680> lots<00:01:29.920> of<00:01:30.079> helpful<00:01:30.560> and 00:01:30.789 --> 00:01:30.799 align:start position:0% pc they have lots of helpful and 00:01:30.799 --> 00:01:32.310 align:start position:0% pc they have lots of helpful and eligible<00:01:31.200> staff<00:01:31.520> that<00:01:31.680> are<00:01:31.840> there<00:01:32.000> to<00:01:32.159> help 00:01:32.310 --> 00:01:32.320 align:start position:0% eligible staff that are there to help 00:01:32.320 --> 00:01:33.910 align:start position:0% eligible staff that are there to help you<00:01:32.560> out<00:01:32.799> and<00:01:32.960> will<00:01:33.119> point<00:01:33.360> you<00:01:33.520> in<00:01:33.600> the<00:01:33.680> right 00:01:33.910 --> 00:01:33.920 align:start position:0% you out and will point you in the right 00:01:33.920 --> 00:01:35.749 align:start position:0% you out and will point you in the right direction<00:01:34.640> so<00:01:34.799> that<00:01:34.960> you<00:01:35.119> don't<00:01:35.360> attempt<00:01:35.680> to 00:01:35.749 --> 00:01:35.759 align:start position:0% direction so that you don't attempt to 00:01:35.759 --> 00:01:41.109 align:start position:0% direction so that you don't attempt to apply<00:01:36.159> thermal<00:01:36.479> paste<00:01:36.720> like<00:01:36.960> this 00:01:41.109 --> 00:01:41.119 align:start position:0% 00:01:41.119 --> 00:01:42.870 align:start position:0% microcenter<00:01:41.759> has<00:01:41.840> been<00:01:42.000> kind<00:01:42.240> enough<00:01:42.560> to<00:01:42.640> give 00:01:42.870 --> 00:01:42.880 align:start position:0% microcenter has been kind enough to give 00:01:42.880 --> 00:01:45.429 align:start position:0% microcenter has been kind enough to give all<00:01:43.119> new<00:01:43.360> customers<00:01:43.920> a<00:01:44.079> free<00:01:44.399> ssd<00:01:45.119> and<00:01:45.280> it's 00:01:45.429 --> 00:01:45.439 align:start position:0% all new customers a free ssd and it's 00:01:45.439 --> 00:01:47.990 align:start position:0% all new customers a free ssd and it's available<00:01:46.159> in<00:01:46.320> store<00:01:46.640> only<00:01:47.280> so<00:01:47.439> see<00:01:47.600> the<00:01:47.759> link 00:01:47.990 --> 00:01:48.000 align:start position:0% available in store only so see the link 00:01:48.000 --> 00:01:50.310 align:start position:0% available in store only so see the link in<00:01:48.079> the<00:01:48.159> description<00:01:48.720> for<00:01:48.880> details<00:01:49.759> so<00:01:50.159> how 00:01:50.310 --> 00:01:50.320 align:start position:0% in the description for details so how 00:01:50.320 --> 00:01:52.389 align:start position:0% in the description for details so how did<00:01:50.560> i<00:01:50.640> get<00:01:50.880> here<00:01:51.280> well<00:01:51.600> as<00:01:51.759> you<00:01:51.920> may<00:01:52.079> or<00:01:52.159> may 00:01:52.389 --> 00:01:52.399 align:start position:0% did i get here well as you may or may 00:01:52.399 --> 00:01:54.710 align:start position:0% did i get here well as you may or may not<00:01:52.560> know<00:01:52.880> i've<00:01:53.040> been<00:01:53.200> running<00:01:53.520> k3s<00:01:54.240> in<00:01:54.320> my<00:01:54.479> own 00:01:54.710 --> 00:01:54.720 align:start position:0% not know i've been running k3s in my own 00:01:54.720 --> 00:01:56.630 align:start position:0% not know i've been running k3s in my own environment<00:01:55.200> for<00:01:55.439> quite<00:01:55.680> some<00:01:55.920> time<00:01:56.320> and<00:01:56.479> i 00:01:56.630 --> 00:01:56.640 align:start position:0% environment for quite some time and i 00:01:56.640 --> 00:01:59.030 align:start position:0% environment for quite some time and i even<00:01:56.880> have<00:01:57.040> a<00:01:57.119> video<00:01:57.439> on<00:01:57.600> setting<00:01:57.920> up<00:01:58.079> k3s<00:01:58.799> with 00:01:59.030 --> 00:01:59.040 align:start position:0% even have a video on setting up k3s with 00:01:59.040 --> 00:02:00.950 align:start position:0% even have a video on setting up k3s with my<00:01:59.200> sequel<00:01:59.840> now<00:02:00.000> there's<00:02:00.240> nothing<00:02:00.560> wrong<00:02:00.799> with 00:02:00.950 --> 00:02:00.960 align:start position:0% my sequel now there's nothing wrong with 00:02:00.960 --> 00:02:03.350 align:start position:0% my sequel now there's nothing wrong with the<00:02:01.119> k3s<00:02:01.600> version<00:02:01.920> of<00:02:02.000> my<00:02:02.240> sequel<00:02:02.799> it<00:02:02.960> runs 00:02:03.350 --> 00:02:03.360 align:start position:0% the k3s version of my sequel it runs 00:02:03.360 --> 00:02:05.830 align:start position:0% the k3s version of my sequel it runs great<00:02:03.680> but<00:02:03.920> at<00:02:04.000> the<00:02:04.159> time<00:02:04.640> the<00:02:04.799> lcd<00:02:05.360> version 00:02:05.830 --> 00:02:05.840 align:start position:0% great but at the time the lcd version 00:02:05.840 --> 00:02:08.070 align:start position:0% great but at the time the lcd version wasn't<00:02:06.079> available<00:02:06.719> and<00:02:06.880> the<00:02:07.040> lcd<00:02:07.520> version<00:02:07.920> is 00:02:08.070 --> 00:02:08.080 align:start position:0% wasn't available and the lcd version is 00:02:08.080 --> 00:02:09.990 align:start position:0% wasn't available and the lcd version is super<00:02:08.479> interesting<00:02:09.039> because<00:02:09.360> it<00:02:09.520> creates<00:02:09.840> a 00:02:09.990 --> 00:02:10.000 align:start position:0% super interesting because it creates a 00:02:10.000 --> 00:02:13.190 align:start position:0% super interesting because it creates a high<00:02:10.239> availability<00:02:11.200> database<00:02:11.920> on<00:02:12.080> the<00:02:12.239> nodes 00:02:13.190 --> 00:02:13.200 align:start position:0% high availability database on the nodes 00:02:13.200 --> 00:02:15.110 align:start position:0% high availability database on the nodes instead<00:02:13.520> of<00:02:13.599> hosting<00:02:14.080> it<00:02:14.400> outside<00:02:14.879> of<00:02:14.959> the 00:02:15.110 --> 00:02:15.120 align:start position:0% instead of hosting it outside of the 00:02:15.120 --> 00:02:17.190 align:start position:0% instead of hosting it outside of the cluster<00:02:15.760> and<00:02:15.920> right<00:02:16.160> around<00:02:16.400> that<00:02:16.640> time<00:02:16.879> i<00:02:16.959> saw 00:02:17.190 --> 00:02:17.200 align:start position:0% cluster and right around that time i saw 00:02:17.200 --> 00:02:19.430 align:start position:0% cluster and right around that time i saw jeff<00:02:17.440> galen<00:02:17.840> create<00:02:18.080> a<00:02:18.160> video<00:02:18.480> on<00:02:18.720> ansible<00:02:19.360> and 00:02:19.430 --> 00:02:19.440 align:start position:0% jeff galen create a video on ansible and 00:02:19.440 --> 00:02:21.270 align:start position:0% jeff galen create a video on ansible and that<00:02:19.680> sent<00:02:19.840> me<00:02:20.000> down<00:02:20.160> a<00:02:20.239> rabbit<00:02:20.560> hole<00:02:20.959> learning 00:02:21.270 --> 00:02:21.280 align:start position:0% that sent me down a rabbit hole learning 00:02:21.280 --> 00:02:24.150 align:start position:0% that sent me down a rabbit hole learning ansible<00:02:21.920> creating<00:02:22.319> a<00:02:22.480> video<00:02:22.800> on<00:02:23.040> ansible<00:02:23.920> and 00:02:24.150 --> 00:02:24.160 align:start position:0% ansible creating a video on ansible and 00:02:24.160 --> 00:02:26.790 align:start position:0% ansible creating a video on ansible and automating<00:02:24.879> a<00:02:24.959> lot<00:02:25.120> of<00:02:25.360> tasks<00:02:26.080> well<00:02:26.480> you<00:02:26.640> know 00:02:26.790 --> 00:02:26.800 align:start position:0% automating a lot of tasks well you know 00:02:26.800 --> 00:02:29.190 align:start position:0% automating a lot of tasks well you know how<00:02:26.959> that<00:02:27.120> goes<00:02:27.760> anyway<00:02:28.480> so<00:02:28.640> i<00:02:28.800> found<00:02:29.040> that 00:02:29.190 --> 00:02:29.200 align:start position:0% how that goes anyway so i found that 00:02:29.200 --> 00:02:31.589 align:start position:0% how that goes anyway so i found that github<00:02:29.680> repo<00:02:30.239> i<00:02:30.400> cloned<00:02:30.800> it<00:02:30.959> and<00:02:31.120> created<00:02:31.440> some 00:02:31.589 --> 00:02:31.599 align:start position:0% github repo i cloned it and created some 00:02:31.599 --> 00:02:33.430 align:start position:0% github repo i cloned it and created some virtual<00:02:32.000> machines<00:02:32.640> and<00:02:32.800> then<00:02:32.959> i<00:02:33.120> tried<00:02:33.280> to 00:02:33.430 --> 00:02:33.440 align:start position:0% virtual machines and then i tried to 00:02:33.440 --> 00:02:35.830 align:start position:0% virtual machines and then i tried to provision<00:02:34.080> a<00:02:34.239> high<00:02:34.480> availability<00:02:35.200> cluster 00:02:35.830 --> 00:02:35.840 align:start position:0% provision a high availability cluster 00:02:35.840 --> 00:02:37.670 align:start position:0% provision a high availability cluster but<00:02:36.160> there<00:02:36.400> was<00:02:36.640> just<00:02:36.879> one<00:02:37.120> problem<00:02:37.519> the 00:02:37.670 --> 00:02:37.680 align:start position:0% but there was just one problem the 00:02:37.680 --> 00:02:39.910 align:start position:0% but there was just one problem the ansible<00:02:38.160> playbook<00:02:38.720> only<00:02:39.040> supported<00:02:39.519> spinning 00:02:39.910 --> 00:02:39.920 align:start position:0% ansible playbook only supported spinning 00:02:39.920 --> 00:02:43.190 align:start position:0% ansible playbook only supported spinning up<00:02:40.319> one<00:02:40.640> lcd<00:02:41.200> node<00:02:41.599> and<00:02:41.760> that<00:02:42.000> meant<00:02:42.400> only<00:02:42.879> one 00:02:43.190 --> 00:02:43.200 align:start position:0% up one lcd node and that meant only one 00:02:43.200 --> 00:02:45.830 align:start position:0% up one lcd node and that meant only one server<00:02:43.519> node<00:02:43.840> which<00:02:44.239> isn't<00:02:44.560> ha<00:02:45.200> i<00:02:45.280> mean<00:02:45.599> it's 00:02:45.830 --> 00:02:45.840 align:start position:0% server node which isn't ha i mean it's 00:02:45.840 --> 00:02:47.990 align:start position:0% server node which isn't ha i mean it's configured<00:02:46.319> for<00:02:46.560> ha<00:02:47.120> but<00:02:47.280> i<00:02:47.440> would<00:02:47.599> have<00:02:47.760> to 00:02:47.990 --> 00:02:48.000 align:start position:0% configured for ha but i would have to 00:02:48.000 --> 00:02:50.309 align:start position:0% configured for ha but i would have to manually<00:02:48.640> add<00:02:49.040> additional<00:02:49.519> server<00:02:49.840> nodes<00:02:50.160> to 00:02:50.309 --> 00:02:50.319 align:start position:0% manually add additional server nodes to 00:02:50.319 --> 00:02:52.710 align:start position:0% manually add additional server nodes to make<00:02:50.560> it<00:02:50.879> ha<00:02:51.519> and<00:02:51.680> that's<00:02:51.920> no<00:02:52.160> fun<00:02:52.560> so 00:02:52.710 --> 00:02:52.720 align:start position:0% make it ha and that's no fun so 00:02:52.720 --> 00:02:55.589 align:start position:0% make it ha and that's no fun so technically<00:02:53.360> it<00:02:53.440> wasn't<00:02:53.920> ha<00:02:54.560> out<00:02:54.720> of<00:02:54.800> the<00:02:54.879> box 00:02:55.589 --> 00:02:55.599 align:start position:0% technically it wasn't ha out of the box 00:02:55.599 --> 00:02:57.750 align:start position:0% technically it wasn't ha out of the box so<00:02:55.760> i<00:02:55.920> decided<00:02:56.319> to<00:02:56.480> dig<00:02:56.640> around<00:02:57.120> in<00:02:57.200> the<00:02:57.360> code 00:02:57.750 --> 00:02:57.760 align:start position:0% so i decided to dig around in the code 00:02:57.760 --> 00:02:59.910 align:start position:0% so i decided to dig around in the code and<00:02:58.000> in<00:02:58.159> the<00:02:58.319> branches<00:02:58.959> and<00:02:59.120> i<00:02:59.280> found<00:02:59.519> a<00:02:59.599> fork 00:02:59.910 --> 00:02:59.920 align:start position:0% and in the branches and i found a fork 00:02:59.920 --> 00:03:02.229 align:start position:0% and in the branches and i found a fork where<00:03:00.080> somebody<00:03:00.480> actually<00:03:01.040> fixed<00:03:01.519> that<00:03:01.840> issue 00:03:02.229 --> 00:03:02.239 align:start position:0% where somebody actually fixed that issue 00:03:02.239 --> 00:03:04.070 align:start position:0% where somebody actually fixed that issue so<00:03:02.400> i<00:03:02.560> could<00:03:02.720> actually<00:03:03.120> create<00:03:03.360> an<00:03:03.599> h<00:03:03.840> a 00:03:04.070 --> 00:03:04.080 align:start position:0% so i could actually create an h a 00:03:04.080 --> 00:03:06.070 align:start position:0% so i could actually create an h a cluster<00:03:04.640> out<00:03:04.800> of<00:03:04.879> the<00:03:04.959> box<00:03:05.280> with<00:03:05.519> ansible<00:03:05.920> and 00:03:06.070 --> 00:03:06.080 align:start position:0% cluster out of the box with ansible and 00:03:06.080 --> 00:03:08.149 align:start position:0% cluster out of the box with ansible and i<00:03:06.239> saw<00:03:06.480> they<00:03:06.720> also<00:03:07.040> added<00:03:07.360> support<00:03:07.680> for<00:03:07.920> cube 00:03:08.149 --> 00:03:08.159 align:start position:0% i saw they also added support for cube 00:03:08.159 --> 00:03:10.390 align:start position:0% i saw they also added support for cube vip<00:03:08.560> this<00:03:08.800> was<00:03:09.040> awesome<00:03:09.440> because<00:03:09.920> this<00:03:10.159> is 00:03:10.390 --> 00:03:10.400 align:start position:0% vip this was awesome because this is 00:03:10.400 --> 00:03:13.509 align:start position:0% vip this was awesome because this is exactly<00:03:11.360> what<00:03:11.599> i<00:03:11.680> was<00:03:11.920> trying<00:03:12.239> to<00:03:12.400> do<00:03:13.040> i<00:03:13.200> love 00:03:13.509 --> 00:03:13.519 align:start position:0% exactly what i was trying to do i love 00:03:13.519 --> 00:03:15.990 align:start position:0% exactly what i was trying to do i love open<00:03:13.760> source<00:03:14.319> so<00:03:14.480> a<00:03:14.560> huge<00:03:14.879> thank<00:03:15.120> you<00:03:15.360> to<00:03:15.519> user 00:03:15.990 --> 00:03:16.000 align:start position:0% open source so a huge thank you to user 00:03:16.000 --> 00:03:18.949 align:start position:0% open source so a huge thank you to user 212<00:03:16.720> 850a 00:03:18.949 --> 00:03:18.959 align:start position:0% 212 850a 00:03:18.959 --> 00:03:21.270 align:start position:0% 212 850a this<00:03:19.200> gave<00:03:19.519> me<00:03:19.840> a<00:03:20.000> nice<00:03:20.239> starting<00:03:20.720> point<00:03:20.959> to 00:03:21.270 --> 00:03:21.280 align:start position:0% this gave me a nice starting point to 00:03:21.280 --> 00:03:23.509 align:start position:0% this gave me a nice starting point to automate<00:03:21.680> the<00:03:21.840> rest<00:03:22.400> again<00:03:22.879> huge<00:03:23.120> thank<00:03:23.360> you 00:03:23.509 --> 00:03:23.519 align:start position:0% automate the rest again huge thank you 00:03:23.519 --> 00:03:25.910 align:start position:0% automate the rest again huge thank you to<00:03:23.760> open<00:03:24.000> source<00:03:24.239> community<00:03:24.879> jeff<00:03:25.120> gearling 00:03:25.910 --> 00:03:25.920 align:start position:0% to open source community jeff gearling 00:03:25.920 --> 00:03:29.750 align:start position:0% to open source community jeff gearling and<00:03:26.159> user<00:03:26.959> 212<00:03:27.680> 850a<00:03:28.480> so<00:03:28.720> after<00:03:29.040> poking<00:03:29.440> around 00:03:29.750 --> 00:03:29.760 align:start position:0% and user 212 850a so after poking around 00:03:29.760 --> 00:03:31.589 align:start position:0% and user 212 850a so after poking around for<00:03:29.920> a<00:03:30.000> little<00:03:30.159> bit<00:03:30.400> i<00:03:30.560> found<00:03:30.799> that<00:03:31.120> most<00:03:31.360> of<00:03:31.519> it 00:03:31.589 --> 00:03:31.599 align:start position:0% for a little bit i found that most of it 00:03:31.599 --> 00:03:33.990 align:start position:0% for a little bit i found that most of it was<00:03:31.840> working<00:03:32.400> but<00:03:32.560> it<00:03:32.720> did<00:03:32.959> need<00:03:33.200> some<00:03:33.440> updates 00:03:33.990 --> 00:03:34.000 align:start position:0% was working but it did need some updates 00:03:34.000 --> 00:03:36.229 align:start position:0% was working but it did need some updates and<00:03:34.239> some<00:03:34.480> configuration<00:03:35.280> changes<00:03:35.920> to<00:03:36.080> work 00:03:36.229 --> 00:03:36.239 align:start position:0% and some configuration changes to work 00:03:36.239 --> 00:03:38.390 align:start position:0% and some configuration changes to work with<00:03:36.400> the<00:03:36.480> latest<00:03:36.959> version<00:03:37.280> of<00:03:37.440> qvim<00:03:38.080> along 00:03:38.390 --> 00:03:38.400 align:start position:0% with the latest version of qvim along 00:03:38.400 --> 00:03:40.309 align:start position:0% with the latest version of qvim along with<00:03:38.560> some<00:03:38.720> other<00:03:38.959> features<00:03:39.360> i<00:03:39.440> wanted<00:03:39.760> to<00:03:39.840> add 00:03:40.309 --> 00:03:40.319 align:start position:0% with some other features i wanted to add 00:03:40.319 --> 00:03:43.509 align:start position:0% with some other features i wanted to add so<00:03:40.640> i<00:03:40.799> decided<00:03:41.280> to<00:03:41.920> roll<00:03:42.159> up<00:03:42.239> my<00:03:42.400> sleeves 00:03:43.509 --> 00:03:43.519 align:start position:0% so i decided to roll up my sleeves 00:03:43.519 --> 00:03:45.910 align:start position:0% so i decided to roll up my sleeves and<00:03:43.680> start<00:03:44.080> hacking<00:03:44.480> away<00:03:44.879> at<00:03:44.959> this<00:03:45.280> fork<00:03:45.760> in 00:03:45.910 --> 00:03:45.920 align:start position:0% and start hacking away at this fork in 00:03:45.920 --> 00:03:47.910 align:start position:0% and start hacking away at this fork in my<00:03:46.080> own<00:03:46.319> branch<00:03:46.879> and<00:03:47.040> before<00:03:47.440> making<00:03:47.760> it 00:03:47.910 --> 00:03:47.920 align:start position:0% my own branch and before making it 00:03:47.920 --> 00:03:50.229 align:start position:0% my own branch and before making it public<00:03:48.560> i<00:03:48.720> wanted<00:03:48.959> to<00:03:49.200> accomplish<00:03:49.920> a<00:03:50.000> few 00:03:50.229 --> 00:03:50.239 align:start position:0% public i wanted to accomplish a few 00:03:50.239 --> 00:03:52.550 align:start position:0% public i wanted to accomplish a few things<00:03:50.799> i<00:03:50.879> wanted<00:03:51.200> to<00:03:51.280> make<00:03:51.519> sure<00:03:51.760> that<00:03:52.159> anyone 00:03:52.550 --> 00:03:52.560 align:start position:0% things i wanted to make sure that anyone 00:03:52.560 --> 00:03:54.869 align:start position:0% things i wanted to make sure that anyone using<00:03:52.879> this<00:03:53.200> could<00:03:53.439> start<00:03:53.680> with<00:03:53.920> an<00:03:54.239> unlimited 00:03:54.869 --> 00:03:54.879 align:start position:0% using this could start with an unlimited 00:03:54.879 --> 00:03:56.789 align:start position:0% using this could start with an unlimited amount<00:03:55.280> of<00:03:55.360> nodes<00:03:55.920> i<00:03:56.000> wanted<00:03:56.319> to<00:03:56.400> make<00:03:56.640> sure 00:03:56.789 --> 00:03:56.799 align:start position:0% amount of nodes i wanted to make sure 00:03:56.799 --> 00:03:59.350 align:start position:0% amount of nodes i wanted to make sure that<00:03:57.120> qvip<00:03:57.680> was<00:03:58.080> rock<00:03:58.319> solid<00:03:58.959> and<00:03:59.040> then<00:03:59.280> it 00:03:59.350 --> 00:03:59.360 align:start position:0% that qvip was rock solid and then it 00:03:59.360 --> 00:04:01.350 align:start position:0% that qvip was rock solid and then it would<00:03:59.519> actually<00:04:00.000> create<00:04:00.319> a<00:04:00.480> load<00:04:00.720> balancer 00:04:01.350 --> 00:04:01.360 align:start position:0% would actually create a load balancer 00:04:01.360 --> 00:04:03.910 align:start position:0% would actually create a load balancer that<00:04:01.599> you<00:04:01.760> could<00:04:02.000> use<00:04:02.480> to<00:04:02.640> make<00:04:02.879> k3s<00:04:03.680> fault 00:04:03.910 --> 00:04:03.920 align:start position:0% that you could use to make k3s fault 00:04:03.920 --> 00:04:06.070 align:start position:0% that you could use to make k3s fault tolerant<00:04:04.480> i<00:04:04.640> also<00:04:04.959> wanted<00:04:05.200> to<00:04:05.360> automate<00:04:05.920> an 00:04:06.070 --> 00:04:06.080 align:start position:0% tolerant i also wanted to automate an 00:04:06.080 --> 00:04:08.070 align:start position:0% tolerant i also wanted to automate an external<00:04:06.560> load<00:04:06.799> balancer<00:04:07.280> so<00:04:07.439> that<00:04:07.599> when<00:04:07.840> you 00:04:08.070 --> 00:04:08.080 align:start position:0% external load balancer so that when you 00:04:08.080 --> 00:04:11.030 align:start position:0% external load balancer so that when you expose<00:04:08.560> the<00:04:08.720> service<00:04:09.519> you<00:04:09.680> get<00:04:09.840> an<00:04:10.000> ip<00:04:10.400> address 00:04:11.030 --> 00:04:11.040 align:start position:0% expose the service you get an ip address 00:04:11.040 --> 00:04:13.030 align:start position:0% expose the service you get an ip address for<00:04:11.280> that<00:04:11.439> service<00:04:11.840> from<00:04:12.080> your<00:04:12.239> cluster<00:04:12.959> and 00:04:13.030 --> 00:04:13.040 align:start position:0% for that service from your cluster and 00:04:13.040 --> 00:04:15.509 align:start position:0% for that service from your cluster and then<00:04:13.360> anyone<00:04:13.920> can<00:04:14.159> use<00:04:14.319> that<00:04:14.640> ip<00:04:15.040> address<00:04:15.360> to 00:04:15.509 --> 00:04:15.519 align:start position:0% then anyone can use that ip address to 00:04:15.519 --> 00:04:19.110 align:start position:0% then anyone can use that ip address to access<00:04:16.079> services<00:04:16.720> within<00:04:17.199> k3s<00:04:18.160> so<00:04:18.639> i<00:04:18.799> had<00:04:19.040> a 00:04:19.110 --> 00:04:19.120 align:start position:0% access services within k3s so i had a 00:04:19.120 --> 00:04:21.349 align:start position:0% access services within k3s so i had a few<00:04:19.359> choices<00:04:19.759> for<00:04:19.840> this<00:04:20.079> step<00:04:20.720> and<00:04:20.880> a<00:04:20.959> quick 00:04:21.349 --> 00:04:21.359 align:start position:0% few choices for this step and a quick 00:04:21.359 --> 00:04:22.950 align:start position:0% few choices for this step and a quick clarification<00:04:22.160> for<00:04:22.320> these<00:04:22.479> two<00:04:22.720> load 00:04:22.950 --> 00:04:22.960 align:start position:0% clarification for these two load 00:04:22.960 --> 00:04:25.030 align:start position:0% clarification for these two load balancers<00:04:23.759> the<00:04:23.919> first<00:04:24.160> load<00:04:24.400> balancer<00:04:24.880> you 00:04:25.030 --> 00:04:25.040 align:start position:0% balancers the first load balancer you 00:04:25.040 --> 00:04:28.150 align:start position:0% balancers the first load balancer you typically<00:04:25.520> need<00:04:25.759> in<00:04:25.919> k3s<00:04:26.639> is<00:04:26.800> a<00:04:27.040> load<00:04:27.360> balancer 00:04:28.150 --> 00:04:28.160 align:start position:0% typically need in k3s is a load balancer 00:04:28.160 --> 00:04:30.790 align:start position:0% typically need in k3s is a load balancer for<00:04:28.400> your<00:04:28.639> kubernetes<00:04:29.440> api<00:04:30.160> this<00:04:30.320> is<00:04:30.400> the<00:04:30.560> load 00:04:30.790 --> 00:04:30.800 align:start position:0% for your kubernetes api this is the load 00:04:30.800 --> 00:04:32.550 align:start position:0% for your kubernetes api this is the load balancer<00:04:31.280> for<00:04:31.600> control<00:04:32.000> plane<00:04:32.320> and<00:04:32.479> this 00:04:32.550 --> 00:04:32.560 align:start position:0% balancer for control plane and this 00:04:32.560 --> 00:04:34.469 align:start position:0% balancer for control plane and this should<00:04:32.720> be<00:04:32.960> fault<00:04:33.199> tolerance<00:04:33.600> so<00:04:33.759> that<00:04:34.080> if<00:04:34.160> you 00:04:34.469 --> 00:04:34.479 align:start position:0% should be fault tolerance so that if you 00:04:34.479 --> 00:04:37.030 align:start position:0% should be fault tolerance so that if you issue<00:04:34.880> k3s<00:04:35.520> commands<00:04:36.000> you<00:04:36.160> can<00:04:36.400> still<00:04:36.720> get<00:04:36.880> a 00:04:37.030 --> 00:04:37.040 align:start position:0% issue k3s commands you can still get a 00:04:37.040 --> 00:04:38.550 align:start position:0% issue k3s commands you can still get a response<00:04:37.520> back<00:04:37.840> and<00:04:38.000> the<00:04:38.160> other<00:04:38.320> load 00:04:38.550 --> 00:04:38.560 align:start position:0% response back and the other load 00:04:38.560 --> 00:04:41.270 align:start position:0% response back and the other load balancer<00:04:39.199> is<00:04:39.360> a<00:04:39.600> service<00:04:40.000> load<00:04:40.240> balancer<00:04:41.040> or 00:04:41.270 --> 00:04:41.280 align:start position:0% balancer is a service load balancer or 00:04:41.280 --> 00:04:43.990 align:start position:0% balancer is a service load balancer or kubernetes<00:04:42.000> for<00:04:42.160> you<00:04:42.320> to<00:04:42.479> expose<00:04:43.199> services<00:04:43.759> on 00:04:43.990 --> 00:04:44.000 align:start position:0% kubernetes for you to expose services on 00:04:44.000 --> 00:04:46.469 align:start position:0% kubernetes for you to expose services on in<00:04:44.160> most<00:04:44.400> cloud<00:04:44.720> environments<00:04:45.440> they<00:04:45.680> supply<00:04:46.240> a 00:04:46.469 --> 00:04:46.479 align:start position:0% in most cloud environments they supply a 00:04:46.479 --> 00:04:48.710 align:start position:0% in most cloud environments they supply a cloud<00:04:47.040> load<00:04:47.280> balancer<00:04:47.759> for<00:04:47.919> you<00:04:48.080> to<00:04:48.320> expose 00:04:48.710 --> 00:04:48.720 align:start position:0% cloud load balancer for you to expose 00:04:48.720 --> 00:04:50.629 align:start position:0% cloud load balancer for you to expose services<00:04:49.280> on<00:04:49.600> and<00:04:49.759> this<00:04:50.000> service<00:04:50.400> load 00:04:50.629 --> 00:04:50.639 align:start position:0% services on and this service load 00:04:50.639 --> 00:04:52.629 align:start position:0% services on and this service load balancer<00:04:51.040> that<00:04:51.199> i'm<00:04:51.360> talking<00:04:51.680> about<00:04:52.080> is<00:04:52.320> for 00:04:52.629 --> 00:04:52.639 align:start position:0% balancer that i'm talking about is for 00:04:52.639 --> 00:04:55.430 align:start position:0% balancer that i'm talking about is for non-cloud<00:04:53.360> environments<00:04:54.479> in<00:04:54.639> self-hosted 00:04:55.430 --> 00:04:55.440 align:start position:0% non-cloud environments in self-hosted 00:04:55.440 --> 00:04:57.430 align:start position:0% non-cloud environments in self-hosted environments<00:04:56.240> and<00:04:56.400> since<00:04:56.639> we<00:04:56.800> don't<00:04:56.960> have<00:04:57.199> a 00:04:57.430 --> 00:04:57.440 align:start position:0% environments and since we don't have a 00:04:57.440 --> 00:05:00.390 align:start position:0% environments and since we don't have a cloud<00:04:58.000> load<00:04:58.240> balancer<00:04:58.880> to<00:04:59.040> give<00:04:59.280> us<00:04:59.520> ips<00:05:00.160> to 00:05:00.390 --> 00:05:00.400 align:start position:0% cloud load balancer to give us ips to 00:05:00.400 --> 00:05:02.950 align:start position:0% cloud load balancer to give us ips to expose<00:05:01.120> our<00:05:01.280> services<00:05:01.919> outside<00:05:02.560> we<00:05:02.720> need<00:05:02.880> to 00:05:02.950 --> 00:05:02.960 align:start position:0% expose our services outside we need to 00:05:02.960 --> 00:05:05.189 align:start position:0% expose our services outside we need to use<00:05:03.199> something<00:05:03.600> that<00:05:03.759> can<00:05:04.080> emulate<00:05:04.639> a<00:05:04.880> cloud 00:05:05.189 --> 00:05:05.199 align:start position:0% use something that can emulate a cloud 00:05:05.199 --> 00:05:07.670 align:start position:0% use something that can emulate a cloud load<00:05:05.440> balancer<00:05:06.320> that<00:05:06.560> kubernetes<00:05:07.199> can<00:05:07.440> ask 00:05:07.670 --> 00:05:07.680 align:start position:0% load balancer that kubernetes can ask 00:05:07.680 --> 00:05:10.310 align:start position:0% load balancer that kubernetes can ask for<00:05:07.840> an<00:05:08.000> ip<00:05:08.320> address<00:05:08.639> from<00:05:09.199> so<00:05:09.520> our<00:05:09.680> services 00:05:10.310 --> 00:05:10.320 align:start position:0% for an ip address from so our services 00:05:10.320 --> 00:05:12.629 align:start position:0% for an ip address from so our services can<00:05:10.479> be<00:05:10.639> exposed<00:05:11.360> so<00:05:11.520> i<00:05:11.680> had<00:05:11.840> choices<00:05:12.240> to<00:05:12.400> make 00:05:12.629 --> 00:05:12.639 align:start position:0% can be exposed so i had choices to make 00:05:12.639 --> 00:05:15.270 align:start position:0% can be exposed so i had choices to make for<00:05:12.800> load<00:05:13.039> balancers<00:05:13.840> qvip<00:05:14.400> can<00:05:14.639> actually<00:05:15.039> do 00:05:15.270 --> 00:05:15.280 align:start position:0% for load balancers qvip can actually do 00:05:15.280 --> 00:05:17.590 align:start position:0% for load balancers qvip can actually do both<00:05:15.759> it<00:05:15.919> can<00:05:16.080> be<00:05:16.160> a<00:05:16.320> service<00:05:16.639> load<00:05:16.880> balancer 00:05:17.590 --> 00:05:17.600 align:start position:0% both it can be a service load balancer 00:05:17.600 --> 00:05:19.590 align:start position:0% both it can be a service load balancer or<00:05:17.840> a<00:05:17.919> load<00:05:18.160> balancer<00:05:18.800> for<00:05:19.039> your<00:05:19.199> control 00:05:19.590 --> 00:05:19.600 align:start position:0% or a load balancer for your control 00:05:19.600 --> 00:05:22.150 align:start position:0% or a load balancer for your control plane<00:05:19.919> for<00:05:20.080> your<00:05:20.240> kubernetes<00:05:20.960> lcd<00:05:21.440> nodes<00:05:22.000> this 00:05:22.150 --> 00:05:22.160 align:start position:0% plane for your kubernetes lcd nodes this 00:05:22.160 --> 00:05:23.830 align:start position:0% plane for your kubernetes lcd nodes this sounded<00:05:22.479> like<00:05:22.720> a<00:05:22.800> great<00:05:23.039> solution<00:05:23.440> because 00:05:23.830 --> 00:05:23.840 align:start position:0% sounded like a great solution because 00:05:23.840 --> 00:05:26.310 align:start position:0% sounded like a great solution because then<00:05:24.080> i<00:05:24.160> didn't<00:05:24.400> have<00:05:24.560> to<00:05:24.639> use<00:05:24.800> metal<00:05:25.199> lb 00:05:26.310 --> 00:05:26.320 align:start position:0% then i didn't have to use metal lb 00:05:26.320 --> 00:05:28.629 align:start position:0% then i didn't have to use metal lb but<00:05:26.479> i<00:05:26.639> love<00:05:26.880> metal<00:05:27.199> lv<00:05:27.600> but<00:05:27.759> taking<00:05:28.080> on<00:05:28.400> one 00:05:28.629 --> 00:05:28.639 align:start position:0% but i love metal lv but taking on one 00:05:28.639 --> 00:05:31.189 align:start position:0% but i love metal lv but taking on one less<00:05:28.880> dependency<00:05:29.600> sounded<00:05:30.000> like<00:05:30.320> a<00:05:30.400> good<00:05:30.639> idea 00:05:31.189 --> 00:05:31.199 align:start position:0% less dependency sounded like a good idea 00:05:31.199 --> 00:05:32.950 align:start position:0% less dependency sounded like a good idea especially<00:05:31.680> when<00:05:31.919> it<00:05:32.000> comes<00:05:32.240> to<00:05:32.560> breaking 00:05:32.950 --> 00:05:32.960 align:start position:0% especially when it comes to breaking 00:05:32.960 --> 00:05:35.510 align:start position:0% especially when it comes to breaking changes<00:05:33.520> it's<00:05:33.680> just<00:05:34.000> less<00:05:34.240> to<00:05:34.400> manage<00:05:34.960> so<00:05:35.120> then 00:05:35.510 --> 00:05:35.520 align:start position:0% changes it's just less to manage so then 00:05:35.520 --> 00:05:37.430 align:start position:0% changes it's just less to manage so then of<00:05:35.680> course<00:05:36.000> the<00:05:36.240> other<00:05:36.479> option<00:05:36.800> for<00:05:36.960> exposing 00:05:37.430 --> 00:05:37.440 align:start position:0% of course the other option for exposing 00:05:37.440 --> 00:05:39.909 align:start position:0% of course the other option for exposing my<00:05:37.600> services<00:05:38.160> was<00:05:38.400> just<00:05:38.639> to<00:05:38.720> use<00:05:39.039> metal<00:05:39.440> albeit 00:05:39.909 --> 00:05:39.919 align:start position:0% my services was just to use metal albeit 00:05:39.919 --> 00:05:40.790 align:start position:0% my services was just to use metal albeit and 00:05:40.790 --> 00:05:40.800 align:start position:0% and 00:05:40.800 --> 00:05:43.430 align:start position:0% and honestly<00:05:41.680> after<00:05:42.080> hours<00:05:42.479> and<00:05:42.639> hours<00:05:43.039> of<00:05:43.199> trying 00:05:43.430 --> 00:05:43.440 align:start position:0% honestly after hours and hours of trying 00:05:43.440 --> 00:05:46.070 align:start position:0% honestly after hours and hours of trying to<00:05:43.600> get<00:05:43.919> qvic<00:05:44.560> service<00:05:44.960> load<00:05:45.199> balancer<00:05:45.840> to<00:05:45.919> be 00:05:46.070 --> 00:05:46.080 align:start position:0% to get qvic service load balancer to be 00:05:46.080 --> 00:05:48.310 align:start position:0% to get qvic service load balancer to be able<00:05:46.240> to<00:05:46.320> work<00:05:46.560> with<00:05:46.720> my<00:05:46.880> services<00:05:47.759> i<00:05:47.919> decided 00:05:48.310 --> 00:05:48.320 align:start position:0% able to work with my services i decided 00:05:48.320 --> 00:05:51.189 align:start position:0% able to work with my services i decided to<00:05:48.479> fall<00:05:48.720> back<00:05:48.960> on<00:05:49.199> good<00:05:49.440> old<00:05:49.680> trusty<00:05:50.320> metal<00:05:50.639> lb 00:05:51.189 --> 00:05:51.199 align:start position:0% to fall back on good old trusty metal lb 00:05:51.199 --> 00:05:53.749 align:start position:0% to fall back on good old trusty metal lb and<00:05:51.360> metal<00:05:51.680> lb<00:05:52.240> just<00:05:52.479> works<00:05:52.960> and<00:05:53.280> i<00:05:53.360> could<00:05:53.600> use 00:05:53.749 --> 00:05:53.759 align:start position:0% and metal lb just works and i could use 00:05:53.759 --> 00:05:56.230 align:start position:0% and metal lb just works and i could use my<00:05:53.919> existing<00:05:54.320> configuration<00:05:55.039> for<00:05:55.280> it<00:05:55.440> so<00:05:55.840> it 00:05:56.230 --> 00:05:56.240 align:start position:0% my existing configuration for it so it 00:05:56.240 --> 00:05:58.710 align:start position:0% my existing configuration for it so it really<00:05:56.720> wasn't<00:05:57.199> a<00:05:57.360> loss<00:05:57.680> at<00:05:57.840> all<00:05:58.240> so<00:05:58.400> at<00:05:58.479> this 00:05:58.710 --> 00:05:58.720 align:start position:0% really wasn't a loss at all so at this 00:05:58.720 --> 00:06:00.870 align:start position:0% really wasn't a loss at all so at this point<00:05:58.960> i<00:05:59.120> had<00:05:59.280> my<00:05:59.520> architecture<00:06:00.479> pretty<00:06:00.639> much 00:06:00.870 --> 00:06:00.880 align:start position:0% point i had my architecture pretty much 00:06:00.880 --> 00:06:03.189 align:start position:0% point i had my architecture pretty much decided<00:06:01.520> qubit<00:06:01.919> for<00:06:02.080> my<00:06:02.240> kubernetes<00:06:02.880> control 00:06:03.189 --> 00:06:03.199 align:start position:0% decided qubit for my kubernetes control 00:06:03.199 --> 00:06:05.350 align:start position:0% decided qubit for my kubernetes control plane<00:06:03.600> and<00:06:03.759> metal<00:06:04.160> llb<00:06:04.479> for<00:06:04.639> my<00:06:04.800> service<00:06:05.120> load 00:06:05.350 --> 00:06:05.360 align:start position:0% plane and metal llb for my service load 00:06:05.360 --> 00:06:07.189 align:start position:0% plane and metal llb for my service load balancer<00:06:06.000> and<00:06:06.080> once<00:06:06.319> i<00:06:06.479> solved<00:06:06.800> creating 00:06:07.189 --> 00:06:07.199 align:start position:0% balancer and once i solved creating 00:06:07.199 --> 00:06:09.430 align:start position:0% balancer and once i solved creating multiple<00:06:07.680> server<00:06:08.000> nodes<00:06:08.560> configuring<00:06:09.199> cube 00:06:09.430 --> 00:06:09.440 align:start position:0% multiple server nodes configuring cube 00:06:09.440 --> 00:06:11.830 align:start position:0% multiple server nodes configuring cube vip<00:06:09.840> and<00:06:10.080> configuring<00:06:10.639> middle<00:06:11.039> of<00:06:11.120> b 00:06:11.830 --> 00:06:11.840 align:start position:0% vip and configuring middle of b 00:06:11.840 --> 00:06:13.909 align:start position:0% vip and configuring middle of b it<00:06:11.919> was<00:06:12.080> time<00:06:12.319> to<00:06:12.400> do<00:06:12.560> some<00:06:12.800> testing<00:06:13.520> for<00:06:13.759> my 00:06:13.909 --> 00:06:13.919 align:start position:0% it was time to do some testing for my 00:06:13.919 --> 00:06:16.309 align:start position:0% it was time to do some testing for my test<00:06:14.240> i<00:06:14.400> created<00:06:14.960> five<00:06:15.280> nodes<00:06:15.680> and<00:06:15.919> these<00:06:16.160> are 00:06:16.309 --> 00:06:16.319 align:start position:0% test i created five nodes and these are 00:06:16.319 --> 00:06:18.870 align:start position:0% test i created five nodes and these are standard<00:06:16.800> ubuntu<00:06:17.440> cloud<00:06:17.759> image<00:06:18.080> notes<00:06:18.639> and<00:06:18.800> i 00:06:18.870 --> 00:06:18.880 align:start position:0% standard ubuntu cloud image notes and i 00:06:18.880 --> 00:06:20.390 align:start position:0% standard ubuntu cloud image notes and i just<00:06:19.120> recently<00:06:19.520> created<00:06:19.840> a<00:06:19.919> video<00:06:20.240> on 00:06:20.390 --> 00:06:20.400 align:start position:0% just recently created a video on 00:06:20.400 --> 00:06:22.390 align:start position:0% just recently created a video on provisioning<00:06:20.960> new<00:06:21.199> ubuntu<00:06:21.680> machines<00:06:22.080> using 00:06:22.390 --> 00:06:22.400 align:start position:0% provisioning new ubuntu machines using 00:06:22.400 --> 00:06:24.390 align:start position:0% provisioning new ubuntu machines using cloud<00:06:22.720> image<00:06:23.280> and<00:06:23.360> cloud<00:06:23.680> init<00:06:24.000> they're<00:06:24.240> the 00:06:24.390 --> 00:06:24.400 align:start position:0% cloud image and cloud init they're the 00:06:24.400 --> 00:06:27.350 align:start position:0% cloud image and cloud init they're the perfect<00:06:24.880> ubuntu<00:06:25.520> minimal<00:06:26.000> server<00:06:26.240> for<00:06:26.479> k3s 00:06:27.350 --> 00:06:27.360 align:start position:0% perfect ubuntu minimal server for k3s 00:06:27.360 --> 00:06:29.189 align:start position:0% perfect ubuntu minimal server for k3s just<00:06:27.600> really<00:06:27.840> check<00:06:28.080> it<00:06:28.240> out<00:06:28.479> so<00:06:28.639> once<00:06:28.960> i<00:06:29.039> had 00:06:29.189 --> 00:06:29.199 align:start position:0% just really check it out so once i had 00:06:29.199 --> 00:06:31.430 align:start position:0% just really check it out so once i had these<00:06:29.520> five<00:06:29.840> servers<00:06:30.479> up<00:06:30.639> and<00:06:30.720> running<00:06:31.120> and 00:06:31.430 --> 00:06:31.440 align:start position:0% these five servers up and running and 00:06:31.440 --> 00:06:33.590 align:start position:0% these five servers up and running and made<00:06:31.680> note<00:06:31.919> of<00:06:32.000> their<00:06:32.240> ip<00:06:32.560> addresses 00:06:33.590 --> 00:06:33.600 align:start position:0% made note of their ip addresses 00:06:33.600 --> 00:06:35.270 align:start position:0% made note of their ip addresses it<00:06:33.680> was<00:06:33.919> time<00:06:34.080> to<00:06:34.240> configure<00:06:34.639> myansible 00:06:35.270 --> 00:06:35.280 align:start position:0% it was time to configure myansible 00:06:35.280 --> 00:06:37.510 align:start position:0% it was time to configure myansible playbook<00:06:35.759> so<00:06:36.000> here<00:06:36.240> in<00:06:36.400> the<00:06:36.479> groupbars<00:06:37.120> file 00:06:37.510 --> 00:06:37.520 align:start position:0% playbook so here in the groupbars file 00:06:37.520 --> 00:06:39.749 align:start position:0% playbook so here in the groupbars file is<00:06:37.680> where<00:06:37.919> all<00:06:38.160> of<00:06:38.240> my<00:06:38.479> variables<00:06:39.120> are<00:06:39.360> set<00:06:39.600> for 00:06:39.749 --> 00:06:39.759 align:start position:0% is where all of my variables are set for 00:06:39.759 --> 00:06:42.150 align:start position:0% is where all of my variables are set for ansible<00:06:40.319> first<00:06:40.560> you<00:06:40.639> can<00:06:40.800> specify<00:06:41.440> the<00:06:41.520> k3s 00:06:42.150 --> 00:06:42.160 align:start position:0% ansible first you can specify the k3s 00:06:42.160 --> 00:06:44.469 align:start position:0% ansible first you can specify the k3s version<00:06:43.039> and<00:06:43.120> then<00:06:43.360> you<00:06:43.440> could<00:06:43.680> specify<00:06:44.240> an 00:06:44.469 --> 00:06:44.479 align:start position:0% version and then you could specify an 00:06:44.479 --> 00:06:46.469 align:start position:0% version and then you could specify an ansible<00:06:44.960> user<00:06:45.440> and<00:06:45.520> this<00:06:45.759> is<00:06:45.840> the<00:06:46.000> user<00:06:46.319> that 00:06:46.469 --> 00:06:46.479 align:start position:0% ansible user and this is the user that 00:06:46.479 --> 00:06:48.469 align:start position:0% ansible user and this is the user that ansible<00:06:46.960> will<00:06:47.120> run<00:06:47.360> as<00:06:47.759> and<00:06:47.919> another<00:06:48.240> quick 00:06:48.469 --> 00:06:48.479 align:start position:0% ansible will run as and another quick 00:06:48.479 --> 00:06:50.710 align:start position:0% ansible will run as and another quick tip<00:06:49.120> if<00:06:49.280> you<00:06:49.360> need<00:06:49.520> to<00:06:49.599> set<00:06:49.759> up<00:06:49.919> ansible<00:06:50.400> i<00:06:50.479> got 00:06:50.710 --> 00:06:50.720 align:start position:0% tip if you need to set up ansible i got 00:06:50.720 --> 00:06:53.189 align:start position:0% tip if you need to set up ansible i got a<00:06:50.960> really<00:06:51.280> quick<00:06:51.520> video<00:06:52.080> on<00:06:52.240> the<00:06:52.400> bare<00:06:52.720> minimum 00:06:53.189 --> 00:06:53.199 align:start position:0% a really quick video on the bare minimum 00:06:53.199 --> 00:06:55.029 align:start position:0% a really quick video on the bare minimum stuff<00:06:53.520> you<00:06:53.680> need<00:06:53.840> to<00:06:53.919> do<00:06:54.160> in<00:06:54.240> order<00:06:54.560> to<00:06:54.720> set<00:06:54.880> up 00:06:55.029 --> 00:06:55.039 align:start position:0% stuff you need to do in order to set up 00:06:55.039 --> 00:06:57.270 align:start position:0% stuff you need to do in order to set up ansible<00:06:55.520> it's<00:06:55.680> a<00:06:55.840> great<00:06:56.160> primer<00:06:56.560> for<00:06:56.720> this<00:06:56.960> too 00:06:57.270 --> 00:06:57.280 align:start position:0% ansible it's a great primer for this too 00:06:57.280 --> 00:06:59.350 align:start position:0% ansible it's a great primer for this too next<00:06:57.599> is<00:06:57.680> setting<00:06:58.080> a<00:06:58.160> system<00:06:58.560> directory<00:06:59.199> and 00:06:59.350 --> 00:06:59.360 align:start position:0% next is setting a system directory and 00:06:59.360 --> 00:07:01.350 align:start position:0% next is setting a system directory and you<00:06:59.520> won't<00:06:59.759> really<00:07:00.000> need<00:07:00.160> to<00:07:00.240> touch<00:07:00.560> this<00:07:01.039> next 00:07:01.350 --> 00:07:01.360 align:start position:0% you won't really need to touch this next 00:07:01.360 --> 00:07:03.830 align:start position:0% you won't really need to touch this next is<00:07:01.440> setting<00:07:01.759> a<00:07:01.840> flannel<00:07:02.400> interface<00:07:02.880> of<00:07:03.039> eth0 00:07:03.830 --> 00:07:03.840 align:start position:0% is setting a flannel interface of eth0 00:07:03.840 --> 00:07:05.990 align:start position:0% is setting a flannel interface of eth0 so<00:07:04.000> flannel's<00:07:04.560> responsible<00:07:05.199> for<00:07:05.440> networking 00:07:05.990 --> 00:07:06.000 align:start position:0% so flannel's responsible for networking 00:07:06.000 --> 00:07:08.950 align:start position:0% so flannel's responsible for networking in<00:07:06.080> k3s<00:07:07.039> and<00:07:07.199> it's<00:07:07.599> pretty<00:07:08.000> dense<00:07:08.560> but<00:07:08.720> if<00:07:08.800> you 00:07:08.950 --> 00:07:08.960 align:start position:0% in k3s and it's pretty dense but if you 00:07:08.960 --> 00:07:10.230 align:start position:0% in k3s and it's pretty dense but if you want<00:07:09.120> to<00:07:09.199> know<00:07:09.440> more<00:07:09.599> about<00:07:09.840> it<00:07:10.000> you<00:07:10.080> should 00:07:10.230 --> 00:07:10.240 align:start position:0% want to know more about it you should 00:07:10.240 --> 00:07:12.150 align:start position:0% want to know more about it you should totally<00:07:10.639> check<00:07:10.880> out<00:07:10.960> their<00:07:11.120> github<00:07:11.599> repo<00:07:12.000> but 00:07:12.150 --> 00:07:12.160 align:start position:0% totally check out their github repo but 00:07:12.160 --> 00:07:14.469 align:start position:0% totally check out their github repo but as<00:07:12.400> i<00:07:12.560> understand<00:07:13.039> it<00:07:13.199> it's<00:07:13.440> responsible<00:07:14.160> for 00:07:14.469 --> 00:07:14.479 align:start position:0% as i understand it it's responsible for 00:07:14.479 --> 00:07:16.950 align:start position:0% as i understand it it's responsible for layer<00:07:14.800> 3<00:07:15.039> communication<00:07:16.080> between<00:07:16.479> nodes<00:07:16.800> in<00:07:16.880> a 00:07:16.950 --> 00:07:16.960 align:start position:0% layer 3 communication between nodes in a 00:07:16.960 --> 00:07:19.909 align:start position:0% layer 3 communication between nodes in a cluster<00:07:17.599> and<00:07:17.759> so<00:07:18.000> here<00:07:18.240> i<00:07:18.479> set<00:07:18.720> at<00:07:19.039> 0<00:07:19.599> because 00:07:19.909 --> 00:07:19.919 align:start position:0% cluster and so here i set at 0 because 00:07:19.919 --> 00:07:21.909 align:start position:0% cluster and so here i set at 0 because that's<00:07:20.160> the<00:07:20.400> ethernet<00:07:20.960> interface<00:07:21.599> on<00:07:21.759> these 00:07:21.909 --> 00:07:21.919 align:start position:0% that's the ethernet interface on these 00:07:21.919 --> 00:07:24.070 align:start position:0% that's the ethernet interface on these virtual<00:07:22.400> machines<00:07:23.120> next<00:07:23.360> i'm<00:07:23.520> setting<00:07:23.840> a 00:07:24.070 --> 00:07:24.080 align:start position:0% virtual machines next i'm setting a 00:07:24.080 --> 00:07:25.990 align:start position:0% virtual machines next i'm setting a server<00:07:24.639> endpoint<00:07:25.120> and<00:07:25.199> this<00:07:25.360> is<00:07:25.520> the<00:07:25.680> ip 00:07:25.990 --> 00:07:26.000 align:start position:0% server endpoint and this is the ip 00:07:26.000 --> 00:07:28.150 align:start position:0% server endpoint and this is the ip address<00:07:26.400> of<00:07:26.560> the<00:07:26.800> vip<00:07:27.039> that<00:07:27.199> will<00:07:27.360> get<00:07:27.599> created 00:07:28.150 --> 00:07:28.160 align:start position:0% address of the vip that will get created 00:07:28.160 --> 00:07:30.390 align:start position:0% address of the vip that will get created for<00:07:28.479> kubernetes<00:07:29.120> control<00:07:29.520> plane<00:07:29.840> and<00:07:29.919> so<00:07:30.160> this 00:07:30.390 --> 00:07:30.400 align:start position:0% for kubernetes control plane and so this 00:07:30.400 --> 00:07:32.710 align:start position:0% for kubernetes control plane and so this vip<00:07:30.639> gets<00:07:30.960> created<00:07:31.520> instead<00:07:31.840> of<00:07:32.160> you<00:07:32.400> having 00:07:32.710 --> 00:07:32.720 align:start position:0% vip gets created instead of you having 00:07:32.720 --> 00:07:35.270 align:start position:0% vip gets created instead of you having to<00:07:32.880> create<00:07:33.199> external<00:07:33.759> load<00:07:34.000> balancers<00:07:34.960> along 00:07:35.270 --> 00:07:35.280 align:start position:0% to create external load balancers along 00:07:35.280 --> 00:07:37.909 align:start position:0% to create external load balancers along with<00:07:35.599> keepa<00:07:35.919> live<00:07:36.160> d<00:07:36.479> this<00:07:36.720> creates<00:07:37.199> a<00:07:37.440> vip 00:07:37.909 --> 00:07:37.919 align:start position:0% with keepa live d this creates a vip 00:07:37.919 --> 00:07:40.070 align:start position:0% with keepa live d this creates a vip that<00:07:38.160> is<00:07:38.319> highly<00:07:38.720> available<00:07:39.360> that's<00:07:39.680> exposed 00:07:40.070 --> 00:07:40.080 align:start position:0% that is highly available that's exposed 00:07:40.080 --> 00:07:41.909 align:start position:0% that is highly available that's exposed through<00:07:40.240> the<00:07:40.319> kubernetes<00:07:41.039> cluster<00:07:41.520> that<00:07:41.759> we 00:07:41.909 --> 00:07:41.919 align:start position:0% through the kubernetes cluster that we 00:07:41.919 --> 00:07:44.309 align:start position:0% through the kubernetes cluster that we can<00:07:42.160> communicate<00:07:42.880> with<00:07:43.280> and<00:07:43.440> kubernetes<00:07:44.080> can 00:07:44.309 --> 00:07:44.319 align:start position:0% can communicate with and kubernetes can 00:07:44.319 --> 00:07:46.550 align:start position:0% can communicate with and kubernetes can too<00:07:44.800> so<00:07:45.120> it's<00:07:45.440> pretty<00:07:45.759> awesome<00:07:46.080> that<00:07:46.319> takes 00:07:46.550 --> 00:07:46.560 align:start position:0% too so it's pretty awesome that takes 00:07:46.560 --> 00:07:48.309 align:start position:0% too so it's pretty awesome that takes care<00:07:46.800> of<00:07:46.960> two<00:07:47.120> to<00:07:47.280> three<00:07:47.520> additional<00:07:47.919> virtual 00:07:48.309 --> 00:07:48.319 align:start position:0% care of two to three additional virtual 00:07:48.319 --> 00:07:49.990 align:start position:0% care of two to three additional virtual machines<00:07:48.639> that<00:07:48.720> you<00:07:49.039> don't<00:07:49.199> have<00:07:49.360> to<00:07:49.440> maintain 00:07:49.990 --> 00:07:50.000 align:start position:0% machines that you don't have to maintain 00:07:50.000 --> 00:07:53.029 align:start position:0% machines that you don't have to maintain anymore<00:07:50.720> next<00:07:51.039> i<00:07:51.120> set<00:07:51.360> my<00:07:51.520> k3s<00:07:52.160> token<00:07:52.560> and<00:07:52.800> this 00:07:53.029 --> 00:07:53.039 align:start position:0% anymore next i set my k3s token and this 00:07:53.039 --> 00:07:54.790 align:start position:0% anymore next i set my k3s token and this should<00:07:53.199> be<00:07:53.520> a<00:07:53.680> secret<00:07:54.160> that<00:07:54.319> you<00:07:54.479> should 00:07:54.790 --> 00:07:54.800 align:start position:0% should be a secret that you should 00:07:54.800 --> 00:07:56.710 align:start position:0% should be a secret that you should obviously<00:07:55.520> keep<00:07:55.680> secret<00:07:56.160> but<00:07:56.319> it's<00:07:56.560> your 00:07:56.710 --> 00:07:56.720 align:start position:0% obviously keep secret but it's your 00:07:56.720 --> 00:07:59.189 align:start position:0% obviously keep secret but it's your password<00:07:57.199> or<00:07:57.280> your<00:07:57.440> token<00:07:57.840> for<00:07:58.000> k3s 00:07:59.189 --> 00:07:59.199 align:start position:0% password or your token for k3s 00:07:59.199 --> 00:08:00.469 align:start position:0% password or your token for k3s and<00:07:59.360> you'll<00:07:59.599> only<00:07:59.759> need<00:08:00.000> this<00:08:00.240> in<00:08:00.319> the 00:08:00.469 --> 00:08:00.479 align:start position:0% and you'll only need this in the 00:08:00.479 --> 00:08:01.990 align:start position:0% and you'll only need this in the beginning<00:08:00.879> or<00:08:01.039> if<00:08:01.120> you<00:08:01.280> join<00:08:01.599> additional 00:08:01.990 --> 00:08:02.000 align:start position:0% beginning or if you join additional 00:08:02.000 --> 00:08:04.309 align:start position:0% beginning or if you join additional nodes<00:08:02.319> later<00:08:02.800> i<00:08:02.960> then<00:08:03.199> added<00:08:03.599> some<00:08:03.840> additional 00:08:04.309 --> 00:08:04.319 align:start position:0% nodes later i then added some additional 00:08:04.319 --> 00:08:06.950 align:start position:0% nodes later i then added some additional arguments<00:08:04.800> to<00:08:04.960> my<00:08:05.199> server<00:08:05.840> and<00:08:06.000> to<00:08:06.160> my<00:08:06.319> agents 00:08:06.950 --> 00:08:06.960 align:start position:0% arguments to my server and to my agents 00:08:06.960 --> 00:08:09.189 align:start position:0% arguments to my server and to my agents but<00:08:07.120> as<00:08:07.199> far<00:08:07.440> as<00:08:07.599> the<00:08:07.680> server<00:08:08.080> goes<00:08:08.400> i<00:08:08.639> disabled 00:08:09.189 --> 00:08:09.199 align:start position:0% but as far as the server goes i disabled 00:08:09.199 --> 00:08:11.270 align:start position:0% but as far as the server goes i disabled the<00:08:09.360> service<00:08:09.759> load<00:08:10.000> balancer<00:08:10.800> we'll<00:08:11.039> want<00:08:11.199> to 00:08:11.270 --> 00:08:11.280 align:start position:0% the service load balancer we'll want to 00:08:11.280 --> 00:08:13.270 align:start position:0% the service load balancer we'll want to do<00:08:11.440> that<00:08:11.680> if<00:08:11.759> we're<00:08:11.919> running<00:08:12.240> metal<00:08:12.639> of<00:08:12.720> b<00:08:13.039> or<00:08:13.199> a 00:08:13.270 --> 00:08:13.280 align:start position:0% do that if we're running metal of b or a 00:08:13.280 --> 00:08:15.350 align:start position:0% do that if we're running metal of b or a service<00:08:13.680> load<00:08:13.919> balancer<00:08:14.479> which<00:08:14.720> we<00:08:14.879> are<00:08:15.199> i'm 00:08:15.350 --> 00:08:15.360 align:start position:0% service load balancer which we are i'm 00:08:15.360 --> 00:08:18.070 align:start position:0% service load balancer which we are i'm telling<00:08:15.680> it<00:08:16.000> not<00:08:16.240> to<00:08:16.479> deploy<00:08:16.960> traffic<00:08:17.680> this<00:08:17.919> is 00:08:18.070 --> 00:08:18.080 align:start position:0% telling it not to deploy traffic this is 00:08:18.080 --> 00:08:19.990 align:start position:0% telling it not to deploy traffic this is up<00:08:18.160> to<00:08:18.319> you<00:08:18.560> if<00:08:18.639> you<00:08:18.800> want<00:08:18.960> to<00:08:19.039> deploy<00:08:19.520> traffic 00:08:19.990 --> 00:08:20.000 align:start position:0% up to you if you want to deploy traffic 00:08:20.000 --> 00:08:21.830 align:start position:0% up to you if you want to deploy traffic you<00:08:20.160> can<00:08:20.319> just<00:08:20.479> delete<00:08:20.800> that<00:08:20.960> arg<00:08:21.440> but<00:08:21.680> i'm 00:08:21.830 --> 00:08:21.840 align:start position:0% you can just delete that arg but i'm 00:08:21.840 --> 00:08:23.350 align:start position:0% you can just delete that arg but i'm going<00:08:22.000> to<00:08:22.080> delete<00:08:22.400> it<00:08:22.479> so<00:08:22.639> i<00:08:22.720> can<00:08:22.960> install<00:08:23.280> it 00:08:23.350 --> 00:08:23.360 align:start position:0% going to delete it so i can install it 00:08:23.360 --> 00:08:25.110 align:start position:0% going to delete it so i can install it with<00:08:23.520> helm<00:08:23.759> later<00:08:24.240> because<00:08:24.639> i<00:08:24.800> like<00:08:24.960> to 00:08:25.110 --> 00:08:25.120 align:start position:0% with helm later because i like to 00:08:25.120 --> 00:08:27.430 align:start position:0% with helm later because i like to install<00:08:25.599> traffic<00:08:26.080> on<00:08:26.240> my<00:08:26.479> own<00:08:26.960> later<00:08:27.199> with 00:08:27.430 --> 00:08:27.440 align:start position:0% install traffic on my own later with 00:08:27.440 --> 00:08:29.350 align:start position:0% install traffic on my own later with helm<00:08:27.840> but<00:08:28.000> if<00:08:28.080> you<00:08:28.240> wanted<00:08:28.479> to<00:08:28.720> install<00:08:29.039> it<00:08:29.199> you 00:08:29.350 --> 00:08:29.360 align:start position:0% helm but if you wanted to install it you 00:08:29.360 --> 00:08:30.869 align:start position:0% helm but if you wanted to install it you could<00:08:29.520> just<00:08:29.680> delete<00:08:30.000> this<00:08:30.160> argument<00:08:30.639> this 00:08:30.869 --> 00:08:30.879 align:start position:0% could just delete this argument this 00:08:30.879 --> 00:08:32.389 align:start position:0% could just delete this argument this next<00:08:31.199> argument<00:08:31.680> is<00:08:31.840> just<00:08:32.080> setting 00:08:32.389 --> 00:08:32.399 align:start position:0% next argument is just setting 00:08:32.399 --> 00:08:34.389 align:start position:0% next argument is just setting permissions<00:08:32.959> on<00:08:33.200> coop<00:08:33.440> config<00:08:33.919> and<00:08:34.000> this<00:08:34.240> is 00:08:34.389 --> 00:08:34.399 align:start position:0% permissions on coop config and this is 00:08:34.399 --> 00:08:36.070 align:start position:0% permissions on coop config and this is really<00:08:34.640> just<00:08:34.880> for<00:08:35.200> convenience<00:08:35.680> so<00:08:35.839> i<00:08:35.919> don't 00:08:36.070 --> 00:08:36.080 align:start position:0% really just for convenience so i don't 00:08:36.080 --> 00:08:38.230 align:start position:0% really just for convenience so i don't have<00:08:36.240> to<00:08:36.320> run<00:08:36.640> sudo<00:08:37.120> when<00:08:37.279> i'm<00:08:37.360> remoted<00:08:37.919> into<00:08:38.159> a 00:08:38.230 --> 00:08:38.240 align:start position:0% have to run sudo when i'm remoted into a 00:08:38.240 --> 00:08:40.230 align:start position:0% have to run sudo when i'm remoted into a node<00:08:38.479> to<00:08:38.640> run<00:08:38.880> coupe<00:08:39.120> control<00:08:39.599> it's<00:08:39.839> probably 00:08:40.230 --> 00:08:40.240 align:start position:0% node to run coupe control it's probably 00:08:40.240 --> 00:08:42.630 align:start position:0% node to run coupe control it's probably a<00:08:40.320> good<00:08:40.479> idea<00:08:41.120> not<00:08:41.360> to<00:08:41.519> this<00:08:41.760> but<00:08:41.919> i<00:08:42.080> got<00:08:42.320> so 00:08:42.630 --> 00:08:42.640 align:start position:0% a good idea not to this but i got so 00:08:42.640 --> 00:08:44.949 align:start position:0% a good idea not to this but i got so tired<00:08:43.039> of<00:08:43.200> typing<00:08:43.599> in<00:08:43.760> sudo<00:08:44.240> every<00:08:44.399> time<00:08:44.640> i<00:08:44.720> was 00:08:44.949 --> 00:08:44.959 align:start position:0% tired of typing in sudo every time i was 00:08:44.959 --> 00:08:47.110 align:start position:0% tired of typing in sudo every time i was testing<00:08:45.279> this<00:08:45.600> the<00:08:45.839> thousand<00:08:46.320> times<00:08:46.640> i<00:08:46.800> spun 00:08:47.110 --> 00:08:47.120 align:start position:0% testing this the thousand times i spun 00:08:47.120 --> 00:08:48.310 align:start position:0% testing this the thousand times i spun this<00:08:47.360> up 00:08:48.310 --> 00:08:48.320 align:start position:0% this up 00:08:48.320 --> 00:08:50.230 align:start position:0% this up that<00:08:48.560> i<00:08:48.720> just<00:08:48.959> changed<00:08:49.279> the<00:08:49.600> permissions<00:08:50.160> of 00:08:50.230 --> 00:08:50.240 align:start position:0% that i just changed the permissions of 00:08:50.240 --> 00:08:52.470 align:start position:0% that i just changed the permissions of this<00:08:50.480> file<00:08:51.120> but<00:08:51.279> feel<00:08:51.519> free<00:08:51.760> to<00:08:52.000> remove<00:08:52.320> that 00:08:52.470 --> 00:08:52.480 align:start position:0% this file but feel free to remove that 00:08:52.480 --> 00:08:54.470 align:start position:0% this file but feel free to remove that argument<00:08:52.880> if<00:08:53.040> you<00:08:53.120> want<00:08:53.519> and<00:08:53.680> the<00:08:53.839> next<00:08:54.080> string 00:08:54.470 --> 00:08:54.480 align:start position:0% argument if you want and the next string 00:08:54.480 --> 00:08:57.030 align:start position:0% argument if you want and the next string of<00:08:54.720> arguments<00:08:55.200> are<00:08:55.680> quite<00:08:56.000> a<00:08:56.080> few 00:08:57.030 --> 00:08:57.040 align:start position:0% of arguments are quite a few 00:08:57.040 --> 00:08:58.150 align:start position:0% of arguments are quite a few but<00:08:57.279> i'll<00:08:57.440> leave<00:08:57.680> these<00:08:57.920> in<00:08:58.000> the 00:08:58.150 --> 00:08:58.160 align:start position:0% but i'll leave these in the 00:08:58.160 --> 00:09:00.790 align:start position:0% but i'll leave these in the documentation<00:08:59.120> but<00:08:59.360> to<00:08:59.600> summarize 00:09:00.790 --> 00:09:00.800 align:start position:0% documentation but to summarize 00:09:00.800 --> 00:09:03.110 align:start position:0% documentation but to summarize the<00:09:00.959> rest<00:09:01.200> of<00:09:01.279> these<00:09:01.519> args<00:09:02.000> as<00:09:02.399> well<00:09:02.720> as<00:09:02.880> the 00:09:03.110 --> 00:09:03.120 align:start position:0% the rest of these args as well as the 00:09:03.120 --> 00:09:05.190 align:start position:0% the rest of these args as well as the agent<00:09:03.440> args<00:09:03.839> you<00:09:03.920> see<00:09:04.160> here<00:09:04.560> is<00:09:04.720> that<00:09:04.880> i<00:09:04.959> found 00:09:05.190 --> 00:09:05.200 align:start position:0% agent args you see here is that i found 00:09:05.200 --> 00:09:07.269 align:start position:0% agent args you see here is that i found that<00:09:05.360> i<00:09:05.519> needed<00:09:06.000> most<00:09:06.240> of<00:09:06.399> these<00:09:06.560> args<00:09:06.959> to<00:09:07.040> make 00:09:07.269 --> 00:09:07.279 align:start position:0% that i needed most of these args to make 00:09:07.279 --> 00:09:09.509 align:start position:0% that i needed most of these args to make k3s<00:09:07.920> a<00:09:08.080> little<00:09:08.240> more<00:09:08.480> responsive<00:09:09.120> what<00:09:09.279> do<00:09:09.440> i 00:09:09.509 --> 00:09:09.519 align:start position:0% k3s a little more responsive what do i 00:09:09.519 --> 00:09:11.910 align:start position:0% k3s a little more responsive what do i mean<00:09:09.760> by<00:09:09.920> that<00:09:10.240> one<00:09:10.399> of<00:09:10.480> the<00:09:10.640> defaults<00:09:11.040> for<00:09:11.200> k3s 00:09:11.910 --> 00:09:11.920 align:start position:0% mean by that one of the defaults for k3s 00:09:11.920 --> 00:09:14.230 align:start position:0% mean by that one of the defaults for k3s is<00:09:12.000> that<00:09:12.240> if<00:09:12.399> the<00:09:12.480> node's<00:09:12.880> not<00:09:13.120> ready<00:09:13.680> it<00:09:13.920> won't 00:09:14.230 --> 00:09:14.240 align:start position:0% is that if the node's not ready it won't 00:09:14.240 --> 00:09:16.630 align:start position:0% is that if the node's not ready it won't schedule<00:09:14.720> additional<00:09:15.200> pods<00:09:15.600> on<00:09:15.760> it<00:09:16.320> until 00:09:16.630 --> 00:09:16.640 align:start position:0% schedule additional pods on it until 00:09:16.640 --> 00:09:19.350 align:start position:0% schedule additional pods on it until that<00:09:16.880> node<00:09:17.279> becomes<00:09:17.680> ready<00:09:18.480> but<00:09:18.640> the<00:09:18.800> timeout 00:09:19.350 --> 00:09:19.360 align:start position:0% that node becomes ready but the timeout 00:09:19.360 --> 00:09:21.190 align:start position:0% that node becomes ready but the timeout is<00:09:19.519> like<00:09:19.760> five<00:09:20.000> minutes<00:09:20.320> long<00:09:20.720> which<00:09:20.959> is<00:09:21.120> a 00:09:21.190 --> 00:09:21.200 align:start position:0% is like five minutes long which is a 00:09:21.200 --> 00:09:23.829 align:start position:0% is like five minutes long which is a long<00:09:21.519> time<00:09:21.920> i<00:09:22.080> mean<00:09:22.480> it's<00:09:22.720> not<00:09:22.959> a<00:09:23.040> long<00:09:23.279> time<00:09:23.680> if 00:09:23.829 --> 00:09:23.839 align:start position:0% long time i mean it's not a long time if 00:09:23.839 --> 00:09:25.590 align:start position:0% long time i mean it's not a long time if you're<00:09:24.000> running<00:09:24.399> multiple<00:09:24.800> replicas<00:09:25.360> of<00:09:25.519> a 00:09:25.590 --> 00:09:25.600 align:start position:0% you're running multiple replicas of a 00:09:25.600 --> 00:09:27.829 align:start position:0% you're running multiple replicas of a pod<00:09:25.920> and<00:09:26.080> you're<00:09:26.240> running<00:09:26.480> pods<00:09:26.800> in<00:09:26.959> aj<00:09:27.680> you 00:09:27.829 --> 00:09:27.839 align:start position:0% pod and you're running pods in aj you 00:09:27.839 --> 00:09:29.750 align:start position:0% pod and you're running pods in aj you would<00:09:28.000> almost<00:09:28.480> not<00:09:28.640> notice<00:09:29.040> at<00:09:29.200> all 00:09:29.750 --> 00:09:29.760 align:start position:0% would almost not notice at all 00:09:29.760 --> 00:09:31.829 align:start position:0% would almost not notice at all especially<00:09:30.320> in<00:09:30.399> larger<00:09:30.800> installations<00:09:31.680> but 00:09:31.829 --> 00:09:31.839 align:start position:0% especially in larger installations but 00:09:31.839 --> 00:09:34.230 align:start position:0% especially in larger installations but in<00:09:32.000> smaller<00:09:32.399> installations<00:09:33.200> like<00:09:33.440> home<00:09:33.760> labs 00:09:34.230 --> 00:09:34.240 align:start position:0% in smaller installations like home labs 00:09:34.240 --> 00:09:36.389 align:start position:0% in smaller installations like home labs i<00:09:34.399> found<00:09:34.640> that<00:09:34.800> five<00:09:35.120> minutes<00:09:35.600> is<00:09:35.760> a<00:09:36.080> really 00:09:36.389 --> 00:09:36.399 align:start position:0% i found that five minutes is a really 00:09:36.399 --> 00:09:38.310 align:start position:0% i found that five minutes is a really long<00:09:36.640> time<00:09:37.120> especially<00:09:37.600> if<00:09:37.680> you're<00:09:37.839> running<00:09:38.160> a 00:09:38.310 --> 00:09:38.320 align:start position:0% long time especially if you're running a 00:09:38.320 --> 00:09:40.630 align:start position:0% long time especially if you're running a replica<00:09:38.959> of<00:09:39.200> one<00:09:39.680> that<00:09:39.839> means<00:09:40.080> your<00:09:40.240> service 00:09:40.630 --> 00:09:40.640 align:start position:0% replica of one that means your service 00:09:40.640 --> 00:09:42.630 align:start position:0% replica of one that means your service is<00:09:40.720> down<00:09:41.040> for<00:09:41.360> at<00:09:41.440> least<00:09:41.680> five<00:09:41.920> minutes<00:09:42.480> so 00:09:42.630 --> 00:09:42.640 align:start position:0% is down for at least five minutes so 00:09:42.640 --> 00:09:44.550 align:start position:0% is down for at least five minutes so i've<00:09:42.880> scraped<00:09:43.200> the<00:09:43.360> internet<00:09:43.920> found<00:09:44.160> a<00:09:44.240> lot<00:09:44.399> of 00:09:44.550 --> 00:09:44.560 align:start position:0% i've scraped the internet found a lot of 00:09:44.560 --> 00:09:46.150 align:start position:0% i've scraped the internet found a lot of these<00:09:44.720> arguments<00:09:45.200> and<00:09:45.440> i've<00:09:45.680> been<00:09:45.839> using 00:09:46.150 --> 00:09:46.160 align:start position:0% these arguments and i've been using 00:09:46.160 --> 00:09:48.470 align:start position:0% these arguments and i've been using these<00:09:46.399> in<00:09:46.560> my<00:09:46.880> home<00:09:47.279> production 00:09:48.470 --> 00:09:48.480 align:start position:0% these in my home production 00:09:48.480 --> 00:09:49.829 align:start position:0% these in my home production home<00:09:48.720> lab 00:09:49.829 --> 00:09:49.839 align:start position:0% home lab 00:09:49.839 --> 00:09:51.430 align:start position:0% home lab for<00:09:50.000> about<00:09:50.240> a<00:09:50.320> year<00:09:50.480> now<00:09:50.880> and<00:09:50.959> they<00:09:51.120> seem<00:09:51.360> to 00:09:51.430 --> 00:09:51.440 align:start position:0% for about a year now and they seem to 00:09:51.440 --> 00:09:52.870 align:start position:0% for about a year now and they seem to work<00:09:51.680> pretty<00:09:51.839> well<00:09:52.080> but<00:09:52.320> you<00:09:52.480> might<00:09:52.640> need<00:09:52.800> to 00:09:52.870 --> 00:09:52.880 align:start position:0% work pretty well but you might need to 00:09:52.880 --> 00:09:54.630 align:start position:0% work pretty well but you might need to do<00:09:53.120> some<00:09:53.279> tweaking<00:09:53.680> depending<00:09:54.160> on<00:09:54.399> your 00:09:54.630 --> 00:09:54.640 align:start position:0% do some tweaking depending on your 00:09:54.640 --> 00:09:57.269 align:start position:0% do some tweaking depending on your services<00:09:55.519> your<00:09:55.680> hardware<00:09:56.640> and<00:09:56.800> what<00:09:57.040> works 00:09:57.269 --> 00:09:57.279 align:start position:0% services your hardware and what works 00:09:57.279 --> 00:09:59.350 align:start position:0% services your hardware and what works best<00:09:57.519> for<00:09:57.680> you<00:09:58.000> and<00:09:58.080> again<00:09:58.399> k3s<00:09:59.040> will<00:09:59.200> work 00:09:59.350 --> 00:09:59.360 align:start position:0% best for you and again k3s will work 00:09:59.360 --> 00:10:01.110 align:start position:0% best for you and again k3s will work without<00:09:59.839> any<00:10:00.080> of<00:10:00.160> those<00:10:00.320> arguments<00:10:00.800> i<00:10:00.880> just 00:10:01.110 --> 00:10:01.120 align:start position:0% without any of those arguments i just 00:10:01.120 --> 00:10:02.949 align:start position:0% without any of those arguments i just mentioned<00:10:01.839> and<00:10:02.160> maybe<00:10:02.480> you<00:10:02.560> should<00:10:02.720> try<00:10:02.880> it 00:10:02.949 --> 00:10:02.959 align:start position:0% mentioned and maybe you should try it 00:10:02.959 --> 00:10:05.030 align:start position:0% mentioned and maybe you should try it that<00:10:03.120> way<00:10:03.360> first<00:10:03.839> next<00:10:04.079> i<00:10:04.240> set<00:10:04.399> the<00:10:04.640> tag 00:10:05.030 --> 00:10:05.040 align:start position:0% that way first next i set the tag 00:10:05.040 --> 00:10:07.030 align:start position:0% that way first next i set the tag version<00:10:05.440> for<00:10:05.600> cube<00:10:05.920> vib<00:10:06.399> and<00:10:06.560> this<00:10:06.720> is<00:10:06.800> just 00:10:07.030 --> 00:10:07.040 align:start position:0% version for cube vib and this is just 00:10:07.040 --> 00:10:08.710 align:start position:0% version for cube vib and this is just the<00:10:07.120> container<00:10:07.680> image<00:10:07.920> tag<00:10:08.320> the<00:10:08.399> current 00:10:08.710 --> 00:10:08.720 align:start position:0% the container image tag the current 00:10:08.720 --> 00:10:10.110 align:start position:0% the container image tag the current version<00:10:09.120> is 00:10:10.110 --> 00:10:10.120 align:start position:0% version is 00:10:10.120 --> 00:10:13.030 align:start position:0% version is v0.4.2<00:10:11.200> and<00:10:11.360> so<00:10:11.760> that's<00:10:12.000> what<00:10:12.240> i'm<00:10:12.399> specifying 00:10:13.030 --> 00:10:13.040 align:start position:0% v0.4.2 and so that's what i'm specifying 00:10:13.040 --> 00:10:15.590 align:start position:0% v0.4.2 and so that's what i'm specifying here<00:10:13.440> and<00:10:13.600> i<00:10:13.760> did<00:10:14.240> similar<00:10:14.720> things<00:10:14.959> for<00:10:15.279> metal 00:10:15.590 --> 00:10:15.600 align:start position:0% here and i did similar things for metal 00:10:15.600 --> 00:10:18.790 align:start position:0% here and i did similar things for metal lb<00:10:16.079> too<00:10:16.640> so<00:10:16.800> for<00:10:17.120> metal<00:10:17.440> lb<00:10:17.839> there's<00:10:18.079> a<00:10:18.320> speaker 00:10:18.790 --> 00:10:18.800 align:start position:0% lb too so for metal lb there's a speaker 00:10:18.800 --> 00:10:21.230 align:start position:0% lb too so for metal lb there's a speaker container<00:10:19.440> which<00:10:19.760> the<00:10:19.920> latest<00:10:20.240> version<00:10:20.560> is 00:10:21.230 --> 00:10:21.240 align:start position:0% container which the latest version is 00:10:21.240 --> 00:10:24.069 align:start position:0% container which the latest version is 0.12.1<00:10:22.320> and<00:10:22.480> then<00:10:22.640> there's<00:10:22.880> a<00:10:23.200> controller<00:10:23.760> tag 00:10:24.069 --> 00:10:24.079 align:start position:0% 0.12.1 and then there's a controller tag 00:10:24.079 --> 00:10:27.509 align:start position:0% 0.12.1 and then there's a controller tag as<00:10:24.240> well<00:10:24.800> which<00:10:25.040> i<00:10:25.279> also<00:10:25.600> set<00:10:25.839> to<00:10:26.200> 0.12.1<00:10:27.279> now 00:10:27.509 --> 00:10:27.519 align:start position:0% as well which i also set to 0.12.1 now 00:10:27.519 --> 00:10:29.350 align:start position:0% as well which i also set to 0.12.1 now these<00:10:27.680> should<00:10:27.839> be<00:10:28.240> lockstep<00:10:28.880> in<00:10:28.959> the<00:10:29.120> same 00:10:29.350 --> 00:10:29.360 align:start position:0% these should be lockstep in the same 00:10:29.360 --> 00:10:31.430 align:start position:0% these should be lockstep in the same version<00:10:29.760> but<00:10:29.920> i<00:10:30.079> made<00:10:30.320> it<00:10:30.399> configurable<00:10:31.120> in<00:10:31.200> my 00:10:31.430 --> 00:10:31.440 align:start position:0% version but i made it configurable in my 00:10:31.440 --> 00:10:33.430 align:start position:0% version but i made it configurable in my template<00:10:32.160> just<00:10:32.399> in<00:10:32.480> case<00:10:32.720> they're<00:10:32.880> not<00:10:33.279> so 00:10:33.430 --> 00:10:33.440 align:start position:0% template just in case they're not so 00:10:33.440 --> 00:10:35.030 align:start position:0% template just in case they're not so that<00:10:33.760> i<00:10:33.920> didn't<00:10:34.079> have<00:10:34.240> to<00:10:34.320> figure<00:10:34.560> that<00:10:34.800> out<00:10:34.959> in 00:10:35.030 --> 00:10:35.040 align:start position:0% that i didn't have to figure that out in 00:10:35.040 --> 00:10:37.430 align:start position:0% that i didn't have to figure that out in the<00:10:35.120> future<00:10:35.600> and<00:10:35.760> next<00:10:36.000> i<00:10:36.160> chose<00:10:36.480> an<00:10:36.720> ip<00:10:37.120> range 00:10:37.430 --> 00:10:37.440 align:start position:0% the future and next i chose an ip range 00:10:37.440 --> 00:10:40.470 align:start position:0% the future and next i chose an ip range for<00:10:37.600> metal<00:10:37.920> lb<00:10:38.560> so<00:10:38.800> this<00:10:39.040> is<00:10:39.200> the<00:10:39.440> range<00:10:39.760> of<00:10:39.920> ips 00:10:40.470 --> 00:10:40.480 align:start position:0% for metal lb so this is the range of ips 00:10:40.480 --> 00:10:43.030 align:start position:0% for metal lb so this is the range of ips that<00:10:40.720> when<00:10:40.880> you<00:10:41.040> expose<00:10:41.519> services<00:10:42.320> they'll<00:10:42.560> be 00:10:43.030 --> 00:10:43.040 align:start position:0% that when you expose services they'll be 00:10:43.040 --> 00:10:45.110 align:start position:0% that when you expose services they'll be exposed<00:10:43.600> on<00:10:43.839> and<00:10:44.000> you<00:10:44.160> can<00:10:44.399> communicate<00:10:44.880> with 00:10:45.110 --> 00:10:45.120 align:start position:0% exposed on and you can communicate with 00:10:45.120 --> 00:10:46.870 align:start position:0% exposed on and you can communicate with them<00:10:45.440> i'll<00:10:45.600> show<00:10:45.760> you<00:10:46.000> some<00:10:46.160> examples<00:10:46.640> here<00:10:46.800> in 00:10:46.870 --> 00:10:46.880 align:start position:0% them i'll show you some examples here in 00:10:46.880 --> 00:10:49.590 align:start position:0% them i'll show you some examples here in a<00:10:46.959> little<00:10:47.120> bit<00:10:47.440> but<00:10:47.600> i<00:10:47.760> set<00:10:48.000> a<00:10:48.079> range<00:10:48.399> from<00:10:48.800> 192 00:10:49.590 --> 00:10:49.600 align:start position:0% a little bit but i set a range from 192 00:10:49.600 --> 00:10:53.990 align:start position:0% a little bit but i set a range from 192 168<00:10:50.519> 30.80<00:10:51.760> all<00:10:51.920> the<00:10:52.000> way<00:10:52.160> up<00:10:52.399> to<00:10:52.560> 90.<00:10:53.279> so<00:10:53.440> i<00:10:53.519> get 00:10:53.990 --> 00:10:54.000 align:start position:0% 168 30.80 all the way up to 90. so i get 00:10:54.000 --> 00:10:56.630 align:start position:0% 168 30.80 all the way up to 90. so i get 10 00:10:56.630 --> 00:10:56.640 align:start position:0% 00:10:56.640 --> 00:10:59.750 align:start position:0% so<00:10:56.959> i<00:10:57.120> get<00:10:57.360> 11<00:10:57.839> ips<00:10:58.320> here<00:10:58.720> typically<00:10:59.279> i<00:10:59.519> only 00:10:59.750 --> 00:10:59.760 align:start position:0% so i get 11 ips here typically i only 00:10:59.760 --> 00:11:01.990 align:start position:0% so i get 11 ips here typically i only need<00:11:00.000> one<00:11:00.160> or<00:11:00.320> two<00:11:00.880> but<00:11:01.120> i<00:11:01.200> set<00:11:01.360> the<00:11:01.519> range<00:11:01.760> from 00:11:01.990 --> 00:11:02.000 align:start position:0% need one or two but i set the range from 00:11:02.000 --> 00:11:04.790 align:start position:0% need one or two but i set the range from 80<00:11:02.240> to<00:11:02.399> 90<00:11:02.880> just<00:11:03.200> in<00:11:03.360> case<00:11:03.920> after<00:11:04.240> that<00:11:04.560> i 00:11:04.790 --> 00:11:04.800 align:start position:0% 80 to 90 just in case after that i 00:11:04.800 --> 00:11:07.030 align:start position:0% 80 to 90 just in case after that i checked<00:11:05.040> my<00:11:05.200> host.ini<00:11:06.160> to<00:11:06.240> make<00:11:06.399> sure<00:11:06.640> i<00:11:06.720> had 00:11:07.030 --> 00:11:07.040 align:start position:0% checked my host.ini to make sure i had 00:11:07.040 --> 00:11:09.350 align:start position:0% checked my host.ini to make sure i had all<00:11:07.200> of<00:11:07.279> the<00:11:07.440> ip<00:11:07.839> addresses<00:11:08.320> in<00:11:08.480> here<00:11:09.040> and<00:11:09.200> the 00:11:09.350 --> 00:11:09.360 align:start position:0% all of the ip addresses in here and the 00:11:09.360 --> 00:11:11.190 align:start position:0% all of the ip addresses in here and the three<00:11:09.600> virtual<00:11:10.000> machines<00:11:10.480> i<00:11:10.560> am<00:11:10.720> going<00:11:10.880> to<00:11:10.959> use 00:11:11.190 --> 00:11:11.200 align:start position:0% three virtual machines i am going to use 00:11:11.200 --> 00:11:14.790 align:start position:0% three virtual machines i am going to use for<00:11:11.360> my<00:11:11.519> masters<00:11:12.079> are<00:11:12.320> 38<00:11:13.040> 39<00:11:13.760> and<00:11:14.000> 40.<00:11:14.560> these 00:11:14.790 --> 00:11:14.800 align:start position:0% for my masters are 38 39 and 40. these 00:11:14.800 --> 00:11:16.949 align:start position:0% for my masters are 38 39 and 40. these are<00:11:14.959> also<00:11:15.360> referred<00:11:15.760> to<00:11:16.079> as<00:11:16.399> your<00:11:16.640> server 00:11:16.949 --> 00:11:16.959 align:start position:0% are also referred to as your server 00:11:16.959 --> 00:11:19.190 align:start position:0% are also referred to as your server notes<00:11:17.440> and<00:11:17.519> then<00:11:17.760> my<00:11:18.079> worker<00:11:18.480> nodes<00:11:18.800> or<00:11:18.959> my 00:11:19.190 --> 00:11:19.200 align:start position:0% notes and then my worker nodes or my 00:11:19.200 --> 00:11:22.310 align:start position:0% notes and then my worker nodes or my agents<00:11:19.839> are<00:11:20.000> going<00:11:20.160> to<00:11:20.240> be<00:11:20.560> 41<00:11:21.279> and<00:11:21.360> 42.<00:11:22.160> so 00:11:22.310 --> 00:11:22.320 align:start position:0% agents are going to be 41 and 42. so 00:11:22.320 --> 00:11:24.389 align:start position:0% agents are going to be 41 and 42. so this<00:11:22.560> means<00:11:22.959> three<00:11:23.200> servers<00:11:23.600> with<00:11:23.839> kubernetes 00:11:24.389 --> 00:11:24.399 align:start position:0% this means three servers with kubernetes 00:11:24.399 --> 00:11:27.110 align:start position:0% this means three servers with kubernetes control<00:11:24.800> plane<00:11:25.279> and<00:11:25.519> ncd<00:11:26.240> making<00:11:26.640> it<00:11:26.720> highly 00:11:27.110 --> 00:11:27.120 align:start position:0% control plane and ncd making it highly 00:11:27.120 --> 00:11:29.430 align:start position:0% control plane and ncd making it highly available<00:11:27.839> and<00:11:27.920> then<00:11:28.240> two<00:11:28.480> worker<00:11:28.880> nodes<00:11:29.279> to 00:11:29.430 --> 00:11:29.440 align:start position:0% available and then two worker nodes to 00:11:29.440 --> 00:11:31.670 align:start position:0% available and then two worker nodes to run<00:11:29.680> my<00:11:29.839> user<00:11:30.160> workloads<00:11:30.959> and<00:11:31.120> if<00:11:31.200> i<00:11:31.360> had<00:11:31.519> more 00:11:31.670 --> 00:11:31.680 align:start position:0% run my user workloads and if i had more 00:11:31.680 --> 00:11:33.190 align:start position:0% run my user workloads and if i had more virtual<00:11:32.079> machines<00:11:32.480> i<00:11:32.560> would<00:11:32.720> just<00:11:32.959> add<00:11:33.040> them 00:11:33.190 --> 00:11:33.200 align:start position:0% virtual machines i would just add them 00:11:33.200 --> 00:11:35.110 align:start position:0% virtual machines i would just add them below<00:11:33.600> so<00:11:33.760> with<00:11:34.000> all<00:11:34.160> of<00:11:34.240> this<00:11:34.399> configured<00:11:34.959> i 00:11:35.110 --> 00:11:35.120 align:start position:0% below so with all of this configured i 00:11:35.120 --> 00:11:37.990 align:start position:0% below so with all of this configured i ran<00:11:35.360> the<00:11:35.680> site<00:11:36.079> playbook<00:11:36.959> and<00:11:37.279> pointed<00:11:37.680> it<00:11:37.839> at 00:11:37.990 --> 00:11:38.000 align:start position:0% ran the site playbook and pointed it at 00:11:38.000 --> 00:11:40.630 align:start position:0% ran the site playbook and pointed it at my<00:11:38.160> host.ini<00:11:39.279> but<00:11:39.440> before<00:11:39.839> i<00:11:39.920> did<00:11:40.160> that<00:11:40.399> i 00:11:40.630 --> 00:11:40.640 align:start position:0% my host.ini but before i did that i 00:11:40.640 --> 00:11:43.190 align:start position:0% my host.ini but before i did that i started<00:11:41.200> pinging<00:11:41.600> my<00:11:41.839> vip<00:11:42.480> obviously<00:11:43.040> it's 00:11:43.190 --> 00:11:43.200 align:start position:0% started pinging my vip obviously it's 00:11:43.200 --> 00:11:45.350 align:start position:0% started pinging my vip obviously it's not<00:11:43.440> there<00:11:44.000> as<00:11:44.160> soon<00:11:44.320> as<00:11:44.480> it<00:11:44.640> comes<00:11:44.959> up<00:11:45.200> it 00:11:45.350 --> 00:11:45.360 align:start position:0% not there as soon as it comes up it 00:11:45.360 --> 00:11:50.949 align:start position:0% not there as soon as it comes up it should<00:11:45.519> respond<00:11:46.560> so<00:11:46.800> i<00:11:46.880> ran<00:11:47.120> the<00:11:47.200> playbook 00:11:50.949 --> 00:11:50.959 align:start position:0% 00:11:50.959 --> 00:11:53.590 align:start position:0% and<00:11:51.120> it<00:11:51.360> installed<00:11:51.839> and<00:11:52.000> configured<00:11:52.639> k3s<00:11:53.440> on 00:11:53.590 --> 00:11:53.600 align:start position:0% and it installed and configured k3s on 00:11:53.600 --> 00:11:57.110 align:start position:0% and it installed and configured k3s on one<00:11:53.839> of<00:11:53.920> the<00:11:54.079> server<00:11:54.399> nodes 00:11:57.110 --> 00:11:57.120 align:start position:0% one of the server nodes 00:11:57.120 --> 00:11:58.949 align:start position:0% one of the server nodes shortly<00:11:57.519> after<00:11:57.760> that<00:11:58.000> the<00:11:58.240> vip<00:11:58.639> started 00:11:58.949 --> 00:11:58.959 align:start position:0% shortly after that the vip started 00:11:58.959 --> 00:12:01.190 align:start position:0% shortly after that the vip started responding<00:11:59.839> so<00:12:00.000> this<00:12:00.240> means<00:12:00.560> qvip<00:12:01.040> is 00:12:01.190 --> 00:12:01.200 align:start position:0% responding so this means qvip is 00:12:01.200 --> 00:12:03.590 align:start position:0% responding so this means qvip is installed<00:12:01.600> on<00:12:01.760> that<00:12:01.920> machine<00:12:02.720> and<00:12:02.880> the<00:12:03.040> vip<00:12:03.360> is 00:12:03.590 --> 00:12:03.600 align:start position:0% installed on that machine and the vip is 00:12:03.600 --> 00:12:06.470 align:start position:0% installed on that machine and the vip is up 00:12:06.470 --> 00:12:06.480 align:start position:0% 00:12:06.480 --> 00:12:07.990 align:start position:0% and<00:12:06.560> then<00:12:06.800> it<00:12:06.959> started<00:12:07.279> joining<00:12:07.760> other 00:12:07.990 --> 00:12:08.000 align:start position:0% and then it started joining other 00:12:08.000 --> 00:12:11.590 align:start position:0% and then it started joining other machines<00:12:08.480> to<00:12:08.639> the<00:12:08.720> cluster 00:12:11.590 --> 00:12:11.600 align:start position:0% machines to the cluster 00:12:11.600 --> 00:12:14.069 align:start position:0% machines to the cluster and<00:12:11.760> then<00:12:12.240> shortly<00:12:12.639> after<00:12:12.880> that<00:12:13.279> i<00:12:13.440> had<00:12:13.680> a<00:12:13.839> high 00:12:14.069 --> 00:12:14.079 align:start position:0% and then shortly after that i had a high 00:12:14.079 --> 00:12:17.509 align:start position:0% and then shortly after that i had a high availability<00:12:15.120> kubernetes<00:12:15.839> cluster<00:12:16.399> on<00:12:16.560> k3s 00:12:17.509 --> 00:12:17.519 align:start position:0% availability kubernetes cluster on k3s 00:12:17.519 --> 00:12:20.069 align:start position:0% availability kubernetes cluster on k3s and<00:12:17.600> that's<00:12:17.839> a<00:12:18.000> ha<00:12:18.480> cluster<00:12:19.120> with<00:12:19.360> that<00:12:19.519> cd 00:12:20.069 --> 00:12:20.079 align:start position:0% and that's a ha cluster with that cd 00:12:20.079 --> 00:12:22.870 align:start position:0% and that's a ha cluster with that cd with<00:12:20.320> a<00:12:20.399> load<00:12:20.560> balancer<00:12:21.120> that's<00:12:21.600> also<00:12:22.160> ha<00:12:22.720> for 00:12:22.870 --> 00:12:22.880 align:start position:0% with a load balancer that's also ha for 00:12:22.880 --> 00:12:26.069 align:start position:0% with a load balancer that's also ha for my<00:12:23.040> control<00:12:23.440> plane<00:12:23.920> and<00:12:24.399> aha<00:12:25.040> load<00:12:25.279> balancers 00:12:26.069 --> 00:12:26.079 align:start position:0% my control plane and aha load balancers 00:12:26.079 --> 00:12:27.990 align:start position:0% my control plane and aha load balancers for<00:12:26.320> all<00:12:26.480> of<00:12:26.560> my<00:12:26.720> services<00:12:27.360> but<00:12:27.519> we<00:12:27.680> need<00:12:27.839> to 00:12:27.990 --> 00:12:28.000 align:start position:0% for all of my services but we need to 00:12:28.000 --> 00:12:30.550 align:start position:0% for all of my services but we need to verify<00:12:28.959> hopefully<00:12:29.360> you<00:12:29.440> trust<00:12:29.760> me<00:12:30.160> but<00:12:30.320> let's 00:12:30.550 --> 00:12:30.560 align:start position:0% verify hopefully you trust me but let's 00:12:30.560 --> 00:12:33.350 align:start position:0% verify hopefully you trust me but let's also<00:12:30.880> verify<00:12:31.519> so<00:12:31.680> we<00:12:31.839> can<00:12:32.079> ssh<00:12:32.720> into<00:12:33.040> one<00:12:33.200> of 00:12:33.350 --> 00:12:33.360 align:start position:0% also verify so we can ssh into one of 00:12:33.360 --> 00:12:35.190 align:start position:0% also verify so we can ssh into one of our<00:12:33.519> server<00:12:33.839> nodes<00:12:34.320> once<00:12:34.560> we're<00:12:34.720> there<00:12:34.959> we<00:12:35.120> can 00:12:35.190 --> 00:12:35.200 align:start position:0% our server nodes once we're there we can 00:12:35.200 --> 00:12:37.590 align:start position:0% our server nodes once we're there we can run<00:12:35.440> sudo<00:12:35.839> coop<00:12:36.079> control<00:12:36.480> kit<00:12:36.720> nodes<00:12:37.360> and<00:12:37.440> we 00:12:37.590 --> 00:12:37.600 align:start position:0% run sudo coop control kit nodes and we 00:12:37.600 --> 00:12:39.910 align:start position:0% run sudo coop control kit nodes and we can<00:12:37.760> see<00:12:38.240> we<00:12:38.399> have<00:12:38.800> five<00:12:39.120> nodes<00:12:39.519> and<00:12:39.600> they're 00:12:39.910 --> 00:12:39.920 align:start position:0% can see we have five nodes and they're 00:12:39.920 --> 00:12:41.750 align:start position:0% can see we have five nodes and they're all<00:12:40.079> online<00:12:40.639> you<00:12:40.720> can<00:12:40.880> see<00:12:41.040> i<00:12:41.200> have<00:12:41.519> three 00:12:41.750 --> 00:12:41.760 align:start position:0% all online you can see i have three 00:12:41.760 --> 00:12:44.150 align:start position:0% all online you can see i have three control<00:12:42.160> plane<00:12:42.560> at<00:12:42.639> cd<00:12:43.040> masters 00:12:44.150 --> 00:12:44.160 align:start position:0% control plane at cd masters 00:12:44.160 --> 00:12:46.870 align:start position:0% control plane at cd masters and<00:12:44.720> two<00:12:45.279> workers<00:12:45.839> or<00:12:46.079> agents<00:12:46.480> ready<00:12:46.720> for 00:12:46.870 --> 00:12:46.880 align:start position:0% and two workers or agents ready for 00:12:46.880 --> 00:12:48.150 align:start position:0% and two workers or agents ready for workloads 00:12:48.150 --> 00:12:48.160 align:start position:0% workloads 00:12:48.160 --> 00:12:50.790 align:start position:0% workloads super<00:12:48.959> super<00:12:49.360> awesome 00:12:50.790 --> 00:12:50.800 align:start position:0% super super awesome 00:12:50.800 --> 00:12:53.509 align:start position:0% super super awesome so<00:12:50.959> instead<00:12:51.279> of<00:12:51.680> ssh<00:12:52.399> into<00:12:52.639> this<00:12:52.800> server<00:12:53.200> let's 00:12:53.509 --> 00:12:53.519 align:start position:0% so instead of ssh into this server let's 00:12:53.519 --> 00:12:56.069 align:start position:0% so instead of ssh into this server let's actually<00:12:53.920> copy<00:12:54.320> our<00:12:54.560> coup<00:12:54.800> config<00:12:55.360> locally<00:12:55.839> so 00:12:56.069 --> 00:12:56.079 align:start position:0% actually copy our coup config locally so 00:12:56.079 --> 00:12:57.990 align:start position:0% actually copy our coup config locally so we<00:12:56.160> can<00:12:56.320> run<00:12:56.560> the<00:12:56.720> rest<00:12:56.959> of<00:12:57.040> the<00:12:57.120> commands<00:12:57.839> so 00:12:57.990 --> 00:12:58.000 align:start position:0% we can run the rest of the commands so 00:12:58.000 --> 00:13:00.069 align:start position:0% we can run the rest of the commands so let's<00:12:58.320> exit<00:12:58.720> out<00:12:58.880> of<00:12:58.959> here<00:12:59.440> you'll<00:12:59.680> want<00:12:59.839> to 00:13:00.069 --> 00:13:00.079 align:start position:0% let's exit out of here you'll want to 00:13:00.079 --> 00:13:02.069 align:start position:0% let's exit out of here you'll want to make<00:13:00.240> a<00:13:00.399> directory<00:13:00.959> for<00:13:01.120> your<00:13:01.360> coup<00:13:01.600> config 00:13:02.069 --> 00:13:02.079 align:start position:0% make a directory for your coup config 00:13:02.079 --> 00:13:04.230 align:start position:0% make a directory for your coup config file<00:13:02.399> if<00:13:02.480> you've<00:13:02.720> never<00:13:02.959> done<00:13:03.200> this<00:13:03.440> before<00:13:03.920> or 00:13:04.230 --> 00:13:04.240 align:start position:0% file if you've never done this before or 00:13:04.240 --> 00:13:06.470 align:start position:0% file if you've never done this before or back<00:13:04.480> up<00:13:04.639> your<00:13:04.880> existing<00:13:05.440> coupe<00:13:05.680> config<00:13:06.079> file 00:13:06.470 --> 00:13:06.480 align:start position:0% back up your existing coupe config file 00:13:06.480 --> 00:13:08.790 align:start position:0% back up your existing coupe config file if<00:13:06.639> it's<00:13:06.800> there<00:13:07.279> then<00:13:07.440> we'll<00:13:07.600> just<00:13:08.000> scp<00:13:08.639> or 00:13:08.790 --> 00:13:08.800 align:start position:0% if it's there then we'll just scp or 00:13:08.800 --> 00:13:10.949 align:start position:0% if it's there then we'll just scp or secure<00:13:09.200> copy<00:13:09.839> that<00:13:10.079> file<00:13:10.399> from<00:13:10.560> one<00:13:10.720> of<00:13:10.800> the 00:13:10.949 --> 00:13:10.959 align:start position:0% secure copy that file from one of the 00:13:10.959 --> 00:13:13.030 align:start position:0% secure copy that file from one of the servers<00:13:11.360> back<00:13:11.519> to<00:13:11.680> our<00:13:11.839> local<00:13:12.079> machine<00:13:12.800> after 00:13:13.030 --> 00:13:13.040 align:start position:0% servers back to our local machine after 00:13:13.040 --> 00:13:15.350 align:start position:0% servers back to our local machine after it<00:13:13.200> transfers<00:13:14.000> we<00:13:14.160> can<00:13:14.320> run<00:13:14.560> a<00:13:14.720> coupe<00:13:14.880> control 00:13:15.350 --> 00:13:15.360 align:start position:0% it transfers we can run a coupe control 00:13:15.360 --> 00:13:17.750 align:start position:0% it transfers we can run a coupe control get<00:13:15.600> nodes<00:13:16.079> and<00:13:16.240> see<00:13:16.399> the<00:13:16.560> same<00:13:16.800> thing<00:13:17.360> awesome 00:13:17.750 --> 00:13:17.760 align:start position:0% get nodes and see the same thing awesome 00:13:17.760 --> 00:13:19.430 align:start position:0% get nodes and see the same thing awesome so<00:13:17.920> now<00:13:18.079> we<00:13:18.240> have<00:13:18.320> cube<00:13:18.560> control<00:13:18.959> running<00:13:19.279> on 00:13:19.430 --> 00:13:19.440 align:start position:0% so now we have cube control running on 00:13:19.440 --> 00:13:21.829 align:start position:0% so now we have cube control running on this<00:13:19.600> machine<00:13:20.320> next<00:13:20.639> i<00:13:20.880> created<00:13:21.279> a<00:13:21.519> super 00:13:21.829 --> 00:13:21.839 align:start position:0% this machine next i created a super 00:13:21.839 --> 00:13:24.710 align:start position:0% this machine next i created a super simple<00:13:22.320> nginx<00:13:22.880> deployment<00:13:23.440> for<00:13:23.600> kubernetes 00:13:24.710 --> 00:13:24.720 align:start position:0% simple nginx deployment for kubernetes 00:13:24.720 --> 00:13:27.269 align:start position:0% simple nginx deployment for kubernetes this<00:13:24.959> deploys<00:13:25.519> an<00:13:25.680> alpine<00:13:26.160> version<00:13:26.560> of<00:13:26.720> nginx 00:13:27.269 --> 00:13:27.279 align:start position:0% this deploys an alpine version of nginx 00:13:27.279 --> 00:13:29.430 align:start position:0% this deploys an alpine version of nginx and<00:13:27.440> sets<00:13:27.680> the<00:13:27.839> replicas<00:13:28.399> to<00:13:28.560> three<00:13:29.120> i<00:13:29.279> did 00:13:29.430 --> 00:13:29.440 align:start position:0% and sets the replicas to three i did 00:13:29.440 --> 00:13:31.590 align:start position:0% and sets the replicas to three i did that<00:13:29.600> by<00:13:29.760> running<00:13:30.079> coop<00:13:30.320> control<00:13:30.800> apply<00:13:31.200> dash 00:13:31.590 --> 00:13:31.600 align:start position:0% that by running coop control apply dash 00:13:31.600 --> 00:13:33.670 align:start position:0% that by running coop control apply dash f<00:13:32.000> and<00:13:32.079> then<00:13:32.240> the<00:13:32.399> path<00:13:32.720> to<00:13:32.880> the<00:13:33.040> deployment 00:13:33.670 --> 00:13:33.680 align:start position:0% f and then the path to the deployment 00:13:33.680 --> 00:13:36.069 align:start position:0% f and then the path to the deployment manifest<00:13:34.480> and<00:13:34.639> then<00:13:34.880> kubernetes<00:13:35.600> told<00:13:35.839> me 00:13:36.069 --> 00:13:36.079 align:start position:0% manifest and then kubernetes told me 00:13:36.079 --> 00:13:38.069 align:start position:0% manifest and then kubernetes told me that<00:13:36.320> deployment<00:13:36.959> was<00:13:37.200> created<00:13:37.760> then<00:13:38.000> i 00:13:38.069 --> 00:13:38.079 align:start position:0% that deployment was created then i 00:13:38.079 --> 00:13:39.350 align:start position:0% that deployment was created then i wanted<00:13:38.320> to<00:13:38.480> check<00:13:38.720> to<00:13:38.880> see<00:13:39.040> how<00:13:39.199> this 00:13:39.350 --> 00:13:39.360 align:start position:0% wanted to check to see how this 00:13:39.360 --> 00:13:41.990 align:start position:0% wanted to check to see how this deployment<00:13:39.920> was<00:13:40.079> doing<00:13:40.720> so<00:13:41.360> i<00:13:41.519> ran<00:13:41.760> coop 00:13:41.990 --> 00:13:42.000 align:start position:0% deployment was doing so i ran coop 00:13:42.000 --> 00:13:44.870 align:start position:0% deployment was doing so i ran coop control<00:13:42.560> describe<00:13:43.120> deployment<00:13:43.839> nginx<00:13:44.720> and 00:13:44.870 --> 00:13:44.880 align:start position:0% control describe deployment nginx and 00:13:44.880 --> 00:13:46.790 align:start position:0% control describe deployment nginx and you<00:13:45.040> can<00:13:45.199> see<00:13:45.519> it<00:13:45.760> is<00:13:45.920> deployed<00:13:46.480> and<00:13:46.639> the 00:13:46.790 --> 00:13:46.800 align:start position:0% you can see it is deployed and the 00:13:46.800 --> 00:13:49.430 align:start position:0% you can see it is deployed and the desired<00:13:47.360> state<00:13:47.680> is<00:13:48.079> three<00:13:48.720> and<00:13:48.959> three<00:13:49.199> were 00:13:49.430 --> 00:13:49.440 align:start position:0% desired state is three and three were 00:13:49.440 --> 00:13:51.750 align:start position:0% desired state is three and three were updated<00:13:50.000> three<00:13:50.240> total<00:13:50.720> three<00:13:51.040> available<00:13:51.600> and 00:13:51.750 --> 00:13:51.760 align:start position:0% updated three total three available and 00:13:51.760 --> 00:13:54.069 align:start position:0% updated three total three available and zero<00:13:52.240> unavailable<00:13:53.040> so<00:13:53.279> all<00:13:53.519> three<00:13:53.760> of<00:13:53.839> my 00:13:54.069 --> 00:13:54.079 align:start position:0% zero unavailable so all three of my 00:13:54.079 --> 00:13:56.230 align:start position:0% zero unavailable so all three of my nginx<00:13:54.560> pods<00:13:54.959> are<00:13:55.120> up<00:13:55.279> and<00:13:55.360> running<00:13:55.760> but<00:13:56.000> this 00:13:56.230 --> 00:13:56.240 align:start position:0% nginx pods are up and running but this 00:13:56.240 --> 00:13:58.470 align:start position:0% nginx pods are up and running but this doesn't<00:13:56.560> give<00:13:56.720> me<00:13:56.959> access<00:13:57.440> to<00:13:57.600> these<00:13:57.920> pods 00:13:58.470 --> 00:13:58.480 align:start position:0% doesn't give me access to these pods 00:13:58.480 --> 00:14:00.870 align:start position:0% doesn't give me access to these pods outside<00:13:58.880> of<00:13:59.040> kubernetes<00:14:00.000> this<00:14:00.240> is<00:14:00.399> where<00:14:00.720> a 00:14:00.870 --> 00:14:00.880 align:start position:0% outside of kubernetes this is where a 00:14:00.880 --> 00:14:03.430 align:start position:0% outside of kubernetes this is where a service<00:14:01.519> and<00:14:01.680> a<00:14:01.760> load<00:14:02.000> balancer<00:14:02.560> comes<00:14:02.880> in<00:14:03.279> the 00:14:03.430 --> 00:14:03.440 align:start position:0% service and a load balancer comes in the 00:14:03.440 --> 00:14:06.230 align:start position:0% service and a load balancer comes in the exact<00:14:03.920> reason<00:14:04.399> why<00:14:04.639> we<00:14:04.880> installed<00:14:05.360> metal<00:14:05.680> lb 00:14:06.230 --> 00:14:06.240 align:start position:0% exact reason why we installed metal lb 00:14:06.240 --> 00:14:08.710 align:start position:0% exact reason why we installed metal lb so<00:14:06.480> then<00:14:06.639> i<00:14:06.800> created<00:14:07.199> a<00:14:07.440> super<00:14:07.760> simple<00:14:08.320> service 00:14:08.710 --> 00:14:08.720 align:start position:0% so then i created a super simple service 00:14:08.720 --> 00:14:11.990 align:start position:0% so then i created a super simple service file<00:14:09.120> this<00:14:09.360> service<00:14:09.760> file<00:14:10.320> is<00:14:10.480> just<00:14:10.800> a<00:14:11.279> service 00:14:11.990 --> 00:14:12.000 align:start position:0% file this service file is just a service 00:14:12.000 --> 00:14:14.470 align:start position:0% file this service file is just a service pointing<00:14:12.480> to<00:14:12.959> the<00:14:13.199> app<00:14:13.519> of<00:14:13.680> nginx<00:14:14.240> that<00:14:14.399> we 00:14:14.470 --> 00:14:14.480 align:start position:0% pointing to the app of nginx that we 00:14:14.480 --> 00:14:16.710 align:start position:0% pointing to the app of nginx that we just<00:14:14.720> created<00:14:15.360> that<00:14:15.519> deployment<00:14:16.240> and<00:14:16.320> we<00:14:16.480> tell 00:14:16.710 --> 00:14:16.720 align:start position:0% just created that deployment and we tell 00:14:16.720 --> 00:14:19.350 align:start position:0% just created that deployment and we tell this<00:14:16.959> service<00:14:17.360> to<00:14:17.600> expose<00:14:18.000> it<00:14:18.240> on<00:14:18.399> port<00:14:18.720> 80<00:14:19.199> and 00:14:19.350 --> 00:14:19.360 align:start position:0% this service to expose it on port 80 and 00:14:19.360 --> 00:14:21.670 align:start position:0% this service to expose it on port 80 and that<00:14:19.519> the<00:14:19.760> target<00:14:20.240> port<00:14:20.560> for<00:14:20.800> that<00:14:21.040> container 00:14:21.670 --> 00:14:21.680 align:start position:0% that the target port for that container 00:14:21.680 --> 00:14:23.670 align:start position:0% that the target port for that container is<00:14:21.839> also<00:14:22.160> port<00:14:22.480> 80<00:14:22.880> and<00:14:23.040> here's<00:14:23.360> where<00:14:23.519> the 00:14:23.670 --> 00:14:23.680 align:start position:0% is also port 80 and here's where the 00:14:23.680 --> 00:14:25.990 align:start position:0% is also port 80 and here's where the magic<00:14:24.079> takes<00:14:24.399> place<00:14:25.040> we<00:14:25.199> tell<00:14:25.440> it<00:14:25.519> that<00:14:25.680> the 00:14:25.990 --> 00:14:26.000 align:start position:0% magic takes place we tell it that the 00:14:26.000 --> 00:14:28.470 align:start position:0% magic takes place we tell it that the type<00:14:26.480> is<00:14:26.800> type<00:14:27.120> load<00:14:27.360> balancer<00:14:28.000> this<00:14:28.240> tells 00:14:28.470 --> 00:14:28.480 align:start position:0% type is type load balancer this tells 00:14:28.480 --> 00:14:31.030 align:start position:0% type is type load balancer this tells kubernetes<00:14:29.519> to<00:14:29.680> tell<00:14:30.079> our<00:14:30.320> cloud<00:14:30.720> load 00:14:31.030 --> 00:14:31.040 align:start position:0% kubernetes to tell our cloud load 00:14:31.040 --> 00:14:34.150 align:start position:0% kubernetes to tell our cloud load balancer<00:14:31.839> to<00:14:32.000> give<00:14:32.160> us<00:14:32.399> an<00:14:32.560> ip<00:14:33.199> and<00:14:33.519> our<00:14:33.680> cloud 00:14:34.150 --> 00:14:34.160 align:start position:0% balancer to give us an ip and our cloud 00:14:34.160 --> 00:14:37.590 align:start position:0% balancer to give us an ip and our cloud load<00:14:34.480> balancer<00:14:35.279> right<00:14:35.519> now<00:14:36.160> is<00:14:36.320> metal<00:14:36.720> lb 00:14:37.590 --> 00:14:37.600 align:start position:0% load balancer right now is metal lb 00:14:37.600 --> 00:14:40.710 align:start position:0% load balancer right now is metal lb so<00:14:37.839> metal<00:14:38.240> lb<00:14:38.800> should<00:14:39.040> hand<00:14:39.279> us<00:14:39.519> an<00:14:39.680> ip<00:14:40.079> address 00:14:40.710 --> 00:14:40.720 align:start position:0% so metal lb should hand us an ip address 00:14:40.720 --> 00:14:43.030 align:start position:0% so metal lb should hand us an ip address that<00:14:40.880> we<00:14:41.120> specified<00:14:41.839> in<00:14:41.920> that<00:14:42.160> range<00:14:42.800> and<00:14:42.880> if 00:14:43.030 --> 00:14:43.040 align:start position:0% that we specified in that range and if 00:14:43.040 --> 00:14:44.790 align:start position:0% that we specified in that range and if all<00:14:43.199> of<00:14:43.279> that<00:14:43.519> happens<00:14:44.079> we<00:14:44.240> should<00:14:44.399> be<00:14:44.560> able<00:14:44.720> to 00:14:44.790 --> 00:14:44.800 align:start position:0% all of that happens we should be able to 00:14:44.800 --> 00:14:47.189 align:start position:0% all of that happens we should be able to get<00:14:45.040> to<00:14:45.199> our<00:14:45.360> service<00:14:46.160> so<00:14:46.320> then<00:14:46.560> i<00:14:46.639> ran<00:14:46.959> coop 00:14:47.189 --> 00:14:47.199 align:start position:0% get to our service so then i ran coop 00:14:47.199 --> 00:14:49.430 align:start position:0% get to our service so then i ran coop control<00:14:47.760> apply<00:14:48.079> dash<00:14:48.480> f<00:14:48.800> and<00:14:48.880> then<00:14:49.040> the<00:14:49.199> path 00:14:49.430 --> 00:14:49.440 align:start position:0% control apply dash f and then the path 00:14:49.440 --> 00:14:51.990 align:start position:0% control apply dash f and then the path to<00:14:49.600> the<00:14:49.760> service<00:14:50.160> file<00:14:50.720> kubernetes<00:14:51.440> told<00:14:51.680> me 00:14:51.990 --> 00:14:52.000 align:start position:0% to the service file kubernetes told me 00:14:52.000 --> 00:14:54.310 align:start position:0% to the service file kubernetes told me it<00:14:52.160> created<00:14:52.560> the<00:14:52.720> service<00:14:53.120> for<00:14:53.279> me<00:14:53.680> and<00:14:53.839> then<00:14:54.160> i 00:14:54.310 --> 00:14:54.320 align:start position:0% it created the service for me and then i 00:14:54.320 --> 00:14:56.389 align:start position:0% it created the service for me and then i wanted<00:14:54.639> to<00:14:54.800> verify<00:14:55.360> that<00:14:55.519> so<00:14:55.680> i<00:14:55.839> ran<00:14:56.160> coop 00:14:56.389 --> 00:14:56.399 align:start position:0% wanted to verify that so i ran coop 00:14:56.399 --> 00:14:59.189 align:start position:0% wanted to verify that so i ran coop control<00:14:56.880> describe<00:14:57.440> service<00:14:58.000> nginx<00:14:58.959> and<00:14:59.040> we 00:14:59.189 --> 00:14:59.199 align:start position:0% control describe service nginx and we 00:14:59.199 --> 00:15:01.829 align:start position:0% control describe service nginx and we could<00:14:59.440> see<00:14:59.760> here<00:15:00.160> that<00:15:00.399> it<00:15:00.560> exposed<00:15:01.360> a<00:15:01.600> load 00:15:01.829 --> 00:15:01.839 align:start position:0% could see here that it exposed a load 00:15:01.839 --> 00:15:04.629 align:start position:0% could see here that it exposed a load balancer<00:15:02.480> ingress<00:15:03.199> of<00:15:03.680> one<00:15:03.839> of<00:15:03.920> the<00:15:04.160> ip 00:15:04.629 --> 00:15:04.639 align:start position:0% balancer ingress of one of the ip 00:15:04.639 --> 00:15:07.670 align:start position:0% balancer ingress of one of the ip addresses<00:15:05.600> that<00:15:05.760> we<00:15:06.000> specified<00:15:06.639> in<00:15:06.800> metal<00:15:07.120> lb 00:15:07.670 --> 00:15:07.680 align:start position:0% addresses that we specified in metal lb 00:15:07.680 --> 00:15:10.230 align:start position:0% addresses that we specified in metal lb so<00:15:07.839> this<00:15:08.079> means<00:15:08.399> my<00:15:08.800> nginx<00:15:09.440> deployment<00:15:10.000> of 00:15:10.230 --> 00:15:10.240 align:start position:0% so this means my nginx deployment of 00:15:10.240 --> 00:15:13.030 align:start position:0% so this means my nginx deployment of three<00:15:10.560> pods<00:15:11.440> is<00:15:11.600> now<00:15:11.920> exposed<00:15:12.480> on<00:15:12.639> a<00:15:12.720> load 00:15:13.030 --> 00:15:13.040 align:start position:0% three pods is now exposed on a load 00:15:13.040 --> 00:15:18.470 align:start position:0% three pods is now exposed on a load balancer<00:15:13.680> at<00:15:13.760> this<00:15:14.079> ip<00:15:14.800> 192<00:15:15.680> 168<00:15:16.920> 30.80<00:15:18.160> and<00:15:18.320> if 00:15:18.470 --> 00:15:18.480 align:start position:0% balancer at this ip 192 168 30.80 and if 00:15:18.480 --> 00:15:20.949 align:start position:0% balancer at this ip 192 168 30.80 and if we<00:15:18.720> go<00:15:18.880> to<00:15:19.040> that<00:15:19.279> ip<00:15:19.600> address<00:15:20.160> we<00:15:20.320> can<00:15:20.560> see<00:15:20.800> the 00:15:20.949 --> 00:15:20.959 align:start position:0% we go to that ip address we can see the 00:15:20.959 --> 00:15:24.150 align:start position:0% we go to that ip address we can see the hello<00:15:21.360> world<00:15:21.680> page<00:15:22.000> from<00:15:22.240> engine<00:15:22.639> x<00:15:23.360> this<00:15:23.920> is 00:15:24.150 --> 00:15:24.160 align:start position:0% hello world page from engine x this is 00:15:24.160 --> 00:15:26.710 align:start position:0% hello world page from engine x this is so<00:15:24.560> awesome<00:15:25.279> so<00:15:25.440> this<00:15:25.680> proves<00:15:26.240> all<00:15:26.399> the<00:15:26.480> way 00:15:26.710 --> 00:15:26.720 align:start position:0% so awesome so this proves all the way 00:15:26.720 --> 00:15:29.110 align:start position:0% so awesome so this proves all the way through<00:15:26.959> that<00:15:27.199> middle<00:15:27.519> lb<00:15:28.079> is<00:15:28.240> working<00:15:28.720> but<00:15:28.880> we 00:15:29.110 --> 00:15:29.120 align:start position:0% through that middle lb is working but we 00:15:29.120 --> 00:15:32.230 align:start position:0% through that middle lb is working but we never<00:15:29.440> really<00:15:29.759> tested<00:15:30.160> the<00:15:30.560> ha<00:15:31.120> side<00:15:31.360> of<00:15:31.600> cubit 00:15:32.230 --> 00:15:32.240 align:start position:0% never really tested the ha side of cubit 00:15:32.240 --> 00:15:34.230 align:start position:0% never really tested the ha side of cubit we<00:15:32.399> know<00:15:32.560> that<00:15:32.720> we<00:15:32.880> can<00:15:33.120> issue<00:15:33.519> kubernetes 00:15:34.230 --> 00:15:34.240 align:start position:0% we know that we can issue kubernetes 00:15:34.240 --> 00:15:36.470 align:start position:0% we know that we can issue kubernetes commands<00:15:34.720> right<00:15:34.959> now<00:15:35.199> with<00:15:35.360> goog<00:15:35.680> control<00:15:36.320> but 00:15:36.470 --> 00:15:36.480 align:start position:0% commands right now with goog control but 00:15:36.480 --> 00:15:38.790 align:start position:0% commands right now with goog control but we<00:15:36.639> didn't<00:15:37.040> take<00:15:37.360> any<00:15:37.600> of<00:15:37.680> those<00:15:37.920> notes<00:15:38.240> down 00:15:38.790 --> 00:15:38.800 align:start position:0% we didn't take any of those notes down 00:15:38.800 --> 00:15:41.030 align:start position:0% we didn't take any of those notes down so<00:15:39.279> let's<00:15:39.519> do<00:15:39.680> that<00:15:40.000> too<00:15:40.399> so<00:15:40.560> i<00:15:40.639> started 00:15:41.030 --> 00:15:41.040 align:start position:0% so let's do that too so i started 00:15:41.040 --> 00:15:43.189 align:start position:0% so let's do that too so i started pinging<00:15:41.440> that<00:15:41.680> vip<00:15:42.079> and<00:15:42.240> while<00:15:42.480> doing<00:15:42.800> it<00:15:43.040> i 00:15:43.189 --> 00:15:43.199 align:start position:0% pinging that vip and while doing it i 00:15:43.199 --> 00:15:46.150 align:start position:0% pinging that vip and while doing it i remote<00:15:43.600> it<00:15:43.759> into<00:15:44.240> my<00:15:44.639> first<00:15:45.199> master<00:15:45.600> node<00:15:46.000> or 00:15:46.150 --> 00:15:46.160 align:start position:0% remote it into my first master node or 00:15:46.160 --> 00:15:47.749 align:start position:0% remote it into my first master node or the<00:15:46.320> server<00:15:46.720> node<00:15:46.959> that's<00:15:47.279> running<00:15:47.600> the 00:15:47.749 --> 00:15:47.759 align:start position:0% the server node that's running the 00:15:47.759 --> 00:15:49.590 align:start position:0% the server node that's running the control<00:15:48.160> plane<00:15:48.560> and<00:15:48.720> it's<00:15:48.880> also<00:15:49.199> one<00:15:49.440> of<00:15:49.519> the 00:15:49.590 --> 00:15:49.600 align:start position:0% control plane and it's also one of the 00:15:49.600 --> 00:15:51.189 align:start position:0% control plane and it's also one of the nodes<00:15:49.920> that's<00:15:50.160> running<00:15:50.480> cube<00:15:50.720> vip<00:15:50.959> that's 00:15:51.189 --> 00:15:51.199 align:start position:0% nodes that's running cube vip that's 00:15:51.199 --> 00:15:54.230 align:start position:0% nodes that's running cube vip that's supplying<00:15:51.920> this<00:15:52.240> vip<00:15:52.639> so<00:15:52.959> i<00:15:53.120> decided<00:15:53.600> to<00:15:54.000> shut 00:15:54.230 --> 00:15:54.240 align:start position:0% supplying this vip so i decided to shut 00:15:54.240 --> 00:15:57.030 align:start position:0% supplying this vip so i decided to shut it<00:15:54.320> down<00:15:54.959> and<00:15:55.279> as<00:15:55.519> you<00:15:55.680> can<00:15:55.920> see<00:15:56.160> on<00:15:56.480> the<00:15:56.639> right 00:15:57.030 --> 00:15:57.040 align:start position:0% it down and as you can see on the right 00:15:57.040 --> 00:15:59.590 align:start position:0% it down and as you can see on the right i'm<00:15:57.360> still<00:15:57.680> getting<00:15:58.000> responses<00:15:58.959> and<00:15:59.279> you<00:15:59.360> can 00:15:59.590 --> 00:15:59.600 align:start position:0% i'm still getting responses and you can 00:15:59.600 --> 00:16:01.430 align:start position:0% i'm still getting responses and you can see<00:15:59.759> on<00:15:59.920> the<00:16:00.079> left<00:16:00.720> i'm<00:16:00.880> not<00:16:01.120> getting<00:16:01.360> a 00:16:01.430 --> 00:16:01.440 align:start position:0% see on the left i'm not getting a 00:16:01.440 --> 00:16:03.829 align:start position:0% see on the left i'm not getting a response<00:16:01.920> from<00:16:02.160> that<00:16:02.320> machine<00:16:02.959> so<00:16:03.199> this<00:16:03.440> means 00:16:03.829 --> 00:16:03.839 align:start position:0% response from that machine so this means 00:16:03.839 --> 00:16:06.230 align:start position:0% response from that machine so this means we<00:16:04.000> have<00:16:04.160> an<00:16:04.399> h<00:16:04.560> a<00:16:04.720> vip<00:16:04.959> now<00:16:05.440> now<00:16:05.680> i<00:16:05.759> can't<00:16:06.000> shut 00:16:06.230 --> 00:16:06.240 align:start position:0% we have an h a vip now now i can't shut 00:16:06.240 --> 00:16:08.870 align:start position:0% we have an h a vip now now i can't shut down<00:16:06.560> a<00:16:06.720> second<00:16:07.120> node<00:16:07.600> an<00:16:07.759> aja<00:16:08.160> cluster<00:16:08.639> of 00:16:08.870 --> 00:16:08.880 align:start position:0% down a second node an aja cluster of 00:16:08.880 --> 00:16:11.189 align:start position:0% down a second node an aja cluster of only<00:16:09.199> three<00:16:09.440> nodes<00:16:09.839> can<00:16:10.079> only<00:16:10.560> lose<00:16:10.959> one 00:16:11.189 --> 00:16:11.199 align:start position:0% only three nodes can only lose one 00:16:11.199 --> 00:16:13.030 align:start position:0% only three nodes can only lose one machine<00:16:11.759> so<00:16:11.920> if<00:16:12.079> i<00:16:12.160> shut<00:16:12.399> down<00:16:12.720> another 00:16:13.030 --> 00:16:13.040 align:start position:0% machine so if i shut down another 00:16:13.040 --> 00:16:15.110 align:start position:0% machine so if i shut down another machine<00:16:13.680> i<00:16:13.759> won't<00:16:14.079> have<00:16:14.240> access<00:16:14.880> to 00:16:15.110 --> 00:16:15.120 align:start position:0% machine i won't have access to 00:16:15.120 --> 00:16:17.350 align:start position:0% machine i won't have access to kubernetes<00:16:15.920> but<00:16:16.079> i<00:16:16.240> will<00:16:16.480> still<00:16:16.720> have<00:16:16.959> access 00:16:17.350 --> 00:16:17.360 align:start position:0% kubernetes but i will still have access 00:16:17.360 --> 00:16:19.030 align:start position:0% kubernetes but i will still have access to<00:16:17.600> all<00:16:17.759> of<00:16:17.839> my<00:16:18.000> workloads<00:16:18.480> that<00:16:18.639> are<00:16:18.720> running 00:16:19.030 --> 00:16:19.040 align:start position:0% to all of my workloads that are running 00:16:19.040 --> 00:16:20.550 align:start position:0% to all of my workloads that are running it's<00:16:19.199> just<00:16:19.440> that<00:16:19.600> i<00:16:19.759> can't<00:16:20.000> change<00:16:20.240> the<00:16:20.399> state 00:16:20.550 --> 00:16:20.560 align:start position:0% it's just that i can't change the state 00:16:20.560 --> 00:16:23.030 align:start position:0% it's just that i can't change the state of<00:16:20.639> kubernetes<00:16:21.360> nor<00:16:21.839> access<00:16:22.320> it<00:16:22.480> over<00:16:22.800> coupe 00:16:23.030 --> 00:16:23.040 align:start position:0% of kubernetes nor access it over coupe 00:16:23.040 --> 00:16:24.389 align:start position:0% of kubernetes nor access it over coupe control<00:16:23.600> so 00:16:24.389 --> 00:16:24.399 align:start position:0% control so 00:16:24.399 --> 00:16:26.710 align:start position:0% control so this<00:16:24.639> is<00:16:25.120> so<00:16:25.360> awesome<00:16:25.839> so<00:16:26.079> i<00:16:26.240> started<00:16:26.560> that 00:16:26.710 --> 00:16:26.720 align:start position:0% this is so awesome so i started that 00:16:26.720 --> 00:16:28.710 align:start position:0% this is so awesome so i started that other<00:16:26.959> node<00:16:27.199> back<00:16:27.519> up<00:16:27.759> and<00:16:27.920> it's<00:16:28.079> responding 00:16:28.710 --> 00:16:28.720 align:start position:0% other node back up and it's responding 00:16:28.720 --> 00:16:31.269 align:start position:0% other node back up and it's responding and<00:16:28.959> obviously<00:16:29.680> qbip<00:16:30.160> is<00:16:30.240> still<00:16:30.480> responding 00:16:31.269 --> 00:16:31.279 align:start position:0% and obviously qbip is still responding 00:16:31.279 --> 00:16:33.269 align:start position:0% and obviously qbip is still responding so<00:16:31.600> what<00:16:31.759> does<00:16:31.920> one<00:16:32.160> do<00:16:32.399> after<00:16:32.639> we<00:16:32.800> build<00:16:33.040> the 00:16:33.269 --> 00:16:33.279 align:start position:0% so what does one do after we build the 00:16:33.279 --> 00:16:35.670 align:start position:0% so what does one do after we build the perfect<00:16:33.680> k3s<00:16:34.240> cluster 00:16:35.670 --> 00:16:35.680 align:start position:0% perfect k3s cluster 00:16:35.680 --> 00:16:37.990 align:start position:0% perfect k3s cluster we<00:16:35.839> burn<00:16:36.160> it<00:16:36.240> down<00:16:36.480> of<00:16:36.639> course<00:16:37.360> there's<00:16:37.600> also<00:16:37.920> a 00:16:37.990 --> 00:16:38.000 align:start position:0% we burn it down of course there's also a 00:16:38.000 --> 00:16:40.710 align:start position:0% we burn it down of course there's also a playbook<00:16:38.480> to<00:16:38.800> totally<00:16:39.279> reset<00:16:39.680> k3s<00:16:40.320> back<00:16:40.560> to 00:16:40.710 --> 00:16:40.720 align:start position:0% playbook to totally reset k3s back to 00:16:40.720 --> 00:16:42.389 align:start position:0% playbook to totally reset k3s back to its<00:16:40.880> initial<00:16:41.199> state<00:16:41.680> so<00:16:41.920> running<00:16:42.240> this 00:16:42.389 --> 00:16:42.399 align:start position:0% its initial state so running this 00:16:42.399 --> 00:16:44.470 align:start position:0% its initial state so running this playbook<00:16:42.959> and<00:16:43.120> pointing<00:16:43.519> at<00:16:43.600> the<00:16:43.839> same<00:16:44.079> host 00:16:44.470 --> 00:16:44.480 align:start position:0% playbook and pointing at the same host 00:16:44.480 --> 00:16:46.790 align:start position:0% playbook and pointing at the same host will<00:16:44.800> totally<00:16:45.279> clean<00:16:45.519> it<00:16:45.680> up<00:16:46.079> it'll<00:16:46.399> clean<00:16:46.639> up 00:16:46.790 --> 00:16:46.800 align:start position:0% will totally clean it up it'll clean up 00:16:46.800 --> 00:16:49.269 align:start position:0% will totally clean it up it'll clean up all<00:16:47.040> nodes<00:16:47.600> remove<00:16:48.160> all<00:16:48.399> containers<00:16:49.120> and 00:16:49.269 --> 00:16:49.279 align:start position:0% all nodes remove all containers and 00:16:49.279 --> 00:16:51.430 align:start position:0% all nodes remove all containers and reset<00:16:49.680> it<00:16:49.839> back<00:16:50.079> to<00:16:50.240> the<00:16:50.320> state<00:16:50.639> it<00:16:50.800> was<00:16:51.120> before 00:16:51.430 --> 00:16:51.440 align:start position:0% reset it back to the state it was before 00:16:51.440 --> 00:16:53.350 align:start position:0% reset it back to the state it was before we<00:16:51.680> ran<00:16:51.839> this<00:16:52.079> playbook<00:16:52.560> this<00:16:52.800> was<00:16:53.040> super 00:16:53.350 --> 00:16:53.360 align:start position:0% we ran this playbook this was super 00:16:53.360 --> 00:16:55.509 align:start position:0% we ran this playbook this was super handy<00:16:53.839> as<00:16:54.000> i<00:16:54.079> was<00:16:54.320> testing<00:16:54.639> on<00:16:54.720> my<00:16:54.880> changes 00:16:55.509 --> 00:16:55.519 align:start position:0% handy as i was testing on my changes 00:16:55.519 --> 00:16:57.590 align:start position:0% handy as i was testing on my changes must<00:16:55.759> have<00:16:55.920> run<00:16:56.160> this<00:16:56.800> at<00:16:56.880> least<00:16:57.199> a<00:16:57.279> thousand 00:16:57.590 --> 00:16:57.600 align:start position:0% must have run this at least a thousand 00:16:57.600 --> 00:16:59.670 align:start position:0% must have run this at least a thousand times<00:16:58.160> and<00:16:58.399> after<00:16:58.720> it's<00:16:58.880> done<00:16:59.120> we're<00:16:59.279> back<00:16:59.519> to 00:16:59.670 --> 00:16:59.680 align:start position:0% times and after it's done we're back to 00:16:59.680 --> 00:17:01.749 align:start position:0% times and after it's done we're back to a<00:16:59.759> good<00:16:59.920> state<00:17:00.320> one<00:17:00.560> note<00:17:01.040> you<00:17:01.199> might<00:17:01.440> want<00:17:01.600> to 00:17:01.749 --> 00:17:01.759 align:start position:0% a good state one note you might want to 00:17:01.759 --> 00:17:03.749 align:start position:0% a good state one note you might want to actually<00:17:02.160> reboot<00:17:02.480> them<00:17:02.720> afterwards<00:17:03.440> i've 00:17:03.749 --> 00:17:03.759 align:start position:0% actually reboot them afterwards i've 00:17:03.759 --> 00:17:05.429 align:start position:0% actually reboot them afterwards i've noticed<00:17:04.000> that<00:17:04.160> the<00:17:04.319> vip<00:17:04.640> stays<00:17:05.039> up<00:17:05.199> and<00:17:05.360> it 00:17:05.429 --> 00:17:05.439 align:start position:0% noticed that the vip stays up and it 00:17:05.439 --> 00:17:07.829 align:start position:0% noticed that the vip stays up and it will<00:17:05.600> respond<00:17:06.319> so<00:17:06.559> i<00:17:06.720> have<00:17:06.959> a<00:17:07.039> playbook<00:17:07.679> to 00:17:07.829 --> 00:17:07.839 align:start position:0% will respond so i have a playbook to 00:17:07.839 --> 00:17:09.909 align:start position:0% will respond so i have a playbook to reboot<00:17:08.400> all<00:17:08.559> of<00:17:08.640> these<00:17:08.880> machines<00:17:09.600> and<00:17:09.679> this 00:17:09.909 --> 00:17:09.919 align:start position:0% reboot all of these machines and this 00:17:09.919 --> 00:17:11.669 align:start position:0% reboot all of these machines and this playbook<00:17:10.319> will<00:17:10.559> actually<00:17:11.039> wait<00:17:11.199> for<00:17:11.360> them<00:17:11.520> to 00:17:11.669 --> 00:17:11.679 align:start position:0% playbook will actually wait for them to 00:17:11.679 --> 00:17:14.949 align:start position:0% playbook will actually wait for them to respond<00:17:12.480> before<00:17:12.880> it<00:17:13.039> reports<00:17:13.439> a<00:17:13.600> success 00:17:14.949 --> 00:17:14.959 align:start position:0% respond before it reports a success 00:17:14.959 --> 00:17:17.669 align:start position:0% respond before it reports a success just<00:17:15.199> like<00:17:15.439> that<00:17:15.839> and<00:17:16.000> so<00:17:16.400> this<00:17:16.720> is<00:17:17.120> everything 00:17:17.669 --> 00:17:17.679 align:start position:0% just like that and so this is everything 00:17:17.679 --> 00:17:19.429 align:start position:0% just like that and so this is everything that<00:17:17.919> everyone<00:17:18.480> struggles<00:17:18.959> with<00:17:19.199> when 00:17:19.429 --> 00:17:19.439 align:start position:0% that everyone struggles with when 00:17:19.439 --> 00:17:22.470 align:start position:0% that everyone struggles with when setting<00:17:19.760> up<00:17:19.919> k3s<00:17:20.959> no<00:17:21.120> more<00:17:21.360> using<00:17:21.679> mysql<00:17:22.319> and 00:17:22.470 --> 00:17:22.480 align:start position:0% setting up k3s no more using mysql and 00:17:22.480 --> 00:17:24.789 align:start position:0% setting up k3s no more using mysql and making<00:17:22.799> that<00:17:23.039> ha<00:17:23.600> if<00:17:23.679> you<00:17:23.839> don't<00:17:24.000> want<00:17:24.240> to<00:17:24.640> no 00:17:24.789 --> 00:17:24.799 align:start position:0% making that ha if you don't want to no 00:17:24.799 --> 00:17:26.470 align:start position:0% making that ha if you don't want to no more<00:17:24.959> spinning<00:17:25.360> up<00:17:25.600> additional<00:17:26.160> load 00:17:26.470 --> 00:17:26.480 align:start position:0% more spinning up additional load 00:17:26.480 --> 00:17:28.950 align:start position:0% more spinning up additional load balancers<00:17:27.120> and<00:17:27.280> keep<00:17:27.520> a<00:17:27.600> live<00:17:27.839> d<00:17:28.400> and<00:17:28.640> making 00:17:28.950 --> 00:17:28.960 align:start position:0% balancers and keep a live d and making 00:17:28.960 --> 00:17:31.669 align:start position:0% balancers and keep a live d and making those<00:17:29.280> aj<00:17:30.080> if<00:17:30.240> you<00:17:30.320> don't<00:17:30.480> want<00:17:30.720> to<00:17:31.200> no<00:17:31.360> more 00:17:31.669 --> 00:17:31.679 align:start position:0% those aj if you don't want to no more 00:17:31.679 --> 00:17:33.990 align:start position:0% those aj if you don't want to no more configuring<00:17:32.320> metal<00:17:32.640> lb<00:17:33.120> or<00:17:33.280> installing<00:17:33.760> with 00:17:33.990 --> 00:17:34.000 align:start position:0% configuring metal lb or installing with 00:17:34.000 --> 00:17:36.470 align:start position:0% configuring metal lb or installing with helm<00:17:34.559> if<00:17:34.720> you<00:17:34.799> don't<00:17:34.960> want<00:17:35.200> to<00:17:35.679> just<00:17:36.160> one 00:17:36.470 --> 00:17:36.480 align:start position:0% helm if you don't want to just one 00:17:36.480 --> 00:17:38.470 align:start position:0% helm if you don't want to just one simple<00:17:36.799> playbook<00:17:37.280> that<00:17:37.520> spins<00:17:37.840> up<00:17:38.160> all<00:17:38.320> of 00:17:38.470 --> 00:17:38.480 align:start position:0% simple playbook that spins up all of 00:17:38.480 --> 00:17:40.950 align:start position:0% simple playbook that spins up all of that<00:17:38.799> in<00:17:39.039> one<00:17:39.360> shot<00:17:39.760> and<00:17:39.919> then<00:17:40.320> you<00:17:40.559> can<00:17:40.720> burn 00:17:40.950 --> 00:17:40.960 align:start position:0% that in one shot and then you can burn 00:17:40.960 --> 00:17:43.029 align:start position:0% that in one shot and then you can burn it<00:17:41.039> down<00:17:41.280> if<00:17:41.440> you<00:17:41.520> want<00:17:41.760> to<00:17:42.000> too<00:17:42.320> so<00:17:42.559> again<00:17:42.880> a 00:17:43.029 --> 00:17:43.039 align:start position:0% it down if you want to too so again a 00:17:43.039 --> 00:17:45.270 align:start position:0% it down if you want to too so again a huge<00:17:43.360> thanks<00:17:43.679> to<00:17:43.840> the<00:17:44.000> k3s<00:17:44.640> community<00:17:45.120> who 00:17:45.270 --> 00:17:45.280 align:start position:0% huge thanks to the k3s community who 00:17:45.280 --> 00:17:47.270 align:start position:0% huge thanks to the k3s community who made<00:17:45.520> this<00:17:45.760> original<00:17:46.160> playbook<00:17:46.799> along<00:17:47.039> with 00:17:47.270 --> 00:17:47.280 align:start position:0% made this original playbook along with 00:17:47.280 --> 00:17:49.830 align:start position:0% made this original playbook along with jeff<00:17:47.520> gearling<00:17:48.080> thank<00:17:48.240> you<00:17:48.400> so<00:17:48.559> much<00:17:49.200> and<00:17:49.440> also 00:17:49.830 --> 00:17:49.840 align:start position:0% jeff gearling thank you so much and also 00:17:49.840 --> 00:17:53.430 align:start position:0% jeff gearling thank you so much and also thank<00:17:50.000> you<00:17:50.160> to<00:17:50.480> github<00:17:50.880> user212<00:17:51.919> 850a 00:17:53.430 --> 00:17:53.440 align:start position:0% thank you to github user212 850a 00:17:53.440 --> 00:17:55.270 align:start position:0% thank you to github user212 850a thank<00:17:53.679> you<00:17:53.840> so<00:17:54.000> much<00:17:54.400> i'll<00:17:54.640> have<00:17:54.799> links<00:17:55.120> in<00:17:55.200> the 00:17:55.270 --> 00:17:55.280 align:start position:0% thank you so much i'll have links in the 00:17:55.280 --> 00:17:57.110 align:start position:0% thank you so much i'll have links in the description<00:17:55.919> to<00:17:56.240> all<00:17:56.400> of<00:17:56.480> the<00:17:56.559> code<00:17:56.799> that<00:17:57.039> i 00:17:57.110 --> 00:17:57.120 align:start position:0% description to all of the code that i 00:17:57.120 --> 00:17:59.669 align:start position:0% description to all of the code that i have<00:17:57.679> in<00:17:57.840> the<00:17:57.919> description<00:17:58.480> below<00:17:59.120> so<00:17:59.360> what<00:17:59.600> do 00:17:59.669 --> 00:17:59.679 align:start position:0% have in the description below so what do 00:17:59.679 --> 00:18:01.990 align:start position:0% have in the description below so what do you<00:17:59.760> think<00:18:00.000> of<00:18:00.080> spinning<00:18:00.480> up<00:18:00.640> a<00:18:00.880> truly<00:18:01.440> ha 00:18:01.990 --> 00:18:02.000 align:start position:0% you think of spinning up a truly ha 00:18:02.000 --> 00:18:04.070 align:start position:0% you think of spinning up a truly ha version<00:18:02.240> of<00:18:02.400> k3s<00:18:02.960> using<00:18:03.280> ansible<00:18:03.760> is<00:18:03.919> there 00:18:04.070 --> 00:18:04.080 align:start position:0% version of k3s using ansible is there 00:18:04.080 --> 00:18:05.510 align:start position:0% version of k3s using ansible is there anything<00:18:04.400> i<00:18:04.480> should<00:18:04.720> contribute<00:18:05.280> to<00:18:05.440> the 00:18:05.510 --> 00:18:05.520 align:start position:0% anything i should contribute to the 00:18:05.520 --> 00:18:07.669 align:start position:0% anything i should contribute to the script<00:18:05.840> to<00:18:06.000> make<00:18:06.160> it<00:18:06.559> easier<00:18:06.880> for<00:18:07.039> you<00:18:07.360> let<00:18:07.520> me 00:18:07.669 --> 00:18:07.679 align:start position:0% script to make it easier for you let me 00:18:07.679 --> 00:18:09.909 align:start position:0% script to make it easier for you let me know<00:18:08.160> in<00:18:08.240> the<00:18:08.400> comments<00:18:08.720> section<00:18:09.039> below<00:18:09.600> and 00:18:09.909 --> 00:18:09.919 align:start position:0% know in the comments section below and 00:18:09.919 --> 00:18:11.669 align:start position:0% know in the comments section below and remember<00:18:10.400> if<00:18:10.480> you<00:18:10.640> found<00:18:11.039> anything<00:18:11.440> in<00:18:11.520> this 00:18:11.669 --> 00:18:11.679 align:start position:0% remember if you found anything in this 00:18:11.679 --> 00:18:13.029 align:start position:0% remember if you found anything in this video<00:18:11.919> helpful 00:18:13.029 --> 00:18:13.039 align:start position:0% video helpful 00:18:13.039 --> 00:18:15.350 align:start position:0% video helpful don't<00:18:13.200> forget<00:18:13.520> to<00:18:13.679> like<00:18:13.919> and<00:18:14.000> subscribe 00:18:15.350 --> 00:18:15.360 align:start position:0% don't forget to like and subscribe 00:18:15.360 --> 00:18:17.430 align:start position:0% don't forget to like and subscribe thanks<00:18:15.600> for<00:18:15.760> watching<00:18:16.160> fix<00:18:16.400> the<00:18:16.559> lights<00:18:16.880> i<00:18:17.280> if 00:18:17.430 --> 00:18:17.440 align:start position:0% thanks for watching fix the lights i if 00:18:17.440 --> 00:18:19.430 align:start position:0% thanks for watching fix the lights i if you<00:18:17.520> weren't<00:18:17.760> here<00:18:18.000> last<00:18:18.240> week<00:18:18.640> small<00:18:19.039> episode 00:18:19.430 --> 00:18:19.440 align:start position:0% you weren't here last week small episode 00:18:19.440 --> 00:18:20.630 align:start position:0% you weren't here last week small episode with<00:18:19.600> the<00:18:19.679> lights<00:18:19.919> i<00:18:20.000> couldn't<00:18:20.240> figure<00:18:20.480> out 00:18:20.630 --> 00:18:20.640 align:start position:0% with the lights i couldn't figure out 00:18:20.640 --> 00:18:22.710 align:start position:0% with the lights i couldn't figure out what<00:18:20.799> was<00:18:20.960> going<00:18:21.200> on<00:18:21.360> with<00:18:21.520> my<00:18:21.760> bottom<00:18:22.080> lights 00:18:22.710 --> 00:18:22.720 align:start position:0% what was going on with my bottom lights 00:18:22.720 --> 00:18:25.190 align:start position:0% what was going on with my bottom lights my<00:18:22.880> bottom<00:18:23.200> lights<00:18:23.679> ended<00:18:24.000> up<00:18:24.320> having<00:18:24.720> a<00:18:24.880> small 00:18:25.190 --> 00:18:25.200 align:start position:0% my bottom lights ended up having a small 00:18:25.200 --> 00:18:26.870 align:start position:0% my bottom lights ended up having a small issue<00:18:25.600> and<00:18:25.679> it<00:18:25.840> took<00:18:26.080> me<00:18:26.240> a<00:18:26.320> long<00:18:26.559> time<00:18:26.799> to 00:18:26.870 --> 00:18:26.880 align:start position:0% issue and it took me a long time to 00:18:26.880 --> 00:18:29.590 align:start position:0% issue and it took me a long time to figure<00:18:27.200> out<00:18:28.080> it<00:18:28.240> ended<00:18:28.559> up<00:18:28.640> being<00:18:28.960> a<00:18:29.120> firewall 00:18:29.590 --> 00:18:29.600 align:start position:0% figure out it ended up being a firewall 00:18:29.600 --> 00:18:32.310 align:start position:0% figure out it ended up being a firewall rule<00:18:29.840> so<00:18:30.080> if<00:18:30.240> it's<00:18:30.480> not<00:18:30.720> dns<00:18:31.440> it<00:18:31.600> is<00:18:31.760> a<00:18:31.840> firewall 00:18:32.310 --> 00:18:32.320 align:start position:0% rule so if it's not dns it is a firewall 00:18:32.320 --> 00:18:33.590 align:start position:0% rule so if it's not dns it is a firewall rule<00:18:32.559> all<00:18:32.720> right<00:18:32.960> changing<00:18:33.280> the<00:18:33.360> light<00:18:33.520> as 00:18:33.590 --> 00:18:33.600 align:start position:0% rule all right changing the light as 00:18:33.600 --> 00:18:35.430 align:start position:0% rule all right changing the light as soon<00:18:33.760> as<00:18:33.840> i<00:18:33.919> mention<00:18:34.240> them 00:18:35.430 --> 00:18:35.440 align:start position:0% soon as i mention them 00:18:35.440 --> 00:18:37.590 align:start position:0% soon as i mention them if<00:18:35.600> it's<00:18:35.760> not<00:18:35.919> dns<00:18:36.400> it's<00:18:36.559> a<00:18:36.640> firewall<00:18:37.039> rule<00:18:37.280> now 00:18:37.590 --> 00:18:37.600 align:start position:0% if it's not dns it's a firewall rule now 00:18:37.600 --> 00:18:38.950 align:start position:0% if it's not dns it's a firewall rule now now<00:18:37.760> you're<00:18:37.919> really<00:18:38.160> testing<00:18:38.480> mines<00:18:38.880> all 00:18:38.950 --> 00:18:38.960 align:start position:0% now you're really testing mines all 00:18:38.960 --> 00:18:40.549 align:start position:0% now you're really testing mines all right<00:18:39.600> it's<00:18:39.760> gonna<00:18:40.000> happen<00:18:40.320> it's<00:18:40.400> gonna 00:18:40.549 --> 00:18:40.559 align:start position:0% right it's gonna happen it's gonna 00:18:40.559 --> 00:18:43.120 align:start position:0% right it's gonna happen it's gonna happen<00:18:40.880> so