►
From YouTube: 20181121 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
B
Okay,
the
first
one
is
that
Lucas
and
Luke
Perkins
from
the
Sierra
started
working
on
both
post
for
Cuba
diem
going
to
GA.
This
book
post
is
going
to
be
published
on
the
3rd
of
December,
and
my
idea
was
to
announce
it
here
so
that
more
people
can
have
a
look
at
the
board
post.
I
think
that
is
pretty
good,
but
it
needs
more
work
and
I'm,
not
sure
if
we
should
look
at
it
right
now
in
the
meeting.
B
A
We
can
hold
I
think
we
can
actually
all
wait
until
next
week
to
actually
have
everyone
should
be
back
by
that
point,
and
then
we
can
all
discuss
what
we
want
to
do
with
the
blog
post,
then,
and
I'll
give
enough
time
for
folks
to
take
a
look
at
it
to
who
haven't
I'm,
actually
gonna
loop
in
some
marketing
folks,
because
they're
really
good
at
you
know,
hyping
it
up
a
bit
and
that
way
they
can.
You
know,
try
and
put
their
spin
doctor
head
on
and
make
it
sound
even
better.
B
A
And
I
think
too,
with
the
sessions
at
could
con,
we
can
try
to.
We
can
try
to
uplift
there
as
well
I.
Think,
there's,
there's
multiple
parts
of
uplift,
like
we
I'm,
pretty
sure
Hebdo
/
VMware
will
probably
coordinate
a
blog
post
or
will
get
our
marketing
folks
for
for
blogging.
You
know
if
the
Seuss
folks
want
to
blog
about
it
too.
You
know
more.
The
merrier
I
think
anybody
who's
contributed
has
been
part
of
this
to
help
sort
of
do
the
uplift
and
general
awareness
of
qadian
I
think
it
would
be
a
good
thing.
A
B
A
Like
actual
uplift
from
regular
channels,
not
from
like
just
developer,
here's
my
blog
post
and
how
it
works,
but
actually
marketing
uplift-
and
you
know
they
have
whole
plans
of
action
and
it's
a
whole
separate
career
field.
But
there's
there's
a
magic
there
there's
a
lot
of
magic
there.
They
do
a
lot
of
work
to
sort
of
make
sure
that
channels
align
and
how
to
get
massive
up
left
and
stuff.
So,
okay,.
C
B
Mean
of
course,
only
if
you
think
this
is
viable
for
Sue
say
but
I
think
it
is
given
you're
a
consumer
of
tbdm.
It's
probably
a
good
idea
to
share
it.
At
least
a
short
blog
post
about
hey
comedian
is
now
GA
and
we
are
a
consumer
and
we
also,
but
possibly
recommend
it
to
others.
If
you
think
it's
viable
for
you
to
make
such
a
post,
it's
gonna
be
great
yeah.
B
Yeah,
so
there
was
a
bit
of
a
drama
yesterday
about
reference
Docs,
but
I'm,
not
gonna,
explain
it
here.
Anyway,
we
have
a
tracking
issue.
We
have
a
list
of
pending,
PRS
I
have
applied
all
labels
to
them.
If
you
have
nuclear's,
please
apply
critical
origins
and
sequence
life
cycle
so
that
we
can
see
the
list
easier.
B
B
A
B
A
So
there's
two
major
sections
and
liz
has
traditionally
done
a
lot
of
the
upgrade
stuff.
So
if
you
actually
go
into
these
tasks,
it's
a
separate
administrative
coaster
and
then
we
have
the
administration
for
Koob
ADM.
So
we
do
two
parts.
Typically
we
deprecated
and
remove
the
old
version
and
we
have
the
upgrading
from
112
to
113.
So
that's
that's
the
one
piece
that
I
was
referring
to
because
usually
that's
kind
of
its
over
in
its
own
section.
It's
often
skipped
and
not
paid
attention
to
I.
B
B
A
B
A
A
D
D
A
F
A
That
we
specifically
well,
we
might
have
to
update
some
Docs,
but
we
pushed
most
of
that
into
what's.
It
called
it's
a
go
Docs
so
because
we
have
in
go
Docs
and
we
reference
it
and
point
to
the
application
that
has
always
been
the
canonical
reference
for
configuration
stuff.
So
that
way,
as
we
remember
time,
we
don't
have
to
do
this
multiple
invocation
and
revisions
in
the
main
documentation.
There
was
a
pain
before
so
we
moved
it
in
that
direction.
Look
my
Sickler
the
cycle
before
I
think
was
last
night.
Well,.
B
A
Might
want
to
run
through
the
troubleshooting
now,
especially
that
the
last
configuration
flag,
stuff
has
been
changed.
There's
been
like
some
old-school
weirdness
in
the
troubleshooting
doc.
I,
don't
know
who's
taking
point
on
that,
but
the
the
old-school
weirdness
was
the
proxy
flag
stuff
and
that
that
has
been
all
merged.
B
B
A
B
A
A
A
A
A
B
As
you
might
disagree
with
this,
but
we
know
we
are
now
are
doing
stable
one
only
instead
of
fixing
the
minor
as
part
of
the
default
version.
This
is
something
that
Alexander
proposed
at
some
point
and
it
shows
a
couple
of
problems
for
us.
The
docs
team
always
generates
like
a
wrong
reference
documentation
for
us,
because
they
we
waited
for
this
change
for
to
the
last
minute
and
they
generated
reference
Docs
with
the
wrongs
default
version,
and
the
other
problem
was
that
we
actually
cannot
merge
this
PR.
B
A
B
Also,
and
also
we
have
a
guard
that
the
guard
is
doing,
it
basically
checks.
If
that
we
don't
kill
too
much
so
by
fetching
stable
one.
You
can
potentially
fish
like
one
one.
Sixteen
and
you
can
be
still
on
one
fourteen,
so
we
motto
all
that
and
we
we
only
evolve.
The
same
version
like
it
falls,
falls
back
to
the
mission
of
the
client.
Basically,
yes,.
A
So
I
would
double
check
the
logic
there
I,
both
Alexander
myself
in
little
mirror,
went
through
it
and
it
worked
fine
for
the
112
release
cycle
and
it's
been
continuing
to
work.
Fine
I
actually
did
start
up
the
end
at
111.
Let
me
edit
that
I
don't
know
it
was
a
while
ago,
but
I'm
not
concerned
about
that
one
anywhere.
Okay,.
A
We
don't
because
we're
tracking
the
milestone,
so
if
you
actually
look
at
the
milestone
currently,
the
milestone
should
be
correct.
Okay,
so
anything
that's
inside
of
there
should
only
be
docks
at
this
point.
There
was
some
minor
stuff,
but
anything,
that's
not
in
the
milestone,
docks,
I.
G
A
A
Most
of
these
other
ones,
there's
only
two
I
think
that's
that's
a
documentation.
This
is
the
only
one
which
I
actually
I,
think
I
poked
for
me
chillin,
I
said:
should
we
close
this
I?
Don't
think
suggesting
more.
Can
you
verify
I
think
was
just
waiting
for
it
for
feedback
from
in,
so
everything
should
be
in
the
milestone.
We've
been
using
the
milestones
since
the
trackers.
D
A
A
D
A
A
B
A
D
B
It's
it's
doing
a
workaround
for
the
way
we
handle
our
couplet
keep
config.
So,
according
to
Clayton
and
Jordan
they're
saying
that
we
are
giving
the
disc
cube
config
too
much
power
and
they
have
to
do
a
workaround
because
of
and
Fabrice
also
commented
there
so
I'm,
not
sure
if
we
should
reconsider
what
we
are
doing.
But
at
least
we
have
a
workaround
for
us
in
the
corporate
now
and
it's
going
to
be
merged
in
114
yeah.
A
A
Honestly,
like
it
was
I,
was
now
I
was
blindsided
by
it.
It
went
in
without
me
knowing
that
it
was
gonna
go
in
like
it
broke
it
broke
on
the
beta
and
I
had
no
insight
into
this
PR
being
merged,
so
like
all
I
did
was
track
down
that
this
was
the
cause
of
the
issue
and
then
I
went
on
pto
and
I
said.
Please
revert
this
and
then,
when
they
said,
here's
a
new
PR
I
said
please
hold
inside
114.
So
we
have
baked
time
because
this
broke
everybody
there.
B
A
D
A
There
is
a
separate
issue
that
we
had
that
we
did
not
get
to
this
cycle
at
all,
which
is
that
it
is
wildly
inconsistent
with
how
we
deal
with
command
line
flags,
slash
configuration
options
and
overrides,
and
we
need
to
gran
unified
field
theory
and
I
think
this
crosses
over
with
component
config
to
as
well.
Alright,
so
I
would
I'm
glad
I'm
totally
fine
with
punting
in
this
until
we
actually
address
component
config
and
all
their
things
together
at
once.
In
the
meantime,
it'll
be
in
this
weird
state
for
some
things
and
I'm.
B
E
A
Key
consumers
that
are
very
active
in
our
community
who
chime
up
every
time,
there's
a
release
and
tell
us
how
how
much
we
need
to
fix
this
problem.
Four
sets
of
problems,
so
we
got.
We
got
some
of
those
issues
done,
but
the
the
grand
unified
field
theory
for
configuration
option,
itis
OSIS-
is
still
a
TBD
yeah.
A
D
A
A
So
I
don't
want
to
take
up
too
much
time
today,
because
I
know
a
lot
of
people
are
out
I'm
supposed
to
be
a
PTO
and
I'm
sure.
This
is
shaking
your
fist
at
me
for
even
being
here,
but
are
there
any
other
topics
specifically
for
113.
G
G
G
D
A
D
So,
just
mentioning
quickly
what
happens
next
I
would
like
to
write
up
so
like
the
burning
down
the
docks
things
that
kind
of
sinking
with
release
team,
obviously
in
getting
getting
the
the
release
out,
but
meanwhile
enough
to
bat
or
like
before
that
also
the
Cuban
energy,
a
blog
post.
Those
are
the
high
critical
things
right
after
that
I'd
like
us
to
yes
start
planning
for
114,
but
especially,
we
should
review
the
roadmap
that
we
wrote
in
in
last
December.
D
G
D
D
A
D
D
A
The
problem
is
some
of
my
approval:
ackles
have
been
revoked
just
because
I
haven't
been
active
in
other
areas,
so
so
sad
clown,
I,
don't
have
super
user.
I
can
I
have
overriding
superuser
privileges.
I
should
not
abuse
I
only
abused
it
when,
like
we
touch
doc
stuff
and
then
I'm,
like
whatever
yeah.
A
D
So
what
would
be
great
is
that,
for
example,
if
you
make
the
staging
repo,
for
example,
if
we
could
get
a
few
reviewers
from
here
or
like
hand
you
in
that
list
of
approvals,
then,
for
example
I
don't
know
myself
and
then
Stefan
is,
is
currently
or
are
currently
driving
trying
to
drive
the
cap,
but
well
we'll
see
how
it
goes,
but
overall
it
needs
some
discussion.
So
so,
let's
plan
in
that
for
for
future
meetings.
Yes,.
A
D
Right
right,
it
doesn't,
is
it,
but
it's
gonna
affect
us.
You
know
many
ways
and
I
get
really
excited.
When
I
started.
Looking
at
all
the
things
we
can
remove
from
queue
better
because,
basically
as
we've,
so
we
will
implement
the
components
config
in
two
places:
queue
button,
cubelet,
cubelets
and
cubed
em,
and
in
both
places
we
have
a
lot
of
code
that
is
totally
generic,
so
that
could
be
written
in
a
total
generic
way.
But
it's
super
specific
to
that
specific
application.
So,
yes,
rid.