►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200824
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
All
right
all
right
all
right
good
morning
afternoon
evening,
everyone
it
is
release
week
here
in
kubernetes,
world
kubernetes
119.
should
be
going
out
the
door
this
week.
I
know
we
have
a
few
things
to
talk
through
and
work
through
today,
and
I'm
excited
to
do
so
with
everyone
here.
So
thank
you
all
for
attending
today
is
monday
august
24th.
A
This
is
a
release
team
meeting
for
119..
This
is
a
kubernetes
meeting
as
well.
We
abide
by
the
kubernetes
code
of
conduct,
which
simplifies
down
to
please
be
excellent
to
one
another
yeah
today
I
figured
we'd
just
kind
of
go
through
stats
of
everything,
see
where
everyone
is
at.
You
know
just
kind
of
where
we're
landing
on
overall
gut
feel
and
what
all
the
items
look
like
for
119.
A
we're
proposing
to
go
live
tomorrow
with
some
of
the
flakes
and
other
things.
I
definitely
want
to
talk
through
that
and
see
if
everyone
still
feels
good
about
that
and
then
I'm
going
to
jump
over
into
some
issues
and
prs
here
and
just
kind
of
talk
through
them
make
sure
that
they
have
an
owner
and
then
again
see
if
everyone
feels
good
on
that
front.
So
to
kick
things
off,
I'd
love
to
turn
it
over
to
nabrun
with
enhancements.
B
B
So
in
total
we
have
like
34
announcements
in
this
release
and
that's
all
on
our
site.
A
Awesome,
thank
you,
neverend.
Any
questions
for.
A
Enhancements
excellent
moving
on
to
thank
you
very
much
neverend.
Moving
on
to
the
big
ticket
item
today,
ci
signal
turn
over
to
dan.
C
Hey
folks
hope
everyone
had
a
nice
weekend,
so
we
are
yellow
right
now.
You
could
maybe
consider
it
red
right
now.
Integration
master
is
reporting
failing,
it's
actually
just
flaking
really
aggressively
haven't
identified
the
root
cause
yet,
but
it
appears
to
be
infrastructure
related
due
to
the
fact
that
there
were
no
changes
to
underlying
tests
or
anything
like
that,
and
it
was
happening
across
the
different
branches.
C
It
is
flaking
more
aggressively
on
master,
so
we're
trying
to
look
at
what
is
going
on
there
like.
I
said
it
is
likely
not
related
to
a
code
quality
issue,
so
that
is
good,
but
we
also
aren't
getting
signal.
So
we
can't
really
say
that
for
sure
so,
we'd
like
to
get
that
resolved.
C
There
were
some
changes
recently
made
to
the
cluster
that
these
jobs
are
running
on,
which
shouldn't
be
impacting
them,
but
could
potentially
be
so
talking
to
aaron
a
little
bit
about
potentially
rolling
those
changes
back
outside
of
that
other
things
are
looking
good,
except
for
on
1.19
verify.
1.19
is
also
having
some
timeouts
once
again
likely
infrastructure
related,
but
we
haven't
been
able
to
identify
the
the
root
cause
there.
C
So
we're
going
to
continue
to
look
at
that,
and
these
are
things
that
we
would
definitely
want
to
get
resolved
by
tomorrow,
despite
them
likely
being
related
to
infrastructure.
So
we'll
continue
to
keep
you
updated
in
the
release
channels.
A
Cool,
thank
you
so
much
dan
yeah.
I
think
that,
obviously
I
think
if
we
stay
in
sync
and
kind
of
check
in
where
everything's
at
we
can
make
that
decision.
You
know
a
little
bit
later
today
and
just
kind
of
keep
going
back
and
forth,
see
where
things
are
at
any
additional
comments
or
questions
concerns
for
ci
signal.
D
There's
one
failing
test
issue
the
cube
control
skew
tests
do.
Did
we
ever
get
a
response
from
ccli
as
to
whether
that
is
release
blocking.
C
Is
that
the
one
related
to
the
version
markers?
Yes?
So
I
don't
believe
it
is
release
blocking,
but
I
don't
think
we
got
explicit
response
from
the
sig
cli
folks
on
that
issue,
so
I
can
ping
them
in
slack.
Okay,.
D
C
Yeah,
so
so
one
of
the
main
issues
with
this
is
that,
despite
it
being
green,
it
could
be
testing
the
wrong
thing
because
of
the
version
marker
issues
right.
So
it's
pulling
the
wrong
kubernetes
version,
which
obviously
that
would
be
an
issue
when
you're
doing
a
skew
test
between
versions.
D
I'm
also
not
sure
that
we're
looking
at
the
same
thing,
because
I
see
skew
tests
that
are
not
green,
so
I
just
put
a
link
in
the
chat
we
can.
We
can
follow
up
all
the
line
on
this
one,
but
just
wanna
make
sure
we're
looking
at
the
same
thing.
A
Absolutely
thank
you,
jordan.
Any
other
questions,
comments
or
concerns
with
ci
signal.
A
Excellent,
let's
move
on
to
bug
triage
with
flat.
G
Hey
we
are
yellow.
Most
of
the
issues
on
our
radar
are
related
to
tests,
one
that
is
important
soon
that
jordan
just
mentioned
with
kubernetes
with
skeptical
skill
tests.
There
is
no
reply
as
of
30
minutes
ago
about
whether
it's
release
blocking
or
not,
but
nothing
more
other
than
that.
D
I
did
want
to
call
out
one
issue:
there's
the
the
endpoint
slice
mirroring
bug
looks
like
it
is
a
regression,
and
so
that
is
the
one
that
I'm
most
concerned
about
resolving.
So
I'm
actually
talking
with
rob
now
to
try
to
look
at
the
minimal,
safe
fix
to
address
the
regression,
but
it
is
likely
that
that
is
a
release.
Blocker.
D
A
Thank
you
very
much.
Any
other
comments,
questions
concerns
for
bug,
triage.
A
H
Hi,
everyone
hope
everyone
is
doing
good.
We
are
green,
okay
website
is
frozen
now
and
I
have
all
the
config
vrs
ready
to
go
once
the
release
is
done
so
that
they
just
change
the
version
and
the
drop
down
displays
four
latest
releases
and
I
reached
out
to
all
the
localization
teams
and
make
sure
that
they're
aware
the
gay
website
is
frozen,
and
it's
all
from
me.
H
I
I
have
a
quick
question
that
so
the
website
march
will
take
place
after
the
code
is
marched,
and
that
issue
is
the
pr
is
done
and
I'm
hoping
for
the
point
of
contact
for
it.
Or
how
do
we
coordinate
this?
The
first
time,
I'm
coordinating
so
is
it
via
the
slack
channel
or
on
the
issue.
A
Yeah
I'd
say
that
it's
we've
kind
of
gone
back
and
forth
on
that
one
throughout
different
releases.
Obviously
through
the
github
issue,
you
know
just
kind
of
going
back
and
forth
there
as
we
go
through
the
release
process,
we'll
typically
we've
again
gone
back
and
forth.
There's
some
some
releases
have
been
a
little
bit
more
vocal,
which
is
you
know
good
to.
Let
people
know
that
things
are
moving
forward.
A
I'd
say
that
priority
would
probably
be
just
github
for,
for
you
know,
point
of
record
and
then
just
in
in
real
time,
as
it
makes
sense
to
put
things
into
sick
release
and
kind
of.
Let
people
know
on
that
front.
A
Absolutely
any
questions
for
docs.
D
Did
did
the
sig
leads,
get
sent
a
draft
of
the
release
notes
to
sweep?
I
know
normally
that
happens
and
there's
normally
a
fair
amount
of
cleanup,
but
I
didn't
remember
seeing
that
get
sent
out.
I
Yeah
we
that
that
was
the
the
you
mean,
the
the
the
actual
draft
of
the
of
the
final
notes:
yeah,
it's
it's
it's
polish
and
sig
release
and
the
the
last
draft
we
generated
after
rc4.
D
Okay-
and
I
know
especially
for
like
deprecations
and
sort
of
the
urgent,
must
read
before
upgrading
sections.
It's
helpful
to
have
sort
of
the
subject
matter.
Experts
sweep
those
to
make
sure
that
those
are
completely
correct
and
some
sometimes
when
there's
a
couple,
pull
requests
that
sort
of
do
things
related
to
each
other.
The
automatically
compiled
release
notes
don't
quite
flow
capturing.
What
people
need
to
do
so
yeah
if
we
could
just
get
eyes,
especially
on
those
sections,
deprecations
api.
I
K
Adolfo
when
you're,
when
you're
ready
with
that
stuff,
can
you
send
out
a
note
to
leads
at
kubernetes.io
sure,
as
well
as
kdev,
just
to
get
people
to
do
a
last
review.
Sure,
of
course,.
A
Cool.
Thank
you.
Thank
you
so
much
adolfo
jordan
and
steven.
Thank
you
sabisa
for
that
for
the
docs
update
and
then
kind
of
yeah.
I
know
what
kind
of
rolled
into
that.
Let's
let's
go
to
releasements,
I'm
sorry.
I
Yeah
so,
as
I
was
saying,
we
we're
we
finished
gathering
the
and
composing
the
final
major
themes
for
the
release
notes.
We
had
a
lot
of
input
from
the
from
hc,
so
shout
out
to
my
shadows,
which
really
who
really
did
a
really
good
job
on
on
pestering
them
and
and
yeah.
That's
what
I
was
saying:
I'm
I'm
gonna
push
a
final
draft
for
people
to
review.
I
I
shouldn't
change
much
from
from
what
it's
currently
published
but
we'll
see,
and
if,
if
there's
anything
you
want
to
change
or
anything
just
let
us
know.
A
Thank
you
so
much
adolfo
any
questions
for
release,
notes.
A
All
right,
let's
move
on
to
comms.
L
With
max
hey
everyone
wish
you
a
nice
release
week.
The
release
block
is
so
far
ready.
We're
just
awaiting
the
last
minute
link
updates,
as
well
as
a
super
secret
name
for
the
release,
and
whatever
else
taylor
has
to
tell
us
about
the
logo
and
and
yeah,
we
have
five
or
five
feature
blocks
they're
in
a
good
draftable
status.
L
Currently
we're
checking
them
and
putting
also
the
cherries
on
top
of
them
rephrasing
here
and
there
some
sentence
to
make
them
a
little
bit
more
fluent
in
the
read
and
I'm
also
in
contact
with
the
cncf
for
them.
It's
really
important
to
know
when
we
are
going
to
do
the
release
because
they
have
to
inform
also
the
yeah
as
they
call
friendly
the
the
media
and
the
newspapers,
the
digital
ones.
A
Awesome,
thank
you
so
much
max
yeah,
oh
and
I'll
sh
I'll
have
that
stuff
typed
up
a
little
bit
later
today,
so
still
feel
good
on
that
front
still
feel
good
with
green.
Any
questions
for
comms.
A
Excellent:
let's
move
on
to
release
branch
management
with
sasha.
M
Hey,
oh,
we
almost
decreed.
We
had
no
updates,
but
stephen
wrote
something.
We
issued
a
release,
blocking
a
release,
block
of
ok
release
and
that's
it
we're
waiting
for
cutting
the
release
tomorrow.
A
All
right,
I
don't
see
tim
on
the
call.
I
talked
a
little
bit
with
him
this
morning
and
I'll
kind
of
go
I'll
just
go
ahead
and
give
my
update.
I
talked
with
tim
and
he
said
that
they
we
have
instructions
on
what
we're
going
to
do
for
the
release
schedule.
I've
gone
ahead
and
put
them
in
this
document.
A
Underneath
the
how
this
meeting
works,
section,
there's
a
release,
day,
plan
entry,
and
so
we
kind
of
have
some
some
stock
steps
to
follow
and
we'd
follow
them
in
that
order
and
make
sure
that
you
know
everything
is
checked
off
as
we
go
through
that.
So,
if
you
have
any
questions
about
kind
of
like
how
the
overall
process
works,
that's
what
we're
going
to
follow.
There's
anything
that
we
need
to
add
to
tim
mentioned
that
you
know.
Obviously,
every
release
is
different,
different
concerns
features
etc.
A
So
if
we
need
to
add
anything
in
there,
we
absolutely
absolutely
should
do
so,
but
in
terms
of
go,
no
go
I'd,
say
that
right
at
the
at
the
point
in
time.
Right
now
we're
no
go
just
because
we
have
some.
You
know
critical
items
that
we
need
to
address
and
to
get
through.
We
can
you
know
that
can
be
updated
throughout
the
day
if
we
get
into
a
better
state.
A
You
know
if
we
see
a
lot
more
green
and
we'll
get
through
that
one
that
one
blocking
issue,
but
until
then
I'd
say
right
now
we're
at
a
no-go.
A
Looking
at
the
sig
scalability
update,
817,
the
jobs
look
good,
no
release
blockers.
Obviously
we
talked
a
little
bit
about
that.
We've
definitely
got
one
that
we're
looking
at
right
now
and
then
I'd
love
to
kick
it
over
to
laurie
before
I
kind
of
go
through
open
discussion
and
then
take
a
look
at
the
open
issues
and
prs
that
we
have
right
now.
A
Well,
congrats
yeah,
hopefully
hopefully
your
uncontainerizing
goes
goes
pretty
well
in
your
new
place,
oh
yeah,
it's.
C
A
Done
awesome,
let's
move
into
open
discussion.
K
Yeah,
so
not
specifically
for
119,
but
as
we
as
we
move
from
119
into
120,
there
was
a
proposal
by
jordan
to
reopen
development
for
120.
K
Take
a
look
at
that
proposal.
The
proposal
has
been
approved
by
architecture,
release
and
testing,
and
I
sent
an
email
a
little
earlier
right
before
this
call
to
notify
the
community
as
well
as
the
sig,
as
well
as
the
the
leads.
K
K
Super
high
level
overview
is
that
we're
going
to
be
limiting,
merges
two
pr's
in
the
to
the
120
milestone.
So
that's,
basically
the
same
milestone
restriction
that
we
apply
for
for
the
release
branches
as
we
cut
a
new
branch.
So
basically
we
shift
it
so
that
only
only
issues
and
pr's
that
are
targeted
for
that
in
development
release
can
be
merged,
so
basically
we're
adding
an
additional
step
of
shifting
that
merge
that
milestone,
merge
restriction
to
120
instead
of
119.
K
The
we
want
to
focus
on
the
failing
tests,
then
documentation
and
cleanup,
and
then
smaller
bug
fixes
before
we
start
to
before.
We
start
to
move
into
a
full
reopen.
K
So,
during
that
low
risk
bug
fix
period,
we'll
we'll
ask
sig,
leads
chairs,
leads
and
milestone
maintainers
to
assess
the
criticality
of
of
the
various
bugs
that
are
in
the
milestone
for
them
before
are
that
are
in
their
area
in
general,
before
targeting
them
for
a
milestone
right,
so
training
the
queue
in
in
these
phases
of
failing
tests,
documentation,
cleanup
and
low
risk
bugs,
and
at
that
point
we're
gonna
ask
sigs
to
continually
look
at
their
ci
signal,
try
to
read
cause
and
fix
test
failures
before
we
officially
open
up
for
development.
K
So,
overall,
this
process
should,
by
my
calculation,
take
roughly
a
week
and
maybe
a
day
or
two
jordan
has
a
pr
that
he's
been
working
for
the
last.
It's
been
some
time.
It's
been
some
time
to
to
target
some
to
target
some
test
flakes
and,
and
that
I
think
we're
close.
I
think
once
we
do
the
release
we
should
be,
it
will
be
maybe
a
week
out
from
merging
that
jordan.
You
want
to
talk
about
that.
A
little
bit.
D
D
So
the
point
of
this
is
not
just
to
make
us
all
suffer
and
like
fix
tests,
but
it
turns
out
tests
are
actually
good
and
when
they
fail
sometimes
they're
telling
us
that
they're
real
bugs
so
there's
a
big
long
list
of
unit
test
flakes
that
were
being
masked
by
our
test
job
retrying
up
to
three
times
and
so
of
these.
You
know
I
don't
know
15
issues
we
found
there
were
actually
like
three
or
four
real
bugs,
so
that's
a
pretty
good
ratio.
So
this
is.
D
This
is
why
we
pay
attention
to
our
tests.
But
if
anyone
is
interested
tomorrow
in
sick
testing,
the
bi-weekly
meeting
I'm
actually
going
to
be
walking
through
sort
of
how
I
went
about
reproducing
some
of
these
things,
some
of
the
tools
and
techniques
for
stress
testing
and
taking
things
that
are
rare,
flakes
and
ci
and
actually
reproducing
them
like
really
frequently
and
really
quickly,
so
that
you
can
fix
them
anyway.
So
we've
got
a
few
hangers
on
here
that
we're
still
trying
to
figure
out.
D
If,
if
we
can't
get
those,
we
will
probably
enable
the
protection
and
do
something
to
mitigate
these
few
flakes,
while
we're
working
on
them
to
keep
new
things
from
getting
introduced.
A
A
Awesome
so
I'm
gonna
go
ahead
and
share
my
screen.
Really
quick,
just
go
through
the
heck,
it's
chrome
there.
It
is.
I'm
gonna
go
through
these
items,
just
really
quick
with
everyone
here.
So
just
for
some
numbers,
we
do
have
11
open
issues
targeting
or
I
think
these
are
yeah.
These
are
issues
targeting
119
of
those.
I
believe
it's
about.
A
Eight
last
check:
okay,
six
open
criticals,
so
there
are
two
without
owners
I
would
like
to
and
we
you
know
we
don't
have
to
do
this
right
now,
but
I
would
like
to
get
some
some
assignees
there
just
so
we
have
some
ownership.
Let
me
grab
the
pull
requests
as
far
as
pull
requests
go.
Let
me
refresh
this.
I
didn't
see
any
criticals,
but
did
see
eight
opens
and
obviously
you
know
some
of
these
aren't
aren't
imperative
to
get
solved
before
we
get
everything
buttoned
up
and
119
released.
A
But
again
I
did
see
two
that
didn't
have
any
assignees
and
so
going
to
work
with
definitely
want
to
work
with
the
team
on
that.
Are
there
any
other
items
that
anyone
has
heard
in
terms
of
critical
issues
or
release
blocking
bugs?
I
know
we
kind
of
we've.
I
I
talked
with
the
leads
last
week
and-
and
we
hadn't
heard
anything
but
did
want
to
open
that
up
for
discussion.
If
anyone
else
has
heard
anything
on
that
front.
C
One
thing
I
want
to
mention
real
quick
is
that
as
part
of
the
integration
jobs
failing
quite
a
bit
that
is
blocking
getting
some
things
merged
as
well
as
you
could
imagine,
because
the
pre-submit
is
also
failing.
So
just
keep
that
in
mind
and
looking
at
some
of
these
pr's,
I
know,
for
instance,
that
top
one
there
is
pretty
much
ready
to
go
in,
but
it's
it's.
It
has
a
hold
right
now
because
we're
just
continuously
retesting
and
it
was
failing.
A
Awesome,
no,
that
sounds
good
yeah.
When
one
domino
goes
knowing
more
or
more
will
fall,
it's
a
good
thing,
cool
cool!
Thank
you.
Dan.
K
A
Yeah,
if
anyone
needs
help
with
anything,
I'm
you
know
blocked
off
the
next
next
couple
days
to
help
with
anything.
So
please,
you
know,
don't
be
a
stranger
if
you
need
help
if
you're,
if
you
feel
swamped
or
anything
like
that,
feel
free
to
reach
out
to
me,
and
we
can
get
this
knocked
out
but
cool.
A
That
sounds
good
to
me.
Thank
you
so
much
everyone,
any
other
items
and
I'll
go
into
kind
of
like
final
comments,
and
then
we
can
now
we
could
put
a
pin
in
it.
A
Excellent
so
last
week
I
did
get
a
bunch
of
good
commentary
around
retro.
We
got
some
new
items
added
into
that
document.
Obviously
we
want
119
to
go
out
before
we
plan
the
retro
and
go
through
those
items.
I'm
going
to
sync
with
tim.
You
know
if
we
get
if
we,
if
we
launch
on
wednesday
I'll
kind
of
you
know,
take
a
temperature
see
if
thursday's
too
soon
to
have
that
retrospective.
A
Otherwise
we
can.
We
can
look
at
having
that
next
week
or
plan
that
accordingly,
but
if
you
have
anything
else
or
as
we
get
into
the
final
hours
of
this
release,
if
you
have
any
comments,
questions
concerns
please
be
sure
to
put
those
into
the
retro
and
we'll
address
those
as
we
go
through
the.
A
Wonderful
well,
thank
you
so
much
everyone.
I
hope
you
have
a
fantastic
monday,
nowhere
to
go,
but
up
and
no
nothing
else
to
do
other
than
release
119.
So
thank
you
very
much
for
your
hard
work.
Looking
forward
to
getting
this
out
this
week
and
yeah
again,
let
me
know
if
you
have
any
problems
and
I'll
get
things
knocked
out.
Thank
you.
So
much.
Everyone
have
a
great
day.