k9casca2/sub-en.vtt
2025-04-08 09:54:04 +02:00

3913 lines
169 KiB
Plaintext

WEBVTT
Kind: captions
Language: en
00:00:00.240 --> 00:00:03.830 align:start position:0%
words<00:00:00.560><c> to</c><00:00:00.719><c> describe</c><00:00:01.599><c> setting</c><00:00:02.000><c> up</c><00:00:02.159><c> k3s</c>
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><c> is</c><00:00:04.240><c> hard</c>
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><c> is</c><00:00:06.000><c> so</c><00:00:06.319><c> difficult</c><00:00:06.799><c> to</c><00:00:06.960><c> set</c><00:00:07.200><c> up</c>
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><c> this</c><00:00:08.559><c> overkill</c>
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><c> is</c><00:00:10.719><c> the</c><00:00:10.800><c> load</c><00:00:11.040><c> balancer</c><00:00:11.519><c> again</c>
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><c> do</c><00:00:13.679><c> i</c><00:00:13.759><c> need</c><00:00:14.080><c> two</c><00:00:14.320><c> load</c><00:00:14.559><c> balancers</c>
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><c> i</c><00:00:16.720><c> use</c><00:00:16.880><c> that</c><00:00:17.039><c> cd</c>
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><c> wait</c><00:00:18.880><c> i</c><00:00:19.039><c> need</c><00:00:19.359><c> two</c><00:00:19.600><c> load</c><00:00:19.840><c> balancers</c><00:00:20.640><c> and</c>
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><c> alive</c><00:00:21.439><c> d</c>
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><c> is</c><00:00:23.279><c> metal</c><00:00:23.600><c> lb</c><00:00:24.000><c> again</c>
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><c> you</c><00:00:25.680><c> heard</c><00:00:25.920><c> of</c><00:00:26.000><c> cubevip</c>
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><c> isn't</c><00:00:28.720><c> that</c><00:00:28.880><c> a</c><00:00:28.960><c> single</c><00:00:29.199><c> point</c><00:00:29.439><c> of</c><00:00:29.519><c> failure</c>
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><c> know</c>
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><c> automate</c><00:00:35.200><c> the</c><00:00:35.280><c> whole</c><00:00:35.520><c> thing</c>
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><c> we're</c><00:00:37.200><c> not</c><00:00:37.520><c> only</c><00:00:37.760><c> going</c><00:00:37.920><c> to</c><00:00:38.000><c> set</c><00:00:38.239><c> up</c><00:00:38.399><c> k3s</c>
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><c> ncd</c><00:00:39.920><c> and</c><00:00:40.160><c> ha</c><00:00:40.640><c> installation</c><00:00:41.440><c> with</c><00:00:41.760><c> cube</c>
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><c> and</c><00:00:42.640><c> middle</c><00:00:42.960><c> of</c><00:00:43.120><c> b</c><00:00:43.600><c> but</c><00:00:43.840><c> we're</c><00:00:44.079><c> also</c><00:00:44.719><c> going</c>
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><c> automate</c><00:00:45.680><c> the</c><00:00:45.840><c> whole</c><00:00:46.079><c> entire</c><00:00:46.480><c> thing</c><00:00:46.960><c> so</c>
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><c> we</c><00:00:47.840><c> can't</c><00:00:48.160><c> really</c><00:00:48.640><c> mess</c><00:00:48.960><c> this</c><00:00:49.200><c> up</c><00:00:49.600><c> and</c><00:00:49.680><c> so</c>
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><c> going</c><00:00:50.079><c> to</c><00:00:50.239><c> fully</c><00:00:50.640><c> automate</c><00:00:51.120><c> the</c>
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><c> of</c><00:00:52.079><c> k3s</c><00:00:52.800><c> so</c><00:00:52.960><c> that</c><00:00:53.199><c> it's</c><00:00:53.360><c> 100</c>
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><c> then</c><00:00:55.600><c> we're</c><00:00:55.760><c> gonna</c><00:00:56.239><c> tear</c><00:00:56.399><c> it</c><00:00:56.559><c> all</c><00:00:56.719><c> down</c><00:00:57.199><c> as</c>
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><c> it</c><00:00:57.600><c> never</c><00:00:57.840><c> happened</c><00:00:58.239><c> but</c><00:00:58.480><c> before</c><00:00:58.800><c> we</c><00:00:58.960><c> do</c><00:00:59.520><c> a</c>
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><c> thanks</c><00:01:00.559><c> to</c><00:01:00.719><c> our</c><00:01:00.879><c> sponsor</c><00:01:01.520><c> microcenter</c>
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><c> you're</c><00:01:02.719><c> thinking</c><00:01:03.039><c> of</c><00:01:03.120><c> building</c><00:01:03.440><c> a</c><00:01:03.520><c> new</c><00:01:03.760><c> pc</c>
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><c> should</c><00:01:04.559><c> look</c><00:01:04.720><c> no</c><00:01:04.879><c> further</c><00:01:05.199><c> than</c>
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><c> if</c><00:01:06.159><c> you've</c><00:01:06.320><c> never</c><00:01:06.560><c> been</c><00:01:06.720><c> to</c>
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><c> you're</c><00:01:07.760><c> missing</c><00:01:08.080><c> out</c><00:01:08.320><c> on</c><00:01:08.400><c> seeing</c>
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><c> huge</c><00:01:09.040><c> selection</c><00:01:09.439><c> of</c><00:01:09.600><c> technology</c><00:01:10.240><c> in</c><00:01:10.320><c> person</c>
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><c> got</c><00:01:11.360><c> everything</c><00:01:11.760><c> for</c><00:01:11.920><c> custom</c><00:01:12.320><c> pc</c>
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><c> from</c><00:01:13.439><c> ssds</c><00:01:14.080><c> and</c><00:01:14.159><c> hard</c><00:01:14.400><c> drives</c><00:01:14.880><c> to</c>
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><c> supplies</c><00:01:16.240><c> to</c><00:01:16.400><c> memory</c><00:01:17.119><c> to</c><00:01:17.280><c> air</c><00:01:17.680><c> and</c>
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><c> cooling</c><00:01:18.720><c> to</c><00:01:18.880><c> motherboards</c><00:01:19.920><c> to</c><00:01:20.080><c> video</c>
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><c> to</c><00:01:21.280><c> processors</c><00:01:22.240><c> and</c><00:01:22.479><c> more</c><00:01:22.880><c> microcenter</c>
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><c> your</c><00:01:23.759><c> one-stop</c><00:01:24.240><c> shop</c><00:01:24.479><c> to</c><00:01:24.640><c> totally</c>
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><c> your</c><00:01:25.680><c> next</c><00:01:25.920><c> pc</c><00:01:26.320><c> build</c><00:01:26.799><c> and</c><00:01:26.960><c> don't</c>
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><c> if</c><00:01:27.759><c> it's</c><00:01:27.840><c> your</c><00:01:28.000><c> first</c><00:01:28.240><c> time</c><00:01:28.400><c> building</c><00:01:28.720><c> a</c>
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><c> they</c><00:01:29.520><c> have</c><00:01:29.680><c> lots</c><00:01:29.920><c> of</c><00:01:30.079><c> helpful</c><00:01:30.560><c> and</c>
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><c> staff</c><00:01:31.520><c> that</c><00:01:31.680><c> are</c><00:01:31.840><c> there</c><00:01:32.000><c> to</c><00:01:32.159><c> help</c>
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><c> out</c><00:01:32.799><c> and</c><00:01:32.960><c> will</c><00:01:33.119><c> point</c><00:01:33.360><c> you</c><00:01:33.520><c> in</c><00:01:33.600><c> the</c><00:01:33.680><c> right</c>
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><c> so</c><00:01:34.799><c> that</c><00:01:34.960><c> you</c><00:01:35.119><c> don't</c><00:01:35.360><c> attempt</c><00:01:35.680><c> to</c>
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><c> thermal</c><00:01:36.479><c> paste</c><00:01:36.720><c> like</c><00:01:36.960><c> this</c>
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><c> has</c><00:01:41.840><c> been</c><00:01:42.000><c> kind</c><00:01:42.240><c> enough</c><00:01:42.560><c> to</c><00:01:42.640><c> give</c>
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><c> new</c><00:01:43.360><c> customers</c><00:01:43.920><c> a</c><00:01:44.079><c> free</c><00:01:44.399><c> ssd</c><00:01:45.119><c> and</c><00:01:45.280><c> it's</c>
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><c> in</c><00:01:46.320><c> store</c><00:01:46.640><c> only</c><00:01:47.280><c> so</c><00:01:47.439><c> see</c><00:01:47.600><c> the</c><00:01:47.759><c> link</c>
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><c> the</c><00:01:48.159><c> description</c><00:01:48.720><c> for</c><00:01:48.880><c> details</c><00:01:49.759><c> so</c><00:01:50.159><c> how</c>
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><c> i</c><00:01:50.640><c> get</c><00:01:50.880><c> here</c><00:01:51.280><c> well</c><00:01:51.600><c> as</c><00:01:51.759><c> you</c><00:01:51.920><c> may</c><00:01:52.079><c> or</c><00:01:52.159><c> may</c>
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><c> know</c><00:01:52.880><c> i've</c><00:01:53.040><c> been</c><00:01:53.200><c> running</c><00:01:53.520><c> k3s</c><00:01:54.240><c> in</c><00:01:54.320><c> my</c><00:01:54.479><c> own</c>
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><c> for</c><00:01:55.439><c> quite</c><00:01:55.680><c> some</c><00:01:55.920><c> time</c><00:01:56.320><c> and</c><00:01:56.479><c> i</c>
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><c> have</c><00:01:57.040><c> a</c><00:01:57.119><c> video</c><00:01:57.439><c> on</c><00:01:57.600><c> setting</c><00:01:57.920><c> up</c><00:01:58.079><c> k3s</c><00:01:58.799><c> with</c>
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><c> sequel</c><00:01:59.840><c> now</c><00:02:00.000><c> there's</c><00:02:00.240><c> nothing</c><00:02:00.560><c> wrong</c><00:02:00.799><c> with</c>
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><c> k3s</c><00:02:01.600><c> version</c><00:02:01.920><c> of</c><00:02:02.000><c> my</c><00:02:02.240><c> sequel</c><00:02:02.799><c> it</c><00:02:02.960><c> runs</c>
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><c> but</c><00:02:03.920><c> at</c><00:02:04.000><c> the</c><00:02:04.159><c> time</c><00:02:04.640><c> the</c><00:02:04.799><c> lcd</c><00:02:05.360><c> version</c>
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><c> available</c><00:02:06.719><c> and</c><00:02:06.880><c> the</c><00:02:07.040><c> lcd</c><00:02:07.520><c> version</c><00:02:07.920><c> is</c>
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><c> interesting</c><00:02:09.039><c> because</c><00:02:09.360><c> it</c><00:02:09.520><c> creates</c><00:02:09.840><c> a</c>
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><c> availability</c><00:02:11.200><c> database</c><00:02:11.920><c> on</c><00:02:12.080><c> the</c><00:02:12.239><c> nodes</c>
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><c> of</c><00:02:13.599><c> hosting</c><00:02:14.080><c> it</c><00:02:14.400><c> outside</c><00:02:14.879><c> of</c><00:02:14.959><c> the</c>
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><c> and</c><00:02:15.920><c> right</c><00:02:16.160><c> around</c><00:02:16.400><c> that</c><00:02:16.640><c> time</c><00:02:16.879><c> i</c><00:02:16.959><c> saw</c>
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><c> galen</c><00:02:17.840><c> create</c><00:02:18.080><c> a</c><00:02:18.160><c> video</c><00:02:18.480><c> on</c><00:02:18.720><c> ansible</c><00:02:19.360><c> and</c>
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><c> sent</c><00:02:19.840><c> me</c><00:02:20.000><c> down</c><00:02:20.160><c> a</c><00:02:20.239><c> rabbit</c><00:02:20.560><c> hole</c><00:02:20.959><c> learning</c>
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><c> creating</c><00:02:22.319><c> a</c><00:02:22.480><c> video</c><00:02:22.800><c> on</c><00:02:23.040><c> ansible</c><00:02:23.920><c> and</c>
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><c> a</c><00:02:24.959><c> lot</c><00:02:25.120><c> of</c><00:02:25.360><c> tasks</c><00:02:26.080><c> well</c><00:02:26.480><c> you</c><00:02:26.640><c> know</c>
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><c> that</c><00:02:27.120><c> goes</c><00:02:27.760><c> anyway</c><00:02:28.480><c> so</c><00:02:28.640><c> i</c><00:02:28.800><c> found</c><00:02:29.040><c> that</c>
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><c> repo</c><00:02:30.239><c> i</c><00:02:30.400><c> cloned</c><00:02:30.800><c> it</c><00:02:30.959><c> and</c><00:02:31.120><c> created</c><00:02:31.440><c> some</c>
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><c> machines</c><00:02:32.640><c> and</c><00:02:32.800><c> then</c><00:02:32.959><c> i</c><00:02:33.120><c> tried</c><00:02:33.280><c> to</c>
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><c> a</c><00:02:34.239><c> high</c><00:02:34.480><c> availability</c><00:02:35.200><c> cluster</c>
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><c> there</c><00:02:36.400><c> was</c><00:02:36.640><c> just</c><00:02:36.879><c> one</c><00:02:37.120><c> problem</c><00:02:37.519><c> the</c>
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><c> playbook</c><00:02:38.720><c> only</c><00:02:39.040><c> supported</c><00:02:39.519><c> spinning</c>
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><c> one</c><00:02:40.640><c> lcd</c><00:02:41.200><c> node</c><00:02:41.599><c> and</c><00:02:41.760><c> that</c><00:02:42.000><c> meant</c><00:02:42.400><c> only</c><00:02:42.879><c> one</c>
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><c> node</c><00:02:43.840><c> which</c><00:02:44.239><c> isn't</c><00:02:44.560><c> ha</c><00:02:45.200><c> i</c><00:02:45.280><c> mean</c><00:02:45.599><c> it's</c>
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><c> for</c><00:02:46.560><c> ha</c><00:02:47.120><c> but</c><00:02:47.280><c> i</c><00:02:47.440><c> would</c><00:02:47.599><c> have</c><00:02:47.760><c> to</c>
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><c> add</c><00:02:49.040><c> additional</c><00:02:49.519><c> server</c><00:02:49.840><c> nodes</c><00:02:50.160><c> to</c>
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><c> it</c><00:02:50.879><c> ha</c><00:02:51.519><c> and</c><00:02:51.680><c> that's</c><00:02:51.920><c> no</c><00:02:52.160><c> fun</c><00:02:52.560><c> so</c>
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><c> it</c><00:02:53.440><c> wasn't</c><00:02:53.920><c> ha</c><00:02:54.560><c> out</c><00:02:54.720><c> of</c><00:02:54.800><c> the</c><00:02:54.879><c> box</c>
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><c> i</c><00:02:55.920><c> decided</c><00:02:56.319><c> to</c><00:02:56.480><c> dig</c><00:02:56.640><c> around</c><00:02:57.120><c> in</c><00:02:57.200><c> the</c><00:02:57.360><c> code</c>
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><c> in</c><00:02:58.159><c> the</c><00:02:58.319><c> branches</c><00:02:58.959><c> and</c><00:02:59.120><c> i</c><00:02:59.280><c> found</c><00:02:59.519><c> a</c><00:02:59.599><c> fork</c>
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><c> somebody</c><00:03:00.480><c> actually</c><00:03:01.040><c> fixed</c><00:03:01.519><c> that</c><00:03:01.840><c> issue</c>
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><c> i</c><00:03:02.560><c> could</c><00:03:02.720><c> actually</c><00:03:03.120><c> create</c><00:03:03.360><c> an</c><00:03:03.599><c> h</c><00:03:03.840><c> a</c>
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><c> out</c><00:03:04.800><c> of</c><00:03:04.879><c> the</c><00:03:04.959><c> box</c><00:03:05.280><c> with</c><00:03:05.519><c> ansible</c><00:03:05.920><c> and</c>
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><c> saw</c><00:03:06.480><c> they</c><00:03:06.720><c> also</c><00:03:07.040><c> added</c><00:03:07.360><c> support</c><00:03:07.680><c> for</c><00:03:07.920><c> cube</c>
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><c> this</c><00:03:08.800><c> was</c><00:03:09.040><c> awesome</c><00:03:09.440><c> because</c><00:03:09.920><c> this</c><00:03:10.159><c> is</c>
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><c> what</c><00:03:11.599><c> i</c><00:03:11.680><c> was</c><00:03:11.920><c> trying</c><00:03:12.239><c> to</c><00:03:12.400><c> do</c><00:03:13.040><c> i</c><00:03:13.200><c> love</c>
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><c> source</c><00:03:14.319><c> so</c><00:03:14.480><c> a</c><00:03:14.560><c> huge</c><00:03:14.879><c> thank</c><00:03:15.120><c> you</c><00:03:15.360><c> to</c><00:03:15.519><c> user</c>
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><c> 850a</c>
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><c> gave</c><00:03:19.519><c> me</c><00:03:19.840><c> a</c><00:03:20.000><c> nice</c><00:03:20.239><c> starting</c><00:03:20.720><c> point</c><00:03:20.959><c> to</c>
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><c> the</c><00:03:21.840><c> rest</c><00:03:22.400><c> again</c><00:03:22.879><c> huge</c><00:03:23.120><c> thank</c><00:03:23.360><c> you</c>
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><c> open</c><00:03:24.000><c> source</c><00:03:24.239><c> community</c><00:03:24.879><c> jeff</c><00:03:25.120><c> gearling</c>
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><c> user</c><00:03:26.959><c> 212</c><00:03:27.680><c> 850a</c><00:03:28.480><c> so</c><00:03:28.720><c> after</c><00:03:29.040><c> poking</c><00:03:29.440><c> around</c>
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><c> a</c><00:03:30.000><c> little</c><00:03:30.159><c> bit</c><00:03:30.400><c> i</c><00:03:30.560><c> found</c><00:03:30.799><c> that</c><00:03:31.120><c> most</c><00:03:31.360><c> of</c><00:03:31.519><c> it</c>
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><c> working</c><00:03:32.400><c> but</c><00:03:32.560><c> it</c><00:03:32.720><c> did</c><00:03:32.959><c> need</c><00:03:33.200><c> some</c><00:03:33.440><c> updates</c>
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><c> some</c><00:03:34.480><c> configuration</c><00:03:35.280><c> changes</c><00:03:35.920><c> to</c><00:03:36.080><c> work</c>
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><c> the</c><00:03:36.480><c> latest</c><00:03:36.959><c> version</c><00:03:37.280><c> of</c><00:03:37.440><c> qvim</c><00:03:38.080><c> along</c>
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><c> some</c><00:03:38.720><c> other</c><00:03:38.959><c> features</c><00:03:39.360><c> i</c><00:03:39.440><c> wanted</c><00:03:39.760><c> to</c><00:03:39.840><c> add</c>
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><c> i</c><00:03:40.799><c> decided</c><00:03:41.280><c> to</c><00:03:41.920><c> roll</c><00:03:42.159><c> up</c><00:03:42.239><c> my</c><00:03:42.400><c> sleeves</c>
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><c> start</c><00:03:44.080><c> hacking</c><00:03:44.480><c> away</c><00:03:44.879><c> at</c><00:03:44.959><c> this</c><00:03:45.280><c> fork</c><00:03:45.760><c> in</c>
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><c> own</c><00:03:46.319><c> branch</c><00:03:46.879><c> and</c><00:03:47.040><c> before</c><00:03:47.440><c> making</c><00:03:47.760><c> it</c>
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><c> i</c><00:03:48.720><c> wanted</c><00:03:48.959><c> to</c><00:03:49.200><c> accomplish</c><00:03:49.920><c> a</c><00:03:50.000><c> few</c>
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><c> i</c><00:03:50.879><c> wanted</c><00:03:51.200><c> to</c><00:03:51.280><c> make</c><00:03:51.519><c> sure</c><00:03:51.760><c> that</c><00:03:52.159><c> anyone</c>
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><c> this</c><00:03:53.200><c> could</c><00:03:53.439><c> start</c><00:03:53.680><c> with</c><00:03:53.920><c> an</c><00:03:54.239><c> unlimited</c>
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><c> of</c><00:03:55.360><c> nodes</c><00:03:55.920><c> i</c><00:03:56.000><c> wanted</c><00:03:56.319><c> to</c><00:03:56.400><c> make</c><00:03:56.640><c> sure</c>
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><c> qvip</c><00:03:57.680><c> was</c><00:03:58.080><c> rock</c><00:03:58.319><c> solid</c><00:03:58.959><c> and</c><00:03:59.040><c> then</c><00:03:59.280><c> it</c>
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><c> actually</c><00:04:00.000><c> create</c><00:04:00.319><c> a</c><00:04:00.480><c> load</c><00:04:00.720><c> balancer</c>
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><c> you</c><00:04:01.760><c> could</c><00:04:02.000><c> use</c><00:04:02.480><c> to</c><00:04:02.640><c> make</c><00:04:02.879><c> k3s</c><00:04:03.680><c> fault</c>
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><c> i</c><00:04:04.640><c> also</c><00:04:04.959><c> wanted</c><00:04:05.200><c> to</c><00:04:05.360><c> automate</c><00:04:05.920><c> an</c>
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><c> load</c><00:04:06.799><c> balancer</c><00:04:07.280><c> so</c><00:04:07.439><c> that</c><00:04:07.599><c> when</c><00:04:07.840><c> you</c>
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><c> the</c><00:04:08.720><c> service</c><00:04:09.519><c> you</c><00:04:09.680><c> get</c><00:04:09.840><c> an</c><00:04:10.000><c> ip</c><00:04:10.400><c> address</c>
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><c> that</c><00:04:11.439><c> service</c><00:04:11.840><c> from</c><00:04:12.080><c> your</c><00:04:12.239><c> cluster</c><00:04:12.959><c> and</c>
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><c> anyone</c><00:04:13.920><c> can</c><00:04:14.159><c> use</c><00:04:14.319><c> that</c><00:04:14.640><c> ip</c><00:04:15.040><c> address</c><00:04:15.360><c> to</c>
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><c> services</c><00:04:16.720><c> within</c><00:04:17.199><c> k3s</c><00:04:18.160><c> so</c><00:04:18.639><c> i</c><00:04:18.799><c> had</c><00:04:19.040><c> a</c>
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><c> choices</c><00:04:19.759><c> for</c><00:04:19.840><c> this</c><00:04:20.079><c> step</c><00:04:20.720><c> and</c><00:04:20.880><c> a</c><00:04:20.959><c> quick</c>
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><c> for</c><00:04:22.320><c> these</c><00:04:22.479><c> two</c><00:04:22.720><c> load</c>
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><c> the</c><00:04:23.919><c> first</c><00:04:24.160><c> load</c><00:04:24.400><c> balancer</c><00:04:24.880><c> you</c>
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><c> need</c><00:04:25.759><c> in</c><00:04:25.919><c> k3s</c><00:04:26.639><c> is</c><00:04:26.800><c> a</c><00:04:27.040><c> load</c><00:04:27.360><c> balancer</c>
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><c> your</c><00:04:28.639><c> kubernetes</c><00:04:29.440><c> api</c><00:04:30.160><c> this</c><00:04:30.320><c> is</c><00:04:30.400><c> the</c><00:04:30.560><c> load</c>
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><c> for</c><00:04:31.600><c> control</c><00:04:32.000><c> plane</c><00:04:32.320><c> and</c><00:04:32.479><c> this</c>
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><c> be</c><00:04:32.960><c> fault</c><00:04:33.199><c> tolerance</c><00:04:33.600><c> so</c><00:04:33.759><c> that</c><00:04:34.080><c> if</c><00:04:34.160><c> you</c>
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><c> k3s</c><00:04:35.520><c> commands</c><00:04:36.000><c> you</c><00:04:36.160><c> can</c><00:04:36.400><c> still</c><00:04:36.720><c> get</c><00:04:36.880><c> a</c>
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><c> back</c><00:04:37.840><c> and</c><00:04:38.000><c> the</c><00:04:38.160><c> other</c><00:04:38.320><c> load</c>
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><c> is</c><00:04:39.360><c> a</c><00:04:39.600><c> service</c><00:04:40.000><c> load</c><00:04:40.240><c> balancer</c><00:04:41.040><c> or</c>
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><c> for</c><00:04:42.160><c> you</c><00:04:42.320><c> to</c><00:04:42.479><c> expose</c><00:04:43.199><c> services</c><00:04:43.759><c> on</c>
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><c> most</c><00:04:44.400><c> cloud</c><00:04:44.720><c> environments</c><00:04:45.440><c> they</c><00:04:45.680><c> supply</c><00:04:46.240><c> a</c>
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><c> load</c><00:04:47.280><c> balancer</c><00:04:47.759><c> for</c><00:04:47.919><c> you</c><00:04:48.080><c> to</c><00:04:48.320><c> expose</c>
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><c> on</c><00:04:49.600><c> and</c><00:04:49.759><c> this</c><00:04:50.000><c> service</c><00:04:50.400><c> load</c>
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><c> that</c><00:04:51.199><c> i'm</c><00:04:51.360><c> talking</c><00:04:51.680><c> about</c><00:04:52.080><c> is</c><00:04:52.320><c> for</c>
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><c> environments</c><00:04:54.479><c> in</c><00:04:54.639><c> self-hosted</c>
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><c> and</c><00:04:56.400><c> since</c><00:04:56.639><c> we</c><00:04:56.800><c> don't</c><00:04:56.960><c> have</c><00:04:57.199><c> a</c>
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><c> load</c><00:04:58.240><c> balancer</c><00:04:58.880><c> to</c><00:04:59.040><c> give</c><00:04:59.280><c> us</c><00:04:59.520><c> ips</c><00:05:00.160><c> to</c>
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><c> our</c><00:05:01.280><c> services</c><00:05:01.919><c> outside</c><00:05:02.560><c> we</c><00:05:02.720><c> need</c><00:05:02.880><c> to</c>
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><c> something</c><00:05:03.600><c> that</c><00:05:03.759><c> can</c><00:05:04.080><c> emulate</c><00:05:04.639><c> a</c><00:05:04.880><c> cloud</c>
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><c> balancer</c><00:05:06.320><c> that</c><00:05:06.560><c> kubernetes</c><00:05:07.199><c> can</c><00:05:07.440><c> ask</c>
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><c> an</c><00:05:08.000><c> ip</c><00:05:08.320><c> address</c><00:05:08.639><c> from</c><00:05:09.199><c> so</c><00:05:09.520><c> our</c><00:05:09.680><c> services</c>
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><c> be</c><00:05:10.639><c> exposed</c><00:05:11.360><c> so</c><00:05:11.520><c> i</c><00:05:11.680><c> had</c><00:05:11.840><c> choices</c><00:05:12.240><c> to</c><00:05:12.400><c> make</c>
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><c> load</c><00:05:13.039><c> balancers</c><00:05:13.840><c> qvip</c><00:05:14.400><c> can</c><00:05:14.639><c> actually</c><00:05:15.039><c> do</c>
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><c> it</c><00:05:15.919><c> can</c><00:05:16.080><c> be</c><00:05:16.160><c> a</c><00:05:16.320><c> service</c><00:05:16.639><c> load</c><00:05:16.880><c> balancer</c>
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><c> a</c><00:05:17.919><c> load</c><00:05:18.160><c> balancer</c><00:05:18.800><c> for</c><00:05:19.039><c> your</c><00:05:19.199><c> control</c>
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><c> for</c><00:05:20.080><c> your</c><00:05:20.240><c> kubernetes</c><00:05:20.960><c> lcd</c><00:05:21.440><c> nodes</c><00:05:22.000><c> this</c>
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><c> like</c><00:05:22.720><c> a</c><00:05:22.800><c> great</c><00:05:23.039><c> solution</c><00:05:23.440><c> because</c>
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><c> i</c><00:05:24.160><c> didn't</c><00:05:24.400><c> have</c><00:05:24.560><c> to</c><00:05:24.639><c> use</c><00:05:24.800><c> metal</c><00:05:25.199><c> lb</c>
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><c> i</c><00:05:26.639><c> love</c><00:05:26.880><c> metal</c><00:05:27.199><c> lv</c><00:05:27.600><c> but</c><00:05:27.759><c> taking</c><00:05:28.080><c> on</c><00:05:28.400><c> one</c>
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><c> dependency</c><00:05:29.600><c> sounded</c><00:05:30.000><c> like</c><00:05:30.320><c> a</c><00:05:30.400><c> good</c><00:05:30.639><c> idea</c>
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><c> when</c><00:05:31.919><c> it</c><00:05:32.000><c> comes</c><00:05:32.240><c> to</c><00:05:32.560><c> breaking</c>
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><c> it's</c><00:05:33.680><c> just</c><00:05:34.000><c> less</c><00:05:34.240><c> to</c><00:05:34.400><c> manage</c><00:05:34.960><c> so</c><00:05:35.120><c> then</c>
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><c> course</c><00:05:36.000><c> the</c><00:05:36.240><c> other</c><00:05:36.479><c> option</c><00:05:36.800><c> for</c><00:05:36.960><c> exposing</c>
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><c> services</c><00:05:38.160><c> was</c><00:05:38.400><c> just</c><00:05:38.639><c> to</c><00:05:38.720><c> use</c><00:05:39.039><c> metal</c><00:05:39.440><c> albeit</c>
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><c> after</c><00:05:42.080><c> hours</c><00:05:42.479><c> and</c><00:05:42.639><c> hours</c><00:05:43.039><c> of</c><00:05:43.199><c> trying</c>
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><c> get</c><00:05:43.919><c> qvic</c><00:05:44.560><c> service</c><00:05:44.960><c> load</c><00:05:45.199><c> balancer</c><00:05:45.840><c> to</c><00:05:45.919><c> be</c>
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><c> to</c><00:05:46.320><c> work</c><00:05:46.560><c> with</c><00:05:46.720><c> my</c><00:05:46.880><c> services</c><00:05:47.759><c> i</c><00:05:47.919><c> decided</c>
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><c> fall</c><00:05:48.720><c> back</c><00:05:48.960><c> on</c><00:05:49.199><c> good</c><00:05:49.440><c> old</c><00:05:49.680><c> trusty</c><00:05:50.320><c> metal</c><00:05:50.639><c> lb</c>
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><c> metal</c><00:05:51.680><c> lb</c><00:05:52.240><c> just</c><00:05:52.479><c> works</c><00:05:52.960><c> and</c><00:05:53.280><c> i</c><00:05:53.360><c> could</c><00:05:53.600><c> use</c>
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><c> existing</c><00:05:54.320><c> configuration</c><00:05:55.039><c> for</c><00:05:55.280><c> it</c><00:05:55.440><c> so</c><00:05:55.840><c> it</c>
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><c> wasn't</c><00:05:57.199><c> a</c><00:05:57.360><c> loss</c><00:05:57.680><c> at</c><00:05:57.840><c> all</c><00:05:58.240><c> so</c><00:05:58.400><c> at</c><00:05:58.479><c> this</c>
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><c> i</c><00:05:59.120><c> had</c><00:05:59.280><c> my</c><00:05:59.520><c> architecture</c><00:06:00.479><c> pretty</c><00:06:00.639><c> much</c>
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><c> qubit</c><00:06:01.919><c> for</c><00:06:02.080><c> my</c><00:06:02.240><c> kubernetes</c><00:06:02.880><c> control</c>
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><c> and</c><00:06:03.759><c> metal</c><00:06:04.160><c> llb</c><00:06:04.479><c> for</c><00:06:04.639><c> my</c><00:06:04.800><c> service</c><00:06:05.120><c> load</c>
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><c> and</c><00:06:06.080><c> once</c><00:06:06.319><c> i</c><00:06:06.479><c> solved</c><00:06:06.800><c> creating</c>
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><c> server</c><00:06:08.000><c> nodes</c><00:06:08.560><c> configuring</c><00:06:09.199><c> cube</c>
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><c> and</c><00:06:10.080><c> configuring</c><00:06:10.639><c> middle</c><00:06:11.039><c> of</c><00:06:11.120><c> b</c>
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><c> was</c><00:06:12.080><c> time</c><00:06:12.319><c> to</c><00:06:12.400><c> do</c><00:06:12.560><c> some</c><00:06:12.800><c> testing</c><00:06:13.520><c> for</c><00:06:13.759><c> my</c>
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><c> i</c><00:06:14.400><c> created</c><00:06:14.960><c> five</c><00:06:15.280><c> nodes</c><00:06:15.680><c> and</c><00:06:15.919><c> these</c><00:06:16.160><c> are</c>
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><c> ubuntu</c><00:06:17.440><c> cloud</c><00:06:17.759><c> image</c><00:06:18.080><c> notes</c><00:06:18.639><c> and</c><00:06:18.800><c> i</c>
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><c> recently</c><00:06:19.520><c> created</c><00:06:19.840><c> a</c><00:06:19.919><c> video</c><00:06:20.240><c> on</c>
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><c> new</c><00:06:21.199><c> ubuntu</c><00:06:21.680><c> machines</c><00:06:22.080><c> using</c>
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><c> image</c><00:06:23.280><c> and</c><00:06:23.360><c> cloud</c><00:06:23.680><c> init</c><00:06:24.000><c> they're</c><00:06:24.240><c> the</c>
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><c> ubuntu</c><00:06:25.520><c> minimal</c><00:06:26.000><c> server</c><00:06:26.240><c> for</c><00:06:26.479><c> k3s</c>
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><c> really</c><00:06:27.840><c> check</c><00:06:28.080><c> it</c><00:06:28.240><c> out</c><00:06:28.479><c> so</c><00:06:28.639><c> once</c><00:06:28.960><c> i</c><00:06:29.039><c> had</c>
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><c> five</c><00:06:29.840><c> servers</c><00:06:30.479><c> up</c><00:06:30.639><c> and</c><00:06:30.720><c> running</c><00:06:31.120><c> and</c>
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><c> note</c><00:06:31.919><c> of</c><00:06:32.000><c> their</c><00:06:32.240><c> ip</c><00:06:32.560><c> addresses</c>
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><c> was</c><00:06:33.919><c> time</c><00:06:34.080><c> to</c><00:06:34.240><c> configure</c><00:06:34.639><c> myansible</c>
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><c> so</c><00:06:36.000><c> here</c><00:06:36.240><c> in</c><00:06:36.400><c> the</c><00:06:36.479><c> groupbars</c><00:06:37.120><c> file</c>
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><c> where</c><00:06:37.919><c> all</c><00:06:38.160><c> of</c><00:06:38.240><c> my</c><00:06:38.479><c> variables</c><00:06:39.120><c> are</c><00:06:39.360><c> set</c><00:06:39.600><c> for</c>
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><c> first</c><00:06:40.560><c> you</c><00:06:40.639><c> can</c><00:06:40.800><c> specify</c><00:06:41.440><c> the</c><00:06:41.520><c> k3s</c>
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><c> and</c><00:06:43.120><c> then</c><00:06:43.360><c> you</c><00:06:43.440><c> could</c><00:06:43.680><c> specify</c><00:06:44.240><c> an</c>
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><c> user</c><00:06:45.440><c> and</c><00:06:45.520><c> this</c><00:06:45.759><c> is</c><00:06:45.840><c> the</c><00:06:46.000><c> user</c><00:06:46.319><c> that</c>
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><c> will</c><00:06:47.120><c> run</c><00:06:47.360><c> as</c><00:06:47.759><c> and</c><00:06:47.919><c> another</c><00:06:48.240><c> quick</c>
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><c> if</c><00:06:49.280><c> you</c><00:06:49.360><c> need</c><00:06:49.520><c> to</c><00:06:49.599><c> set</c><00:06:49.759><c> up</c><00:06:49.919><c> ansible</c><00:06:50.400><c> i</c><00:06:50.479><c> got</c>
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><c> really</c><00:06:51.280><c> quick</c><00:06:51.520><c> video</c><00:06:52.080><c> on</c><00:06:52.240><c> the</c><00:06:52.400><c> bare</c><00:06:52.720><c> minimum</c>
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><c> you</c><00:06:53.680><c> need</c><00:06:53.840><c> to</c><00:06:53.919><c> do</c><00:06:54.160><c> in</c><00:06:54.240><c> order</c><00:06:54.560><c> to</c><00:06:54.720><c> set</c><00:06:54.880><c> up</c>
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><c> it's</c><00:06:55.680><c> a</c><00:06:55.840><c> great</c><00:06:56.160><c> primer</c><00:06:56.560><c> for</c><00:06:56.720><c> this</c><00:06:56.960><c> too</c>
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><c> is</c><00:06:57.680><c> setting</c><00:06:58.080><c> a</c><00:06:58.160><c> system</c><00:06:58.560><c> directory</c><00:06:59.199><c> and</c>
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><c> won't</c><00:06:59.759><c> really</c><00:07:00.000><c> need</c><00:07:00.160><c> to</c><00:07:00.240><c> touch</c><00:07:00.560><c> this</c><00:07:01.039><c> next</c>
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><c> setting</c><00:07:01.759><c> a</c><00:07:01.840><c> flannel</c><00:07:02.400><c> interface</c><00:07:02.880><c> of</c><00:07:03.039><c> eth0</c>
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><c> flannel's</c><00:07:04.560><c> responsible</c><00:07:05.199><c> for</c><00:07:05.440><c> networking</c>
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><c> k3s</c><00:07:07.039><c> and</c><00:07:07.199><c> it's</c><00:07:07.599><c> pretty</c><00:07:08.000><c> dense</c><00:07:08.560><c> but</c><00:07:08.720><c> if</c><00:07:08.800><c> you</c>
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><c> to</c><00:07:09.199><c> know</c><00:07:09.440><c> more</c><00:07:09.599><c> about</c><00:07:09.840><c> it</c><00:07:10.000><c> you</c><00:07:10.080><c> should</c>
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><c> check</c><00:07:10.880><c> out</c><00:07:10.960><c> their</c><00:07:11.120><c> github</c><00:07:11.599><c> repo</c><00:07:12.000><c> but</c>
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><c> i</c><00:07:12.560><c> understand</c><00:07:13.039><c> it</c><00:07:13.199><c> it's</c><00:07:13.440><c> responsible</c><00:07:14.160><c> for</c>
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><c> 3</c><00:07:15.039><c> communication</c><00:07:16.080><c> between</c><00:07:16.479><c> nodes</c><00:07:16.800><c> in</c><00:07:16.880><c> a</c>
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><c> and</c><00:07:17.759><c> so</c><00:07:18.000><c> here</c><00:07:18.240><c> i</c><00:07:18.479><c> set</c><00:07:18.720><c> at</c><00:07:19.039><c> 0</c><00:07:19.599><c> because</c>
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><c> the</c><00:07:20.400><c> ethernet</c><00:07:20.960><c> interface</c><00:07:21.599><c> on</c><00:07:21.759><c> these</c>
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><c> machines</c><00:07:23.120><c> next</c><00:07:23.360><c> i'm</c><00:07:23.520><c> setting</c><00:07:23.840><c> a</c>
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><c> endpoint</c><00:07:25.120><c> and</c><00:07:25.199><c> this</c><00:07:25.360><c> is</c><00:07:25.520><c> the</c><00:07:25.680><c> ip</c>
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><c> of</c><00:07:26.560><c> the</c><00:07:26.800><c> vip</c><00:07:27.039><c> that</c><00:07:27.199><c> will</c><00:07:27.360><c> get</c><00:07:27.599><c> created</c>
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><c> kubernetes</c><00:07:29.120><c> control</c><00:07:29.520><c> plane</c><00:07:29.840><c> and</c><00:07:29.919><c> so</c><00:07:30.160><c> this</c>
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><c> gets</c><00:07:30.960><c> created</c><00:07:31.520><c> instead</c><00:07:31.840><c> of</c><00:07:32.160><c> you</c><00:07:32.400><c> having</c>
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><c> create</c><00:07:33.199><c> external</c><00:07:33.759><c> load</c><00:07:34.000><c> balancers</c><00:07:34.960><c> along</c>
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><c> keepa</c><00:07:35.919><c> live</c><00:07:36.160><c> d</c><00:07:36.479><c> this</c><00:07:36.720><c> creates</c><00:07:37.199><c> a</c><00:07:37.440><c> vip</c>
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><c> is</c><00:07:38.319><c> highly</c><00:07:38.720><c> available</c><00:07:39.360><c> that's</c><00:07:39.680><c> exposed</c>
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><c> the</c><00:07:40.319><c> kubernetes</c><00:07:41.039><c> cluster</c><00:07:41.520><c> that</c><00:07:41.759><c> we</c>
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><c> communicate</c><00:07:42.880><c> with</c><00:07:43.280><c> and</c><00:07:43.440><c> kubernetes</c><00:07:44.080><c> can</c>
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><c> so</c><00:07:45.120><c> it's</c><00:07:45.440><c> pretty</c><00:07:45.759><c> awesome</c><00:07:46.080><c> that</c><00:07:46.319><c> takes</c>
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><c> of</c><00:07:46.960><c> two</c><00:07:47.120><c> to</c><00:07:47.280><c> three</c><00:07:47.520><c> additional</c><00:07:47.919><c> virtual</c>
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><c> that</c><00:07:48.720><c> you</c><00:07:49.039><c> don't</c><00:07:49.199><c> have</c><00:07:49.360><c> to</c><00:07:49.440><c> maintain</c>
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><c> next</c><00:07:51.039><c> i</c><00:07:51.120><c> set</c><00:07:51.360><c> my</c><00:07:51.520><c> k3s</c><00:07:52.160><c> token</c><00:07:52.560><c> and</c><00:07:52.800><c> this</c>
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><c> be</c><00:07:53.520><c> a</c><00:07:53.680><c> secret</c><00:07:54.160><c> that</c><00:07:54.319><c> you</c><00:07:54.479><c> should</c>
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><c> keep</c><00:07:55.680><c> secret</c><00:07:56.160><c> but</c><00:07:56.319><c> it's</c><00:07:56.560><c> your</c>
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><c> or</c><00:07:57.280><c> your</c><00:07:57.440><c> token</c><00:07:57.840><c> for</c><00:07:58.000><c> k3s</c>
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><c> you'll</c><00:07:59.599><c> only</c><00:07:59.759><c> need</c><00:08:00.000><c> this</c><00:08:00.240><c> in</c><00:08:00.319><c> the</c>
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><c> or</c><00:08:01.039><c> if</c><00:08:01.120><c> you</c><00:08:01.280><c> join</c><00:08:01.599><c> additional</c>
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><c> later</c><00:08:02.800><c> i</c><00:08:02.960><c> then</c><00:08:03.199><c> added</c><00:08:03.599><c> some</c><00:08:03.840><c> additional</c>
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><c> to</c><00:08:04.960><c> my</c><00:08:05.199><c> server</c><00:08:05.840><c> and</c><00:08:06.000><c> to</c><00:08:06.160><c> my</c><00:08:06.319><c> agents</c>
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><c> as</c><00:08:07.199><c> far</c><00:08:07.440><c> as</c><00:08:07.599><c> the</c><00:08:07.680><c> server</c><00:08:08.080><c> goes</c><00:08:08.400><c> i</c><00:08:08.639><c> disabled</c>
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><c> service</c><00:08:09.759><c> load</c><00:08:10.000><c> balancer</c><00:08:10.800><c> we'll</c><00:08:11.039><c> want</c><00:08:11.199><c> to</c>
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><c> that</c><00:08:11.680><c> if</c><00:08:11.759><c> we're</c><00:08:11.919><c> running</c><00:08:12.240><c> metal</c><00:08:12.639><c> of</c><00:08:12.720><c> b</c><00:08:13.039><c> or</c><00:08:13.199><c> a</c>
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><c> load</c><00:08:13.919><c> balancer</c><00:08:14.479><c> which</c><00:08:14.720><c> we</c><00:08:14.879><c> are</c><00:08:15.199><c> i'm</c>
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><c> it</c><00:08:16.000><c> not</c><00:08:16.240><c> to</c><00:08:16.479><c> deploy</c><00:08:16.960><c> traffic</c><00:08:17.680><c> this</c><00:08:17.919><c> is</c>
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><c> to</c><00:08:18.319><c> you</c><00:08:18.560><c> if</c><00:08:18.639><c> you</c><00:08:18.800><c> want</c><00:08:18.960><c> to</c><00:08:19.039><c> deploy</c><00:08:19.520><c> traffic</c>
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><c> can</c><00:08:20.319><c> just</c><00:08:20.479><c> delete</c><00:08:20.800><c> that</c><00:08:20.960><c> arg</c><00:08:21.440><c> but</c><00:08:21.680><c> i'm</c>
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><c> to</c><00:08:22.080><c> delete</c><00:08:22.400><c> it</c><00:08:22.479><c> so</c><00:08:22.639><c> i</c><00:08:22.720><c> can</c><00:08:22.960><c> install</c><00:08:23.280><c> it</c>
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><c> helm</c><00:08:23.759><c> later</c><00:08:24.240><c> because</c><00:08:24.639><c> i</c><00:08:24.800><c> like</c><00:08:24.960><c> to</c>
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><c> traffic</c><00:08:26.080><c> on</c><00:08:26.240><c> my</c><00:08:26.479><c> own</c><00:08:26.960><c> later</c><00:08:27.199><c> with</c>
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><c> but</c><00:08:28.000><c> if</c><00:08:28.080><c> you</c><00:08:28.240><c> wanted</c><00:08:28.479><c> to</c><00:08:28.720><c> install</c><00:08:29.039><c> it</c><00:08:29.199><c> you</c>
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><c> just</c><00:08:29.680><c> delete</c><00:08:30.000><c> this</c><00:08:30.160><c> argument</c><00:08:30.639><c> this</c>
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><c> argument</c><00:08:31.680><c> is</c><00:08:31.840><c> just</c><00:08:32.080><c> setting</c>
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><c> on</c><00:08:33.200><c> coop</c><00:08:33.440><c> config</c><00:08:33.919><c> and</c><00:08:34.000><c> this</c><00:08:34.240><c> is</c>
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><c> just</c><00:08:34.880><c> for</c><00:08:35.200><c> convenience</c><00:08:35.680><c> so</c><00:08:35.839><c> i</c><00:08:35.919><c> don't</c>
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><c> to</c><00:08:36.320><c> run</c><00:08:36.640><c> sudo</c><00:08:37.120><c> when</c><00:08:37.279><c> i'm</c><00:08:37.360><c> remoted</c><00:08:37.919><c> into</c><00:08:38.159><c> a</c>
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><c> to</c><00:08:38.640><c> run</c><00:08:38.880><c> coupe</c><00:08:39.120><c> control</c><00:08:39.599><c> it's</c><00:08:39.839><c> probably</c>
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><c> good</c><00:08:40.479><c> idea</c><00:08:41.120><c> not</c><00:08:41.360><c> to</c><00:08:41.519><c> this</c><00:08:41.760><c> but</c><00:08:41.919><c> i</c><00:08:42.080><c> got</c><00:08:42.320><c> so</c>
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><c> of</c><00:08:43.200><c> typing</c><00:08:43.599><c> in</c><00:08:43.760><c> sudo</c><00:08:44.240><c> every</c><00:08:44.399><c> time</c><00:08:44.640><c> i</c><00:08:44.720><c> was</c>
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><c> this</c><00:08:45.600><c> the</c><00:08:45.839><c> thousand</c><00:08:46.320><c> times</c><00:08:46.640><c> i</c><00:08:46.800><c> spun</c>
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><c> up</c>
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><c> i</c><00:08:48.720><c> just</c><00:08:48.959><c> changed</c><00:08:49.279><c> the</c><00:08:49.600><c> permissions</c><00:08:50.160><c> of</c>
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><c> file</c><00:08:51.120><c> but</c><00:08:51.279><c> feel</c><00:08:51.519><c> free</c><00:08:51.760><c> to</c><00:08:52.000><c> remove</c><00:08:52.320><c> that</c>
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><c> if</c><00:08:53.040><c> you</c><00:08:53.120><c> want</c><00:08:53.519><c> and</c><00:08:53.680><c> the</c><00:08:53.839><c> next</c><00:08:54.080><c> string</c>
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><c> arguments</c><00:08:55.200><c> are</c><00:08:55.680><c> quite</c><00:08:56.000><c> a</c><00:08:56.080><c> few</c>
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><c> i'll</c><00:08:57.440><c> leave</c><00:08:57.680><c> these</c><00:08:57.920><c> in</c><00:08:58.000><c> the</c>
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><c> but</c><00:08:59.360><c> to</c><00:08:59.600><c> summarize</c>
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><c> rest</c><00:09:01.200><c> of</c><00:09:01.279><c> these</c><00:09:01.519><c> args</c><00:09:02.000><c> as</c><00:09:02.399><c> well</c><00:09:02.720><c> as</c><00:09:02.880><c> the</c>
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><c> args</c><00:09:03.839><c> you</c><00:09:03.920><c> see</c><00:09:04.160><c> here</c><00:09:04.560><c> is</c><00:09:04.720><c> that</c><00:09:04.880><c> i</c><00:09:04.959><c> found</c>
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><c> i</c><00:09:05.519><c> needed</c><00:09:06.000><c> most</c><00:09:06.240><c> of</c><00:09:06.399><c> these</c><00:09:06.560><c> args</c><00:09:06.959><c> to</c><00:09:07.040><c> make</c>
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><c> a</c><00:09:08.080><c> little</c><00:09:08.240><c> more</c><00:09:08.480><c> responsive</c><00:09:09.120><c> what</c><00:09:09.279><c> do</c><00:09:09.440><c> i</c>
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><c> by</c><00:09:09.920><c> that</c><00:09:10.240><c> one</c><00:09:10.399><c> of</c><00:09:10.480><c> the</c><00:09:10.640><c> defaults</c><00:09:11.040><c> for</c><00:09:11.200><c> k3s</c>
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><c> that</c><00:09:12.240><c> if</c><00:09:12.399><c> the</c><00:09:12.480><c> node's</c><00:09:12.880><c> not</c><00:09:13.120><c> ready</c><00:09:13.680><c> it</c><00:09:13.920><c> won't</c>
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><c> additional</c><00:09:15.200><c> pods</c><00:09:15.600><c> on</c><00:09:15.760><c> it</c><00:09:16.320><c> until</c>
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><c> node</c><00:09:17.279><c> becomes</c><00:09:17.680><c> ready</c><00:09:18.480><c> but</c><00:09:18.640><c> the</c><00:09:18.800><c> timeout</c>
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><c> like</c><00:09:19.760><c> five</c><00:09:20.000><c> minutes</c><00:09:20.320><c> long</c><00:09:20.720><c> which</c><00:09:20.959><c> is</c><00:09:21.120><c> a</c>
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><c> time</c><00:09:21.920><c> i</c><00:09:22.080><c> mean</c><00:09:22.480><c> it's</c><00:09:22.720><c> not</c><00:09:22.959><c> a</c><00:09:23.040><c> long</c><00:09:23.279><c> time</c><00:09:23.680><c> if</c>
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><c> running</c><00:09:24.399><c> multiple</c><00:09:24.800><c> replicas</c><00:09:25.360><c> of</c><00:09:25.519><c> a</c>
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><c> and</c><00:09:26.080><c> you're</c><00:09:26.240><c> running</c><00:09:26.480><c> pods</c><00:09:26.800><c> in</c><00:09:26.959><c> aj</c><00:09:27.680><c> you</c>
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><c> almost</c><00:09:28.480><c> not</c><00:09:28.640><c> notice</c><00:09:29.040><c> at</c><00:09:29.200><c> all</c>
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><c> in</c><00:09:30.399><c> larger</c><00:09:30.800><c> installations</c><00:09:31.680><c> but</c>
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><c> smaller</c><00:09:32.399><c> installations</c><00:09:33.200><c> like</c><00:09:33.440><c> home</c><00:09:33.760><c> labs</c>
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><c> found</c><00:09:34.640><c> that</c><00:09:34.800><c> five</c><00:09:35.120><c> minutes</c><00:09:35.600><c> is</c><00:09:35.760><c> a</c><00:09:36.080><c> really</c>
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><c> time</c><00:09:37.120><c> especially</c><00:09:37.600><c> if</c><00:09:37.680><c> you're</c><00:09:37.839><c> running</c><00:09:38.160><c> a</c>
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><c> of</c><00:09:39.200><c> one</c><00:09:39.680><c> that</c><00:09:39.839><c> means</c><00:09:40.080><c> your</c><00:09:40.240><c> service</c>
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><c> down</c><00:09:41.040><c> for</c><00:09:41.360><c> at</c><00:09:41.440><c> least</c><00:09:41.680><c> five</c><00:09:41.920><c> minutes</c><00:09:42.480><c> so</c>
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><c> scraped</c><00:09:43.200><c> the</c><00:09:43.360><c> internet</c><00:09:43.920><c> found</c><00:09:44.160><c> a</c><00:09:44.240><c> lot</c><00:09:44.399><c> of</c>
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><c> arguments</c><00:09:45.200><c> and</c><00:09:45.440><c> i've</c><00:09:45.680><c> been</c><00:09:45.839><c> using</c>
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><c> in</c><00:09:46.560><c> my</c><00:09:46.880><c> home</c><00:09:47.279><c> production</c>
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><c> lab</c>
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><c> about</c><00:09:50.240><c> a</c><00:09:50.320><c> year</c><00:09:50.480><c> now</c><00:09:50.880><c> and</c><00:09:50.959><c> they</c><00:09:51.120><c> seem</c><00:09:51.360><c> to</c>
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><c> pretty</c><00:09:51.839><c> well</c><00:09:52.080><c> but</c><00:09:52.320><c> you</c><00:09:52.480><c> might</c><00:09:52.640><c> need</c><00:09:52.800><c> to</c>
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><c> some</c><00:09:53.279><c> tweaking</c><00:09:53.680><c> depending</c><00:09:54.160><c> on</c><00:09:54.399><c> your</c>
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><c> your</c><00:09:55.680><c> hardware</c><00:09:56.640><c> and</c><00:09:56.800><c> what</c><00:09:57.040><c> works</c>
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><c> for</c><00:09:57.680><c> you</c><00:09:58.000><c> and</c><00:09:58.080><c> again</c><00:09:58.399><c> k3s</c><00:09:59.040><c> will</c><00:09:59.200><c> work</c>
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><c> any</c><00:10:00.080><c> of</c><00:10:00.160><c> those</c><00:10:00.320><c> arguments</c><00:10:00.800><c> i</c><00:10:00.880><c> just</c>
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><c> and</c><00:10:02.160><c> maybe</c><00:10:02.480><c> you</c><00:10:02.560><c> should</c><00:10:02.720><c> try</c><00:10:02.880><c> it</c>
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><c> way</c><00:10:03.360><c> first</c><00:10:03.839><c> next</c><00:10:04.079><c> i</c><00:10:04.240><c> set</c><00:10:04.399><c> the</c><00:10:04.640><c> tag</c>
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><c> for</c><00:10:05.600><c> cube</c><00:10:05.920><c> vib</c><00:10:06.399><c> and</c><00:10:06.560><c> this</c><00:10:06.720><c> is</c><00:10:06.800><c> just</c>
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><c> container</c><00:10:07.680><c> image</c><00:10:07.920><c> tag</c><00:10:08.320><c> the</c><00:10:08.399><c> current</c>
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><c> is</c>
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><c> and</c><00:10:11.360><c> so</c><00:10:11.760><c> that's</c><00:10:12.000><c> what</c><00:10:12.240><c> i'm</c><00:10:12.399><c> specifying</c>
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><c> and</c><00:10:13.600><c> i</c><00:10:13.760><c> did</c><00:10:14.240><c> similar</c><00:10:14.720><c> things</c><00:10:14.959><c> for</c><00:10:15.279><c> metal</c>
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><c> too</c><00:10:16.640><c> so</c><00:10:16.800><c> for</c><00:10:17.120><c> metal</c><00:10:17.440><c> lb</c><00:10:17.839><c> there's</c><00:10:18.079><c> a</c><00:10:18.320><c> speaker</c>
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><c> which</c><00:10:19.760><c> the</c><00:10:19.920><c> latest</c><00:10:20.240><c> version</c><00:10:20.560><c> is</c>
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><c> and</c><00:10:22.480><c> then</c><00:10:22.640><c> there's</c><00:10:22.880><c> a</c><00:10:23.200><c> controller</c><00:10:23.760><c> tag</c>
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><c> well</c><00:10:24.800><c> which</c><00:10:25.040><c> i</c><00:10:25.279><c> also</c><00:10:25.600><c> set</c><00:10:25.839><c> to</c><00:10:26.200><c> 0.12.1</c><00:10:27.279><c> now</c>
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><c> should</c><00:10:27.839><c> be</c><00:10:28.240><c> lockstep</c><00:10:28.880><c> in</c><00:10:28.959><c> the</c><00:10:29.120><c> same</c>
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><c> but</c><00:10:29.920><c> i</c><00:10:30.079><c> made</c><00:10:30.320><c> it</c><00:10:30.399><c> configurable</c><00:10:31.120><c> in</c><00:10:31.200><c> my</c>
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><c> just</c><00:10:32.399><c> in</c><00:10:32.480><c> case</c><00:10:32.720><c> they're</c><00:10:32.880><c> not</c><00:10:33.279><c> so</c>
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><c> i</c><00:10:33.920><c> didn't</c><00:10:34.079><c> have</c><00:10:34.240><c> to</c><00:10:34.320><c> figure</c><00:10:34.560><c> that</c><00:10:34.800><c> out</c><00:10:34.959><c> in</c>
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><c> future</c><00:10:35.600><c> and</c><00:10:35.760><c> next</c><00:10:36.000><c> i</c><00:10:36.160><c> chose</c><00:10:36.480><c> an</c><00:10:36.720><c> ip</c><00:10:37.120><c> range</c>
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><c> metal</c><00:10:37.920><c> lb</c><00:10:38.560><c> so</c><00:10:38.800><c> this</c><00:10:39.040><c> is</c><00:10:39.200><c> the</c><00:10:39.440><c> range</c><00:10:39.760><c> of</c><00:10:39.920><c> ips</c>
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><c> when</c><00:10:40.880><c> you</c><00:10:41.040><c> expose</c><00:10:41.519><c> services</c><00:10:42.320><c> they'll</c><00:10:42.560><c> be</c>
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><c> on</c><00:10:43.839><c> and</c><00:10:44.000><c> you</c><00:10:44.160><c> can</c><00:10:44.399><c> communicate</c><00:10:44.880><c> with</c>
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><c> i'll</c><00:10:45.600><c> show</c><00:10:45.760><c> you</c><00:10:46.000><c> some</c><00:10:46.160><c> examples</c><00:10:46.640><c> here</c><00:10:46.800><c> in</c>
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><c> little</c><00:10:47.120><c> bit</c><00:10:47.440><c> but</c><00:10:47.600><c> i</c><00:10:47.760><c> set</c><00:10:48.000><c> a</c><00:10:48.079><c> range</c><00:10:48.399><c> from</c><00:10:48.800><c> 192</c>
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><c> 30.80</c><00:10:51.760><c> all</c><00:10:51.920><c> the</c><00:10:52.000><c> way</c><00:10:52.160><c> up</c><00:10:52.399><c> to</c><00:10:52.560><c> 90.</c><00:10:53.279><c> so</c><00:10:53.440><c> i</c><00:10:53.519><c> get</c>
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><c> i</c><00:10:57.120><c> get</c><00:10:57.360><c> 11</c><00:10:57.839><c> ips</c><00:10:58.320><c> here</c><00:10:58.720><c> typically</c><00:10:59.279><c> i</c><00:10:59.519><c> only</c>
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><c> one</c><00:11:00.160><c> or</c><00:11:00.320><c> two</c><00:11:00.880><c> but</c><00:11:01.120><c> i</c><00:11:01.200><c> set</c><00:11:01.360><c> the</c><00:11:01.519><c> range</c><00:11:01.760><c> from</c>
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><c> to</c><00:11:02.399><c> 90</c><00:11:02.880><c> just</c><00:11:03.200><c> in</c><00:11:03.360><c> case</c><00:11:03.920><c> after</c><00:11:04.240><c> that</c><00:11:04.560><c> i</c>
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><c> my</c><00:11:05.200><c> host.ini</c><00:11:06.160><c> to</c><00:11:06.240><c> make</c><00:11:06.399><c> sure</c><00:11:06.640><c> i</c><00:11:06.720><c> had</c>
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><c> of</c><00:11:07.279><c> the</c><00:11:07.440><c> ip</c><00:11:07.839><c> addresses</c><00:11:08.320><c> in</c><00:11:08.480><c> here</c><00:11:09.040><c> and</c><00:11:09.200><c> the</c>
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><c> virtual</c><00:11:10.000><c> machines</c><00:11:10.480><c> i</c><00:11:10.560><c> am</c><00:11:10.720><c> going</c><00:11:10.880><c> to</c><00:11:10.959><c> use</c>
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><c> my</c><00:11:11.519><c> masters</c><00:11:12.079><c> are</c><00:11:12.320><c> 38</c><00:11:13.040><c> 39</c><00:11:13.760><c> and</c><00:11:14.000><c> 40.</c><00:11:14.560><c> these</c>
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><c> also</c><00:11:15.360><c> referred</c><00:11:15.760><c> to</c><00:11:16.079><c> as</c><00:11:16.399><c> your</c><00:11:16.640><c> server</c>
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><c> and</c><00:11:17.519><c> then</c><00:11:17.760><c> my</c><00:11:18.079><c> worker</c><00:11:18.480><c> nodes</c><00:11:18.800><c> or</c><00:11:18.959><c> my</c>
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><c> are</c><00:11:20.000><c> going</c><00:11:20.160><c> to</c><00:11:20.240><c> be</c><00:11:20.560><c> 41</c><00:11:21.279><c> and</c><00:11:21.360><c> 42.</c><00:11:22.160><c> so</c>
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><c> means</c><00:11:22.959><c> three</c><00:11:23.200><c> servers</c><00:11:23.600><c> with</c><00:11:23.839><c> kubernetes</c>
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><c> plane</c><00:11:25.279><c> and</c><00:11:25.519><c> ncd</c><00:11:26.240><c> making</c><00:11:26.640><c> it</c><00:11:26.720><c> highly</c>
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><c> and</c><00:11:27.920><c> then</c><00:11:28.240><c> two</c><00:11:28.480><c> worker</c><00:11:28.880><c> nodes</c><00:11:29.279><c> to</c>
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><c> my</c><00:11:29.839><c> user</c><00:11:30.160><c> workloads</c><00:11:30.959><c> and</c><00:11:31.120><c> if</c><00:11:31.200><c> i</c><00:11:31.360><c> had</c><00:11:31.519><c> more</c>
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><c> machines</c><00:11:32.480><c> i</c><00:11:32.560><c> would</c><00:11:32.720><c> just</c><00:11:32.959><c> add</c><00:11:33.040><c> them</c>
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><c> so</c><00:11:33.760><c> with</c><00:11:34.000><c> all</c><00:11:34.160><c> of</c><00:11:34.240><c> this</c><00:11:34.399><c> configured</c><00:11:34.959><c> i</c>
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><c> the</c><00:11:35.680><c> site</c><00:11:36.079><c> playbook</c><00:11:36.959><c> and</c><00:11:37.279><c> pointed</c><00:11:37.680><c> it</c><00:11:37.839><c> at</c>
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><c> host.ini</c><00:11:39.279><c> but</c><00:11:39.440><c> before</c><00:11:39.839><c> i</c><00:11:39.920><c> did</c><00:11:40.160><c> that</c><00:11:40.399><c> i</c>
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><c> pinging</c><00:11:41.600><c> my</c><00:11:41.839><c> vip</c><00:11:42.480><c> obviously</c><00:11:43.040><c> it's</c>
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><c> there</c><00:11:44.000><c> as</c><00:11:44.160><c> soon</c><00:11:44.320><c> as</c><00:11:44.480><c> it</c><00:11:44.640><c> comes</c><00:11:44.959><c> up</c><00:11:45.200><c> it</c>
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><c> respond</c><00:11:46.560><c> so</c><00:11:46.800><c> i</c><00:11:46.880><c> ran</c><00:11:47.120><c> the</c><00:11:47.200><c> playbook</c>
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><c> it</c><00:11:51.360><c> installed</c><00:11:51.839><c> and</c><00:11:52.000><c> configured</c><00:11:52.639><c> k3s</c><00:11:53.440><c> on</c>
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><c> of</c><00:11:53.920><c> the</c><00:11:54.079><c> server</c><00:11:54.399><c> nodes</c>
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><c> after</c><00:11:57.760><c> that</c><00:11:58.000><c> the</c><00:11:58.240><c> vip</c><00:11:58.639><c> started</c>
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><c> so</c><00:12:00.000><c> this</c><00:12:00.240><c> means</c><00:12:00.560><c> qvip</c><00:12:01.040><c> is</c>
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><c> on</c><00:12:01.760><c> that</c><00:12:01.920><c> machine</c><00:12:02.720><c> and</c><00:12:02.880><c> the</c><00:12:03.040><c> vip</c><00:12:03.360><c> is</c>
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><c> then</c><00:12:06.800><c> it</c><00:12:06.959><c> started</c><00:12:07.279><c> joining</c><00:12:07.760><c> other</c>
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><c> to</c><00:12:08.639><c> the</c><00:12:08.720><c> cluster</c>
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><c> then</c><00:12:12.240><c> shortly</c><00:12:12.639><c> after</c><00:12:12.880><c> that</c><00:12:13.279><c> i</c><00:12:13.440><c> had</c><00:12:13.680><c> a</c><00:12:13.839><c> high</c>
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><c> kubernetes</c><00:12:15.839><c> cluster</c><00:12:16.399><c> on</c><00:12:16.560><c> k3s</c>
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><c> that's</c><00:12:17.839><c> a</c><00:12:18.000><c> ha</c><00:12:18.480><c> cluster</c><00:12:19.120><c> with</c><00:12:19.360><c> that</c><00:12:19.519><c> cd</c>
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><c> a</c><00:12:20.399><c> load</c><00:12:20.560><c> balancer</c><00:12:21.120><c> that's</c><00:12:21.600><c> also</c><00:12:22.160><c> ha</c><00:12:22.720><c> for</c>
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><c> control</c><00:12:23.440><c> plane</c><00:12:23.920><c> and</c><00:12:24.399><c> aha</c><00:12:25.040><c> load</c><00:12:25.279><c> balancers</c>
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><c> all</c><00:12:26.480><c> of</c><00:12:26.560><c> my</c><00:12:26.720><c> services</c><00:12:27.360><c> but</c><00:12:27.519><c> we</c><00:12:27.680><c> need</c><00:12:27.839><c> to</c>
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><c> hopefully</c><00:12:29.360><c> you</c><00:12:29.440><c> trust</c><00:12:29.760><c> me</c><00:12:30.160><c> but</c><00:12:30.320><c> let's</c>
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><c> verify</c><00:12:31.519><c> so</c><00:12:31.680><c> we</c><00:12:31.839><c> can</c><00:12:32.079><c> ssh</c><00:12:32.720><c> into</c><00:12:33.040><c> one</c><00:12:33.200><c> of</c>
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><c> server</c><00:12:33.839><c> nodes</c><00:12:34.320><c> once</c><00:12:34.560><c> we're</c><00:12:34.720><c> there</c><00:12:34.959><c> we</c><00:12:35.120><c> can</c>
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><c> sudo</c><00:12:35.839><c> coop</c><00:12:36.079><c> control</c><00:12:36.480><c> kit</c><00:12:36.720><c> nodes</c><00:12:37.360><c> and</c><00:12:37.440><c> we</c>
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><c> see</c><00:12:38.240><c> we</c><00:12:38.399><c> have</c><00:12:38.800><c> five</c><00:12:39.120><c> nodes</c><00:12:39.519><c> and</c><00:12:39.600><c> they're</c>
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><c> online</c><00:12:40.639><c> you</c><00:12:40.720><c> can</c><00:12:40.880><c> see</c><00:12:41.040><c> i</c><00:12:41.200><c> have</c><00:12:41.519><c> three</c>
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><c> plane</c><00:12:42.560><c> at</c><00:12:42.639><c> cd</c><00:12:43.040><c> masters</c>
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><c> two</c><00:12:45.279><c> workers</c><00:12:45.839><c> or</c><00:12:46.079><c> agents</c><00:12:46.480><c> ready</c><00:12:46.720><c> for</c>
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><c> super</c><00:12:49.360><c> awesome</c>
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><c> instead</c><00:12:51.279><c> of</c><00:12:51.680><c> ssh</c><00:12:52.399><c> into</c><00:12:52.639><c> this</c><00:12:52.800><c> server</c><00:12:53.200><c> let's</c>
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><c> copy</c><00:12:54.320><c> our</c><00:12:54.560><c> coup</c><00:12:54.800><c> config</c><00:12:55.360><c> locally</c><00:12:55.839><c> so</c>
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><c> can</c><00:12:56.320><c> run</c><00:12:56.560><c> the</c><00:12:56.720><c> rest</c><00:12:56.959><c> of</c><00:12:57.040><c> the</c><00:12:57.120><c> commands</c><00:12:57.839><c> so</c>
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><c> exit</c><00:12:58.720><c> out</c><00:12:58.880><c> of</c><00:12:58.959><c> here</c><00:12:59.440><c> you'll</c><00:12:59.680><c> want</c><00:12:59.839><c> to</c>
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><c> a</c><00:13:00.399><c> directory</c><00:13:00.959><c> for</c><00:13:01.120><c> your</c><00:13:01.360><c> coup</c><00:13:01.600><c> config</c>
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><c> if</c><00:13:02.480><c> you've</c><00:13:02.720><c> never</c><00:13:02.959><c> done</c><00:13:03.200><c> this</c><00:13:03.440><c> before</c><00:13:03.920><c> or</c>
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><c> up</c><00:13:04.639><c> your</c><00:13:04.880><c> existing</c><00:13:05.440><c> coupe</c><00:13:05.680><c> config</c><00:13:06.079><c> file</c>
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><c> it's</c><00:13:06.800><c> there</c><00:13:07.279><c> then</c><00:13:07.440><c> we'll</c><00:13:07.600><c> just</c><00:13:08.000><c> scp</c><00:13:08.639><c> or</c>
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><c> copy</c><00:13:09.839><c> that</c><00:13:10.079><c> file</c><00:13:10.399><c> from</c><00:13:10.560><c> one</c><00:13:10.720><c> of</c><00:13:10.800><c> the</c>
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><c> back</c><00:13:11.519><c> to</c><00:13:11.680><c> our</c><00:13:11.839><c> local</c><00:13:12.079><c> machine</c><00:13:12.800><c> after</c>
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><c> transfers</c><00:13:14.000><c> we</c><00:13:14.160><c> can</c><00:13:14.320><c> run</c><00:13:14.560><c> a</c><00:13:14.720><c> coupe</c><00:13:14.880><c> control</c>
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><c> nodes</c><00:13:16.079><c> and</c><00:13:16.240><c> see</c><00:13:16.399><c> the</c><00:13:16.560><c> same</c><00:13:16.800><c> thing</c><00:13:17.360><c> awesome</c>
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><c> now</c><00:13:18.079><c> we</c><00:13:18.240><c> have</c><00:13:18.320><c> cube</c><00:13:18.560><c> control</c><00:13:18.959><c> running</c><00:13:19.279><c> on</c>
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><c> machine</c><00:13:20.320><c> next</c><00:13:20.639><c> i</c><00:13:20.880><c> created</c><00:13:21.279><c> a</c><00:13:21.519><c> super</c>
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><c> nginx</c><00:13:22.880><c> deployment</c><00:13:23.440><c> for</c><00:13:23.600><c> kubernetes</c>
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><c> deploys</c><00:13:25.519><c> an</c><00:13:25.680><c> alpine</c><00:13:26.160><c> version</c><00:13:26.560><c> of</c><00:13:26.720><c> nginx</c>
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><c> sets</c><00:13:27.680><c> the</c><00:13:27.839><c> replicas</c><00:13:28.399><c> to</c><00:13:28.560><c> three</c><00:13:29.120><c> i</c><00:13:29.279><c> did</c>
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><c> by</c><00:13:29.760><c> running</c><00:13:30.079><c> coop</c><00:13:30.320><c> control</c><00:13:30.800><c> apply</c><00:13:31.200><c> dash</c>
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><c> and</c><00:13:32.079><c> then</c><00:13:32.240><c> the</c><00:13:32.399><c> path</c><00:13:32.720><c> to</c><00:13:32.880><c> the</c><00:13:33.040><c> deployment</c>
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><c> and</c><00:13:34.639><c> then</c><00:13:34.880><c> kubernetes</c><00:13:35.600><c> told</c><00:13:35.839><c> me</c>
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><c> deployment</c><00:13:36.959><c> was</c><00:13:37.200><c> created</c><00:13:37.760><c> then</c><00:13:38.000><c> i</c>
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><c> to</c><00:13:38.480><c> check</c><00:13:38.720><c> to</c><00:13:38.880><c> see</c><00:13:39.040><c> how</c><00:13:39.199><c> this</c>
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><c> was</c><00:13:40.079><c> doing</c><00:13:40.720><c> so</c><00:13:41.360><c> i</c><00:13:41.519><c> ran</c><00:13:41.760><c> coop</c>
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><c> describe</c><00:13:43.120><c> deployment</c><00:13:43.839><c> nginx</c><00:13:44.720><c> and</c>
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><c> can</c><00:13:45.199><c> see</c><00:13:45.519><c> it</c><00:13:45.760><c> is</c><00:13:45.920><c> deployed</c><00:13:46.480><c> and</c><00:13:46.639><c> the</c>
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><c> state</c><00:13:47.680><c> is</c><00:13:48.079><c> three</c><00:13:48.720><c> and</c><00:13:48.959><c> three</c><00:13:49.199><c> were</c>
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><c> three</c><00:13:50.240><c> total</c><00:13:50.720><c> three</c><00:13:51.040><c> available</c><00:13:51.600><c> and</c>
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><c> unavailable</c><00:13:53.040><c> so</c><00:13:53.279><c> all</c><00:13:53.519><c> three</c><00:13:53.760><c> of</c><00:13:53.839><c> my</c>
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><c> pods</c><00:13:54.959><c> are</c><00:13:55.120><c> up</c><00:13:55.279><c> and</c><00:13:55.360><c> running</c><00:13:55.760><c> but</c><00:13:56.000><c> this</c>
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><c> give</c><00:13:56.720><c> me</c><00:13:56.959><c> access</c><00:13:57.440><c> to</c><00:13:57.600><c> these</c><00:13:57.920><c> pods</c>
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><c> of</c><00:13:59.040><c> kubernetes</c><00:14:00.000><c> this</c><00:14:00.240><c> is</c><00:14:00.399><c> where</c><00:14:00.720><c> a</c>
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><c> and</c><00:14:01.680><c> a</c><00:14:01.760><c> load</c><00:14:02.000><c> balancer</c><00:14:02.560><c> comes</c><00:14:02.880><c> in</c><00:14:03.279><c> the</c>
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><c> reason</c><00:14:04.399><c> why</c><00:14:04.639><c> we</c><00:14:04.880><c> installed</c><00:14:05.360><c> metal</c><00:14:05.680><c> lb</c>
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><c> then</c><00:14:06.639><c> i</c><00:14:06.800><c> created</c><00:14:07.199><c> a</c><00:14:07.440><c> super</c><00:14:07.760><c> simple</c><00:14:08.320><c> service</c>
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><c> this</c><00:14:09.360><c> service</c><00:14:09.760><c> file</c><00:14:10.320><c> is</c><00:14:10.480><c> just</c><00:14:10.800><c> a</c><00:14:11.279><c> service</c>
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><c> to</c><00:14:12.959><c> the</c><00:14:13.199><c> app</c><00:14:13.519><c> of</c><00:14:13.680><c> nginx</c><00:14:14.240><c> that</c><00:14:14.399><c> we</c>
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><c> created</c><00:14:15.360><c> that</c><00:14:15.519><c> deployment</c><00:14:16.240><c> and</c><00:14:16.320><c> we</c><00:14:16.480><c> tell</c>
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><c> service</c><00:14:17.360><c> to</c><00:14:17.600><c> expose</c><00:14:18.000><c> it</c><00:14:18.240><c> on</c><00:14:18.399><c> port</c><00:14:18.720><c> 80</c><00:14:19.199><c> and</c>
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><c> the</c><00:14:19.760><c> target</c><00:14:20.240><c> port</c><00:14:20.560><c> for</c><00:14:20.800><c> that</c><00:14:21.040><c> container</c>
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><c> also</c><00:14:22.160><c> port</c><00:14:22.480><c> 80</c><00:14:22.880><c> and</c><00:14:23.040><c> here's</c><00:14:23.360><c> where</c><00:14:23.519><c> the</c>
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><c> takes</c><00:14:24.399><c> place</c><00:14:25.040><c> we</c><00:14:25.199><c> tell</c><00:14:25.440><c> it</c><00:14:25.519><c> that</c><00:14:25.680><c> the</c>
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><c> is</c><00:14:26.800><c> type</c><00:14:27.120><c> load</c><00:14:27.360><c> balancer</c><00:14:28.000><c> this</c><00:14:28.240><c> tells</c>
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><c> to</c><00:14:29.680><c> tell</c><00:14:30.079><c> our</c><00:14:30.320><c> cloud</c><00:14:30.720><c> load</c>
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><c> to</c><00:14:32.000><c> give</c><00:14:32.160><c> us</c><00:14:32.399><c> an</c><00:14:32.560><c> ip</c><00:14:33.199><c> and</c><00:14:33.519><c> our</c><00:14:33.680><c> cloud</c>
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><c> balancer</c><00:14:35.279><c> right</c><00:14:35.519><c> now</c><00:14:36.160><c> is</c><00:14:36.320><c> metal</c><00:14:36.720><c> lb</c>
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><c> metal</c><00:14:38.240><c> lb</c><00:14:38.800><c> should</c><00:14:39.040><c> hand</c><00:14:39.279><c> us</c><00:14:39.519><c> an</c><00:14:39.680><c> ip</c><00:14:40.079><c> address</c>
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><c> we</c><00:14:41.120><c> specified</c><00:14:41.839><c> in</c><00:14:41.920><c> that</c><00:14:42.160><c> range</c><00:14:42.800><c> and</c><00:14:42.880><c> if</c>
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><c> of</c><00:14:43.279><c> that</c><00:14:43.519><c> happens</c><00:14:44.079><c> we</c><00:14:44.240><c> should</c><00:14:44.399><c> be</c><00:14:44.560><c> able</c><00:14:44.720><c> to</c>
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><c> to</c><00:14:45.199><c> our</c><00:14:45.360><c> service</c><00:14:46.160><c> so</c><00:14:46.320><c> then</c><00:14:46.560><c> i</c><00:14:46.639><c> ran</c><00:14:46.959><c> coop</c>
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><c> apply</c><00:14:48.079><c> dash</c><00:14:48.480><c> f</c><00:14:48.800><c> and</c><00:14:48.880><c> then</c><00:14:49.040><c> the</c><00:14:49.199><c> path</c>
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><c> the</c><00:14:49.760><c> service</c><00:14:50.160><c> file</c><00:14:50.720><c> kubernetes</c><00:14:51.440><c> told</c><00:14:51.680><c> me</c>
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><c> created</c><00:14:52.560><c> the</c><00:14:52.720><c> service</c><00:14:53.120><c> for</c><00:14:53.279><c> me</c><00:14:53.680><c> and</c><00:14:53.839><c> then</c><00:14:54.160><c> i</c>
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><c> to</c><00:14:54.800><c> verify</c><00:14:55.360><c> that</c><00:14:55.519><c> so</c><00:14:55.680><c> i</c><00:14:55.839><c> ran</c><00:14:56.160><c> coop</c>
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><c> describe</c><00:14:57.440><c> service</c><00:14:58.000><c> nginx</c><00:14:58.959><c> and</c><00:14:59.040><c> we</c>
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><c> see</c><00:14:59.760><c> here</c><00:15:00.160><c> that</c><00:15:00.399><c> it</c><00:15:00.560><c> exposed</c><00:15:01.360><c> a</c><00:15:01.600><c> load</c>
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><c> ingress</c><00:15:03.199><c> of</c><00:15:03.680><c> one</c><00:15:03.839><c> of</c><00:15:03.920><c> the</c><00:15:04.160><c> ip</c>
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><c> that</c><00:15:05.760><c> we</c><00:15:06.000><c> specified</c><00:15:06.639><c> in</c><00:15:06.800><c> metal</c><00:15:07.120><c> lb</c>
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><c> this</c><00:15:08.079><c> means</c><00:15:08.399><c> my</c><00:15:08.800><c> nginx</c><00:15:09.440><c> deployment</c><00:15:10.000><c> of</c>
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><c> pods</c><00:15:11.440><c> is</c><00:15:11.600><c> now</c><00:15:11.920><c> exposed</c><00:15:12.480><c> on</c><00:15:12.639><c> a</c><00:15:12.720><c> load</c>
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><c> at</c><00:15:13.760><c> this</c><00:15:14.079><c> ip</c><00:15:14.800><c> 192</c><00:15:15.680><c> 168</c><00:15:16.920><c> 30.80</c><00:15:18.160><c> and</c><00:15:18.320><c> if</c>
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><c> go</c><00:15:18.880><c> to</c><00:15:19.040><c> that</c><00:15:19.279><c> ip</c><00:15:19.600><c> address</c><00:15:20.160><c> we</c><00:15:20.320><c> can</c><00:15:20.560><c> see</c><00:15:20.800><c> the</c>
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><c> world</c><00:15:21.680><c> page</c><00:15:22.000><c> from</c><00:15:22.240><c> engine</c><00:15:22.639><c> x</c><00:15:23.360><c> this</c><00:15:23.920><c> is</c>
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><c> awesome</c><00:15:25.279><c> so</c><00:15:25.440><c> this</c><00:15:25.680><c> proves</c><00:15:26.240><c> all</c><00:15:26.399><c> the</c><00:15:26.480><c> way</c>
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><c> that</c><00:15:27.199><c> middle</c><00:15:27.519><c> lb</c><00:15:28.079><c> is</c><00:15:28.240><c> working</c><00:15:28.720><c> but</c><00:15:28.880><c> we</c>
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><c> really</c><00:15:29.759><c> tested</c><00:15:30.160><c> the</c><00:15:30.560><c> ha</c><00:15:31.120><c> side</c><00:15:31.360><c> of</c><00:15:31.600><c> cubit</c>
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><c> know</c><00:15:32.560><c> that</c><00:15:32.720><c> we</c><00:15:32.880><c> can</c><00:15:33.120><c> issue</c><00:15:33.519><c> kubernetes</c>
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><c> right</c><00:15:34.959><c> now</c><00:15:35.199><c> with</c><00:15:35.360><c> goog</c><00:15:35.680><c> control</c><00:15:36.320><c> but</c>
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><c> didn't</c><00:15:37.040><c> take</c><00:15:37.360><c> any</c><00:15:37.600><c> of</c><00:15:37.680><c> those</c><00:15:37.920><c> notes</c><00:15:38.240><c> down</c>
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><c> let's</c><00:15:39.519><c> do</c><00:15:39.680><c> that</c><00:15:40.000><c> too</c><00:15:40.399><c> so</c><00:15:40.560><c> i</c><00:15:40.639><c> started</c>
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><c> that</c><00:15:41.680><c> vip</c><00:15:42.079><c> and</c><00:15:42.240><c> while</c><00:15:42.480><c> doing</c><00:15:42.800><c> it</c><00:15:43.040><c> i</c>
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><c> it</c><00:15:43.759><c> into</c><00:15:44.240><c> my</c><00:15:44.639><c> first</c><00:15:45.199><c> master</c><00:15:45.600><c> node</c><00:15:46.000><c> or</c>
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><c> server</c><00:15:46.720><c> node</c><00:15:46.959><c> that's</c><00:15:47.279><c> running</c><00:15:47.600><c> the</c>
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><c> plane</c><00:15:48.560><c> and</c><00:15:48.720><c> it's</c><00:15:48.880><c> also</c><00:15:49.199><c> one</c><00:15:49.440><c> of</c><00:15:49.519><c> the</c>
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><c> that's</c><00:15:50.160><c> running</c><00:15:50.480><c> cube</c><00:15:50.720><c> vip</c><00:15:50.959><c> that's</c>
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><c> this</c><00:15:52.240><c> vip</c><00:15:52.639><c> so</c><00:15:52.959><c> i</c><00:15:53.120><c> decided</c><00:15:53.600><c> to</c><00:15:54.000><c> shut</c>
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><c> down</c><00:15:54.959><c> and</c><00:15:55.279><c> as</c><00:15:55.519><c> you</c><00:15:55.680><c> can</c><00:15:55.920><c> see</c><00:15:56.160><c> on</c><00:15:56.480><c> the</c><00:15:56.639><c> right</c>
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><c> still</c><00:15:57.680><c> getting</c><00:15:58.000><c> responses</c><00:15:58.959><c> and</c><00:15:59.279><c> you</c><00:15:59.360><c> can</c>
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><c> on</c><00:15:59.920><c> the</c><00:16:00.079><c> left</c><00:16:00.720><c> i'm</c><00:16:00.880><c> not</c><00:16:01.120><c> getting</c><00:16:01.360><c> a</c>
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><c> from</c><00:16:02.160><c> that</c><00:16:02.320><c> machine</c><00:16:02.959><c> so</c><00:16:03.199><c> this</c><00:16:03.440><c> means</c>
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><c> have</c><00:16:04.160><c> an</c><00:16:04.399><c> h</c><00:16:04.560><c> a</c><00:16:04.720><c> vip</c><00:16:04.959><c> now</c><00:16:05.440><c> now</c><00:16:05.680><c> i</c><00:16:05.759><c> can't</c><00:16:06.000><c> shut</c>
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><c> a</c><00:16:06.720><c> second</c><00:16:07.120><c> node</c><00:16:07.600><c> an</c><00:16:07.759><c> aja</c><00:16:08.160><c> cluster</c><00:16:08.639><c> of</c>
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><c> three</c><00:16:09.440><c> nodes</c><00:16:09.839><c> can</c><00:16:10.079><c> only</c><00:16:10.560><c> lose</c><00:16:10.959><c> one</c>
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><c> so</c><00:16:11.920><c> if</c><00:16:12.079><c> i</c><00:16:12.160><c> shut</c><00:16:12.399><c> down</c><00:16:12.720><c> another</c>
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><c> i</c><00:16:13.759><c> won't</c><00:16:14.079><c> have</c><00:16:14.240><c> access</c><00:16:14.880><c> to</c>
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><c> but</c><00:16:16.079><c> i</c><00:16:16.240><c> will</c><00:16:16.480><c> still</c><00:16:16.720><c> have</c><00:16:16.959><c> access</c>
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><c> all</c><00:16:17.759><c> of</c><00:16:17.839><c> my</c><00:16:18.000><c> workloads</c><00:16:18.480><c> that</c><00:16:18.639><c> are</c><00:16:18.720><c> running</c>
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><c> just</c><00:16:19.440><c> that</c><00:16:19.600><c> i</c><00:16:19.759><c> can't</c><00:16:20.000><c> change</c><00:16:20.240><c> the</c><00:16:20.399><c> state</c>
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><c> kubernetes</c><00:16:21.360><c> nor</c><00:16:21.839><c> access</c><00:16:22.320><c> it</c><00:16:22.480><c> over</c><00:16:22.800><c> coupe</c>
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><c> so</c>
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><c> is</c><00:16:25.120><c> so</c><00:16:25.360><c> awesome</c><00:16:25.839><c> so</c><00:16:26.079><c> i</c><00:16:26.240><c> started</c><00:16:26.560><c> that</c>
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><c> node</c><00:16:27.199><c> back</c><00:16:27.519><c> up</c><00:16:27.759><c> and</c><00:16:27.920><c> it's</c><00:16:28.079><c> responding</c>
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><c> obviously</c><00:16:29.680><c> qbip</c><00:16:30.160><c> is</c><00:16:30.240><c> still</c><00:16:30.480><c> responding</c>
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><c> what</c><00:16:31.759><c> does</c><00:16:31.920><c> one</c><00:16:32.160><c> do</c><00:16:32.399><c> after</c><00:16:32.639><c> we</c><00:16:32.800><c> build</c><00:16:33.040><c> the</c>
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><c> k3s</c><00:16:34.240><c> cluster</c>
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><c> burn</c><00:16:36.160><c> it</c><00:16:36.240><c> down</c><00:16:36.480><c> of</c><00:16:36.639><c> course</c><00:16:37.360><c> there's</c><00:16:37.600><c> also</c><00:16:37.920><c> a</c>
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><c> to</c><00:16:38.800><c> totally</c><00:16:39.279><c> reset</c><00:16:39.680><c> k3s</c><00:16:40.320><c> back</c><00:16:40.560><c> to</c>
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><c> initial</c><00:16:41.199><c> state</c><00:16:41.680><c> so</c><00:16:41.920><c> running</c><00:16:42.240><c> this</c>
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><c> and</c><00:16:43.120><c> pointing</c><00:16:43.519><c> at</c><00:16:43.600><c> the</c><00:16:43.839><c> same</c><00:16:44.079><c> host</c>
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><c> totally</c><00:16:45.279><c> clean</c><00:16:45.519><c> it</c><00:16:45.680><c> up</c><00:16:46.079><c> it'll</c><00:16:46.399><c> clean</c><00:16:46.639><c> up</c>
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><c> nodes</c><00:16:47.600><c> remove</c><00:16:48.160><c> all</c><00:16:48.399><c> containers</c><00:16:49.120><c> and</c>
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><c> it</c><00:16:49.839><c> back</c><00:16:50.079><c> to</c><00:16:50.240><c> the</c><00:16:50.320><c> state</c><00:16:50.639><c> it</c><00:16:50.800><c> was</c><00:16:51.120><c> before</c>
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><c> ran</c><00:16:51.839><c> this</c><00:16:52.079><c> playbook</c><00:16:52.560><c> this</c><00:16:52.800><c> was</c><00:16:53.040><c> super</c>
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><c> as</c><00:16:54.000><c> i</c><00:16:54.079><c> was</c><00:16:54.320><c> testing</c><00:16:54.639><c> on</c><00:16:54.720><c> my</c><00:16:54.880><c> changes</c>
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><c> have</c><00:16:55.920><c> run</c><00:16:56.160><c> this</c><00:16:56.800><c> at</c><00:16:56.880><c> least</c><00:16:57.199><c> a</c><00:16:57.279><c> thousand</c>
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><c> and</c><00:16:58.399><c> after</c><00:16:58.720><c> it's</c><00:16:58.880><c> done</c><00:16:59.120><c> we're</c><00:16:59.279><c> back</c><00:16:59.519><c> to</c>
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><c> good</c><00:16:59.920><c> state</c><00:17:00.320><c> one</c><00:17:00.560><c> note</c><00:17:01.040><c> you</c><00:17:01.199><c> might</c><00:17:01.440><c> want</c><00:17:01.600><c> to</c>
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><c> reboot</c><00:17:02.480><c> them</c><00:17:02.720><c> afterwards</c><00:17:03.440><c> i've</c>
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><c> that</c><00:17:04.160><c> the</c><00:17:04.319><c> vip</c><00:17:04.640><c> stays</c><00:17:05.039><c> up</c><00:17:05.199><c> and</c><00:17:05.360><c> it</c>
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><c> respond</c><00:17:06.319><c> so</c><00:17:06.559><c> i</c><00:17:06.720><c> have</c><00:17:06.959><c> a</c><00:17:07.039><c> playbook</c><00:17:07.679><c> to</c>
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><c> all</c><00:17:08.559><c> of</c><00:17:08.640><c> these</c><00:17:08.880><c> machines</c><00:17:09.600><c> and</c><00:17:09.679><c> this</c>
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><c> will</c><00:17:10.559><c> actually</c><00:17:11.039><c> wait</c><00:17:11.199><c> for</c><00:17:11.360><c> them</c><00:17:11.520><c> to</c>
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><c> before</c><00:17:12.880><c> it</c><00:17:13.039><c> reports</c><00:17:13.439><c> a</c><00:17:13.600><c> success</c>
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><c> like</c><00:17:15.439><c> that</c><00:17:15.839><c> and</c><00:17:16.000><c> so</c><00:17:16.400><c> this</c><00:17:16.720><c> is</c><00:17:17.120><c> everything</c>
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><c> everyone</c><00:17:18.480><c> struggles</c><00:17:18.959><c> with</c><00:17:19.199><c> when</c>
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><c> up</c><00:17:19.919><c> k3s</c><00:17:20.959><c> no</c><00:17:21.120><c> more</c><00:17:21.360><c> using</c><00:17:21.679><c> mysql</c><00:17:22.319><c> and</c>
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><c> that</c><00:17:23.039><c> ha</c><00:17:23.600><c> if</c><00:17:23.679><c> you</c><00:17:23.839><c> don't</c><00:17:24.000><c> want</c><00:17:24.240><c> to</c><00:17:24.640><c> no</c>
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><c> spinning</c><00:17:25.360><c> up</c><00:17:25.600><c> additional</c><00:17:26.160><c> load</c>
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><c> and</c><00:17:27.280><c> keep</c><00:17:27.520><c> a</c><00:17:27.600><c> live</c><00:17:27.839><c> d</c><00:17:28.400><c> and</c><00:17:28.640><c> making</c>
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><c> aj</c><00:17:30.080><c> if</c><00:17:30.240><c> you</c><00:17:30.320><c> don't</c><00:17:30.480><c> want</c><00:17:30.720><c> to</c><00:17:31.200><c> no</c><00:17:31.360><c> more</c>
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><c> metal</c><00:17:32.640><c> lb</c><00:17:33.120><c> or</c><00:17:33.280><c> installing</c><00:17:33.760><c> with</c>
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><c> if</c><00:17:34.720><c> you</c><00:17:34.799><c> don't</c><00:17:34.960><c> want</c><00:17:35.200><c> to</c><00:17:35.679><c> just</c><00:17:36.160><c> one</c>
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><c> playbook</c><00:17:37.280><c> that</c><00:17:37.520><c> spins</c><00:17:37.840><c> up</c><00:17:38.160><c> all</c><00:17:38.320><c> of</c>
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><c> in</c><00:17:39.039><c> one</c><00:17:39.360><c> shot</c><00:17:39.760><c> and</c><00:17:39.919><c> then</c><00:17:40.320><c> you</c><00:17:40.559><c> can</c><00:17:40.720><c> burn</c>
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><c> down</c><00:17:41.280><c> if</c><00:17:41.440><c> you</c><00:17:41.520><c> want</c><00:17:41.760><c> to</c><00:17:42.000><c> too</c><00:17:42.320><c> so</c><00:17:42.559><c> again</c><00:17:42.880><c> a</c>
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><c> thanks</c><00:17:43.679><c> to</c><00:17:43.840><c> the</c><00:17:44.000><c> k3s</c><00:17:44.640><c> community</c><00:17:45.120><c> who</c>
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><c> this</c><00:17:45.760><c> original</c><00:17:46.160><c> playbook</c><00:17:46.799><c> along</c><00:17:47.039><c> with</c>
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><c> gearling</c><00:17:48.080><c> thank</c><00:17:48.240><c> you</c><00:17:48.400><c> so</c><00:17:48.559><c> much</c><00:17:49.200><c> and</c><00:17:49.440><c> also</c>
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><c> you</c><00:17:50.160><c> to</c><00:17:50.480><c> github</c><00:17:50.880><c> user212</c><00:17:51.919><c> 850a</c>
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><c> you</c><00:17:53.840><c> so</c><00:17:54.000><c> much</c><00:17:54.400><c> i'll</c><00:17:54.640><c> have</c><00:17:54.799><c> links</c><00:17:55.120><c> in</c><00:17:55.200><c> the</c>
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><c> to</c><00:17:56.240><c> all</c><00:17:56.400><c> of</c><00:17:56.480><c> the</c><00:17:56.559><c> code</c><00:17:56.799><c> that</c><00:17:57.039><c> i</c>
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><c> in</c><00:17:57.840><c> the</c><00:17:57.919><c> description</c><00:17:58.480><c> below</c><00:17:59.120><c> so</c><00:17:59.360><c> what</c><00:17:59.600><c> do</c>
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><c> think</c><00:18:00.000><c> of</c><00:18:00.080><c> spinning</c><00:18:00.480><c> up</c><00:18:00.640><c> a</c><00:18:00.880><c> truly</c><00:18:01.440><c> ha</c>
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><c> of</c><00:18:02.400><c> k3s</c><00:18:02.960><c> using</c><00:18:03.280><c> ansible</c><00:18:03.760><c> is</c><00:18:03.919><c> there</c>
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><c> i</c><00:18:04.480><c> should</c><00:18:04.720><c> contribute</c><00:18:05.280><c> to</c><00:18:05.440><c> the</c>
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><c> to</c><00:18:06.000><c> make</c><00:18:06.160><c> it</c><00:18:06.559><c> easier</c><00:18:06.880><c> for</c><00:18:07.039><c> you</c><00:18:07.360><c> let</c><00:18:07.520><c> me</c>
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><c> in</c><00:18:08.240><c> the</c><00:18:08.400><c> comments</c><00:18:08.720><c> section</c><00:18:09.039><c> below</c><00:18:09.600><c> and</c>
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><c> if</c><00:18:10.480><c> you</c><00:18:10.640><c> found</c><00:18:11.039><c> anything</c><00:18:11.440><c> in</c><00:18:11.520><c> this</c>
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><c> helpful</c>
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><c> forget</c><00:18:13.520><c> to</c><00:18:13.679><c> like</c><00:18:13.919><c> and</c><00:18:14.000><c> subscribe</c>
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><c> for</c><00:18:15.760><c> watching</c><00:18:16.160><c> fix</c><00:18:16.400><c> the</c><00:18:16.559><c> lights</c><00:18:16.880><c> i</c><00:18:17.280><c> if</c>
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><c> weren't</c><00:18:17.760><c> here</c><00:18:18.000><c> last</c><00:18:18.240><c> week</c><00:18:18.640><c> small</c><00:18:19.039><c> episode</c>
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><c> the</c><00:18:19.679><c> lights</c><00:18:19.919><c> i</c><00:18:20.000><c> couldn't</c><00:18:20.240><c> figure</c><00:18:20.480><c> out</c>
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><c> was</c><00:18:20.960><c> going</c><00:18:21.200><c> on</c><00:18:21.360><c> with</c><00:18:21.520><c> my</c><00:18:21.760><c> bottom</c><00:18:22.080><c> lights</c>
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><c> bottom</c><00:18:23.200><c> lights</c><00:18:23.679><c> ended</c><00:18:24.000><c> up</c><00:18:24.320><c> having</c><00:18:24.720><c> a</c><00:18:24.880><c> small</c>
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><c> and</c><00:18:25.679><c> it</c><00:18:25.840><c> took</c><00:18:26.080><c> me</c><00:18:26.240><c> a</c><00:18:26.320><c> long</c><00:18:26.559><c> time</c><00:18:26.799><c> to</c>
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><c> out</c><00:18:28.080><c> it</c><00:18:28.240><c> ended</c><00:18:28.559><c> up</c><00:18:28.640><c> being</c><00:18:28.960><c> a</c><00:18:29.120><c> firewall</c>
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><c> so</c><00:18:30.080><c> if</c><00:18:30.240><c> it's</c><00:18:30.480><c> not</c><00:18:30.720><c> dns</c><00:18:31.440><c> it</c><00:18:31.600><c> is</c><00:18:31.760><c> a</c><00:18:31.840><c> firewall</c>
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><c> all</c><00:18:32.720><c> right</c><00:18:32.960><c> changing</c><00:18:33.280><c> the</c><00:18:33.360><c> light</c><00:18:33.520><c> as</c>
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><c> as</c><00:18:33.840><c> i</c><00:18:33.919><c> mention</c><00:18:34.240><c> them</c>
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><c> it's</c><00:18:35.760><c> not</c><00:18:35.919><c> dns</c><00:18:36.400><c> it's</c><00:18:36.559><c> a</c><00:18:36.640><c> firewall</c><00:18:37.039><c> rule</c><00:18:37.280><c> now</c>
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><c> you're</c><00:18:37.919><c> really</c><00:18:38.160><c> testing</c><00:18:38.480><c> mines</c><00:18:38.880><c> all</c>
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><c> it's</c><00:18:39.760><c> gonna</c><00:18:40.000><c> happen</c><00:18:40.320><c> it's</c><00:18:40.400><c> gonna</c>
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><c> so</c>