►
From YouTube: 20190213 kubeadm office hours
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
A
B
B
B
B
So
we
have
a
few
things
that
are
left
that
we
need
so
I'm
going
to
be
working
on
a
kept
for
for
this
this
week.
Some
of
the
things
that
we
need
to
figure
out
is
some
of
the
yeah
Mille.
We
don't
have
quite
exactly
how
we're
going
to
do
everything
in
the
amel
in
a
same
way,
so
we're
going
to
need
to
work
on
building
an
example
amel
and
how
that
might
look
and
how
that
might
support
all
the
features
that
we
need
to
do
with
this
example
is
like
with
rpm
dependencies.
B
B
B
B
No
I
don't
think
so
anyways.
So
that's
pretty
much
where
we
are
I'll
be
working
on
the
cap
to
condense.
All
of
this
other
things
that
we
need
to
think
about
are
actually
compiling
the
code.
Everything
that
I've
done
so
far
is
just
taking
the
binaries,
so
it
doesn't
actually
compile
the
code.
It
just
gets
the
binaries
and.
B
So
if
anybody
wants
to
look
into
any
of
these
things,
that
would
actually
be
really
awesome,
because
I'm
gonna
be
trying
to
work
on
the
cap,
and
some
of
these
things
will
need
to
explained
in
the
cap,
probably
for
a
well-formed
cap
as
well
as
some
of
the
research
into
how
we'll
support
some
of
these
functions
in
the
amel
yeah.
So
if
somebody
has
some
ideas
and
we'd
really
like
to
jump
in
on
this,
they
can
contact
me
I
would
love
some
help.
A
This
is
pretty
important,
though
the
one
terminus
of
this
thing,
we'll
all
set
to
sync
with
haniss
about
the
other
side
of
this
puzzle
that
we
talked
about,
which
is
the
release
process
generating
the
packages,
is
one
aspect,
but
actually
getting
this
into
a
well-defined
release
process
and
handing
it
off
to
the
release.
Team
is
another
piece
that
needs
to
be
solved
as
well
as
all
that
removing
all
of
the
existing
tech
dead
stuff
so
Hennis
wants
to
meet.
Sometime
soon.
A
A
So
we'll
have
to
do
that
work,
and
then
we
can
update
again
I.
Don't
given
the
time
horizon
for
some
of
this
stuff,
we
might
be
a
little
hard
pressed
to
flip
the
switch
every
removing
the
old
packages,
but
we
can
probably
get
to
the
point
where
we
actually
have
the
new
packages
being
generated
so
I'm.
Okay
with
that
in
the
mainline-
and
you
know,
and
then
in
the
distant
is
115
flips,
we
could
possibly
do
the
shuffle
the
packaging
and
then
start
the
release
process
cap
as
soon
as
115
gets
opened
up.
B
A
C
A
E
We
well,
it's
not
finished
only
once
it's
finished
only
then
we
can
have
and
we
have
to
modify
kind
again
because
currently
Fabrizio
implemented
it
with
the
menu
way
of
copying
cert,
and
we
don't
have
a
test
path
for
this
scenario.
But
so
we
have
to
it's
under
question,
I'm,
not
sure
if
Ben
is
going
to
accept
more
pls
for
this.
E
E
C
C
E
A
E
E
A
Sounds
good
to
me:
I
think
we're
just
simplifying
the
process
and
will
have
a
will
have
a
better
testing
story.
We
keep
getting
there
incrementally
and
we'll
be
able
to
actually
be
execute
and
have
a
full-fledged
intent
test
specifically
for
committee
and
proper,
we
have
the
suite
ready
to
go.
We
just
need
to
add
the
test
and
set
the
jittery
for
that
specific
deployment.
E
We
have
a
peer
from
Rohit,
I
I
cannot
pronounce
his
name,
we
kind
of
blocked
on
this,
because
we
all
decided
what
to
do.
It
appear
and
we're
hopefully
going
to
finish
this
by
the
end
of
this
week,
and
this
is
the
final
phase
and
the
joy
phases
phases
should
be
complete,
and
at
that
point
we
should
do
some.
How
do
you
think
I
guess.
E
We
found
a
book
in
Cobra
with
Rafael
that
basically,
the
joint
command
line
now
so
now
the
joint
command
line
with
the
extra
32-bit
byte
key
that
we
have
to
add
with
you
know,
with
the
opposed
certificates.
Functionality
is
going
to
be
super
quarter
it
with
information
and
we
might
have
to
like
revisit
the
whole
situation
with
the
unnamed
flags.
F
E
E
H
A
A
Are
there,
those
are
the
major
deliverables
that
we
wanted
to
hit,
am
I
missing
any
other
major
deliverables
that
we
wanted
to
hit
for
this
cycle.
A
boat
I
think
these
these
two
I
think
the
test
automation
work
to
that
you
you've
done
little
mirror
is
also
one
of
the
major
milestones,
major
things
we
want
to
hit
this
cycle.
It's.
E
A
E
A
C
So
in
the
original
proposal
we
were
saying
if
you
want
to
pass
your
key,
you
have
to
use
the
config,
but
we
decided
to
pull
to
move
out
of
the
rod.
Are
the
change
of
the
coffin
fee
for
this
cycle,
and
now
I
can
level
like
custard
API
had
some
problem
in
capturing
the
generated
configure.
So
we
have
to
decide
if
we
want
to
add
a
flag
for
passing
the
key
in
it.
A
I,
don't
think
it's
a
when
we
originally
talked
about
this
particular
flag
or
option.
We
considered
it
a
not
nice
to
have
right
like
it
would
be
a
good
thing
to
have,
but
for
the
primary
use
case
for
most
people
burned
on
you
know
just
getting
things
started.
We
auto-generating
the
certificates
seemed
like
a
reasonable
math
words.
We
you
know
for
production
grade
environments,
then
they
would
definitely
have
their
own.
So
it
passed
me
over
your
requirement.
G
I
A
I
E
B
J
E
Related
to
the
diff
library
we
had
so
I
call
source
or
another
another
ticket.
We
had
about
inconsistency.
The
default
in
the
default
put
for
Cuba
diem
up
great,
and
we
have
a
bit
of
a
situation
because
because
we
cannot
back
for
this
patch
to
other
to
all
the
releases
in
a
sense,
it's
a
critical
things
become,
but
we
actually
updating
my
whole
dependency
mentor
dependency.
So
Tim
have
you
seen
like
instances
of
this
being
done,
like
backporting,
copper
and
other
older
businesses.
Typically.
A
A
Because
it's
been
broke
because
it's
not
a
regressive
like
you,
don't
need
to
back
port
things.
It's
nice
to
back
port
fixes.
Backporting
dependencies
is
usually
not
done
you
you
do
need
to
back
port
security
things
in
regressions,
but
there's
always
bugs
in
the
code.
We
release.
You
can't
back
part
everything
otherwise
progress.
A
You
make
it
it's
okay
to
punt
on
this
to
this
cycle
and
just
mark
it
as
done
to
release
this
cycle
and
make
sure
that
it's
in
the
release,
notes
which
it
is
I,
don't
think
we
need
to
back
port
it
because
you're
going
to
get
about
a
lot
of
resistance,
trying
to
get
the
vendor
Tennessee
back
ported
into
a
previous
cycle.
Unless
it's
a
critical
bug
fix
and
it's
not
necessarily
critical,
there's
work
rooms
for
a
lot
of
this
stuff
for
the
committee
and
if
stuff
you
could
just
generate
into
your
own
hand.
A
E
A
E
H
H
E
A
A
H
C
A
A
D
A
A
E
We
are
already
storing
the
the
certificates
on
disk,
so
it's
usually
easier
to
read
them
from
disk
instead
of
the
process.
Memory,
but
I
agree
that
it's
it
increases.
It
increases
the
security
risks
to
something
like
that,
because
we
are
keeping
them
from
for
the
lifespan
of
the
process.
So
the
old
method
is
technically
more
secure
in
terms
of
the
process:
lifespan,
yeah.
A
E
Yeah,
well,
we
could
I
guess
we
could
close
this
the
original
to
do
yeah.
We
can
remove
the
original
traduce
because
they
are
misleading.
We
shouldn't
probably
do
this
in
terms
of
security
and
it
will
suspect
to
evict
the
inspector
or
exploits
and
branch
prediction.
I
was
able
to
own
myself,
so
it
definitely
works.
E
A
A
A
A
So
the
a
lot
of
the
things
that
we
originally
had
on
this
list
are
no
longer
there
and
we
have
ones
that
have
been
around
for
a
long
time,
but
we
haven't
actually
made
traction
on
some
of
them,
so
like
one
one
of
the
ones
I
want
to
call
out
here,
in
particular,
is
that
we've
had
the
quote-unquote
graduate
police
director
opens
to
GA
on
our
cycle
for
many
many
cycles.
This
is
a
this
would
require
lifting
and
changing
of
the
config,
as
well
as
communicating
with
API
machinery,
but
I'm
gonna
be
honest.
A
Even
though
I've
been
on
this
list.
I
know
what
needs
to
get
done.
I
will
probably
not
have
time
to
do
it.
So
if
there
are
other
folks
that
want
to
step
up
here
and
to
do
a
long
standing,
cleanup
site,
refactor
work,
that
is
it's
not
easy.
So
you
have
to
have
experienced
both
the
API
machinery
and
to
convey
I.
E
A
This
seems,
like
user
error,
I'll
need
to
verify
that
one
configure
secure
serving
yes,
this
is
a
good
one.
I
know
that
I
believe
we
have
PRS
against
this,
but
we
have
some
issues.
They
didn't
actually
finish.
It
configure
secure
serving
for
controller
manager
and
schedule
error.
We
don't
actually
do
this
yet
today
we
actually
have
a
bunch
of
security
issues
that
are
kind
of
dropped
on
the
floor
right
now,
because
this
will
be
out
for
several
months.
If
there's
any
person
who
loves
security
and
must
get
involved.
C
A
A
A
A
A
E
A
D
A
E
A
A
E
Yeah,
so
we're
consuming
a
module.
I
could
check
that
somebody
implemented
in
the
underlying
check
for
a
previous
is
kind
of
confusing,
because
on
linux
is
not
so
easy
to
detect.
What
is
the
module?
Enable
is
the
module
audit
and
something
like
that.
I,
don't
remember
the
exact
details,
but
this
is
like
kind
ecosystem.
A
E
K
A
E
Also,
the
problem
there
is
that
every
single
distro
has
specific
query
surrounding
the
kernel
config
and
the
path
where
the
config
is
stored
after
the
user
installs
the
district.
So
we
oftentimes
get
a
new
PR
that
basically
includes
a
new
path
as
part
of
the
verification
process,
but
it's
a
lot
of
fun.
A
E
A
A
A
A
F
I
F
A
A
E
E
E
E
So
fabricated,
this,
because
we
want
to
link
correctly
between
a
correctly
to
specific
versions
of
go
doc.
Currently,
everything
is
bound
to
master.
That
was
a
problem,
but
this
is
definitely
help
wanted.
If
somebody
wants
to
take
a
look
at
this,
at
the
same
time,
we,
like
the
group,
don't
really
have
the
time
for
his
sole
comported.
A
E
Yes,
the
problem
is
like
the:
if
you
go
to
website
K
website
and
in
the
old
branch
in
the
docs,
you
can
click
a
link,
and
this
this
is
going
to
link
to
the
master
branch.
Basically,
because
go
dogs
always
fish
the
master
branch
and
in
the
master
branch
we
already
deleted,
like
those
versions
of
the
config.
A
I,
don't
think
this
is
gonna,
be
much
of
a
problem
going
forwards
because
we're
gonna
have
to
support
the
version
across
release
cycles
and
because
we
only
support
3,
those
things
should
be
live
for
the
most
part.
There
could
be
a
window
of
opportunity
where
it
won't
be,
but
when
we
were
changing
alphas,
that
was
a
problem
there,
having
climbed
to
close
this,
unless
someone
else
actually
reports
the
issue
itself.
Yes,
this
one
from.
E
E
So
in
terms
of
certificates
or
additions,
by
the
way
we
don't
have
any
good
dogs.
So
this
added
some
basic
documentation,
but
people
want
more
detail
and
maybe
the
next
meeting
we
can
discuss
but
including
the
rotation
documentation,
because
people
don't
know
how
to
do
it
and
they
could
go
about
it.
A
Okay,
we
can.
We
can
leave
this
one
to
open
this
Help
Wanted
for
this
cycle.
I
fix
to
jump
on
it,
I
think
we're
kind
of
at
time
now,
but
we
still
have
a
couple
more
to
go
through.
Do
you
want
it
tomorrow?
We
were
tentatively
planning
to
finish
off
the
the
backlog
grooming
by
tomorrow.
So
folks
wanted
to
join
same
bat-time
same
bat-channel,
then
we'll
finish
off
and
get
114
nail
down.
Okay,.