►
From YouTube: 20181017 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
Hello
today
is
October,
17th,
I,
think
2018.
This
is
the
cuvette
diem
office
hours.
Let's
walk
through
the
agenda
here.
I
saw
that
Luba
mayor
beats.
You
I
had
a
PR
about
merging
the
which
Prix
ARS
this
one
there's
been
several
PRS
around
the
phase
render
stuff
I.
Think
most
of
them
are.
The
initial
ones
have
been
merged.
I,
don't
know
if
I've
reviewed
this
one
yet
yeah.
B
A
B
Yeah,
the
parent
self
is
very
clear
and
the
next
agenda
topic
is
like
defining
the
list
of
faces
and
I
one
is
Fabrice
here.
Okay,
basically
I
wanted
us
to
discuss
like
here
the
faces
we
want
these
to
be
for
1:13,
and
we
want
this
to
be
the
solid
list
and
base
of
the
list
we
can
create.
We
already
have
a
tracking
issue.
We
can
create
some
check,
marks
and
assign.
A
A
A
Had
his
original
breakdown
I
didn't
see
anything
that
I
objected
to
some
of
the
naming.
I
think
is,
quite
you
know
questionable,
just
as
far
as
what
how
we
want
to
name
it
sub
commands,
as
we
you
know,
manage
this
in
the
future.
We
can
debate
some
of
that.
Most
of
the
other
ones
are
uncontroversial.
A
A
A
One
thing
that
I
don't
I
I,
don't
know
about
the
packaging
problem
and
how
much
we
are
going
to
manage
packaging
for
this
release
or
if
I
need
to
talk
with
DIMMs,
to
figure
out
what
the
state
is
of
pushing
packaging
into
a
better
at
home
and
location.
I
think
we
will
probably
still
have
the
release
repository
for
this
cycle,
because
it's
a
compressed
cycle.
A
C
D
On
the
packaging
side,
I
think
especially
the
LPM
packaging
side
of
things,
I
kind
of
hope
to
have
a
look
at
that.
But
my
time
is
really
emitted
over
the
next
three
weeks,
because
I'm
traveling
in
then
on
vacation.
So
it
will
only
be
then
where
I
can
really
sort
of
sit
down
start,
having
a
look
getting
a
feel
for
what
needs
to
be
done
there.
Okay,.
A
I
fully
expect
in
the
future,
to
4kk
to
be
the
canonical
packaging
to
actually
store
it
in
the
crib.
Rene
discriminates
repository
and
build
from
there.
That's
the
goal
in
the
hope.
I
do
have
some
issues
currently
with
how
we
sort
of
auto-generate
the
specs,
but
I
should
write
some
of
that
stuff
down
so
by
the
time
you're
ready
to
work
on
it
and
other
folks
are
ready
to
work
on
it.
You
know.
A
There's
you
know
a
long
time
ago,
if
you
look
at
the
relation
taury
there's
this
very
large,
complete
refactor
of
the
spec
file.
I
did
and
it
died
on
the
vine,
because
there
was
no
one
there
and
that
was
like
year
and
a
half
ago
yeah,
but
it's
a
major
overall
because
like
they
are
the
way
we
do
packaging
is
not
the
way
you
typically
do
packaging.
A
A
Not
just
like
force
the
function,
and
maybe
after
the
freeze,
which
is
in
November,
maybe
schedule
a
time
to
sit
down
and
talk
together.
Whoever
is
interested
on
this
call.
We
can
just
have
like
a
little
separate
breakout
session.
I
know
that
I
just
want
to
be
done
with
this
problem,
because
it's
not
it's
not
a
packaging
problem
per
se
as
much
as
it
is
a.
How
do
we
release
artifacts
from
the
from
kubernetes
communities.
C
A
A
F
A
A
B
So
I
opened
the
Google
Doc
for
the
phases
before
that
fabrizio
created.
Actually,
he
posted
an
old
list
about
the
phases
and
I
see
some
problems.
Minor
problems
here
like
in
terms
of
the
order,
but
putting
significance
so
I
like
corrected
the
issues
and
I
posted
him
posting
them
here
in
this
Google
Doc.
Now.
A
Don't
think
that
would
affect
that
well,
I,
guess
that
could
affect
some
ordering
you're
still
going
to
do
those
same
operations,
but
when
you
do
a
right
can
when
you
would
either
do
a
right,
configure,
writing
and
e-file.
That
would
add
extra
steps
so
part
of
that
conversation
that's
going
on
with
ordering,
but
could
be
done
within
those
separate
phases.
I,
don't
think
you
would
add
a
new
phase
or
change
anything
else.
Okay,.
G
B
A
B
B
A
That
is
generally
usable,
but
I,
don't
know
how
many
people
would
use
it
in
the
separate
components.
I
think
what
we
could
possibly
do
or
have
a
policy
for
is
it
seems
to
be
a
repeating
pattern
of.
We
could
hide
the
sub
phases
for
the
individual
sub
commands
and
expose
them
if
needed
over
time.
They'll
still
be
there,
and
users
still
should
have
the
as
long
as
the
users
have
the
ability
to
execute
some
hidden
sub
commands.
That
would
be
fine
right.
A
B
B
B
G
A
A
H
You
sure
do
but
like
I
prefer
to
like
I'm
just
trying
just
saying
in
basically
I
would
like
to
do
some
like
a
be
testing
like.
If
we
can
I
know.
We
know
that
time
is
of
the
essence,
but,
like
I,
don't
know
if
if
something
else
would
be
of
more
benefit,
if
we
can
just
try
two
different
versions
of
what
we
want
to
do
in
there
and
like
decide,
oh
yeah,
that's
pretty
elegant
or
no
that's
or
horrible,
whatever
I
just
well.
A
C
B
A
Yeah
we
can.
This
was
kind
of
added
in
to
do
enabling
that
that
could
actually
probably
be
kind
of
no
I,
don't
know
who
uses
it.
You
do
want
the
ability
to
set
some
of
those
things
up
on
the
beginning.
I
would
leave
it
underneath
alpha
as
a
potential
option
right
now,
there's
gonna
the
push
for
dynamic
web
hooks
for
auditing
is
still
ongoing
and
that's
the
ideal
scenario
where,
basically,
you
still
need
a
knob
that
you
turn
out
for
the
API
server
and
you
want
to
have
that
knob
exposed.
A
So
you
you
pass
it
in
as
part
of
your
initialization
that
says
yes,
I
want
dynamic
web
hook,
enabling
for
audit
enabled
and
then
a
person
an
administrator
can
then
do
an
API
call
directly
to
the
API
server
to
say
here's
my
web
hook
and
I.
You
know
here's
the
authentication,
everything
else
I
need
to
do.
I
do
that
and
now
auditing
is
hooked
up
to
basically
have
a
proxy.
B
A
G
G
A
Don't
think
it
should
be
an
explicit
phase.
I
think
it
would
be
like
in
because
it's
not
something
that
people
it
doesn't
make
any
sense
to
execute
it
independently.
It
would
be
part
of
the
feature.
Gated
items
are
basically
part
of
general
initialization
and
they're.
Not
they
may
they
roll
up
into
arguments
that
get
passed
into
the
API
server.
Okay,.
B
G
G
B
And
so
this
is
the
codes
in
here
we
should.
We
are
writing
the
manifest
okay,
I'm
gonna.
Add
this
other
node
here,
so
anything
about
the
control
plane
itself.
Apart
from
this
I,
don't
think
we
have
any
specific
here.
We
have
they
basically
just
scheduled,
and
this
this
should
be
exposed,
probably
as
a
like
non
hidden
faces.
I
agree.
B
A
With
some
of
the
certs
Jason
I,
don't
know
if
chuck
is
on
to
do
we
want
for
SED.
Do
we
want
to
have
a
is
the
is
the
certificate
generation
underneath
certs
for
the
NC
d
aspect,
because
we
just
said
that
that
all
the
streets
here
or
do
you
want
to
have
you
know
kuba
diem
and
it
ed
CD,
certs
or
some
other
thing
like
that?.
B
G
G
G
I
All
of
the
individual
certs
based
on,
like
you
know,
local
at
CB
versus
external
ICD,
we're
kind
of
clutching
that
logic
in
two
different
places.
But
at
the
same
time
it
is
kind
of
nice
to
have
just
kind
of
like
one
search
command
that
can
help
put
all
of
the
certs.
If
you're
gonna
use
some
somewhere
else
too
so
I
don't
know
there
are
pluses
and
minuses
to
both
I
think
it.
F
B
So
if
we
move
certs
under,
for
instance,
if
we
have
control
plane,
API
server,
if
we
move
the
third-generation
functional
under
the
API
server
like
we
have
to
add
another
sub
phase
of
the
sub
phase,
one
of
them
should
be
the
writing
of
the
manifest
file
and
the
other
one
should
be
the
generation
from
the
API
server.
So
this
one
should
have
a
couple
sub
changes
technically.
A
There
might
be
the
ability
now
that
we're
thinking
about
it
in
the
way
Fabricio
is
set
up.
The
internal
data
structure,
if
we
might
be
just
be
able
to
link,
leaves
of
the
tree
right.
There's
no
reason
like
you
can't
add
a
sub
command
to
two
separate
other
sub
commands.
We
did
this
in
sort
of
wait.
Yes,.
A
That
way,
it's
exposed
in
two
ways:
if
a
person,
if
a
user
wants
to
generate
all
the
search
that
could
just
do
certs
or
if
they
wanted
to
to
walk
the
component,
they
could
do
it
be
a
component.
I
I
don't
and
it's
just
going
to
execute
the
same
code,
but
it
just
links
to
two
different
locations
and
slaved
up
through
the
data
structure.
The
phase
Runner
just
as
a
another
link
right.
G
A
A
If
I'm
just
setting
up
an
individual
components,
I
would
almost
like
all
of
the
aspects
of
that
component
and
sub
commands
needed
for
me
to
configure
that
component
underneath
that
sub
command
right.
So
everything
relating
to
sed
should
be
underneath
that
CD,
everything
related
to
the
API
server
should
be
just
under
the
API
server.
And
if
we
add
that
linking
capability
there's
nothing
to
say
that
we
can't
have
our
cake
and
eat
it
too.
B
A
B
A
G
G
B
G
A
A
B
K
A
B
University
yeah,
okay,
so
mark
on
propane,
is
pretty
clear.
So
so
much
notes.
A
I'd
almost
wanted
hidden
I,
don't
think
people
should
be
explicitly
doing
that
because,
ideally,
that's
data
is
stored
directly
into
the
node
itself
and
not
as
annotation
on
the
node
right.
We
even
talked
about
this.
This
should
be
part
of
the
node
status
and
I
believe
and
toughen
had
mentioned
that
as
well.
So
I
think
the
having
that
that
should
be
hidden
right.
It's
still
there.
We
still
execute
it
right
now,
but
I
don't
think
we
should
be
exposing
that
to
the
user.
A
B
J
G
G
A
A
B
A
B
B
F
F
B
B
F
F
F
That's
what
I
think
I
think
we
might
it'd
be
good
if
we
had
some,
like
general
guidance
around
whether
these
commands
are
idempotent
or
not
like
it
would
be
good.
If
you
know
all
of
them
had
side
effects
or
all
of
them
noticed
if
they'd
been
run
twice
or
something
like
that,
just
to
make
it
more
accessible
and
to
understand.
A
We
have
a
separate
repo
now
to
move
this
thing.
I
don't
know
if
people
are
keeping
track
of
all
the
to-do
items.
I
think
it's
it's
not
that
important
right
now,
I
would
say,
but
there
is
a
separate
location
now
that
has
been
created
for
bootstrap
tokens
where
we
can
land
this,
this
utility
function,
there's
a
there's.
A
A
G
G
B
Okay,
Ahmad
and
Oh
Mike
at
the
end,
I
guess:
let's
go.
A
A
Yeah
I'll
get
rid
of
Allah
postie,
you
could
probably
there's
two
parts
of
our
back:
creating
or
updating
our
back
roads
for
rotating
certificate.
I
would
probably
lump
them
together.
I,
don't
know
anyone
that
would
use
this
other.
Do
I,
wouldn't
even
even
hide
it.
I
mean
like
what
user
is
gonna
care
about
this?
A
A
B
A
A
B
B
B
A
G
If
we
are,
if
I
got
it
right
from
the
discussion
of
you're,
saying
that,
basically,
all
the
details
of
booster
token
included,
Reebok
and
and
the
in
config
maps
are
not
useful
for
the
AR
are
not
useful
for
the
user.
So
why
don't
ever
only
a
unique
phrase?
That's
it
underneath
it
that
does
a
5
action.
It's
just,
but
I,
don't
see
in
either
the
utility
of
having
Eden
freezes
is
just
a
piece
of
code
that
does
a
far
ivar.
B
B
A
A
A
A
Exactly
so,
I
think
just
open
a
tracking
issue
for
the
long
term
to
set
the
milestone
to
114,
so
that
we
may
get
to
114
well
well,
will
reinvestigate
to
see
what
the
maturity
is.
But,
ideally,
you
know
in
the
long
term
I'd
like
to
get
us
out
of
the
management
of
the
addons
last
cycle
at
the
end
of
the
cycle.
The
add-ons
and
the
manifest
management
caused
a
lot
of
consternation.
B
A
B
K
G
G
A
G
B
A
G
A
G
D
A
A
G
A
No,
that
that's
fixed,
so
that
should
be
fixed
the
or
it
should
be
I
have
to
go
check
to
see
if
it's
all
done
done
now,
but
there
are
issues
there
like
three
different
issues
already
open
on
this.
We
should
just
link
all
of
them
and
and
just
double
check
that
the
current
work
that
Luca
has
pushed
actually
fixes.
This
problem,
I
have
not
had
a
chance
to
verify
that
yet.
Okay.