►
From YouTube: Kubernetes 1.20 Release Team Meeting 20201005
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,
everyone
welcome
to
the
october
5th
I
think
yeah
october
5th
kubernetes
120
release
meeting.
My
name
is
jeremy.
I
am
the
release
lead
for
this.
The
cycle
this
meeting
is
recorded.
So
please
be
mindful
of
what
you
say.
The
meeting
will
appear
on
youtube
and,
of
course,
this
meeting
is
covered
by
the
kubernetes
code
of
contact,
which
can
be
summarized
as
be
excellent
to
one
another.
B
Hi
this
is
kirsten
the
enhancements
lead.
I
have
our
status
as
yellow,
but
it's
really
green
because
you
get
in
what
you
get
in
by
the
deadline
tomorrow
is
enhancements.
Freeze,
which
means
that
any
enhancement
that
isn't
going
to
be
tracked
after
tomorrow
won't
be
in
the
1.20
release
we
have
about.
We
have
39
tracked
right
now,
so
those
are
ones
that
are
definitely
going
forward
towards
code
freeze.
We
have
30
at
risk,
which
means
that
they
said
they
wanted
to
go
into
120,
but
they're
missing
something
in
their
cap.
B
A
good
portion
of
them
still
have
prs
out
that
are
like
complete,
so
they
just
have
to
get
merged
by
the
end
of
the
day
tomorrow,
which
I
think
a
good,
a
good
handful
of
them
will
we
have
43
untracked,
which
means
that
they
told
us
that
it's
just
not
going
to
be
in
this
release.
It's
actually
a
good
number.
Usually
people
don't
respond,
19
deferred,
which
means
like
they
want
to
be
in
a
different
release:
30
pending
and
14
unresponsive,
so
about
44
unresponsive
right
now.
B
The
unresponsive
14
are
ones
that
are
marked
unresponsive
because
they
had
been
unresponsive
for
like
multiple
release
cycles
and
then
the
pending
or
people
who
weren't
responsive
this
release
cycle.
But
those
30
have
not
responded
at
all
this
release
cycle,
so
we
have
about
44.,
but
a
third
of
them
didn't
respond
at
all
this
time.
Around
so
yeah
I
mean,
I
think,
we're
in
good
shape,
like
we
have
actually
a
good
number
of
tracked,
and
I
think
you
know
a
good
number
of
the
at-risk
are
going
to
go
in
as
well.
A
Yeah
for
sure,
do
you
want
to
send
a
notice
today,
just
reminding
people
of
the
enhancement
freeze
tomorrow.
C
A
That'd
be
super
helpful
of
the
at-risk
ones.
Do
you
would
it
be
worthwhile
for
us
to
try
to
help
get
some
reviews
for
those
things
I
assume
if
they
have
pr's
open
they're,
just
waiting
for.
B
I
mean
they're
they're
they're
people
who
can
get
reviews.
I
think,
like
the
ones
that
basically,
the
ones
that
have
pr's
up
right
now,
like
especially
the
newer
pr's,
are
definitely
people
who
can
get
reviews
for
their
pr's
if
they
want
them
and
there's
like
a
lot
of
motion
around
some
of
them.
So
I
don't.
I
don't
personally
think
that
there's
a
lot
of
people
that
need
a
lot
of
help,
getting
reviews
yeah.
A
Cool
sounds
great.
I
think
that
that
number
of
39
so
far
is
looking.
It
looks
pretty
good.
I
think,
compared
to
the
last
few
cycles.
Yeah.
B
B
It's
going
to
be
more
than
39
it'll,
probably
be
like
44
or
45,
so
yeah
there's
a
lot.
A
E
So,
let's
report
today
just
bear
with
me
one
second,
okay,
so
I've
I've
been
making
some
good
progress
on
automating
the
reporting,
so
I've
and
I've
thrown
a
link
into
into
a
generated
partially
generated
report
in
in
sheets
there.
On
that.
There's
two
pivot
tables
that
I've
I've
manually
put
together
today,
but
in
terms
of
the
progress
on
automating,
the
reporting
and
the
first
two
sheets
for
the
blocking
jobs
and
the
informing
jobs
are
generated
from
data
that
I'm
working
on
on
a
fork
of
test
infra.
E
So
on
my
testing
for
fork,
I
have
a
flaking
flake,
flake
tracker
branch
and
that
I
am
hoping
to
submit
a
pr
for
to
drop
it
into
the
experiments
folder
in
test
infra.
So
it
won't
be
supported
by
test
infra,
it's
a
kind
of
a
place
for
experiments,
so
we've,
so
that's
been
my
focus
over
the
last
a
few
days
on
the
board
and
I'm
kind
of
calling
this
where
we're
at
as
kind
of
red
at
the
moment,
because
we
have
a
lot
of
noise
in
our
signal.
E
A
large
portion
of
that
noise
is
owing
to
a
failure
to
extract
kubernetes
binaries
before
tests
kick
off
so
that's
and
causing
a
lot
of
jobs
to
be
flaky
and
as
a
team,
we're
kind
of
working
through
possible
root,
causes
and
possible
mitigations
and
work
grounds.
Essentially
with
a
failing.
E
We
have
a
curl,
that's
failing
because
of
a
possibly
because
of
a
weird,
open,
ssl
issue,
and
given
that
we're
pulling
down
files
from
a
gcp
booklet
that
you
know,
the
work
around
that
we'll
probably
go
with
is
to
use
gsutils
instead
of
coral.
So
that's
something
I
want
to
discuss
today
and
get
that
work.
Get
that
fixed
up
this
week.
E
You
know
so
so
across
master
blocking
we
have
nine
flaking
and
nine
passing
jobs,
and
then
I
have
nine
flaking
jobs
and
mass
from
forming
and
there's
a
couple
of
items
on
that
list
that
I
need
to
look
at
it
there
as
well
in
terms
of
one
two,
the
one
two:
zero
blocking
and
1.20
and
forming
jobs.
I
don't
know
if
they're
created
and
I'm
not
I've
not
looked
at
that.
So
I'll.
Look
at
that
this
week.
A
Great,
thank
you
so
most
of
the
failures
you
think
are
related
to
that
19386
issue
in
test
and
fraud
and.
E
Yeah:
okay,
it's
a
it's
a
lot
of
noise
that
we
need
to
get
rid
of.
We
we
haven't
done
full
root,
cause
analysis
on
it
yet,
but
in
terms
of
what
how
the
how
the
change
on
the
ci
infrastructure
that
brought
this
about,
so
we
haven't
done
that
level
of
digging
and
but
I
don't
think
any
of
us
have
time
or
the
access
to
do
that
or
ca,
and
so,
but
we're
reasonably
confident
that
that
that
if
we
either
upgrade
coral
or
or
work
around,
it
should
be
good.
E
A
E
A
A
beautiful
issue,
I
love
that
all
right.
Thank
you
so
much
for
that.
Is
there
anything
that
you
need
in
addition
to
that,
or
it
sounds
like
you
guys.
Have
it
pretty
much
under
control.
E
Yeah
I'd
if
anyone
was
interested
to
take
a
look
at
that
that
that
google
sheet
and
wade
through
it-
and
it's
not
quite
as
I
wanted
to
be-
it's
not
how
that
automated
report-
it's
not
the
final
home
for
that
holiday
report,
and
I
have
ideas
in
that.
But
it's
a
temporary
home
for
it's
a
temporary
home
for
the
report.
Okay,
but
but
it's
fresh,
it's
new,
it
may
contain
bugs
so
any
feedback.
I'd
appreciate.
F
A
Cool,
thank
you
so
much
for
that
update
any
questions
for
ci
signal.
I
see
another
message
in
chat.
Nico
asked
rob,
can
you
add
him
and
jorge
in
that
pr.
D
A
A
All
right,
moving
on
to
docs
looks
like
kristen's
gonna.
Give
us
update
today.
G
I
created
a
pr
to
merge
master
into
the
dev
120
advanced,
to
keep
it
in
sync
and
between
the
time
I
wrote
this
update,
and
now
it's
already
been
merged,
so
yay
and
we
did
assign
all
the
enhancements
to
our
team
members
to
all
the
shadows
and
we'll
start
tracking
those
this
week
after
enhancements
freeze
and
that's
it
for
docs
this
week.
Thanks.
A
Cool.
Thank
you
for
that
update
any
questions
for
docs.
C
Hi
jackie
here
release
no
shadow.
Our
status
is
green.
Last
week
we
had
shadow
on
boarding,
someone
bordered
all
the
shadows.
We
also
merged
the
release,
notes
for
kubernetes
one
two,
oh
alpha
one
and
this
week
we'll
start
reviewing
all
the
notes
using
the
new
fix
command
this
week.
A
Cool
great
that
the
orientation
was
was
cool
to
sit
through.
I
hadn't
had
much
exposure
to
release
note,
so
it
was
cool
to
see
that
any
questions
for
the
release
notes,
team.
A
All
right
moving
on
to
comms
so
columns
this
week
we
are
green,
we're
still
tracking
enhancements
and
and
reviewing
for
potential
plug
and
release
blog
and
future
blog
posts.
We
also
added
a
new
team
member
since
last
week,
xander
gravinsky
alexander.
Do
you
want
to.
H
Meet
yourself
and
give
us
an
introduction,
sure
I'm
xander
nice
to
see
so
many
familiar
faces
here.
I
work
at
apple
previously,
hashicorp
been
kind
of
in
like
the
kubernetes
community,
doing
kubernetes
adjacent
stuff
for
a
while,
but
this
is
my
first
time
on
a
release
cycle,
so
super
excited
to
be
here
and
get
the
chance
to
work
with
all
you
folks.
A
That's
that's
about
it
from
release
comms
for
this
week,
cool
thanks
for
the
update
and
welcome
xander
we're
happy
to
have
you
next
up
is
release
branch
management.
Marco
couldn't
make
it
today
and
basically
there's
no
real
update
there,
except
next
week
they
are
still
planning
on
cutting
the
alpha
2
release
that'll
happen
on
the
13th,
so
just
stay
tuned
for
that
and
release
notes.
You
guys
can
kind
of
watch
that
and
see
how
it
goes.
I
Thanks,
jeremy,
hello,
everybody
hope
everybody
had
a
nice
weekend.
I
want
to
first
say
it's
great
to
see
so
many
shadows,
giving
updates
already,
if
you're
a
shadow
you
can
give
updates
in
here
too
just
talk
with
your
lead
and
feel
free
to
give
updates.
So
for
those
shadows
who
are
already
giving
updates
great
excited
to
see
many
more
first
thing
is,
as
we
all
know,
shadow
selection
has
been
completed.
I
What
I
would
like
to
happen
is
we
did
the
shadow
orientation
as
a
as
a
team.
Last
thursday,
I
conducted
one
I'm
going
to
try
and
get
the
recording
to
that
and
I'll
send
it
out
to
everybody
who
couldn't
make
it
feel
free
to
have
take
a
look
at
that
and
and
ping
me
with
any
questions
you
may
have,
and
you
should
be
having
orientations
which
eat
with
each
of
your
teams.
I
know
I
heard
an
update
from
release
notes.
I
So
if
you
haven't
had
an
orientation,
the
leads
should
be
orientating
and
bringing
you
on
board
as
a
set
of
shadows.
So
that'll
be
time
for
you
to
meet
your
lead
and
other
shadows
and
figure
out
how
you're
going
to
be
working
throughout
this
cycle.
If
you
haven't.
I
A
Great
thanks
lucky
any
questions
for
lockheed
nope,
okay,
moving
on,
if
you
have
any
questions
during
this
time,
I'll
just
mention
again
feel
free
to
reach
out
to
me
or
feel
free
to
reach
out
to
lockheed.
Both
of
us
are
happy
to
answer
any
of
those
questions
as
we
go
next
up.
My
update
this
week
is
obviously
enhancement
freeze,
as
we
mentioned
so
we'll
have
a
good
idea
about
what
things
are
going
to
land
in
the
release
you
know
hopefully
after
tomorrow.
A
Obviously
things
can
fail,
can
fall
out
by
code
freeze,
which
would
be
the
next
major
milestone
after
that
on
november
12th
and
we're
still
shooting
for
december
8th
as
our
release
date.
One
small
update.
We
sent
a
doodle
out
last
week
to
kind
of
collect
times
that
would
be
good
for
having
a
more
asia
pacific.
Maybe
europe
friendly
time,
we
didn't
get
a
ton
of
responses
on
it,
but
the
time
that
ended
up
winning
is
essentially
6
a.m.
Mountain
time,
5
30
p.m,
in
india.
A
So
kind
of
you
know
across
the
time
zones
there
so
like
two,
two
o'clock-ish,
I
think
in
berlin
central
european
time,
so
we'll
send
a
meeting
invite
out
for
that
and
we'll
ping
just
to
kind
of
coordinate
how
we
do
asynchronous
updates
and
just
ensure
we
have
continuity
between
those
meetings
and
then
we'll
revisit
it
after
a
couple
weeks
to
see
how
it's
going.
A
If
nobody
is
attending,
then
we'll
just
cancel
that
come
back
to
one
meeting,
but
we'll
see
how
this
goes
so
be
on
the
lookout
for
an
update
there
sometime
today
and
that's
about
it
for
me,
we
don't
have
an
update
from
scalability
it's
pretty
early
in
cycle,
so
there's
not
a
whole
lot
of
changes.
J
Just
the
retro
items
I
think,
we've
gone
through
all
of
the
old
retro
items
now
through
our
fish
efficient,
slack
thread
mechanism,
the
119
retro
items,
though
I
think
we
talked
about
these
last
week.
We
said
something
that
I
looked
in
the
agenda
and
I
didn't
see
what
that
something
was.
A
All
right,
great,
open
discussion,
anybody
have
anything
they
want
to
bring
up
one
one
thing
to
just
come
back
to
as
we're
going
through
the
cycle.
If
you
have
any
items
that
you
think
would
be
great
areas
for
improvement
or
things
we're
doing
really
well
right
now,
please
add
them
to
the
retro
doc,
which
is
linked
in
the
open
discussion
section.
A
A
Next
up,
we
can
just
walk
through
the
board
real,
quick
and
see.
If
there's
been
any
major
updates,
we
won't
walk
through
every
single
item,
but
look
at
the
major
ones.
Let
me
share
my.
A
A
All
right,
let's
get
rid
of
this
thing,
anything
done.
We
cleaned
up
the
owner
aliases.
It
was
just
a
small
thing
that
hadn't
hadn't
been
done
in
the
first
week
of
the
release.
A
All
the
leads
should
be
added,
so
you
should
be
getting
additional
pings
for
reviews
for
things
that
go
into
sig
release
any
other
items
anybody
wants
to
mention.
I
did
have
one
for
adding
the
cncf
inclusive
speaker
training
as
a
requirement
for
the
lead
onboarding,
so
the
pr
open
for
that
and
we're
just
waiting
for
the
rest
of
the
lead
team
to
to
go
through
and
complete
that
training.
Just
to
make
sure
we
wanted
to
make
sure
we
were
in
sync
with
what
the
requirement
was
for
the
sig
chairs
and
the
tech
leads.
A
J
Just
that
about
an
hour
ago,
I
had
a
chat
with
the
release,
leads
about
cs
signal
and
what
we
want
to
do
there.
So
I
hope
we
will
have
a
plan
to
present
to
everyone
soon
like
we
have
it
and
we
have
it.
We
just
need
to
I'll
sign
off
on
it,
so
that
would,
if
you're
into
ci
signal
or
shadow,
then
you
might
want
to
check
in
with
with
me
and
jorge.
J
A
Yeah,
I
think,
that's
dependent
on
us
pushing
forward
with
the
res
the
changes
to
the
enhancements
process
that
we're
collectively
calling
the
receipts
system.
A
Part
of
that,
I
think
we're
gonna
move
away
from
some
of
this.
You
know
the
enhancements
team
pinging
away.
What's
the
status
of
this?
Are
you
going
to
be
in
120
or
not
to
to
a
more
explicit
people
have
to
move?
You
know
make
a
pr
to
put
something
into
the
release
and
I
think,
as
we
work
through
that
process,
we
can
define
what
this
one
looks
like.
J
We
define
what
the
process
looks
like
yeah.
It
makes
sense
and
just
in
the
release
notes
channel,
we
talked
about
keps
website,
so
basically
that
being
an
objective
for
120,
like
being
able
to
have
a
website
with
the
caps
that
you
could
query
by
author
status,
etc.
So
if
you
are
interested
in
that
topic,
go
to
the
release,
notes,
channel
and
there's
a
thread
from
friday,
where
you'll
see
some
folks
pinging
in
suggestions
how
it
actually,
how
to
do
it.
A
A
Cool
well,
I
think
we
can
end
a
little
early
today
and
give
people
some
time
back
to
to
work
towards
enhancements,
freeze
or
anything
else
they're
working
on,
unless
anybody
has
anything
they
want
to
bring
up
now.