►
From YouTube: Kubernetes 1.13 Release Team Meeting 20181112
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
Hi
everybody
happy
Monday
welcome
to
our
113
burndown
I've
pasted
the
link
to
the
dots
in
the
chat.
Please
add
your
attendance
if
you've
not
done
so
already
and
as
always,
this
meeting
is
being
recorded
and
will
go
up
on
YouTube
shortly
after
so
please
be
mindful
of
what
you
say
with
that:
let's
get
started.
A
It's
the
co.
Almost
the
code
freeze
week,
we
are
in
code
slush
officially
as
of
5
p.m.
Friday,
thanks
to
:
Ahmet
for
emerging
the
merge
blocking
criteria,
so
all
the
PRS
are
now
blocked
on
will
be
blocked
on
4
labels,
as
mentioned
earlier,
so
I've
been
going
over
all
pending
PRS
as
much
as
possible,
especially
the
ones
that
we
are
tracking
for
any
failing
tests
or
enhancements
over
the
weekend,
and
some
of
them
didn't
have
the
priority
label,
which
I
was
able
to
add.
A
So
that
said,
if
you
come
across
any
issue,
that's
not
having
those
labels.
Please
remind
the
owners
to
add
it
or
add
those.
If
you
know
what
what
is
like
set
priority
and
milestone,
of
course,
that
that
is
for
code
slush
and
your
code
freezes
on
track.
As
of
now
for
end
of
week,
Friday
1116
so
again,
we've
been
convene
continuously,
reminding
thanks
to
the
awesome
enhancement
leads
and
lead
and
shadows.
A
We
we've
been
completely
on
all
of
the
enhancements
issues,
reminding
folks
that
code
freeze
is
just
less
than
a
week
away
and
I've
been
trying
to
get
a
sense
of
what
is
left
for
all
the
enhancements
to
go
in
will
circle
back
to
that
more
in
the
enhancements
section.
Beta
1
is
also
going
to
be
this
Friday,
but
we
do
see
a
few
CI
signal
issues.
That's
concerning
at
this
point,
so
beta
1
will
depend
on
CI
greenness.
Can
we
can
discuss
more
about
it
in
the
CI
section?
A
Is
here
today
to
keep
a
status
update
so
that
so
that
we
can
understand,
what's
left
out
of
the
cube
admin,
ga
effort
and
113?
And
lastly,
as
for
a
general
announcement,
is
the
license
issue
that
we
were
tracking
in
the
hickety
repo?
There
was
great
traction
on
that
late
last
week.
They
liked
the
upstream
change
went
in
and
we
also
updated
the
relevant
KK
files
to
have
the
correct
license
right
now,
so
that
is
now
out
of
the
blocker.
A
B
Yes,
so
I
was
just
looking
through
the
PRS
that
got
merged
to
make
sure
that
everything
was
working
properly.
It
looks
like
the
merge.
Automation
itself
is
fine,
but
the
require
matching
label
plug-in,
which
is
what's
responsible
for
ensuring
that
there's
a
needs,
kind
and
needs
priority
label.
That's
it's
working,
fine,
but
it's
not.
B
It
reacts
to
new
PRS
and
when
labels
are
updated
on
the
PR
of
the
appropriate
type,
so
old,
PRS
that
never
had
a
priority
label
before
this
automation
was
even
enabled
and
if
they
never
had
a
priority
label
change
or
anything
like
that,
they
didn't
get
the
needs
priority
label.
So
I
noticed
that
there's
I
mean
a
whole,
not
a
whole.
Lot
of
PRS
have
merged
in
the
master.
Since
code,
slash
went
into
effect,
there's
like
just
a
handful
I
guess
some
of
those
are
missing
the
appropriate
priority
and
kinds.
Okay,.
A
A
B
A
B
A
D
D
So
thank
you
for
taking
the
time
and
doing
that
and
kind
of
wrangling
a
lot
of
this
stuff
together,
but
as
of
last
week,
so
we're
down
to
from
last
week
from
where
we
were,
we
had
one
that
we
thought
was
in
limbo
because
they
were
saying
this
is
four
five,
six
five
saying
that
we
have
it
available
for
it
and
then,
as
of
Friday,
it
said,
okay
or
I
think
what
Saturday
or
Sunday
they
said.
No
longer
gonna
be
part
of
this,
so
so
that's
being
taken
out
of
limbo.
D
D
There's
a
I
probably
should
have
put
it
in
here,
but
there
is
a
dashboard
of
all
of
the
PRS
and
everything.
That's
that's
sort
of
going
into
it
right
now.
There
are
seven
PRS
that
are
winning
to
merge
with
three
conformance
blockers.
So
there's
a
lot
of
stuff
to
really
get
done
before
the
end
of
this.
The
end
of
this
week
for
Windows,
so
we're
gonna,
be
hearing
from
them
come
Wednesday
to
see
where
we
are
gonna,
be
with
inside
of
that
process
as
well.
The
Adam
Trese
ESI
plugins
again.
D
This
is
a
another
big
one
as
well.
There's
two
PRS
that
are
closed.
There's
a
lot
of
active
involvement,
a
lot
of
stuff
where
it's
being
happening
on
them,
but
still
waiting
on
that
one
dot
expect
to.
Finally
merge
and
I
believe
we'll
hear
from
sod
on
Wednesday
as
well
to
figure
out
where
we
are
in
regards
of
that
tube
213.
This
is
something
that
we
talked
about:
there's
the
no
communique.
So
today
it's
it's
out.
Probably
if
I
had
to
guess
that's
probably
gonna
happen.
5
p.m.
my
time,
I'm
Eastern,
so.
A
A
D
The
third
party's
device
monitoring
plugins
as
of
Friday,
nothing
was
happening
that
kept
wasn't
approved
or
anything
like
that.
But
now
that
it's
finally
approved
it's
still
waiting
for
merge.
There
is
one
PR,
that's
being
that
is
active
right
now,
so
we're
just
got
to
monitor
that
as
a
continues
to
go
yeah
the
same
thing
was:
625
is
related
to
594,
we'll
just
kind
of
see
this
it'll
probably
get
moved
out
as
well
just
waiting
for
a
fishel
confirmation
from
sod
on
it
yep
and
then
626.
D
This
is
the
one
that
to
work
on
the
VCR
plug-in.
This
is
still
an
entry
component.
There
has
been
any
active
work
for
about
four
to
seven
days,
so
in
my
opinion,
we
should
probably
just
go
ahead
and
remove
it
at
the
end
of
the
day,
but
I
don't
want
to
gauge
anybody
else's
thoughts
on
it
as
well.
Yeah.
A
I
again
pinged
sang
on
slack
just
just
because
there
was
some.
He
said.
The
feature
is
kind
of
on
track
three
days
ago,
but
I
haven't
know
again,
I'm
not
seeing
what
pr's
is
it
waiting
on?
So
in
lack
of
that
I
think
we
should
definitely
move
it
out
end
of
day
today
and
then
see
if,
if
we
hear
back
from
them,
I'll.
D
A
D
A
D
I,
like
I,
said
so
for
me.
We
we've
just
got
these
ones
that
we're
tracking
I
think
after
Wednesday
we're
going
to
be
in
a
pretty
good
situation
of
where
we
feel
comfortable,
what's
going
to
be
happening
and
then
yeah
and
we
should
be
kind
of
off
to
the
races
after
after
code
freeze
yeah,
but
from
there
go
ahead.
No.
A
Just
one
quick
note
before
Lieberman
gives
an
update.
The
server
side
apply
also
fell
out
of
113
just
to
given
just
a
facial
update.
Here
they
were
unable
to
wrangle
things,
so
it's
going
to
114
now
so
for
all
of
these
I
think,
thanks
for
those
detail,
update
Kendrick
most
of
those
are
just
a
couple
of
PRS
here
and
there,
and
all
of
them
also
have
dogs
in
place
so
I'm.
A
In
my
mind,
I'm
kind
of
timeboxing
things
to
go
in
early
Wednesday
or
at
least
end
of
day
Wednesday
if
they
have
to
be
in
1:13,
mainly
because
most
of
these
are
also
adding
into
in
tests.
So
we
want
to
CCI
stabilize
at
least
for
the
next
couple
of
days
before
freeze
so
yeah
I
think
we
have
I
will
make
a
call
on
most
of
these
by
Wednesday,
and
we
should,
if,
at
that
point,
if
pr's
are
still
active,
then
we
should
go
ahead
and
be
able
to
move
them
out.
That
is
a
risk.
A
A
A
A
E
That's
actually
a
bit
of
a
blocker
for
us.
If
we
have
this,
it's
going
to
be
easier
for
us
to
move
forward,
so
the
next
one
could
be
the
MTG
a
now.
We
have
a
couple
of
issues
to
track
in
terms
of
code
changes.
Now
here
is
one
of
them.
I
just
wanted
to
quickly
explain
to
you
what
this
is
about.
So
this
is
something
we
are
doing.
We
are
a
factor
in
all
the
commands
subcommands
of
qadian,
and
we
have
a
big
list
of
PRS
here.
F
E
E
E
Okay
in
terms
of
dogs,
we
have
a
tracking
issue
at
the
website.
Repository
and
I
created
one
pra,
it's
already
merged,
like
it
merged
immediately
yesterday,
and
we
have
a
Bella
which
is
still
a
placeholder
and
I'm,
going
to
try
to
update
it
before
before
the
19th
of
November,
and
we
don't
have
anything
anything
else.
You
only
have
these
two
to
be
ours
for
dogs.
E
E
E
A
D
C
A
E
A
E
A
1.13
blocking
the
one
chest:
okay,
so
there
are
now.
If
you
see
the
last
two
cube
idiom
jobs
there,
GC
113
112
on
113
and
GC
113,
these
seem
to
be
passing
consistently.
It
says
yeah,
so
I'm
just
trying
to
understand
the
difference
between
these
jobs
and
the
one
that's
failing
in
the
113,
all
body,
okay,.
E
Because
of
the
the
problem
we
have
with
these
test
infrastructure,
/n
framework
problems
like
these
are
the
things
I'm
talking
about
like
these
four
items.
Here
we
cannot
skip
them,
which
means
that
these
this
family
of
tests,
like
12
or
13,
they're
gonna,
remain
red
at
all
times
and
that's
why
we
don't
want
to
get
them
into
this
dashboard,
which
is
the
whole
yeah.
E
A
D
A
Would
I
would
leave
it
there
with
with
like
a
note
saying
now
that
we
know
that
these
this
because
of
just
Indra,
and
we
would
want
to
watch
this
in
114
the
next
cycle
when
you
guys
get
it,
get
it
fine.
So,
okay,
I'm,
okay,
leaving
it
here,
because
at
this
point
we've
assessed
that
it's
not
a
it's
it's
a
test
in
price
you
rather
than
a
product
issue,
so
I'm
not
too
worried
about
the
staying
here
and
failing
versus
booting
it
out.
Hopefully,.
A
My
only
question
is
that
the
first
issue-
one
one,
six
three
they
and
a
shoes
to
track.
It
has
quite
a
few
open,
PRS
and
you're,
confident
about
all
of
that
kind
of
making
it
in
sometimes
this
week.
I
know
this
is
out
of
trade,
doesn't
really
come
under
the
code.
Freeze
thing,
but
still
I
would
like
to
know
when
these
we
expect
these
to
land.
Well,.
E
E
A
F
F
A
I'm,
like
really
concerned
only
about
the
upgrade
tests
at
this
point,
mainly
because
ever
since
we
cut
the
112
branch,
I
mean
113
branch,
the
upgrade
the
GCE
master
of
craters
being
fake,
a
timing
out
on
the
dashboard.
Incidentally,
this
coincides
with
horizontal
what
I
mean
HPA
auto-scaling
PR
that
got
merged
they've
got
cherry
picked
into
112
on
the
same
day
so
which
makes
me
think
that
that
could
be
something
that's
causing
the
upgrade
to
time
out.
A
One
good
part
here
is
if,
when
I
dig
into
the
logs,
the
upgrade
itself
passes
it's
some
job
after
that.
That's
timing
out
there
on
at
15
hours,
so
I'm
working
I
think
Justin
on
this
I'm
working
closely
with
him
to
track
this
and
see
what
could
have
caused
this.
But
this
seems
to
be
the
biggest
concern
at
this
point,
and
if
this
is
not
resolved,
/
understood
by
Friday,
this
could
block
beta
1,
especially
if
the
upgrade
flows
are
in
kind
of
I
mean.
A
If,
if
up
great
roles
are
not
passing,
then
this
will
block
beta.
One
I
will
keep
folks
updated
on
this
Maria.
Would
you
mind,
following
up
on
the
resource,
Kota
failure
that
is
just
listed
below
that
this
is
again
something
that's
happening
consistently
on
the
upgrade
one
of
the
great
jobs
but
looks
like
the
owner
is
not
sure
about
what
the
fixes,
so,
if
you
could
just
follow
up
with
the
scheduling
folks
on
this
will
be
created,
sounds
good
yeah
and
one
I'm
sorry
for
the
drawers
noise.
A
Here
my
daughter
is
singing
it's
the
cutest
thing
ever
she's
home
and
I'm
yeah,
and
the
only
remaining
thing
is
the
performance
nutrition
that
we,
the
issues
still
open
since
we
haven't
heard
from
Wojtek.
If
all
the
concerns
are
addressed
with
the
latest
runs,
I
pinged
him
a
couple
of
times.
I
will
follow
up
again
with
him,
but
from
the
runs
we
had
a
large-scale
run.
We
had
a
couple
of
GC
GC
hundred
nodes
run.
A
F
A
A
Over
previous
values
and
also
Bobby
from
scheduling
he
reverted,
one
more
culprit
see
a
PR
which
he
thinks
actually
picked
a
CPU
resource
consumption
up
so
that
one
merged
sometime
last
week,
I
think
Friday
or
Thursday,
and
after
that
I
see
the
numbers
for
those
runs
match
with
what
was
there
earlier
like
two
weeks
out
so
but
yeah?
Maybe
if
you
have
some
time
we
can
compare
the
latest
runs
and
then
and
then
ping
Wojtek
again
that'll
be
great.
A
G
As
far
as
the
open
issues
are
concerned,
there's
an
issue
related
to
six
storage
which
Nico
paints
the
owner
and
they're
gonna,
give
us
an
update,
probably
by
next
two
days
or
something
then
there's
another
issue
related
to
cube.
Atm
upgrade
failure,
I'm,
not
sure
what
seriously
on
this
did
not
mention
any
notes.
You.
A
Know
that's
actually
I
added
it
my
bag.
This
is
the
this
is.
This
was
the
upgrade
the
one
failure
in
the
cube
admin
upgrade
that
loop
ma
was
talking
about.
They
have
some
PR
soap
and
I
just
wanted
to
list
the
issue
here,
since
it
might
not
show
up
in
any
of
your
queries,
since
that
one
is
not
in
KK,
so
I
just
added
it
here,
but
that
it's
in
your
radar,
oh
yeah,.
G
Then
important
soon,
this
issue
is
a
windows
conformance
end-to-end
test
which
will
move
slightly,
be
shifted
to
114
yep.
Then
we
have
just
a
second
yeah.
This
issue
of
the
plugin
watcher
getting
notified
was
recently
added
and
Nico
is
gathering
more
information
about
it
and
this
this
issue,
two
failed
volume
attached
T
that
operation
or
leave
the
volume
state
uncertain.
This
is
already
like
it
has
a
PR
out
which
is
being
reviewed
and
should
get
merged
very
soon
awesome
and.
F
G
A
A
H
Everybody
so
yeah,
placeholder
PRS,
are
in
a
good
place
now.
Five,
nine
eight
should
have
a
PR
open
today
and
I'll
put
that
six.
Two
two
need
to
talk
to
my
Erin
about
that
again:
that's
it's
DD
to
interpretation
just
want
to
make
sure
whether
or
not
anything
is
to
go
into
talks
for
that
I
think
he
might
be
busy
cuz
he's
in
Shanghai
yeah
for
coop
con,
but
if
something
it
does
come
in
for
this
it'll
be
pretty
small
anyway,
I
think
so
I'm
great
about
it
and
then
two
one
three.
H
As
mentioned
previously,
it's
probably
going
to
be
bumped
today,
so
we
probably
need
anything
for
that.
Yeah
so
we'll
be
doing
a
dry
run
of
dock
generation
this
week,
just
a
test
at
the
follow
it's
gonna
be
run
in
parallel
with
a
beta
one
release.
So
it's
not
gonna
block
that
and
it
will
require
that
either.
D
H
A
A
It
sounds
good
yeah
when
I,
when
I
was
just
looking
through
all
the
enhancements.
Most
of
them
had
placeholders,
which
is
a
good
thing
and
yeah
I
think
you're.
On
top
of
this,
if
you
need
any
help
following
up
with
any
of
these
placeholder
peers,
to
move
them
to
completion,
don't
feel
free
to
reach
out
to
us
and
we
can
split
the
work
you.
A
E
H
Yeah
the
reference
Doc's
will
be
generated
like
on
release
day
I
think
you
will
probably
want
to
get
do
a
few
tests
before
that
I
think
there
was
a
difficulty
in
the
112
release
around
doing
it.
It's
so
last-minute.
So
probably
a
couple
test
runs
a
few
days
beforehand
and
then
the
final
one
will
be
cut
day
of
release
and
correct
me.
If
I'm
wrong
nice
yeah.
A
I
I
Those
of
you
that
weren't
there,
but
you
know,
feel
free
to
check
out
that
and
we're
gonna
be
sending
that
out
too
well,
you
know
for
the
release
team.
You
know
check
that
out
review,
it
leave
comments
and
you
know
we'll
sure,
incorporate
them
me
and
the
shadows.
The
second.
The
second
thing
is
okay,
yeah
known
issues,
so
every
release
we
can
early
create
an
own
issues.
Github
issue
in
the
KK
repo
and
I
have
a
few
known
issues
that
I've,
you
know.
I
A
I
I
Sure
yeah
I
can
go
create
that
now
and
then
I
can
edit
the
copied,
because
you
know
the
whole
item
on
the
list.
The
third
update
item
is
Dave.
The
release
notes
shadow
who's
been
released.
Machado
last
release
on
this
release
is
gonna
start
reaching
out
to
cichlids
and
shares
four
major
themes
afternoon
after
any
feedback
from
today's
meeting.
I
If
any
so
there's
a
doc
there
safely
slash
chair
comes
if
anyone's
inference
and
sig
leads
or
we're
asking
them
to
do
to
the
Bach,
and
you
know
feel
free
to
check
that
out
at
and
feedback
and
we'll
for
sure
incorporated
in
its
becomes.
A
current
deadline
is
pretty
early
for
this.
We're
giving
folks
like
week
and
a
half
the
current
deadline
that
we
set
for
I
set
for
this
coming
in
is
or,
for
you
know,
all
the
major
themes.
I
So
you
know
is
November
21st,
which
is
the
day
of
beta
2,
and
at
that
point,
if
we
didn't
get
anything
from
sig
leads
we're
just
gonna
start
guessing,
and
you
know
writing
our
own
major
themes
for
each
song.
The
notes
that
have
been
submitted-
or
you
know
if
it's
an
active,
sig
or
something
that
doesn't
have
major
themes
and
the
release,
notes
and
will
probably
just
not
included
in
the
major
themes.
Yeah.
A
D
A
A
That
brings
us
to
the
end
of
the
agenda,
so
the
release
is
just
starting
to
get
really
crazy,
as
with
everything
else,
huge
tanks.
For
all
of
you
all
the
leads,
and
also
the
shadows.
Who've
been
like
amazing
and
super
active
this
time.
Thanks
a
lot
for
all
your
hard
work.
Hopefully
we
will
enter
code
freeze
with
fewer
chest
failures
and
with
a
little
bit
more
enhancement
so
that
we
can
have
something
sizable
in
our
blog
post,
so
cool
with
that
I.
Don't
have
anything
else
left
any
questions,
feedback
suggestions.