►
From YouTube: This Week in Cloud Native
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everybody
good
afternoon.
This
is
duffy
cooley
coming
at
you
with
this
week
in
cloud
native
episode.
Three
I'm
glad
you're
here
and
I'm
really
excited
about
this
next
episode.
A
So,
let's
dig
into
it
see
what's
happening
this
week,
if
you're
here
on
the
chat,
go
ahead
and
say
hello,
I'd
love
to
I'd,
love
to
you
know,
see
you
here
every
week
as
we're
going
through
this
process,
so
I'd
love
to
know
that
you're
here
the
only
way.
I
know
that
that's
happening
is
if
you're
in
the
chat.
So
if
you're
here
check
in
love
to
see
folks
showing
up
here
all
right.
A
The
next
thing
I
have
for
you
today
is
this
page,
which
is
kind
of
our
weekly
thing,
where
we're
going
to
keep
I'm
keeping
notes
on
on
stuff.
That
is
exciting.
That
happens
during
the
week
or
during
the
last
two
weeks
in
cloud
native
space
and
if
there's
anything
that
you
would
like
me
to
cover,
you
can
always
just
go
to
hackmd
dot
io
at
twicn
this
week
in
cloud
native
and
put
in
a
note
for
me
and
I'll
read
it
to
you
live
on
screen
and
that's
my
plan
for
every
week.
A
So,
if
that's
so,
if
you
see
anything,
that's
interesting,
you
can
either
just
shout
out
to
me
on
twitter
or
you
can
put
it
in
the
hackmd
notes,
and
I
will
cover
it
every
week
and
this
episode
for
this
week's
update.
I
wanted
to
talk
about.
What's
coming,
let's
see
here,
we
have
one
of
the
changes
that
I
saw
on
youtube,
which
I
was
pretty
excited
about.
Was
this
one
here
where
we
have
playlists
and
there
are
playlists
for
every
show?
A
And
so,
if
you
want,
if
you
missed
your
episode
with
siam
or
with
maddie
or
leo
leonardo
or
any
of
these
other
folks,
you
can
go
ahead
and
just
either
subscribe
directly
to
that
playlist
or
you
can
go
back
and
watch
what
watch
the
the
episode
that
happened.
While
you
were
away,
but
each
of
the
channels
seems
to
have
their
own
playlist
associated
there
and
that's
pretty
exciting,
so
there's
new
content.
A
Every
day
of
the
week
this
week,
tim
banks
was
hosting
sydney
miller,
one
of
the
just
incredibly
awesome
people
in
tech,
and
this
is
talking
about
sydney's
journey
into
tech
and
how
she's
helping
others
kind
of
along
that
same
path.
Sydney
works
at
equinix
metal
and
it
was
really
a.
A
I
think,
it's
a
pretty
good
episode
that
happened
earlier
today
check
that
one
out
cloud
native
land,
next,
with
leonardo
maria
all
about
the
community,
we'll
have
guests
from
various
latin
american
countries
showing
challenges,
opportunities
and
value
in
building
a
community
in
latin
america.
Come
check
it
out.
Cncf
face-off
is
kind
of
a
game.
Show
hosted
by
maddie
and
if
you're
interested
in
you
know
kind
of
participating
in
that
it
should
be
super
fun
and
matt
stratton
will
be
hosting
it.
A
If
you
want
to
be
a
part
of
it,
you
can
actually
just
follow
this
link
and
it
will
take
you
to
a
forum
where
you
can
pick
your
team.
What
you
want
to
what
what
you
want
that
team
to
be
called
all
that
good
stuff
and
and
and
then
participate
in
the
show,
and
so
I
think,
that'll
really
be
fun,
like
I
said,
siam's
doing,
search
magic
all
about
the
different
certified
kubernetes
certifications
we
have
spotlight
live
with
dan
pop.
We
have
lgtm
with
rock
code.
He
just
did.
A
One
on
prometheus
was
really
fun
kind
of
getting
from
idea
to
commit
on
that
100
days
with
anayas
unease
and
cloud
native
classroom
with
cat
costume.
I
think
she
just
did
thanos,
if
I
remember
correctly,
and
then
fields
tested
with
caslin
so
definitely
check.
Those
shows
out
they're
happening
right
here
on
cloud
native
tv
feel.
Please
subscribe
to
this
show.
A
If
you
I
mean
to
this
channel
on
twitch,
you
should
see
a
subscribe
button
down
around
there
somewhere
and
go
ahead
and
click
that
button
get
notified
whenever
we're
online
there'll
always
be
something
interesting
happening
in
the
kubernetes
space.
One
of
the
exciting
announcements
is
that
this
early
bird
pricing,
which
is
about
650
off
of
the
on-site
pricing
on
200
off
the
standard
pricing,
is
ending
july
4th.
So
if
you
want
to
get
that
pricing
get
it
done
now,
you
can
save
a
bunch
of
money
either
as
a
corporate
or
an
individual.
You
can
save.
A
So
july
5th
the
sale
ends
july
5th,
so
definitely
want
to
make
that
happen.
One
of
the
other
commits
I
saw
happen
in
the
kubernetes
community
this
week,
which
I
thought
was
pretty
exciting
to
me
anyway,
was
the
cube.
Adm
now
runs
as
not
root,
and
this
is
part
of
a
cap,
but
let's
take
a
look
at
the
commit
it's
kind
of
an
exciting
commit.
A
So
this
is
actually
the
cap
right
here.
It's
a
bunch
of
work
by
vinay.
A
And
what
this
represents
is
a
change
in
the
way
that
we
operate,
the
static
pod
manifests
and
other
things
run
by
keybdm
in
such
a
way
that
they
are
significantly
more
secure.
The
running
is
not
root.
All
of
the
capabilities
have
been
dropped
other
than
the
ones
that
are
necessary
for
that
application
to
run
and
if
you're
interested
in
this
work,
or
you
want
to
kind
of
read
through
what's
happened
or
what
the
changes
are
definitely
check.
These
issues
out,
I
was
thinking
about
for
our
play
time.
A
I
would
kind
of
explore
rootless,
cube
adm,
but
I
don't
think
I'm.
I
don't
think
I
quite
have
the
right
setup
for
that
today.
So
I'm
probably
going
to
explore
something
else
in
that
space,
but
maybe
not
that,
but
maybe
on
the
next
episode.
If
I
have
a
little
bit
more
time
to
set
up,
I
might
set
that
one
up,
because
I'm
actually
kind
of
interested
in
seeing
how
that's
going
like
it
should
be
a
really
fun
one.
A
So
rootless,
cube
adm.
That
means,
like
your
control,
plane,
your
scheduler,
your
cube
proxy,
all
of
those
components,
running
rootless
and
as
a
user
that
is
not
root,
and
that
way,
if
for
some,
if
by
some
chance,
somebody
were
to
exploit
one
of
those
control
claim
components
on
inside
of
your
cluster.
They
wouldn't
be
able
to
actually
take
over
the
cluster,
which
is
actually
pretty
cool.
A
Hey.
We
got
people
checking
in,
let's
see
who
these
folks
are
got
samomi
hello,
good,
to
see
you
what
was
kind
doing
when
running
kubernetes
before
in
kind's
project.
Actually,
in
my
in
my
play
time,
I'm
gonna
show
that,
but
the
way
that
kind
was
doing
it
was
leveraging
just
regular,
cube,
adm
inside
of
a
root
container,
so
kind
in
itself.
A
Under
no
circumstances,
it
should
be
considered
like
secure
right
because,
like
you're
running
privileged
containers
on
your
host
that
have
that
have
significant
privilege,
otherwise
we
wouldn't
be
able
to
like
stand
up
containers
and
that
sort
of
stuff.
Now
there
is
some
change
happening
inside
of
the
kind
project
that
would
enable
rootless
mode.
In
fact,
I've
seen
one
of
the
heroes
of
rootless
one
of
the
heroes.
No
pun
intended
of
rootless
mode
in
the
project
working
on
just
exactly
that.
A
Akihiro
has
been
working
on
implementing
rootless,
rootless
kind,
so
that'll
be
kind
of
exciting,
and
I
imagine
this
work
kind
of
overlaps,
or
at
least
relates,
but
I
haven't
looked
at
it
too
closely.
Yet.
A
A
If
you
haven't
checked
out
the
kubernetes
podcast,
it's
probably
worth
checking
out
it's
a
pretty
decent
podcast
they've
always
got
some
really
good
stuff
happening
inside
of
that
space,
and
then
also
the
recent
tgik
tgik
158
was
hosted
by
nadir
and
jason
tabirus,
who
are
good
friends
of
mine,
who
I
worked
with
at
coreos
or
sorry
adheptio,
and
they
did
a
whole
episode
on
cluster
api
with
tinkerbell,
so
if
you're
interested
in
tinkerbell
or
cluster
api
or
how
to
mash
these
words
together
definitely
check
out
that
episode.
It's
tgik158.
A
We
got
a
great
question
by
emily
fox
talking
about
the
security
tag
working
on
a
server-less
security
paper,
which
will
be
a
really
interesting
one.
A
How
to
build
a
helm
plug-in
in
minutes
and
avoiding
kubernetes
cluster
outages
with
synthetic
monitoring?
I
haven't
looked
at
that
one.
Yet
that
looks
pretty
interesting,
but
there's
a
bunch
of
different,
really
great
articles,
including
this
one,
which
I
also
thought
about
playing
with
how
to
monitor
kubernetes
costs
with
lens
ide.
A
If
you
haven't
heard
about
the
lens
ide,
it's
another
open
source
ide
for
kubernetes,
and
it's
actually
pretty
cool,
so
justin,
reminding
us
all
that
if
you're
going
to
be
at
the
participant
at
the
contributor
summit
or
you're
going
to
come
to
los
angeles
to
be
a
part
of
cubecon,
and
you
want
to
go
to
disneyland
as
part
of
that
trip,
you
should
definitely
join
all
of
us
together
going
to
disneyland
and
we
called
it
cubie.
We
call
it
qbland.
A
We
did
this
back
in
san
diego
before
the
pandemic,
and
it
was
really
a
lot
of
fun.
But
definitely
you
know
if
that's
something.
That's
interesting
to
you
check
that
out.
He's
got
a
form
to
add
yourself
and
there's
no
discounts
or
anything,
but
like
it's
a
great
way
of
like
you
know,
hanging
out
with
folks
in
the
community
in
a
place
that
is
totally
unrelated
to
kubernetes.
A
And
then
we
have
the
ss
the
editorial
articles,
here's
one
that
I
pulled
out,
which
was
craig
craig
box
talking
to
steve
mcgee
talking
about
sre
for
everyone
else.
I
thought
that
was
a
really
good
one.
A
Get
ops
for
rabbitmq
with
alexis
richardson,
I
mean
that's
a
really
interesting
one
rabbitmq
and
get
ups.
I'm
I'm
surprised
by
that.
I
guess
we'll
see
how
that
goes.
It'll
be
kind
of
a
fun
one
to
play
through
and
then
alex
ellis
wrote
a
book
on
golang
and
alex
is
incredibly
transparent
about
things
that
are
happening,
and
so,
if
you're
curious
about
how
that
goes
like
what
he
went
through
to
write
that
book
and
how
that's
actually
working
for
working
in
the
space
or
not,
definitely
check
that
out
like.
A
A
So
if
you
want
to
be
a
part
of
the
part
of
this
mailing
list,
all
you
got
to
do
is
click
on
that
link,
the
security,
announce
group
and
click
join
group
and
then
you'll
be
able
to
you
know
you
can
kind
of
pick
how
often
you
get
spammed
it
can
be
on
every
notification.
It
can
be
a
digest,
it's
up
to
you,
how
you
do
it,
but
definitely
a
good
one
to
watch
out
for
if
security
inside
of
kubernetes
is
something
that
you're.
A
One
of
the
other
things
from
the
community
I
saw
is
this
cncf
end
user
community
providing
insights
into
kubernetes
cluster
management
with
technology
radar,
and
so
this
is
a
pretty
good
article
talking
about
like
how
folks
are
managing
their
kubernetes
clusters
and
what
tooling
and
stuff-
and
this
is
a
pretty
interesting
one
and
it's
one
of
the
first
things
I've
seen
come
out
of
the
the
user
group
around.
A
You
know
the
cncf
user
group
group,
so
I
think
that's
a
pretty
good
one
so
definitely
check
that
out
if
you're
interested
and
then
it's
play
time
so
today
for
playtime,
my
plan
was
to
set
up
an
environment
from
scratch
and
find
an
issue
that
has
not
yet
been
merged.
A
Something
super
simple
and
and
then
show
how
to
build
that
commit
and
then
test
that
commit
according
to
what
the
issuers
describes
and
and
kind
of
work
through
that
kind
of
end
to
end
right.
So
that
was
that
was
my
goal
for
today.
Kind
of
help
you
get
your
environment
set
up
work
through
like
what
it
looks
like
to
actually
test
a
commit
and
show
that
the
commit
changes.
What
it
says
is
going
to
change,
and
that
was
my
goal
and
I
figure
we
can
do
that
in
about
45
minutes.
A
So
the
commit
I
picked
actually
is
like
I
said
it
was
going
for
something
really
super
simple.
Oh
not
this
one,
that's
not
a
super
simple
one!
There
we
go.
So
this
is
an
open
issue
and-
and
it
looks
like
this
person
had
found
a
you
know-
a
leftover
word
alpha
in
a
command,
a
cube,
adm
help
command
and
went
ahead
and
put
in
the
fix
basically
to
remove
the
word
alpha
from
the
cubanium
help
command,
and
what
I
want
to
show
is
how
to
actually
get.
A
I
mean
first,
I
kind
of
want
to
work
through
the
ui
here
a
little
bit,
so
we
can
actually
understand
like
where
this
commit
is
in
time
or
where
other
commits
are
in
time.
I
want
to
show
you
that
stuff
and
then
I'm
going
to
show
you
how
to
set
up
an
environment
in
which
we
can
actually
test
that
this
commit
changes,
what
it
expected
to
change-
and
this
is
a
super
super
simple
example,
but
I
think
it'll
give
you
the
tools
to
test
a
more
complex
example.
A
If
you
choose
to
do
so
yourself,
so
first
thing
I
wanted
to
show
you
was
like
this
page
here.
So
if
you,
if
you
have
a
commit,
that's
been
committed
like
this
one
here
it's
been
merged
right,
then
what
you
can
do
is
you
can
actually
click
on
the
commit
link
down
here,
which
is
the
commit
hash
and
now
you're
looking
at
the
actual
commit
that
is
represented
inside
of
the
code
base
and
one
of
the
questions
that
people
frequently
ask
is
where,
in
time
is
this
commit
right?
Is
this
commit?
A
I
mean
it's
clearly
been
merged
to
master,
but
is
it
also
part
of
a
branch
or
a
tag
or
anything
else
like
that
and
the
reason
I'm
taking
you
to
this
page
right?
If
you
look
at
the
commit,
you
can
actually
see
what
branches
and
tags
it
is
associated
with
right.
So
right
at
the
moment
it's
on
master
and
there
are.
A
There
is
no
branch,
but
it
is
associated
with
the
tag
v122
beta0,
which
me,
I
think,
is
the
top
of
tree
right
now
we
can
go
look,
but
if
you're
ever
wondering
like
whether
a
commit,
if
you've
narrowed
the
problem
that
you
have
down
to
a
single
commit-
and
you
want
to
see
if
that
commit-
is
part
of
a
particular
release
or
or
or
has
made
it
or
it
has
been
reported
back
ported
or
any
of
those
things.
This
is
the
way
that
you
find
that
out
right.
A
A
A
So
here
is
another
page
that
we've
committed
and
we
can
see
that
this,
oh
man,
I
guess
there's
so
many
commits
that
happen
like
so
frequently
and
so
and
so
on
in
such
an
automated
way,
but
it's
kind
of
hard
to
find
one
that
is,
like
you
know,
historically
relevant.
Let's
see
if
I
can
figure
out
a
way
to
do
this.
A
A
Was
committed
on
2019,
and
we
can
see
down
here
below
that
we
see
a
different
output
instead
of
showing
us
just
the
just
the
top
of
tree
branch
or
the
top
of
tree
tag.
We
can
also
see
that
this
commit
was
part
of
every
tag
from
v118
alpha
2
all
the
way
to
current
right,
and
if
we
click
on
between,
we
can
see
this
commit
resides
in
each
of
the
tagged
versions
from
118
alpha
2
all
the
way
to
122.0
beta0.
A
A
And
next
up
we're
going
to
build
this
and
we're
going
to
test
and
see
if
it
works,
and
so
I
kind
of
want
to
so
that'll
involve
setting
up
a
build
environment,
we're
going
to
leverage
kind
for
a
lot
of
the
build
environment
and
we're
going
to
go
ahead
and
build
cube.
Adm
with
this
commit,
and
I'm
going
to
show
you
that
I'm
going
to
show
you
the
before
and
after
right,
all
right.
So
let's
check
this
out.
A
A
Oh.Net,
this
is
the
tool
that
lets
you
set
environment
variables
when
you
move
into
a
directory
so
and
you're
not
in
the
directory.
The
environment
variables
are
empty,
but
when
you
move
into
it
all
of
the
environment
variables
that
you
have
specified
inside
of
your
dot
and
var
c
are
loaded
into
your
environment.
A
A
I
am
this
weekend
cloud
native
deer,
edit
dot,
and
this
creates
a
dm
file,
but
there's
nothing
in
there
right
now.
A
A
A
And
there's
lots
of
ways
to
do
this.
This
is
just
the
way
that
I've
been
using
for
this
and
I
kind
of
like
it
because
it
actually
it's
pretty
frequently
updated
and
pretty
well
maintained,
because
it's
part
of
the
solution
stack
at
travis
ci,
and
so
I'm
actually
pretty
pretty
convinced
that
it
will
be
around
for
a
while
and
then
it's
pretty
reasonably
tested
right.
So
gimme
go
is
a
bash
script
that
sets
the
environment
variables.
A
So
if
you're
going
to
use
go
in
any
kind
of
like
containerized
environment,
this
is
a
really
great
tool,
but
also
even
locally
right,
like
we
understand
that
like
clearly
go
changes
versions
faster
than
many
of
the
distribution
package,
managers
and
stuff
keep
up
with,
and
so
it
can
sometimes
be
difficult
to
like
determine
which
one
you
want
to
use
like
python
has
something
like
this:
that's
called
like
pip-m,
or
something
like
that.
A
These
are
environment
variables
that
it
set
it
unset,
goose
and
unset
go
arch,
and
then
I
went
ahead
and
set
export
go
root
and
that's
where
the
that's
that's,
where
the
version
of
go
that
is
stable,
currently
has
been
put,
and
then
it
added
it
to
my
path
before
everything
else,
making
sure
that
that
version
of
go
would
be
leveraged
and
then
gave
me,
and
then
I
exported
a
bunch
of
environment
variables
inside
of
this
space
right.
So
let's
take
a
look
at
that.
One.
A
A
A
A
A
A
A
A
A
And
what
I'm
doing
here
is
I'm
just
adding
the
gopass
binary
directory
our
bin
directory
into
before
our
regular
path,
and
that
way,
any
bins
that
are
in
there
are
going
to
get
loaded
up
right.
So
let's
go
ahead
and
exit
and
if
I
do
dram
allow
and
then,
if
I
do,
which
kind
we
can
see
that
that's
the
version
of
kind
that
we're
using
pretty
darn
cool
all
right
next
up.
A
What
we're
going
to
do
is
we're
going
to
check
out
the
kubernetes
code
base
and
we're
going
to
look
at
that
commit
we're
probably
going
to
use
like
some
some
github
cli
commands
or
we
could
not.
But
I
think
I
think
I
want
to
show
you
the
github
client
commands,
because
they
can
really
make
your
in
your
life
a
lot
easier
when
working
through
this
kind
of
stuff.
A
Let
me
actually
just
make
this
a
little
bit
bigger
too,
because
I
think
maybe
that's
a
little
too
okay.
Small
better
looks
like
we
have
a
question.
I
want
to
jump
over
here
and
see
what
the
question
is
once
indirect
and
another
and
give
me
him
yeah.
I
know
it
does
seem
like
a
duplicate,
so
I
wonder
if
there's
like
a
catch
in
the
fact
that,
like
maybe
it's
trying
to
determine
in
fact
that
it
isn't
an
environment
manager
or
maybe
it
doesn't
know
that
or
something
does
seem
kind
of
like
a
double
kit.
A
I'm
not
setting
go
root
twice,
I'm
setting
go
paths
and
go
root
and
it's
only
setting
go
root,
one
the
one
time.
So,
if
I
do
echo
go
root
setting
it
to
that,
and
if
I
look
at
the
I
mean
it
is
setting
it
sorry
you're
right,
it
is
sitting
at
twice,
but
it's
sending
it
to
the
same
value
right.
It's
setting
it,
which
is
weird.
I
agree.
A
This
is
just
telling
us
where
we
got
the
environment
variables
yeah.
I
think
that's
it.
It's
only
setting
it
once
it's
only
setting
go
root
here
now,
if
we
had,
I
don't
know.
If
we
had
like
eval
dot
gimme
I
mean
we
had
eval
that
path,
then
it
would
actually
make
it
real
right,
but
we're
not
doing
that
we're
actually
kind
of
highlighting
where
that
content
came
from.
A
So
we
got
that
set
up,
let's
jump
in
let's
jump
in
a
little
further
here
and
play
with
this
stuff,
so
we've
got
to
go
environment
now.
The
next
thing
I
do
personally
is:
I
actually
go
ahead
and
check
out
what
go,
what
go
111
mods
off,
because
I
kind
of
want
it
to
be
under
my
source
tree,
and
I
think
that
might
just
be
the
way
that
I
do
it.
I'm
not
sure
that
everybody
does
it
that
way.
But
let
me
show
you
what
that
looks
like.
A
And
you
have
to
when
you're
going
to
check
out
the
kubernetes
source
code
you
have
to
use
like
the
the
the
I
o
moniker
like
a
lot
of
times.
A
If
you're
gonna
do
something
like
this,
you
would
normally
do
like
a
go,
get
like
github.com
username,
slash
project,
and
although
you
can
do
that
with
goget
and
kubernetes,
it
messes
it
up,
because
a
lot
of
the
paths
inside
of
the
code
base
require
that
that
that
they
are
importing
from
k,
h,
dot,
io,
slash,
kubernetes
blah,
and
so,
if
you
don't
have
that
pass,
if
you
don't
have
the
checkout
in
that
pass,
then
things
get
really
weird
and
woogy
and
they
don't
work
terribly
well,
and
so,
when
you're
going
through
this,
you
definitely
want
to
make
sure
that
you
check
out
the
kubernetes
code
base
with
go,
get
k,
h,
dot,
io,
kubernetes
or
your
environment
will
not
work
in
the
way
that
you
expect.
A
It
will
be
quite
painful,
so
we
can
see
that
this
checked
out
and
it's
going
to
complain
about
no
go
files,
because
this
isn't
an
automatic
build
that
would
be
kind
of
nuts.
Can
you
imagine
you
do
go,
get
google
do
this
and
it
just
builds
the
world
that
would
be
a
lot
of.
That
would
be
a
lot
of
work,
so
that
doesn't
happen
there.
It
works
out,
okay
for
kind
right,
but
like
for
kubernetes
now,
so
it's
moved
it
into
go
source
case
dot,
co,
io,
not
kubernetes.
So
if
we
move
into
that.
A
A
A
A
And
kind
will
automatically
detect
what
the
source
is
where,
where
your
source
is
checked
out
and
then
it
will
build
based
on
what
it
sees
here
right.
So
I'm
going
to
go
ahead
and
build
top
of
tree
and
hope
it
works.
Otherwise
I
might
have
to
back
out
and
do
actually
you
know
what
this
is
probably
a
bad
idea.
Let's
do
this.
Let's
do
kind.
A
A
You
can't
actually
tell
it
where
it
is
yeah.
One
of
the
questions
was:
can
you
tell
kind
to
use
where
the
source
code
is
by
any
chance
instead
of
using
your
grow
path?
And
the
answer
is
absolutely
yes,
in
fact,
while
that's
building
I'm
going
to
go
ahead
and
bring
up
another
window
and
show
you
that
right.
So
if
I
do
kind
build,
node
image
help.
A
A
While
we're
waiting
for
this
to
build,
let's
go
back
and
look
at
that
change
that
we
actually,
I
did
introduce
one
other
command.
It
was
the
github
cli,
and
I
wanted
to
kind
of
talk
to
talk
to
that
guy,
real
quick.
So
that's
on
cli.github.com,
it's
very
handy
like
you
can
actually
do
things
like
pull
a
particular
pull
request.
A
A
A
A
Right
now
we're
building
a
docker
image.
Now
a
lot
of
these
steps
that
make
this
seem
like
it's
going
to
take
a
really
long
time
will
take
longer
the
first
time
and
then
those
images
will
be
cached
right,
and
so
you
don't
have
to
actually
go
through
that,
like
initial
cost
over
and
over
again,
the
subsequent
build
we
do
of
kubernetes
will
be
faster
than
what
we're
seeing
here.
A
A
It's
pretty
solid
little
think
pad.
I'm
actually
really
happy
with
it.
The
one
that
I
had
before
this
was
a
x1
carbon
and
it
kind
of
suffered
a
little
bit
sometimes
in
like
in
in
doing
work,
because
I
think
most
of
my
biggest
problems
were
related
to
the
video
card,
like
the
video
card
itself
was
actually
kind
of
slow,
and
so
because
it
was
still
the
intel
chip
and
so
even
all
wired
up
correctly
and
everything.
It
still
couldn't
really
cut
something
like
the
stream
that
we're
doing
here,
like
it
wouldn't
be.
A
It
just
wouldn't
have
enough
resources
to
like
to
make
the
video
stuff
work
with
this
with
the
amd
chip
you
get
a
radeon
built
in,
so
it's
very
similar
to
like
that
intel
video
card,
but
it's
using
it's
using
radio
and
stuff,
so
it's
actually
pretty
significantly
faster
comparatively
so
I've
not
had
nearly
the
same
problems
with
this,
as
I
had
with
the
old
one.
A
A
A
I
can
see
map
of
my
memory
graph.
A
I
want
to
see
it
simpler,
more
complex.
I
can
see
disk
I
o
and
my
networking
for
and
my
network
upload
and
download,
so
pretty
cool
stuff.
A
A
Yeah
we're
big.
I
I'm
building
a
I'm
building,
basically
the
top
of
tree
for
kind
right
now,
and
then
I'm
gonna
pull
a
commit
from
upstream
and
then
go
ahead
and
build
that
commit
and
show
that
the
change
that
that
commit
represents
has
been
changed.
Yeah.
I
didn't
put
anything
in
the
notes
for
what
I
was
going
to
do
today,
but
I
should
probably
put
that
in
there
that's
a
very
good
call
out.
Thank
you
very
much
good
to
see
you
russ.
A
A
And
so
there's
all
of
our
binaries
that
we're
building
the
api
server
controller
manager
scheduler
proxy-
and
this
is
the
one
we
care
about
today-
cube
adm
and
the
reason
we
care
about
that
one.
So,
specifically,
is
we
want
to
make
sure
that
the
change
that
we're
making
to
cube
adm
shows
up
as
a
change
in
the
system.
A
A
A
Looks
like
we're
almost
done
with
the
build
a
pi
4.
I
mean
yes,
I
think
I
think
that
you
can
leverage
kind
we're
gonna.
As
long
as
you
can
put
kind
there,
then
you
can
use
kind
to
build
your
your
source
code
right
and
I'm
pretty
sure.
Although,
like
I
mean
maybe
we
should
just
go
look
because
I'm
actually
kind
of
curious
about
that
myself,
so
kind
arm
and
arm
53.
What
is
that
about
kind?
A
A
A
We
have
a
report
of
it
working
here
on
apple
silicon
yeah,
so
11,
1
and
11
should
just
work,
so
I
would
say,
give
it
a
try,
great
question:
this
is
the
question
I'm
responding
to.
Would
this
work
for
a
pi
4
or
would
you
would
you
recommend,
cross
compiling
and
I
think
it
would
work
so
pretty
cool
I've
not
tried
it,
but
I
don't
actually
have
I
don't
have
a.
A
I
don't
have
a
pie
to
play
with,
but
I
think
I
think
that,
with
a
lot
of
folks
like
moving
toward
the
apple
silicon
max
and
stuff,
there
could
be
more
people
playing
with
this
stuff,
and
so
I
would
expect
that
it
would
continue
to.
A
A
A
A
A
Type
and
what
we've
done
here
is
we
basically
just
leveraged
kind
as
a
kind
of
a
build
environment
for
everything
where
I
don't,
I'm
not
building
anything
by
my
hand,
I'm
just
actually
just
leveraging
kind
to
do
the
build
itself,
and
then
I
can
go
ahead
and
verify
that
the
change
is
there
or
not
as
a
reminder
of
the
change
that
we're
talking
about
here.
Let's
go
ahead
and
bounce
back
here
and
look
at
this
change.
A
A
A
A
A
A
A
A
A
A
A
A
A
The
necroman
message
now
what's
interesting
is
what's
happening
is
that
I
have
all
of
these
commits
in
this
huge
library
of
commits
on
my
system,
because
I
have
checked
out
that
pull
request.
I
can
now
put
the
commit
from
that
pull
request
anywhere
in
time
anywhere
on
any
branch
that
is
local
in
my
environment.
A
So
what
I've
done
is
I've
gone
ahead
and
pulled
that
commit
and
put
it
on
top
of
the
branch
that
we
built
our
original
kind
node
image
on
right.
So
now,
if
I
do
get
log
you
can
see
here
is
the
commit
that
was
made
right
to
correct
the
example
of
cubadium
help,
and
this
was
the
commit
for
the
tag
that
defined
it
right.
It
was
basically
where
the
tag
was
defined.
A
A
A
It
shouldn't
take
quite
as
long
to
build
all
of
this.
Actually,
I
think
I
just
did
I
just
added
a
branch
name
so
likely
that
reset
the
the
cache,
but
if
you
didn't
actually
actually
know,
I
added
a
commit,
so
it's
a
new
cache,
and
so
it
will
it
has
to
rebuild
from
scratch,
but
it
won't
hopefully
not
take
as
long
oh.
There
we
go.
A
A
A
A
So
if
you're
going
to
use
kind
as
a
build
environment,
one
of
the
questions
that
sometimes
people
have
is,
if
I'm
going
to
leverage
that
as
a
kind,
a
build
environment,
how
do
I
run
tests
against
the
code
that
I'm
working
with
kind
of
like
at
build
time
or
before
build
time
like?
Can
I
do
unit
tests
and
that
sort
of
stuff
like
where
is
the
code
checked
out
and
can
I
still
do
unit
tests
and
I'll
show
you
a
couple
of
different
ways
to
do
that.
A
A
We
can
see
already
that
this
build
is
way
faster
than
the
other.
Build
was
right
because
we
already
have
our
build
container
and
our
build
container
is
kind
of
in
a
fix
it.
It's
associated
with
a
particular
period
of
time
for
the
kubernetes
code
base,
and
so
as
long
as
we're
still
within
that
same
time,
we
don't
have
to
build
another
build
container.
We
can
leverage
that
same
build
container.
That
was
already
built
right
with
that
particular
version
of
go
with
those
particular
sets
of
tools.
A
But
we
are
building
all
the
binaries
with
our
change
and
at
the
moment,
we're
building
all
of
it
right
because
we're
testing
all
of
cube
with
cube
adm,
with
cube
kettle
with
the
api
server
controller
manager,
scheduler
all
that
stuff
right,
and
so
because
we're
doing
that
we're
getting
a
pretty
complete
view
of
whether
this
change
actually
messed
anything
up
for
any
other
component
within
this
distributed
system
or
whether
it's
actually
or
whether
it's
literally
just
a
change
in
docs,
and
we
can
look
from
the
code.
That
is
just
a
change
in
docs
right.
A
We
don't
need
to
actually
build
all
all
of
the
world
for
this,
but
as
an
example,
what
I'm
walking
you
through
here
is
kind
of
showing
you
what
it
looks
like
to
build
all
of
the
world
for
this
and
then
use
that
new
environment
to
prove
that
your
change
works.
So
say
you
were
making
a
change
to,
like.
A
I
don't
know,
you're,
making
a
change
to
that
rootless
configuration
that
we
talked
about
before
and
the
way
that
you
did
it
is,
you
had
to
add
a
particular
security
context
capability.
For
you
know,
system
bind
or
something
inside
of
the
api
server.
A
How
would
you
verify
that
the
the
change
you
made
to
the
manifest
for
the
static
pod
manifest
was
was
was
correct
like
how
could
you?
How
could
you
verify
that
and
that's
this
is
definitely
one
way
to
go
about
making
that
sort
of
a
change.
Another
example
of
a
change
like
this
was,
I
remember
there
was
a
bug
in
ipvs
and
somebody
patched
that
bug
and
they
were
showing
and
I
was
working
with,
and
I
was
showing
how
to
verify
that.
A
So,
if
you
wanted
to
kind
of
dig
more
into
like
that
use
case,
I
wrote
it
up
as
a
blog.
A
Using
kind
to
test
the
pr
for
kubernetes,
and
so
this
was
actually
showing
how
to
leverage
theorem,
gimme
and
this
whole
environment
to
go
ahead
and
do
the
source
of
testing
that
we're
doing
here,
live
inside
of
this
environment
and
exactly
why
to
change
and
how
to
check
out
the
code,
how
to
check
out
the
branch
and
how
to
verify
that
the
thing
works-
and
this
is
all
right
here.
The
same
thing
I'm
actually
covering
in
my
doc
is
all
right
here,
and
so
I'm
going
to
actually
go
ahead
and
put
this
into
this.
A
We're
at
the
top
of
the
hour,
so
I'm
going
to
shut
it
down
here
as
soon
as
this
build
is
done
and
we
show
that
it
works,
I'm
going
to
go
ahead
and
end
the
episode.
So
thank
you
both
for
signing
in.
I
hope
there
are
other
folks
out
there
if
you're
out
there
and
want
to
say
hello,
say
hello.
Give
me
a
wave
good
to
see
you
all,
and
I
look
forward
to
doing
this
again
in
two
weeks
and
we'll
do
more
kind
of
tips
like
this
and
kind
of
explore.
A
Different
things
like
this
going.
A
A
A
Built
yeah,
for
me,
I
mean
like
when
I,
if
I'm
doing
any
development
for
the
control
plane
or
any
of
that,
do
you
mean
like
do
you
mean
the
code
base
itself
like
if
you
were
going
to
modify
the
controller
manager
or
modify
the
api
server
that
kind
of
stuff,
or
did
you
mean
something
else?
I'm
curious
about
your
question.
A
A
Yeah
so
the
debug
test
cycle,
so
if
you're,
if
you
can
actually
you
know,
this
is
a
pretty
quick
loop
for
for
building
again
and
again,
if
you're
making
changes
to
code
and
you
want
to
prove
that
it
works.
Alternatively,
what
you
could
do
is
actually
I
have
seen
examples
of
folks
leveraging
other
tools
and,
in
fact,
there's
a
great
example
of
this
in
cluster
api
of
leveraging
other
tools
to
do
kind
of
a
faster
break.
A
Loop
fix
model
for
how
this
works,
but
in
this
particular
test,
if
you
know
what
you're
changing
and
you
want
to
actually
you
know
you've
made
it
past
your
unit
test
and
you're
ready
to
actually
like
validate
that
your
change
works.
This
is
one
way
to
go
and
because
it's
cube
adm,
you
can
actually
modify
quite
a
lot
about
this.
You
could
turn
on
debug.
You
can
turn
on
lots
of
different
stuff.
A
A
See
you
next
see
you
in
two
weeks.
I
hope
you
all
have
a
wonderful.