►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220406
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220406
A
All
right,
hello,
everyone,
my
name,
is
james
lavrock.
I
will
be
your
host
today.
I
am
the
release
team
lead
for
keeping
a124.
This
is
a
release
team
meeting
wednesday
6
april
2022.
This
is
week
13
of
the
release.
Can
I
just
before
we
get
started?
Can
I
remind
everyone
that
this
meeting,
as
with
all
of
our
meetings,
is
governed
by
the
kubernetes
code
of
conduct?
So
please
refer
to
that
document
for
your
interactions
with
us
here
today.
A
If
you
are
here
with
us,
live,
please
add
yourself
to
the
attendees
list
and
then
we
can
move
on.
I
have
no
open
discussion
items,
so
we
shall
move
on
to
updates,
beginning
with
enhancements
grace.
B
Hi
everyone
enhancement
status
is
green,
we
have
46
tracked
1435
filed
an
exception,
got
accepted
and
they
got
all
their
stuff,
and
so
they've
just
been
reintroduced
to
the
release.
I
realized.
I
made
a
few
mistakes
on
the
sheet
during
the
code
freeze
party
and
that
I
would
remove
the
issue
like
remove
their
mouse
or
remove
track.
Yes,
but
I
didn't
actually
update
it
on
the
sheet
to
be
removed
from
a
milestone.
B
So
I
think
there
was
two
occasions
of
that
and
then
one
of
them,
the
cab
author
pulled
out
after
code
freeze
by
citing
that
they
are
not
ready
for
test
freeze
or
something,
and
so
I
just
want
to
give
a
thank
you
to
megha
for
reaching
out
to
me
and
inform
me
of
all
those
situations
huge
help.
B
One
situation
that
just
came
up
this
morning
to
876
I
put
there
is
they
got
removed
in
enhancement
freeze
because
I
thought
they
were
going
into
beta
and
their
latest
milestone
is
1.23.
So
until
now,
it's
still
not
1.24,
but
all
their
code
is
merged,
and
so
I'm
looking
for
guidance
as
to
what
to
do
do.
They
need
to
file
an
enhancement
exception
request
because
they
already
got
their
code
in.
What's
the
play.
A
A
Okay,
yeah.
I
think
they
should
file
an
exception,
because
I'm
presuming
that
they
want
to
be
noted
that
they're
they're
here
and
I
suppose
the
alternative.
We
asked
them
to
pull
it
out,
but
I
really
don't
want
to
do
that
when
I
want
to
try
to
stabilize
master
as
much
as
the
main
branch
as
much
as
possible
right
now.
So,
okay
yeah,
let's,
let's
catch
up
with
that
one
offline
and
yeah,
I
would
accept
just
an
exception
and
we'll
just
get
it
added
and
we'll
just
what
it
is.
C
Hello,
everyone,
our
current
status,
is
yellow
on
massive
blocking.
We
have
currently
we
have
zero
feeling,
but
earlier
today
we
have
also
seen
four
failing
tests,
but
the
tests
are
passing
now
and
we
have
ten
flakes
in
which
three
of
them
are
verified
and
we
are,
we
are
absorbing
others
and
on
mastering
forming.
We
have
two
feeling
and
seven
fix
so
yeah.
A
All
right,
thank
you.
So
much
does
anyone
have
any
questions
for
ci
signal.
D
Hey
sorry,
I'm
outside,
so
I'm
on
mobile,
I'm
not
able
to
turn
my
video
on.
We
have
one
blocking
issue
and
if
you
open
prs,
I
think
four
prs
james.
Could
you
open
that
blogging
issue?
Please?
Oh
yeah.
D
So
this
is
a
tracker
for
the
go
118
changes
and
one
of
the
pr's
is
really
also
go
118.
I
think
it'll
coming
in
so
yeah.
F
D
Again,
118
tracker,
the
second
one,
one
attractor
and
this
one
something
I
think
we
have
this
just
failing
test
this
can
be
merged
in.
D
I
have
notified
on
the
on
the
issues
to
how
it
merged
before
the
test
freeze
but
yeah,
I'm
tracking
it
actively
and
all
the
four
pr's
I
have
notified
the
authors
to
please
merge
before
1pm
one
utc,
so
yeah
we'll.
A
D
I
have
to
go
back
and
then
ask
about
which
one
of
them
could
we
just
moved
out?
I
don't
think
we
are
going
to
take
the
ones
if
they
don't
qualify.
They're,
not
urgent,
I'll,
ask
about
the
criticality
of
the
issues
and
move
it
out.
The
one
thing
that
will
just
still
go
in
is
the
go.
118
merges
right
that
that
haven't.
A
A
Those
if
we
the
go
118
stuff,
is
pretty
critical.
To
my
mind.
If
the
rest
of
these
I
took,
I
did
take
a
brief
look
at
them
in
mostly
be
adding
tests
and
seeing
as
they're
not
marked
as
critical
urgent
I'd
say
we
should.
We
should
probably
just
remove
them
and
just
if
the
authors
feel
they're
critical
urgent,
we
can
have
a
conversation
around
that,
but
yeah.
D
A
D
Will
message
the
authors
again
saying:
hey,
we
can't
take
it
anymore,
but
if
you
think
we
absolutely
should
let
us
know-
and
I
will
call
it
sure.
A
All
right,
thank
you
very
much.
Anyone
have
any
questions
comments.
A
One
quick
one
to
make
by
the
way
is,
you
may
have
seen
us
scrolling
past
on
this
one,
the
fix
we
need
in
golang
for
for
kubernetes
that
we
discussed
in
our
previous
meetings
that
got
merged
to
the
118
branch,
so
we're
hopeful
it
will
land
in
go
118
1,
which
comes
out
tomorrow,
which
will
will
simplify
many
of
our
problems.
A
G
Hello
before
I
continue
to
say,
did
you
on
call
or
no?
G
No,
okay,
I'll?
Take
it
hello,
everyone.
I
think
that
the
current
status
is
a
very.
I
use
this
joke
yesterday,
a
very
greenish
sort
of
yellow,
almost
a
chartreuse
we're
in
a
very
good
spot.
I
think
we've
got
the
the
docs
ready
for
review
deadline
was
yesterday
and
we
are
at
one
with
no
pr
and
two
with
node
with
with
with
which
are
still
in
the
draft
er
state.
G
Now
one
of
the
ones
in
the
draft
pr
state
is
actually
the
docker
ship
removal
umbrella
issue,
which
is
probably
miscategorized
so
really
we're
at
one-on-one
there.
So
I'm
quite
pleased
with
where
we
are
so
now.
We've
got
a
run
to
the
docs
ready
deadline,
so
any
any
help
on
review
that
folks
can
provide
would
be
greatly
appreciated,
and
I
do
I
think,
I'll
probably
take
this
offline
with
you
james,
I'm
not
entirely
sure
what
we
do
with
the
particular
the
one
with
no
pr
still.
That's
that's
now.
G
That's
two
weeks
past
the
the,
although
it's
it's
also
one
the
it's
282086
which
just
came
in
with
a
with
a
an
exception
fairly
recently,
so
I'm
not
sure
quite
what
to
do
on
on
that.
G
This
one
just
came
back
in
and
then
the
the
other
one
is
two
eight
nine
six.
G
G
Why
I
was
doing
that
one
this
one?
Oh,
did
they
just
okay,
so
they've
got
a
draft
pr,
but
I
have
not.
Rather
they've
got
a
placeholder
pr.
I
don't
think
that
unless,
unless
they've
done
something
yeah
they've
got
no
files
changed
yet
so
I'm
not
sure
quite
what
we
need
to
do
to
to
get
that
one
moving
I'll
I'll
reach
out
to
the
to
the
sig
and
see
if
we
can't
unblock
that,
but
I'm
I'm
hoping
that
this
can
be
move
forward
in
the
next
today.
A
Yeah
yeah
in
general
at
this
point
it's
reaching
out
to
the
six
yeah
one
point
of
kind
of
of
note
or
discussion
we
had
about
that
recently
is:
can
you
dm
the
six
chairs,
like
like
post
a
link
post,
a
message
in
their
stick
channel
and
then
like
dm
them,
with
a
link
to
that
message
that
that
can
often
help
to
to
unblock
them,
because
six
years
tends
to
get
a
lot
a
lot
of
notifications.
They
can't
keep
yeah.
G
But
yeah
and
I
thought
just
in
the
chat
there
cc.
I
appreciate
that
I'll
I'll
chat
with
you
offline
about
that.
If
we
can
reach
out
to
that
particular
person,
I
imagine.
C
Yeah,
hey,
it's
paddle
from
release,
notes
and
the
status
currently
is
yellow
because
the
pr
for
alpha
four,
both
the
ps,
the
website,
pr
and
release,
notes
generation
pr
are
in
process.
There
are
some
revisions
going
on.
There
were
some
modifications
that
were
suggested
by
each
member
of
the
release
team
and
that
has
been
taken
into
account
consideration
by.
C
Is
currently
working
on
generating
the
prs
and
we
are
waiting
for
the
beta
card.
A
C
Maybe
it
would
be
great
if
you
can
go
through
the
prs
again
and
leave
any
comments
after
reviewing
it.
That
would
be
it.
A
Sure
we
could
take
a
look
at
that
all
right.
Any
questions
for
release,
notes.
F
Do
we
have
the
the
key
themes
ironed
out
yet
for
the
release.
E
A
Okay,
well,
thank
you
for
updates.
Moving
on
to
mickey
thomas.
F
F
One
question
james
I
had
for
you
was:
I
know,
we're
trying
to
figure
out
whether
or
not
there's
going
to
be
at
least
release
delay.
We
do
need
to
do
the
the
webinar
scheduling
with
the
cncf,
so
I
just
wanted
to
figure
out
like
when,
when
do
we
think
we
might
know
for
sure
when
that
can
be
scheduled,
is
that
post
thursday.
A
Post
thursday,
at
the
very
least,
I
think,
probably
once
the
rc's
out
on
monday,
we'll
have
a
good
idea.
Okay,
so
probably
hold
I'll
I'll
respond
to
an
email.
Actually
I
haven't
yet
and
just
kind
of
say
you
know
we're
holding
until
until
we
know
whether
there's
a
delay
or
not
to
avoid
scheduling
and
having
to
reschedule
it.
F
A
Yeah
yeah
I
mean
I
can
I
have
to
go
immediately
after
this
this
meeting,
so
if
you
want
to,
if
you
want
to
that's
fine.
F
And
then
the
last
thing
is
we
were
starting
work
on
the
release
blog.
I
was
hoping
to
get
all
the
removal
stuff
knocked
out
before
we
start
work
on
that,
but,
given
that
that's
been
taking
a
little
bit
longer
than
expected,
we're
just
gonna
start
working
on
our
first
draft
for
this
and
then
also
get
a
placeholder
pr
sure
cool.
A
Cool
all
right,
thank
you
and
it
looks
like
we've
got
the
link
for
the
major
themes.
Thank
you
very
much
pro.
Thank
you.
A
So
yeah
we
can
yeah.
We
could
take
a
look
through
that
excellent
right.
Okay,
any
questions
for
comms.
A
H
It's
an
indicator
of
that
we're
at
the
end
of
our
cycle
and
everybody's,
doing
a
great
job,
and
I
know
it's
going
to
get
a
little
crazy
for
some
of
you
coming
into
these
last
few
weeks.
So
if
you
need
any
support,
james
and
I
are
here-
and
we
will
help
navigate
this,
but
everything
else
is
looking
great.
A
No
all
right
well!
Thank
you
very
much
jose
for
the
update.
Moving
on
me.
First
item:
big
news:
congratulations
to
cece,
who
will
be
our
release,
lead
for
kubernetes
125.
A
cece
has
been
with
us
for
a
few
releases
now
and
he's
done
an
absolutely
excellent
job
and
I
am
super
excited
to
see,
see
her
leader
release
herself.
So
congratulations
cc.
A
Moving
on
to
more
mundane
matters,
we
accepted
one
exception
request.
This
actually
came
in
on
on
friday,
but
I
missed
it
because
I
can't
read,
but
we
have
done
through
that
and
that's
the
simple
one-liner
which
isn't
actually
a
code
changes
which
is
a
configuration
change.
So
we
got
that
in.
We
were
asked
to
re-evaluate
a
exception
request
that
we
rejected
before
which
we
did.
We
spent
a
little
while
looking
at
it.
A
We
eventually
determined
that
we
didn't
want
to
risk
the
stability
of
the
main
branch
at
this
point
when
we're
so
close
to
the
release.
So
we
we
ultimately
didn't
change
our
decision
and
stayed
with
the
rejection
at
this
point
other
than
the
one
that's
been
mentioned
above
about
the
enhancements
exception,
they're,
not
expecting
any
further
exceptions,
and-
and
they
would
have
to
be
really
critical-
release
blockers
to
be
allowed
in
at
this
stage.
A
I
think,
but
it
could
happen
and
probably
will,
as
these
things
go
all
right,
does
anyone
that's
what
I
have.
They
don't
have
any
questions
for
me.
B
Not
for
you,
but
I
just
added
an
item
to
the
agenda
at
the
top
yeah,
so
the
bug,
triage
team
and
hebba
has
been
looking
into
migrating
over
from
the
sheet
to
github
beta,
just
so
enhancement
can
kind
of
like
see
what
it
looks
like
and
it's
beautiful.
B
If
pebble's
here,
I
think
she's
looking
for
approval
for
a
github
action
issue.
So
no
we're
not
sure
what
is
what
is
the
way
going
forward.
I
think
bob
told
us
that
we
need
to
file
an
org
issue.
I'm
not
sure
what
else
from
here.
A
So
this
will
be:
oh
okay,
you
need
a
github
action
created
in
order
to
to
do
some
do
some
stuff,
so
this
is
for
going
forward.
125.
is
that
right.
B
This
is
for
right
now,
but
it's
not
critical
for
their
operation
and,
like
more
so,
we
can
look
at
it
going
forward.
Sure.
E
So
yeah
we
need,
we
need
to
create
a
github
app
and
then
use
it
to
create
a
github
action.
So
we
can
automate
the
the
update
for
the
project
we've
created,
because
now
we
we
are
updating
it
manually,
which
is
you
know
like
it's.
E
It's
not
great,
so
I
believe
we
we
had
like
a
good,
a
good
setup
as
as
as
a
view
and
how
we
can
how
we
can
use
the
project
so
far,
but
to
be
to
to
make
sure
that,
yes,
everything
is
like
end
to
end
will
work,
and
this
is
what
we
need
to
what
we
you
know
like
what
we
are
looking
for.
We
need
to
create
this
get
a
git
app
in
the
org
level
at
you
know
like
in
the
org
level
and
then
github
action
for
this
specific
project.
A
Okay,
I
must
admit-
I'm
not
100
in
the
process
here,
if,
if
bob
has
said
that
we
should
do
it
this
way,
that
makes
a
lot
of
sense.
I
would
expect
we
would
need
to
talk
to
the
sig
release.
Leads
would
be
my
expectation,
I
would
probably
you
can
tag
them
on
here
if
you
want,
but
it's
probably
easier
to
create
a
thread
and
sig
release
and
tag.
Sig
release
leads
and
get
them
in
there
and
they
probably
require
people.
A
I
don't
think
I
have
the
privileges
necessary
to
to
approve
this
myself.
For
example,
yeah
talk
to
them
and
see
what
we
can
get
and
get
done,
and
very
supportive.
Of
course,.
D
This
is
a
great
initiative,
because
today
we
create
a
spreadsheet,
which
is
a
very
bespoke.
Spreadsheet
has
a
lot
of
trouble.
I
said,
probably
spend
like
two
days
just
to
set
it
up,
because
it
has
to
be
copied
over
from
the
previous
release
and
stuff
like
that
yeah.
This
is
going
to
streamline
the
process
intensely.
A
Yeah
sounds
great.
Absolutely
a
plus
one,
like
I
say,
tag,
sig
release
leads
and
see
what
they
say
we
need
to
do.
We
can
go
from
there.
A
All
right
any
further
questions
any
points,
anything
else,
anything
anything
else.
Anyone
would
like
to
discuss.