►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200608
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,
hello,
hello,
hello:
this
is
a
release
team
meeting
for
the
119
kubernetes
release,
I'm
Taylor
Dolezal,
your
host
and
release
lead
for
the
cycle.
I
want
to
wish
you
all
a
fantastic
Monday,
no
matter
where
you're
at
in
your
day.
This
is
a
kubernetes
community
meeting.
So
please
divide
by
the
kubernetes
code
of
conduct,
which
is
the
Excel
to
one
another.
Today
we
are
going
to
really
just
go
through
see.
What's
going
on
with
everyone.
A
I
know
last
week
was
in
intense,
to
say
the
very
least,
a
lots
going
on
lots
of
good
discussion,
reflection
and
we're
kind
of
picking
it
up
again.
This
week,
I
do
have
an
announcement
on
just
calendar
and
what
we
can
expect
we're
going
to
shift.
That
forward
is
the
is
basically
the
TLDR
on
that
front,
but
I'll
cover
that
here
at
the
end.
So
if
things
are
taking
a
bit
longer
to
get
done,
don't
worry
about
it.
We're
going
to
revisit
that
a
little
bit
later
today
and
then
have
news
to
you.
Should.
B
A
So
so
the
the
thought
on
that
front
was
really
to
push
everything
out
two
weeks.
So
today
we
had
code
freeze
scheduled.
We
are
thinking
of
pushing
that
out
by
two
weeks,
looking
at
all
of
the
milestones
and
then
moving
that
forward
by
two
weeks.
I
think
the
only
thing
I
can
think
of
that
might
be
potential
impact
is
cube
cons.
A
So
that's
really
where
I'd
have
my
eyes
on
definitely
wants
a
noodle
on
that
and
look
through
how
that
schedule
falls
kind
of
like
where
we
can
move
things
such
there
won't
be
such
you
know.
People
don't
be
rushing
before
or
after
keep
kind
to
knock
things
out,
but
I
think
that's.
My
only
concern
not
sure
how
everyone
else
feels,
but
would
love
to
open
that
up
before
yeah.
B
So
that's
also
my
biggest
concern
when
we
initially
did
the
the
updates
to
the
schedule.
The
first
one
that
I
proposed
was
included
a
two-week
blackout
period
for
cube
con
headway.
We
actually
ended
up
mixing
that
one
because
it
looked
like
it
was.
It
seemed
better
to
close
the
release
cycle
ahead
of
cube
con.
So
I
think
the
current
cycle
gives
us
a
buffer
of
a
weekend
change
before
cube
con,
something
like
that.
I
think.
B
Maybe,
before
the
new
cube,
con
dates
were
published
and
the
so
I
think
yet
I
think
the
problem
would
be
dancing
around
cube
con.
We
can
push
so
I
again
from
what
Taylor
said.
The
idea
would
be
to
target
code
freeze
two
weeks
later
than
it's
currently
targeted
and
then
move
all
of
the
the
move.
All
the
milestones
that
are
behind
that
forward
two
weeks
as
well.
That
would
leave
us
I.
A
A
C
Just
have
one
quick
question,
so
thanks.
Thank
you,
folks,
for
being
empathetic
and
understanding
during
these
things.
It's
nice
to
be
a
part
of
this
community
in
this
reduce
team
moving
code
freeze.
Does
that
mean
that
we
can
move
our
dogs
deadline?
Also
I
know
the
code
freeze
on
June,
21st,
think
dogs.
Initial.
The
first
deadline
is
on
12th
of
June,
so
I
just
don't
want
to
bring
that
up
too.
So
yeah.
B
C
E
Hi,
everyone
I
hope
you
are
doing
well
with
what
is
going
on
around
us
and
yeah.
So
as
for
the
enhancements
update,
we
are
green.
We
are
currently
going
a
bit
slow
on
pinging.
We
practically
did
not
bring
anyone
in
the
last
week,
considering
all
the
circumstances,
and
since
this
is
a
tough
time
for
everyone,
we
thought
it's
better
to
give
everyone
their
own
time
in
going
through
the
work
and
setting
their
own
pace.
E
We
have
at
one
exception,
request
last
week,
which
we
are
discussing
with
the
cigarette
now
whether
to
accept
it
or
not
and
other
than
that,
the
we
are
tracking
44
announcements.
14
are
in
alpha
17
in
beta
and
13
in
stable.
Apart
from
that,
we
don't
have
any
other
updates.
So
any
questions
or
comments.
F
With
Dan
hey
folks,
we
are
red
today,
mostly
just
because
there's
a
PR
merged
that
turned
a
test
red
on
master
blocking.
So
we
are
by
definition
red,
but
it
shouldn't
be
a
too
big
of
a
deal
and
we've
already
pained
the
person
who
opened
that
PR
I'm,
not
exactly
sure
that
that
is
the
the
route
calls.
But
it
looks
like
it
could
definitely
be
related.
So
we'll
be
continuing
to
monitor
that
the
other
flaky
tests
on
master
blocking
are
still
related
to
the
kind
test
timeouts.
F
F
I'm
master,
informing,
nollie
tests
that
are
failing
are
the
windows
tests
per
usual,
which
we
actually
made
some
progress
with
an
issue
that
was
raised
there,
but
now
it's
back
to
its
regular
level
of
failure.
I
pinged
sig
windows
a
couple
times
over
the
last
week
and
trying
to
get
an
answer
if
they
are
getting
any
any
value
from
this
and
if
not,
if
they
need
to
be
on
the
informing
dashboards
because
they
have
been
failing
for
a
months
and
so
we'll
continue
to
monitor.
F
That,
of
course,
and
then
a
new
test
on
the
open,
stack,
conformance
job
was
introduced
and
it
has
not
passed
since
being
introduced.
So
I've
pinged
the
the
testing
folks
to
take
a
look
at
that
and
see
if
we
need
to
do
a
rebirth
there
or
see.
What's
going
on
outside
of
that,
the
other
flaky
tests
on
informing
are
kind
of
the
same
ones.
We've
seen
Cube
admin
tests
still
having
some
some
timeouts,
and
then
there
is
a
network
signet
work
test
on
the
GC
master
scale
correctness,
that's
also
showing
on
a
few
other
jobs.
F
A
G
So
our
numbers
are
pretty
stable.
We
I
think
we'd
all
pained
our
open
bug,
issues
and
PRS
last
week
ahead
of
the
expected
blackout
date.
So
I
don't
know
how
much
there's
a
little
activity
you
can
see.
Some
of
the
open
issues
are
down,
but
otherwise
most
of
the
numbers
are
stable,
so
I
think
we're
green,
especially
especially
we're
gonna
add
two
weeks:
it's
yeah
about
the
last
week,
I
think
was
definitely
a
wash
or
for
a
lot
of
people.
So.
C
D
B
C
Agree
I
had
the
similar
tag,
but
I
would
I
just
want
to
bring
it
out,
because
this
is
the
first
time
I'm
in
this
situation.
This
is
my
second
release.
It's
like
I
still,
the
first
one
I
was
a
shadow
and
this
time
on
the
beach,
so
I
just
want
to
bring
it
up
for
more
hear
from
more
experienced
folks
and
and
vices.
Thank
you.
Yeah.
B
I
Conscious
of
our
green
reached
out
for
the
future
blocks,
we
have
three
feature
box
blocks
at
the
moment,
confirmed
waiting
for
some
couple
of
more
responses,
but
it
looks
good.
Potentially
we
get
even
more
than
the
normal
5,
which
we
expect,
maybe
we'll
ending
at
around
7
or
so,
which
is
quite
nice.
A
A
B
Just
a
note
on
zero,
three
three,
so
essentially
what
was
done
there?
Was
we
I?
So
we
have
two
branches
that
we
maintain
4k
release.
One
is
master
branch
and
the
other
one
is
to
build
admins
branch,
so
the
build
admins
branch
is
used
by
the
build
admins
which
are
Googlers,
who
have
who
have
the
power
to
cut
the
Deb's
and
rpms
for
for
patch
releases.
So
the
the
build
admins
branch
is
essentially
an
older
version
of
master
that
has
patches
on
top
of
it,
so
zero.
B
Three
three
is
a
forward
port
of
the
updates
that
we've
made
in
the
build
admins
branch
into
master
to
essentially
get
rid
of
the
build
admins
branch.
The
idea
is
that
we
want
to
push
the
build
admins
towards
how
many
times
have
I
said
Bildad
minutes
now
towards
using
using
master
and
updating
their
tools
to
use
master
as
opposed
to
using
an
older
version,
because
we
can't
depend
on
and
it's
it's
tricky
to
maintain.
You
know
if
there
are
basil
changes.
B
If
there
are
test
changes
that
have
to
happen
in
our
images,
we
have
to
maintain
those
in
two
branches.
I'd
much
prefer
that
we
just
do
that
on
master,
so
I'm
gonna
be
sending
an
email
out
to
them
later
today
to
talk
a
little
bit
about
that,
but
yeah.
That
one
includes
the
big
fix
for
for
that
branch.
For
that
release
is
that
it
includes
a
mitigation
to
an
update
to
our
specs
update
to
our
package
or
Deb
in
rpm
specs
to
mitigate
the
CNI
man-in-the-middle
attack
that
was
announced
on
June
1st.
So
thank.
J
We'll
do
the
same
for
that
and
then
also
just
want
to
really
encourage
folks,
if
you
have
questions
as
a
shadow
reach
out
to
your
leads
reach
out
to
me,
reach
out
to
Taylor
any
of
the
other
folks
here
who
have
some
experience
in
the
past
started
a
simple
question
start
some
dialogue.
If
you're
not
sure
about
that
feel
free
to
ping
me
feel
free
to
use
the
shadows.
Mailing
list
as
well
wanna
make
sure
that
people
feel
comfortable
asking
questions.
A
Absolutely
agree,
thank
you
Tim
and
yeah.
It's
again.
This
is
this.
Is
the
best
place
to
ask
questions,
we're
all
here
to
help
and
want
to
see
everyone
be
successful,
because
if,
if
we're
not,
we
can't
be
successful
as
a
team
collectively,
so
a
huge
plus
one
on
that
front
this
week
biggest
update
I
have
for
you
is
what
we
had
already
talked
about
is
the
fact
that
we'll
be
pushing
out
some
deadlines
by
about
two
weeks.
A
Others
one
week
we'll
get
that
PR
here
a
little
bit
later
today,
and
we
can
kind
of
start
dialogue
around
that.
But
please
again,
let
me
know
if
there
or
your
leads
know,
if
there's
anything
that
you
think
needs
to
be
addressed
or
might
be
a
special
situation
leading
up
to
cute
con
or
anything
on.
The
schedule
looks
like
that
other
than
that
I
don't
have
anything
and
would
like
to
open
it
up
to
the
floor.
If
anybody
has
anything
else,.
A
A
Think
we
had
one
thing
in
our
nuts
from
the
previous
session:
it's
one
thing:
I
saw
but
I
know
Laurie
Apple
again
she
presented
last
week
and
has
been
aired.
Last
meeting
and
she's
been
really
helpful
and
kind
of
fixing
looking
at
fixing
a
lot
of
the
process
around
the
release
cycle,
kind
of
getting
rid
of
some
of
the
cruft
and
things
that
we
either
have
to
do
know
and
also
pick
up.
A
So
there
are
meetings
working
through
that
I
think
that
she's
posted
a
couple
links
in
the
cig
release
slack
channel
so
be
sure
to
check
that
out.
I
believe
there's
another
session
happening
on
Wednesday
9:00
to
10:00
Pacific
and
we're
just
talking
through
a
couple
things:
they're
gonna
try
to
get
that
recorded
and
available
for
anyone
that
wants
to
watch
it
and
is
not
able
to
attend.
B
So,
to
add
on
to
the
Laurie
stuff,
Laurie
is
doing
a
phenomenal
job
and
and
wrangling
a
lot
of
the
stuff.
This
is,
this
is
years
of
I,
think
I
think
it's
indicative
of
years
of
technical
debt
within
the
project,
that's
kind
of
just
ballooned
after
some
time
and
led
to
kind
of
a
you
know,
less
than
optimal
processes
and
in
certain
places
what
you
can
do
as
a
release
team
member
is,
is
one
attend.
Those
meetings
give
honest
feedback.
B
B
So
you
know
a
lot
of
us
have
been
doing
this
for
a
while
and
are
kind
of
we're
not
necessarily
set
in
our
ways,
but
we
we
know
that
a
thing
works
to
a
certain
level
of
efficiency
and-
and
it
works
well
enough
for
the
time
being
right.
If
you
have
things
that
you
see
that
can
be
fixed,
you
know
so
like
really
interesting
to
see
stuff.
Like
you
know
the
release,
notes,
release
knows
changes
take
off
and
to
see
you
know,
enhancement,
issue
open,
for
you
know
applying
machine
learning
on
top
of
release.
B
Now
it's
right
like
stuff
like
that,
if
you
have
ideas
and
and
as
far
you
know
as
far
out
as
you
may
think,
they
are
please
please
let
us
know
right.
The
the
second
thing
you
can
be
doing.
Is
it's
it's
really.
It's
really
your
voice
right!
You
know.
The
first
thing
is
like
use
your
voice,
don't
feel
that
you
don't
feel
that
you
don't
have
one
on
this
team.
This
is
a
team
that
is
as
large
as
it
is
for
a
reason.
B
So
you
know
a
lot
of
what
would
happen
prior
is
is
that
we
would
have
a
retro
we'd,
write,
pages
and
pages
of
wonderful
feedback
for
the
cycle
and
and
then
we
would
kind
of
review
it
close
to
the
next
retro
right
and
that's
not
really
useful
right.
So
turning
turning
the
retro
items
into
really
actionable
feedback
and
then
once
we
turned
it
into
actual
actionable
items,
whether
whether
it
be
in
an
issue
or
becomes
a
calendar
event
becomes,
you
know
some
process
change.
We
have
to
then
do
that
work
right.
B
So
if
there
is
work
that
is
assigned
to
you
right
now,
please
please
work
on
it.
If
there
is
work
that
is
assigned
to
you
know
your
previous
lead,
someone
who
is
previously
on
the
release
team,
and
you
see
that
that
work
is
slowing
down,
offer
to
pick
it
up,
see
where
they're
at
I
think
that
you
know
one
of
the
the
things
that
we
lose
in
time
is
the
fact
that
there
is
a
lack
of
continuity
or
a
bit
of
a
lack
of
continuity
between
the
you
know.
B
The
leads
are
the
team
for
from
the
old
cycle
and
the
team
from
the
new,
so
so
take
a
little
extra
effort
in
and
kind
of
digging
through
what
we
have
on
our
you
know,
and
everything
that's
on
that
backlog
is
kind
of
the
stuff.
That
Laurie
is
asking
you
about
right
now,
right
so
take
some
time
to
dig
into
stuff.
That's
previously
assigned
to
old
team
members
and
stuff
that
seems
to
be
seems
to
be
kind
of
stalling
out
right
and
I
guess
the
third
one
is
also
take
time
for
yourself
right.
B
If
you
we
got
a
lot
going
on
right
now
and
if
you
feel
you
need
that
time,
tell
tell
someone
tell
someone
I
have
not
been.
You
know,
first,
first
and
foremost,
if
you
feel
that
you
can
you
know
you,
can
you
have
an
honest
dialogue
with
your
with
your
role?
Lead.
Do
that
you
know
if
you
need
that
time.
Take
that
time
right.
This
is.
This
is
work
that
we
do
upstream
and
it
is
free
work
that
we
do
right.
So
this
is
not
your
day-to-day
job.
B
If
you
need
that
time,
this
is
not
the
most
important
thing
right
now
right.
So
so
let
someone
know
and
and
and
have
the
team,
have
the
team
help
you
and
giving
giving
you
the
time
that
you
need
and
and
I
guess
for
I'm
not
always
on
these
calls
because
outlook.