►
From YouTube: Kubernetes 1.12 Release Team Meeting 20180813
Description
A
A
A
All
right,
I
think
we
have
good
critical
mass
and
it's
to
past
the
hour,
so
I
am
going
to
get
started.
As
always,
we've
got
the
the
standard
location
for
the
meeting
minutes.
If
you
could
drop
your
name
in
there
on
attendance,
I
would
appreciate
it
and
then
keep
in
mind
that
we
are
recording
this
and
it
just
posted
to
YouTube
for
posterity
and
all
of
the
world
to
see
so
behave
accordingly.
I
know
you
all
do
and
well
so
usual
standing
at
agenda
really
at
this
point,
I
want
to
start
out
with
features
again.
A
We've
got
Steven
this
week.
Last
week,
I
spent
quite
a
bit
of
time,
starting
to
read
through
I
mean
across
that
set
of
66
or
so
features.
There
is
a
ton
of
information,
there's
a
few
things
in
there.
Maybe
that
I
feel
are
a
little
worrying,
but
I
want
to
see
what
the
the
features
team,
if
there's
anything
that
you
have
thoughts
on
the
you
wanna
share
there.
B
Yeah,
so
yes,
the
features
are
kind
of
daunting.
At
this
point,
we've
got
a
few
features
that
are
currently
quote-unquote
at
risk,
which
means
they
don't
have
the
required
information
but
I'm
kind
of
giving
them
a
pass,
because
they
said
they
were
going
to
get
the
information
so
I'm
doing
a
kind
of
like
a
set
of
follow.
Ups
right
now
there
are
a
few
features
that
are
kind
of
like
we're.
I
guess
new
to
the
process
of
dealing
with
feature
like
that,
so
core
DNS
becoming
the
default
thread
would
be
one
example.
B
C
B
That
is
still
a
pending
question,
so
there
there
are
a
few
like
weird
ones
in
here
that
I'm
that
I'm
still
trying
to
track
down
I
didn't
have
as
much
time
yesterday,
not
yesterday
that
last
week
kind
of
on
a
customer
does
it,
but
I'm
gonna.
A
A
E
B
Totally
so
for
an
initial
pass,
basically,
everything
up
to
future
freeze
I,
try
to
make
sure
that
it
is
well
described,
has
the
proposal,
and
essentially
all
of
the
docs.
If
it's
graduating
I
said
all
the
doc
statuses
to
needs
of
it.
If
it's
coming
in
as
new
I
say,
the
stocks
are
required,
the
test,
usually
we
don't
have
a
good
shape
of
what
that
should
look
until
people
can
accept
what
the
features
are
going
to
be
so
I
haven't
looked
at
tests
specifically
this
flat.
A
From
my
perspective,
I've
been
trying
to
go
through
to
just
understand
so
I
mean
someone.
Some
are
easy,
like
the
switch
default
DNS
plug
into
core
DNS,
like
you,
can
read
that
and
kind
of
understand
what
it
is.
A
number
of
the
other
ones
are
maybe
not
as
clear,
especially
if
you
don't
have
the
domain
knowledge
within
this
thing.
D
A
Been
trying
to
invest
the
time
to
go
in
and
and
at
least
have
a
mental
map
of.
What's
what
and
then
I've
been
attending
the
sig
meetings
as
well,
where
so
like,
if
you
sort
the
spreadsheet
by
sig,
it's
easier
than
to
say,
okay,
like
this
sig,
has
these
six
things
I'm
gonna
pop
in
to
the
meeting
and
have
a
pulse
of
where
they
are
and
and
what
the
what
the
outlook
is
kind
of.
A
Looking
like
it's
it's
still
early,
some
of
these
things
are
are
just
really
getting
moving,
haven't,
seen
code
associated
with
them
yet,
but
then,
at
the
same
time
we're
down
to
it's
a
30
something
days
to
the
release.
You
know,
since
master
branch
opened,
it's
been
about
60
and
we've
got
about
30
remaining,
so
I'm
kind
of
wanting
to
see
things
getting
a
little
more
concrete
at
this
point.
Otherwise,
sometime
fairly
soon
we
kind
of
start
transitioning
into
a
phase
where
I'm
thinking
we
were
kind
of
raising
the
flag
with
the
sig
saying:
hey?
A
Is
this
really
on
track?
Because
we
don't
want
to
create
a
whole
bunch
of
extra
team
team
work
here,
where
we're
tracking
and
trying
to
push
for
for
whether
it
stock
updates
or
tests
or
just
understanding
the
state
and
health
of
things
that
have
been
where
this
thing's
either
just
clearly
not
on
track
or
is
explicitly
internally
decided
that
they're
not
going
forward.
So
then,
because
the
process
is
a
little
kind
of
ad-hoc
on
on
collection
of
features
and
tracking
of
status
and
and
with
the
milestone
manager,
now
turned
off.
E
A
Were
a
couple
where
I
wondered
initially:
if
there
was
a
interconnecting
route
since
I
hadn't
seen
it
I
was
going
to
ask,
but
then
once
I
got
a
little
more
understanding.
I
realized
that
no
there
wasn't
so
I
personally
haven't
seen
ones,
but
if
anybody
else
is
going
through
and
feels
like
hey
does
this
impact
cig
foo
his
xigbar
talked
to
cig
foo,
not
seeing
artifact,
so
that
raised
it?
A
F
Tim
asked
a
question
about
us,
of
course:
okay,
so
Jen
Rondo
brought
up
to
me.
She
said
that
she
had
heard
some
buzz
around,
seek
release
or
other
things
about
a
move
from
the
default
container,
runtime
interface
being
docker
to
container
D.
Had
anybody
else
heard
anything
about
that
I
did
look
through
the
feature.
Tracking
sheet
saw
nothing
about
it
and
didn't
know.
If
anybody
had.
B
I
haven't
personally
seen
that
I
can
I
can
say
from
the
Red
Hat
perspective,
at
least
yeah,
that
we're
going
to
be
moving
to
you
cryo,
but
yeah,
but
I
haven't
heard
anything
from
the
upstream
community
about
making
that
a
default
or
making
anything
a
default
really
just.
G
C
F
C
A
A
A
C
Agree
like
I,
just
probably
no
singer,
these
things
thought
there's
like
CSI
C
and
I
CRI.
So
you
want
like
tests
that
make
sure
you're
conforming
to
those
implementations,
but
then
we
want
to
make
sure
that
we
can
also
verify
that
a
given
kubernetes
cluster
when
having
all
this
bits
plugged
in
still
satisfies
at
the
bare
minimum
the
expectations
of
a
conformant
communities
cluster,
so
I'm
working
through
those
challenges
with
individual
owners
through
sig
note
and
sink
storage.
At
the
very
least
I'm,
not
super
familiar
with
the
CNI
storage
Ranko.
A
G
So
we
do
have
a
couple
of
tests
failing
again
on
the
master
release,
I'm
sorry
master
blocking,
and
there
is
one
reopen
on
Q
barium,
which
failed
again.
So
there's
a
discussion
about
that
I
think
near,
like
all
he
pointed
out
when
I
asked
him
so
based
on
that,
but
but
mainly
right
now,
the
most
of
our
tests
are
failing
on
upgrade.
We
have
new
failures,
we
have
videos
which
Oh
God
fix,
but
we
have
also
new
failures
which
are
appearing
on,
though,
stop
great,
so
I'm,
sorry,
raising
issues
and
bringing
the
people
on
that.
A
Do
you
have
a
sense
at
this
point
whether
those
particular
upgrade
failures,
so
we
had
a
set
of
them
over
the
last
few
weeks,
but
then
it
feels
like
there's
more.
The
initial
set
were
ones
that
cluster
life
cycle
had
triage
to
being
not
cluster
up
a
cluster
life
cycle.
The
upgrade
had
happened,
but
then
subsequent
testing
had
failed.
So
I
don't
know.
If,
if
that
implies,
we
have
something
for
API,
breakage
or
behavioral
breakage.
That's
a
problem
that
we're
able
to
upgrade
the
cluster,
but
things
that
used
to
run
are
no
longer.
G
That's
something
that
definitely
yeah,
so
that's
something
that
we
need
to
dig
into
more
because
there
that
there
are
some
failures
and
upgrade
which
are
not
clear,
like
no
way
they're
fail.
There
are
a
couple
of
them
which
look
like
they
are
failing
on
upgrade
tests,
but
that's
something
that
I
want
to
confirm
with
people.
Maybe
I'll
get
attached
with
the
testing
and
try
to
figure
out
whether
they
have
to
on
that
a
part
on
that.
G
Of
course,
I
have
also
tried
to
ping
the
sick
people
themselves
and
see
if
they
can
say
that
that
these
tears
are
not
there
from.
So.
If
you
can
eliminate
those
six,
then
we
can
totally
your
pinpoint
the
source
of
the
issue.
That's
what
I'm
working
on
right
now,
trying
to
eliminate
dough-like,
see
if
it
was
attacks
occurring,
think
those
sick
guys
they
cannot
take
their
deaths,
are
the
ones
which
are
fallen
and
if
they
say
no,
then
it's
probably
not
that
that's
again
an
explosion,
then
take
ask
you
something
to
figure
out.
E
A
H
A
A
Okay,
do
we
yeah
I,
see
Gwen
welcome
back
Gwen,
you
wanna
talk
a
bit
about
where
we
are
on
bugs
aside
from
the
these
test
failures.
D
I'm
glad
to
be
back
so
bugs
are
basically
super
stable,
anything
that
has
the
milestone
label
currently
on
it.
There
are
there's
some
there's
one
little
change,
there's
mostly
the
same
bugs
two
of
them
are
getting
lots
of
work
and
two
of
them
I,
basically
prodded
them
today,
because
I
haven't
seen
any
activity
on
it
since
June,
so
just
being
a
little
proactive
on
that,
and
then
there
was
a
new
little
bug.
That's
actually
an
old
bug
that
had
there
that
that's
just
recently
gotten
some
attention
and
oh.
D
And
my
special
mention
is
there
was
an
issue
yeah
that
was
the
really
Oh
No.
There
was
a
new
bug
this
one
six
one,
the
priority
important
soon,
there's
a
new
one,
that's
an
old
one,
but
it's
being
worked
on
so
I
wouldn't
worry
about
that
for
now
and
then
the
special
mention
there
was
a
bug
that
got
closed,
but
the
related
PR
was
only
a
partial,
fixed
and
I
think
it
was
closed
in
error.
So
I'm,
probably
up
on
that.
D
A
D
G
Yeah
so
yeah
I
I
just
noticed
that
the
bunch
of
fate
is
like
that
that
there
are
at
least
seven
eight
deaths
that
failed
on
six
storage.
So
I've
already
pinned
them
about
it,
I'm
not
as
a
issue
yet
because
it's
a
single
gun
but
I've,
already
pink
them
on
the
channel
and
so
they're
getting
a
look
at
it.
If
they
can
confirm
that
it's
just
if
I
have,
if
I
see
an
under
another
trailer
and
I'll,
probably
then
you
show
next
time,
but
for
now
one
time
you
get
in
anyway,
and
these.
A
D
A
Think
I
know
what's
going
on
here
and
I
submitted
a
PR
last
week
for
a
trivial
little
fix
up
for
that
one,
but
then
I
hit
a
halt
when
I
ran
the
e
to
eat.
Us
I
hit
a
whole
bunch
of
weird
failures,
and
then
there
was
also
a
issue
last
week
with
was
something
that
was
causing
quite
a
bit
of
flakes
and
things
failing
to
merge.
A
G
A
Alright,
so
that
was
our
main
set
of
things,
features
bugs
and
and
CI
signal,
though
one
other
thing
I
wanted
to
mention
was
that
tomorrow
we
should
be
building
our
beta
and
that
that
should
be
happening
from
the
branch,
hopefully,
so
we're
we're
working
through
new
things
and
all
of
these
mechanisms.
So
it's
easy
to
say:
we're
gonna
build
a
beta
tomorrow.
Will
we
may
have
a
fun
day
making
it
so
Caleb?
Are
you
oh
wait?
Did
we
lose
Katie
you
still
here.
Caleb?
Will
you
be
around
tomorrow
if
we
bump
into
any
quirks
okay.
C
I
Many
questions
right
now:
the
I
need
to
figure
out
what
time
will
actually
work
for
me
tomorrow
might
need
to
be
later
than
the
evening
again.
Unless
we
went
into
Wednesday
I'm
a
more
wide
open,
I
think
we
should
get
it
start
in
case
we
run
into
you,
know,
know
the
permissions
issue
and
then
I
was
also
thinking.
I
You
know
to
get
more
of
the
shadows
involved.
You
know
we
could
do
a
live
zoom
or
maybe
better
to
do
if,
if
I
actually
captured
everything
with
script
and
then
do
a
zoom
after
we're
done,
so
we
can
kind
of
go
through
it
faster.
Instead
of
you
know
it
takes
an
hour
to
build,
and
then
you
know,
I
think
they'll
probably
be
better
for
everyone,
so
that
sound
good
yeah.
A
I
was
thinking
that
this
time,
based
based
on
the
prior
and
that
this
maybe
has
the
additional
wrinkle
of
the
branch
creation
that
if
with
a
small
group
of
people,
we
go
through
kind
of
nail
it
down
and
and
actually
then
PR
our
draft
dock,
that
we
have
on
what
the
process
is
go
ahead
and
PR
that
and
on
the
next
one
bring
the
shadows
and
to
run
through
it
all.
As
a
group,
okay,.
J
E
I
I
A
Have
a
beta
1,
a
beta
to
an
RC
one
that
are
technically
on
the
calendar
that
we
can
do
so
after
after
this
one
there's
three
more
opportunities
to
so
I
want
to
I
want
to
try
to
at
least
spare
a
bigger
group
from
the
pain
of
really
going
through
the
initial
bits,
but
I
think
after
this
one.
We
should
have
the
process
doc
that
we
had
started
relatively
cleaned
up
and
then
we've
got
three
times
to
exercise
it
with
a
group.
A
And
then,
if
I
recall,
oh
no,
we
don't
the
only
the
only
thing
in
there
would
be
the
the
fast-forwards
of
the
branch,
the
while
you're
out
on
vacation.
Those
couple
days.
Doug
will
have
one
of
the
shadows
do
that,
but
we've
got
a
bit
of
time
yet
also
for
after
we
make
the
branch
to
start
working
on
the
making
sure
that
fast
forward
stuff
is
all
clean
and
crisp
before
you're
out.
A
D
A
That's
a
good
question,
so
we
those
are
in
the
the
YouTube
recordings
I.
C
D
G
A
Just
a
second
and
I'll
share
the
draft
doc
that
we
had
started,
so
this
is
very
much
work-in-progress
I'm,
dropping
it
in
the
zoom
and
I'll
drop
it
in
the
minutes
and
then
I
think
after
tomorrow.
What
we'll
do
is
we'll
take
that
dock
and
having
having
gone
through
it
once
and
then
tomorrow
exercising
what
we
think
we
have
seeing.
If
we
run
into
any
other
issues,
then
we'll
PR
the
contents
over
into
markdown
thanks.
J
C
A
C
A
Well,
for
the
the
official
builds
I
think
it
would
technically
be
Doug,
but
Doug
is
also
going
through
the
process
of
learning
it.
So
it's
kind
of
a
mix,
we're
definitely
leaning
on
Caleb
and
I.
Think
he's
also
kind
of
a
conduit
for
miscellaneous
Google
folks.
So
it's
it's
a
bit
indirect
at
the
moment.
C
I
guess
maybe
I
do
have
one
other
questions
now
that
I'm
looking
at
the
query
quite
a
bit
posted
for
issues
there
are
labels
such
as
milestone,
needs
approval
and
status
approved
for
a
milestone
that
I
am
led
to
believe
we
aren't
going
to
be
using
as
part
of
this
release
cycle.
Should
we
be
removing
those
from
issues.
A
D
D
B
D
B
A
Homework
to
do
if
they
have
attention
yeah,
and
then
that
goes
back
to
the
question
of
who
has
the
ability
to
assign
the
milestone
label
if
it's,
if
it's
overly
broad
random
thing
or
the
ability
to
remove
all
so
things
come
and
go
strangely,
but
I'm
I'm
not
sure
that
the
the
milestone
approval
label
dramatically
changes
that
so
I
I.
Definitely
would
like
this
to
be
simpler.
C
C
This
means
that
any
of
these
I
don't
have
a
number
offhand,
but
let's
just
say
it's
70
plus
people
could
arbitrarily
attach
a
milestone
to
their
pull
request
because
they
want
to
get
their
code
snuck
in
without
a
sink
lead
having
sufficiently
checked
it
over.
You
know
people
just
want
quick
fixes
in
or
maybe
they
really
want
to
get
their
feature
in
under
the
gate.
They
don't
wanna
have
to
go
through
the
bureaucracy
of
talking
to
people
about
it
and
making
sure
people
are
aware
what's
happening.
C
So
it
was
boring
if
we
want
to
still
have
that
level
of
control.
We
can
do
that
today
in
the
interim
we've
since
added
a
command
where
people
can
like
apply
the
milestone
via
bot
command
and
it's
gated
to
the
same
group
of
people.
However,
we
haven't
gone
through
and
kicked
out
everybody
who
has
direct
access
to
the
rebound
so
that,
like
whole
process,
whatever
still
exists,.
C
So,
like
my
personal
opinion,
is
less
labels
good,
more
labels.
Bad
friction
is
annoying,
but
yeah
I
linked
our
discussion
and
it's
true
that
while
we
expressed
opinions
in
our
discussion
of
removing
labels,
we
never
actually
came
to
that
consensus.
We
just
decided
to
turn
off
the
bot
that
nags
people
about
the
labels,
so
I
kind
of
leave
it
to
you
to
suggest
whether
or
not
you
want
to
now
as
humans
have
to
remind
people
that
they
have
to
apply
those
labels
or
change
the
process
to
be
simpler.
C
B
A
C
A
Sure,
okay,
so
I
wanna
I,
still
haven't
fully
reviewed.
The
proposal
that
chase
and
the
proposals
that
Jason
Steven
are
talking
about
and
it's
sort
of
sig
p.m.
sort
of
sig
release
also.
A
I
want
to
have
a
a
better
sense
of
what
others
are
proposing
for
the
long-term
direction
and
then
I
I
don't
want
to
go
and
make
too
drastic
of
a
change
like
this
week
and
for
the
next
month
then
or
the
next
six
weeks,
if
we're
about,
if
there's
a
loose
consensus,
starting
to
form
around
a
particular
direction,
I'd
prefer
to
at
least
be
semi
aligned
with
what
might
be
that
direction.
So
I
will
prioritize
getting
finished
reading
through
those
today
and
then
make
a
decision
and
an
update.
A
I
I
personally,
like
the
idea
of
having
the
sig
leads,
approve
explicitly
just
because
it
gives
me
some
sense
of
okay,
subject
matter:
expert
in
an
area
that
I
am
NOT
and
across
all
of
the
set
of
SIG's.
This
is
the
release.
Lead
is
never
going
to
be
just
to
give
that,
even
if
it's
just
a
single
bit
of
information,
a
little
bit
of
a
some
visibility
that
that
somebody
has
has
thought
about
it.
A
B
Sounds
good
so
from
just
from
the
perspective
of
those
two
proposals,
the
my
proposal
specifically
was
meant
to
solve
the
idea
of
like
issue
triage
right
issue
and
feature
issue,
triage
and
jaysis
proposals
kind
of
like
long
term,
but
we're
the
last
conversation
we
had
was
that
we
should
find
a
nice
meeting
point
in
the
middle
and
we
haven't
necessarily
found
that
yet
so
definitely
read
the
proposals
but
know
that
they
will
probably
be
morphed
into
some
singular
proposal
at
some
point,
but
yeah
I
will
I
will
do
an
update
for
that
milestone,
PR
and
all
the
issue
stuff.
B
A
B
C
A
And
then
we'll
see,
I
still
have
this
nagging
feeling
that
we're
gonna
finish
in
September
and
go
holy
crap.
That
was
a
mess
we
had
so
many
surprises
but
fingers
crossed.
We
don't
have
that
outcome
and
and
we'll
we'll
see
how
we
have
all
this
all
right
anything
else.
Anyone
wants
to
talk
about
sick
beer
yields
the
floor.