►
From YouTube: 20190306 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
March
6
2019.
This
is
the
standard
kopitiam
office
hours
and
we
have
a
pretty
short
agenda
for
today,
so
we'll
try
and
keep
it
short
and
sweet.
Try
to
be
respectful
everybody
else's
time.
If
you
have
other
topics
that
you
want
to
discuss,
please
add
them
to
the
bottom
of
the
agenda:
we'll
try
to
roll
through
it
for
those
who
are
not
in
the
know.
This
is
a
code
freeze
week.
So
we
are.
A
That
should
be
the
primary
objective
for
us
as
a
group
for
us
to
get
those
work
items
done
for
the
priorities
that
we
laid
out
in
the
beginning
of
the
cycle.
So,
as
you
can
see
in
the
duct,
the
priorities
are
primarily
around
eh-eh
and
joint
phases.
But
let's
start
going
through
the
agenda.
First
up,
David
Tate's
marshalling
yeah.
B
Daniel
yeah
I
just
wanted
to
this.
Oh,
this
is
not
that's
not
priority
for
for
the
release.
I
just
want
to
get
eyes
on
this.
The
couple
of
people
looking
at
the
the
issue
a
set
of
your
worth,
bringing
up
here
it
it's
basically
the
there's
a
the
way
so
there's
an
omit
empty
tag
on
on
the
paint
field
in
in
the
node
registration
API
and
having
that
omit
empty,
prevents,
marshaling,
a
different
sort
of
marshalling
a
different
value.
B
If
it's
an
empty
slice
versus
when
it's
a
mil
slice,
an
empty
slice
means
you
know
there
should
be
no
taint
or
arm
sight.
The
yeah,
an
empty
place
means
that
there
should
be
no
taint
and
enough
light
means
so
I
I,
don't
I,
don't
care,
let's
tube
ATM
decide
and
the
the
question
that's
being
discussed,
and
the
issue
is
whether
removing
that
tag
is,
you
know,
violates
the
you
know.
A
B
Suppose
that
I'm,
using
coop,
ADM
and
I
want
to
so
I'm
using
prove
idiom
types
and
I
am
marshalling
a
a
config
to
to
disk
to
then
to
pass
through
video,
okay
and
I
would
like
the
I
would
like
Kobe
diem
to
bring
up
a
control
plane.
You
know
a
control,
plane,
node
and
not
apply
the
the
master,
no
schedule
paint
to
it
to
begin
with
right.
That's
that
that's
I
mean
that's
part
of
the
that's
part
of
the
config
right.
B
A
That's
reasonable
again:
we're
not
gonna
give
to
it
this
cycle,
but
I
think
it
seems
like
a
total,
reasonable
thing
and
as
we
batch
stuff
for
API
modifications
in
the
V
1
beta
1,
/,
1
15
ish
time
frame,
it
seems
like
a
potential
there.
It
has
anything
I
changed
this.
Is
there
a
potential
one
that
you
can
add
to
your
your
list?
Ross,
unless
you
have
already
having
on
your
list.
A
Guys
are
a
top
of
your
game
way
to
go
so
we'll
probably
talk
about
this
Daniel
in
the
115
time
frame
and
we're
gonna,
probably
batch
up
all
the
API
changes
for
for
115
Nov
1
beta
1
funk.
So
if
you
have
other
changes
or
if
you
as
users,
you
know
spread
the
word.
If
you
have
users
who
are
using
the
configuration
apparatus
and
knee
changes,
115
is
the
place
to
do
it
in,
because
what
we
probably
going
to
do
is
is
match
a
bunch
of
changes,
get
them
into
1.
A
A
E
A
F
A
This
one's
already
done
so
in
merge
queue,
other
ones
already
merged.
Is
there
anything
else?
That's
critical.
That
folks
are
aware
of
that.
We
want
to
get
in
for
115,
or
are
we
kind
of
pretty
much
good
because
it
looks
like
those
are
the
two
primaries.
The
premiere
looks
like
you're
on
top
of
both
I.
G
G
A
G
A
G
G
E
G
G
Basically,
the
idea
is
to
copy/paste
the
old
stuff
change
the
versions
and
also
possibly
verify
if
something
has
changed
and
add
this
as
extra
sentence
here
and
there
and
also
verify
the
whole
setup.
That's
part
of
the
documenting
part.
If
you
have
troubles
with
the
verification
part,
that's
a
problem,
so
I
guess
we
can
help,
but
the
idea
is
that
you
can
send
the
Box
PR
first
make
the
version
changes
and
then
maybe
I
can
help
with
the
testing
part
or
fabrizio
or
someone
else.
A
G
I
mean
there's,
it
feels
like
there
is
technical
depth
in
there
as
well.
I,
don't
know
we
I
guess
we
just
should
just
watch
when
the
first
draft
games
out
comes
out.
Okay
and
I
don't
have
any
details
on
the
nose
yet
I
know
that
we
still
are
not
solving
the
problem
with
the
external
dependencies,
but
the
good
thing
is
the
dis
cycle.
The
release
team
are
going
to
do
it
instead
of
me
deems
in
Jordan
legit
yeah.
G
A
A
A
On
dogs
sounds
good,
I
know
that
you
know
if
we,
if
there
are
other
people
who
are
looking
for
that
week,
time
frame
between
planning,
we
do
have
a
tremendous
amount
of
other
Doc's.
That
kind
of
fall
underneath
our
umbrella,
that
we
should
probably
deprecated
and
deleting
that
stuff
might
not
be
a
bad
idea,
because
it
generally
causes
confusion.
A
G
We
should
probably
go
over
them
with
you.
Tim
I
should
participate,
because
I
noticed
that
a
large
fire
portion
of
the
setup
folder
in
the
in
the
docks
is
quote
called
specific
stuff
and
also
I
saw
that
I
saw
that
the
seek
the
chair
of
the
squad
provider
wanted
ownership
of
this
folder
as
well.
Well,.
A
G
A
A
H
Yes,
so
for
this
one,
these
about
integration
tests
for
how
the
copy
and
the
copy
of
the
secrets,
418
and
I
just
wanted
to
to
tell
you
that
I'm,
a
stirring
up
request
for
this.
This
is
about
the
integration,
not
end-to-end
tests.
This
is
something
that
we
should
also
include
at
some
point,
since
this
experimental
I
don't
think
this
is
very,
very
pressing,
but
I
would
like
to
have
this
as
soon
as
possible.
So
I
will
open
up
a
request.
I,
don't
know,
maybe
this
week
to
to
include
that
as
well.
This
is
a
run.
H
So
basically,
this
is
very
similar
to
what
the
mark
control
plane
in
tourism
test
are
doing.
So
it's
basically
mimic
in
a
very,
very
simple,
ap
server,
very,
very
simple,
and
basically
what
I
am
going
to
do
is
to
check
that
the
upload
actually
creates
the
secret
with
the
contents
with
the
encrypted
contents.
That's
for
the
upload
part
or
the
download
part
I'm
going
to
assume
that
there
is
secrets.
Are
there
and
then
I'm
going
to
check
that
the
certificates
and
the
keys
are
written
into
the
temporary
directory
with
the
right
permissions.
A
Because
I
would
rather
see
that
built
as
there
is
a
separate
test
suite
for
cubanÃa
man,
ten
tests
and
in
the
115
time
frame,
because
what
that
I
don't
think
we're
gonna
be
able
to
land
that
or
want
to
land
that
for
114
in
the
115
time
frame,
we
should
have
there's
a
broader
set
of
tests.
We
need
to
enable
in
order
to
push
H
a
to
GA
and
those
are
all
behavioral
intense
week
tests.
A
G
So,
just
to
talk
about
the
integration
test,
a
little
there's
something
wrong
in
the
way
we
do
parallel
testing
in
the
kubernetes
repository.
So
if
you
set
up
up
elementary
API
server
and
another
test
is
doing
the
same,
this
can
cause
problems,
because
the
way
goal
is
doing
this
it.
The
endpoint
of
the
API
server
you're
going
to
use,
may
be
already
used
by
analysis
that
is
running
in
parallel
and
we
had
a
problem
with
that.
G
Before
one
of
the
tests
I
wrote,
it
was
perfectly
well
concurrent,
but
something
else
was
conflated
with
the
basically
the
path
I
was
already
using.
So
I
think
we
should
like
the
suggestion
that
Tim
is
making
to
move
this
to
the
end-to-end
framework
is
a
better
idea
and
also
we
Mir
fabrics
are
going
to
add
support
for
who
end-to-end
testing
for
this
eventually
yeah
good,
yeah
I.
Think
it's
a
we
shouldn't
date.
The
simple
API
server
idea,
I
mean
to
elementary,
not
a
simple.
G
H
A
One
of
the
things
we
need
to
do
for
1:15
and,
if
you're
already
starting
down
this
road,
it's
probably
a
good
idea
is
inside
of
the
tracking
issue.
There's
a
breakdown
of
some
of
the
intent
tests
cases
we
need
to
verify.
You
know
such
as
copying
out
the
config
and
making
sure
it's
encrypted,
there's
a
bunch
of
tests.
We
need
to
do
right,
but
if
we
want
to
have
a
separate
tracking
issue
for
just
the
suite
of
tests,
you
know
that
relates
to
this
broader
issue,
the
location
for
this
specific
suite
has
already
been
created.
A
G
G
A
H
H
A
G
G
I
was
thinking
the
same
dashboard
for
now,
but
maybe
later
we
are
going
to
have
to
maybe
have
HD
upgrade
sets
up,
so
it
makes
sense
to
be
a
separate
dashboard
as
well
I
already
dumped
like
the
kind
job
string
here.
Oh
it
looks
like
we
have
a
breakage
I
know,
sorry
so
I
don't
know.
Maybe
I
should
make
a
new
dashboard
for
kind
specifically.