►
From YouTube: Kubernetes Release Team Meeting 20210922
Description
For more info, see https://git.k8s.io/community/sig-release
A
Hello:
okay,
hello:
everyone
welcome
to
the
kubernetes
1.23
weekly
release
team
meeting.
This
is
week
five
of
the
release
cycle.
Do
you
want
to
make
a
note
that
we
are
a
kubernetes
project
and
we
do
abide
by
the
cncf
code
of
conduct,
which
boils
down
to
just
to
be
excellent
and
and
kind
to
each
other,
and
this
video?
This
meeting
is
recorded
and
posted
to
youtube.
A
First
off,
please
sign
in
here
and
your
name,
your
role
and
your
pronouns
as
well.
I've
noticed
a
few
people
having
issues
and
they
they
could
only
comment.
A
So
I'm
going
to
take
a
look
and
to
see
pretty
much
anyone
who
is
in
the
release
dash
team.
Google
group
should
have
the
right
to
edit
this.
So
I
did
make
some
changes
just
added
some
emails,
but
didn't
actually
remove
anyone,
so
this
shouldn't
have
affected
any
person,
except
for
one
person
that
did
ask
for
their
email
to
be
updated.
So
I'll
take
a
look.
You
know
jesse.
I
saw
you
commenting
also
sam.
I
saw
you
commenting
as
well
mickey
now
I
see
editing.
A
That
was
one
part
one
email
I
did
did
add,
or
your
additional
email
as
well,
and
I
think
I
believe
karen
or
no
thank
someone
else
from
the
release
comms
as
well.
A
So
with
that,
let's
start
off
with
intro
to
myself
my
name
is
ray
lahano.
This
is
your
first
time
me
coming
to
this
meeting.
I'm
the
1.23
release
lead
I'm
going
to
ask
everyone
here
and
want
to
sign
in
I'm
going
to
start
off
with
open
discussions
before
we
go
into
the
updates.
I'm
going
to
start
off
with
james
with
this
github
discussion
on
the
release
team
selection
process.
B
So
this
is
a
topic
which
we
discussed
at
the
wider
sig
release
meeting
yesterday
and
the
decision
there
was
to
break
this
out
into
a
github
discussion.
So
you
can
see
there's
a
whole
lot
of
text
there,
I'm
not
going
to
read
it
all
to
you,
but
the
summary
is
that
I
and
others
feel
that
the
selection
process
for
the
release
team-
it
will
release
him
in
general.
In
particular,
release
team
shadows
could
be
improved,
especially
at
the
scale.
It
is
now
where
we
had
in
this
cycle.
185
applicants
for
about
24-25
spaces.
B
So
what
I'm
really
looking
for
and
mention
it
now
is
opinions
from
people
or
or
feedback
on
the
process
in
in
general.
Obviously,
this
is
the
only
vehicle
for
feedback.
We
have
the
retros
as
well,
which
are
some
of
the
comments
have
been
brought
into
this,
but
really
from
anyone,
but
especially
shadow
applicants
and
especially
multiple
time.
Shadow
applicants
for
rna
would
absolutely
love
to
have
feedback.
A
Thank
you,
james
yeah,
so
I
think
it's
actually.
We
actually
get
better
insight
from
shadows
who
applied
multiple
times,
like
james
mentioned,
what
that
was
like
and
their
opinions
on
what
can
be
improved.
A
James
listed
out
several
good
bullets
here
that
I'm
not
going
to
review,
but
please
take
the
time,
especially
for
those
shadows
who
have
not
you
know,
took
several
tries
to
to
be
selected,
and
also
this
is
out
on
this
link
to
this
to
this
discussions
on
the
sick
release
channel
as
well,
so
it'll
be
good
to
even
like
possibly
send
this
out
to
shadows,
who
haven't
been
selected
after
a
number
of
tries
as
well,
because
I
know
we
could
always
improve
on
the
selection
process.
A
With
that
in
mind,
it's
always
very
hard
to
select
shadows.
As
james
mentioned,
we
have
a
very
low
number
of
shadow
roles
available
for
release.
Like
you
know,
we
had
over
180
applicants
this
time
for
about
24
shadow
spots,
so
it's
always
very
difficult
to
select
the
shadows
for
a
release
cycle,
any
comments
or
questions
regarding
that.
A
All
right
and
move
on
to
another
enhancement
issue,
so
this
was
actually
brought
up
in
a
slack
thread
and
grace
reminded
me
last
meeting
cycle
that
we
should
talk
about
here
as
well.
A
So
in
the
in
the
cap
in
a
which
is
a
kubernetes
enhancement
proposal
there
is
you
select
what
stage
that
the
enhancement
is
in,
but
sometimes
enhancements
don't
go
through
that
stage
for
for
a
particular
release.
A
So
some
so
several
contributors
feel
like
it
needs
to
be
revised
on
how
we
determine
the
kept
stages
and
how
we,
how
kept
transition
into
those
stages,
so
there's
enhancement
issue
with
some
suggestions
here
I
do
advise.
I
do
suggest
everyone
to
go
over
them.
Also,
if
you're
not
familiar
with
with
caps
himself,
we
do
have
under
the
kubernetes
enhancements
repo.
We
there
is
a
little
reveal
on
caps
as
well
just
to
take
a
look
into
what
is
a
kubernetes
enhancement,
enhancement
proposal.
A
What
are
the
required
fields,
and
you
could
go
back
and
take
a
look
into
this
enhancement
issue,
to
see
what
is
proposed,
and
why
this?
Why
contributors
prefer
something
that
has
a
turn,
and
it
has
a
transitional
phase
in
the
kubernetes
enhancement
proposal,
finding
that
it
has
been
brought
up
before,
but
it
is
brought
up
now
and
we
should
definitely
take
a
look
at
it,
especially
going
into
since
there's
a
little
bit
more
of
a
break
between
123
and
124
with
the
holidays.
But
it
might
be
a
good
time
to
start.
A
We
may
not
make
the
change
then,
but
we
could
start
looking
into
what
what
changes
we
can
do
to
improve
the
enhancement
process
in
our
recycle.
So
do
ask
everyone
to
take
a
look
into
this
enhancement
issue.
You
know
if
you
could
also
do
a
little
more
research
on
your
own
as
well
and
to
even
provide
feedback.
If
you,
if
you'd,
like
any
comments
or
questions
with
that.
A
A
I
get
related
github
discussion
on
this
as
well
that
we
typically
have
release
retros
at
the
end
of
the
cycle
and
since
with
this
cycle
is
around
the
the
christmas
holiday
or
the
the
holidays
or
at
the
end
of
the
year,
it's
also
might
be
better
to
have
a
retro
mid
cycle,
so
we
could
course
correct
the
better
attendance
as
well
for
those
for
the
stakeholders
in
the
really
cycle,
so
there's
multiple
benefits
of
having
it.
So
we
did
implement
this
in
for
1.23.
A
I
also
have
a
open
pull
request
as
well
in
the
release
lead
and
the
american
advisor
handbooks
as
well
to
have
it
to
have
the
first
retro
inmate
during
mid
cycle.
So
this
has
changed
in
the
all
the
calendars:
the
release
team,
google
calendar
also
in
in
the
kubernetes
in
the
contrabex
or
the
community
calendar
as
well.
So
it's
been
changed
to
to
the
first
retro
being
on
november
3.,
so
we're
coupling
it
with
the
start
of
the
monday
wednesday
friday
burn
down
meetings
which,
which
starts
this
week
as
well.
So
any
so.
A
I
do
advise
also
with
the
release.
Retro
is
to
add
in
your
any
topics.
You
would
like
to
discuss.
There's
a
link
up
here.
I'm
not
gonna,
go
all
the
way
to
the
top,
but
there's
a
release
up.
There
is
a
link
to
the
top
at
the
top
of
the
meeting
notes
to
add
in
any
discussion
topics
for
the
for
the
release.
Retro.
C
Yeah
ours
today
is
pretty
straightforward,
largely
the
same
as
last
week,
where
we're
green.
There
were
two
exception
requests
that
were
filed
and
approved,
but
aside
from
that,
the
numbers
haven't
changed
from
enhancements
freeze,
so
we're
tracking
57
right
now
and
we're
we're
kind
of
in
the
chill
period
of
the
release
for
us
now.
C
So
I
think
we
will
start
following
up
with
enhancement
owners
for
code
freeze,
I'm
thinking
probably
two
weeks
before
the
monday
that
closest
aligns
with
two
weeks
before
before
code
freeze
is
when
we'll
we'll
start
following
up
on
that,
but
yeah
aside
from
that
everything's
good
on
our
end.
A
Cool.
Thank
you.
I'm
also
with
that.
We'll
also
send
out
another
email
to
the
community
in
late
october-ish,
with
also
another
call
for
exceptions
as
well.
So
all
right
any
comments
or
questions
for
xander
or
the
enhancements
team.
D
D
One
of
the
master,
informing
failing
ones
is
no
issue
open
on
github,
but
this
is
open
for
a
couple
of
weeks
now
or
so,
and
it
seems
like
this
is
a
bit
abandoned
or
not
picked
up,
but
this
is
causing
a
failure
for
the
last
days
or
weeks
now.
D
So
I
don't
know
if
we
should
ping
sick
note
again
or
so,
but
this
is
this
should
be
the
the
team
which
is
responsible
for
the
the
failures.
Then
something
else.
D
So
I
would
so
the
c
sigma
guys
or
one
of
us
basically
had
the
idea
that
we
could
mention
in
the
issue
templates
that
we
reference
six.
Basically.
So
if
we
open
an
issue
that
we
also
should
tag
directly
sig
note
or
something
else,
this
would
be
something
maybe
that
we
could
change.
D
Ci
signal
group
on
on
slack
and
there's
also
already
an
issue
open
on
kubernetes
to
migrate
this
tool
to
kubernetes,
and
we
would
like
to
further
enhance
this
tool
and
maybe
automate
this
process
of
sending
reports
and,
in
general,
just
updating
the
tool
make
it
better,
enhance
it
and
so
on
yeah.
D
D
E
The
template
I
have
received
like
hussein's
lgtm
on
my
pr
do.
I
need
to
like
bring
this
up
to
sig,
release
or
contributor
experience,
because,
like
for
the
final
approval.
A
A
See,
paris,
okay,
yeah,
yes,
it
would
from
when
I've
updated
templates
as
well.
The
only
thing
that
there
was
really
no
way
to
test
until
you
emerge,
not
that
I
know
and
until
you
actually
merge
it
and
and
you
test
with
the
template
or
when
you
create
an
issue,
then
you'll
see,
then
you
use
that
new
template
yeah,
I
would
ping
contributes.
It
looks
like
allison
and
paris
are
the
reviewers
mentioned
here
and
you
could
take
a
look
and
they
could
take
a
look
in
that.
A
All
right,
if
you
need
help
playing
them,
I
could
help
ping
them
as
well.
How
about
the
do?
You
need
additional
help
for
it
to
migrate
the
ci
signal,
reporting
tool
or
any
enhancements
on
that
tool.
F
A
Okay,
cool:
do
you
have
a
question
on
these
two
failing
tests
since
adolfo
is
here
so
dolph
was
one
of
the
release
managers?
How
how
deep
do
you
go
into
failures
and
master
and
forming
when,
before
you
cut
you
like
an
alpha
beta
or
before
you
cut
the
release.
G
G
Then,
whenever
I'm
I'm
running
the
I'm
in
I'm
doing
the
the
release
manager,
role
myself,
I
always
try
to
depend
on
the
inside
of
the
of
the
ci
signal
team
and
if,
if
needed,
I
then
go
to
the
actual
seek
then
that's
that's
handling,
try
to
get
an
opinion,
but
that's
like
a
like
a
personal
style.
I
mean.
F
Maybe
I
can
give
like
more
info.
You
know
regarding
that
containing
the
failing
test.
You
know
it
was
flaking
for
a
while
and
then
you
know
signal
like
I
said:
yeah,
it's
flaking,
so
it's
probably
gonna.
You
know
be
resolved,
but
then
you
know
now
it's
failing
like
continuously,
so
I
think
we
need
their
support.
I
I
will
try
to
reach
out,
take
note
again
and
continue
topic
with
them,
but
it's
great
that
you
know
they
have
also.
You
know
some
eyes.
You
know
on
those
issues.
A
All
right,
thank
you.
Let
us
know
if
you
need
help
pinging
signaled
for
that
container
d
issue
or
the
other
failing
job
as
well.
Yep.
A
H
Hi,
so
kristoff
is
not
here
today,
so
I'll
be
trying
to
give
the
report.
The
status
is
green.
So
when
we
say
green,
it
pro
means
no
blocking
issues
and
prs
no
critical
things,
so
they're
all
zero.
F
H
Last
week
it
was
probably
20s
8
or
something
so
yeah,
nothing
out
of
the
line
there.
We,
the
the
members
of
the
team,
have
started
following
following
up
on
the
issues
in
the
prs
asking
like
is
something
to
be.
You
can
be
solved
or
not
trying
to
engage
on
the
issues
so
yeah.
That's
all.
I
Oh,
so
we
are
green
in
docs.
Our
integration
branch
for
the
website
is
healthy.
One
of
the
things
that
we're
looking
at
this
week
are
the
none
requireds
a
set
of
issues
just
to
confirm
that
they
in
fact
do
not
need
documentation
and
we
are
continuing
to
post
nudges
and
whatnot
on
the
placeholder
for
the
placeholder
pr.
So
you
may
see
us
in
your
issues
to
say
please
kindly
open
placeholder
prs.
A
Yeah
I
did
see
that
and
thank
you
for
that,
because
since
october
is
a
little
bit
quiet,
but
we
do
have
kubecon
quiet
in
terms
of
milestones
for
the
release
and
all
the
docs
related
milestones
are
going
to
be
around
us
thanksgiving
and
the
release
is
right
there
first
week
of
december,
so
I
did
add
that
to
my
to
my
state
of
the
release,
email
and
see,
please
start
early,
so
we
should
watch
out
for
that
all
right.
Any
comments
or
questions
for
docs
or
nate.
J
Yes,
sam
cece's,
not
here
so
I'll,
pick
that
up
yeah.
We
are
green
as
well,
nothing
terribly
exciting,
so
the
pr
for
the
alpha
two
release
notes
has
just
been
merged
just
now.
We
need
to
do
the
release
note
website,
one
which
I'll
be
doing
shortly
and
yeah
that's
pretty
much.
It.
A
Okay,
great,
let's
see
that's
merge.
I
do
have
now
rights
to
review
those
prs
for
their
website.
Pr
for
the
website,
release
notes
so
feel
free
to
ping
me
if
you
need
a
review,
any
comments
or
questions
for
release,
notes
or
sam.
A
Sam,
I
did
ping
you
on
slack
just
to
I
saw
you
were
only
able
to
make
comments
and
I'll
check
again
just
to
make
sure
you're
on
the
release
team.
Google
group
thanks
all
right
next
up
is
comms
with
karen.
K
Hey,
we
are
green.
We
are
still
waiting
for
people
to
drop
in
their
blog
opt-ins,
but
no
one's
responded.
So
I'm
gonna
have
my
team
go
and
reach
out
to
this
this
week
and
just
remind
them
that
they
can
do
that.
And
then
I
will
be
working
with
my
team
to
reach
out
to
cncf
to
schedule
the
release
webinar.
So
that's
it.
A
Okay,
cool
yeah,
thank
you
and
I
think,
as
part
of
the
lead
group
myself
in
the
league
shadows,
and
we
could
also
take
a
look
at
the
enhancements
and
see
what
would
be
good
for
a
feature
blog.
I
know.
Sigdoc's
wreck
they've
asked
for
a
feature
blog
on
the
pod
security
mission
controller.
We're
going
to
go
for
that
status
updates.
I
know
we
had
an
alpha
blog,
a
blog
for
it
when
it
went
to
alpha
last
release,
but
they
suggested
another
one.
A
Since
now
it
will
be
automated
on
since
it's
the
next
phase
of
the
cycle
or
if
the
enhancements
also
we
know
the
dual
stack
is
also
a
big
one
that
is
targeted
going
to
too
stable,
so
that
one
might
also
be
a
great
feature
blog
well.
So
I
will
reach
out
with
myself
in
the
in
the
lead
shadows,
to
take
a
look
to
identify
which
enhancements
will
be
good
feature
box
for
world
23..
A
Thanks
all
right
any
comments
or
questions
for
comms
or
karen.
L
Hello,
well,
sorry,
I
don't
have
a
cur
I'm
trying
to
yeah
sorry,
I
was
trying
to
to
open
the
dock
and
I
can't
I
don't
have
the
status
sorry.
I
thought
that
someone
else
was
taking
care
of
this.
So
apologies
today.
A
That's
okay
and
did
see
that
123
alpha
2
was
cut
last
week
in
alpha.
3
is
going
to
be
scheduled
to
cut
for
next
week.
A
Great,
thank
you.
Veronica
I'll.
Also
make
sure
that
that
you
have
the
rights
to
edit
as
well.
You
enabling.
G
Can
I
add
something
so
for
next
week's
release
we
haven't
yet
sent
the
open
call
to
the
other
release
managers
to
see
who's
going
to
be
taking
charge
of
the
pre-releases,
but
as
we
were
starting
the
cycle
arnon
arnold
nukem
he
volunteered
to
to
cut
the
the
alpha
3
version.
So
even
when
we
don't
have
the
the
complete
roster
for
the
next
three
releases,
he
will
be
taking
well.
I
have
to
get
double
check
with
him,
but
he
offered
to
take
care
of
her
alpha
3.
G
A
All
right
moving
on,
I
think,
don't
see
jeremy
on
the
call.
I
know
he
had
another
another
appointment,
so
jeremy,
the
emeritus
lead.
He
meant
he
updated
the
doc
that
he
will
reach
out
to
folks
who
were
not
able
to
do
the
shadow
orientation.
A
All
right
time
for
my
updates,
I
can
mention
alpha
3
is
scheduled
for
next
tuesday
september
28th
and
unlike
a
dolphin
mention
arno
well
well,
we'll
cut
that's
volunteered
to
do
that.
Last
friday,
I
sent
a
state
of
the
release.
Email
included,
there's
a
link
for
that
here
as
well.
That's
that
was
sent
to
a
number
of
kubernetes.
A
F
A
Just
click
on
this
link,
there
was
also
a
call
for
feature
blogs,
as
well
with
the
link
to
the
tracking
sheets
and
for
and
leads
have
the
ability
to
to
enter
feature
blogs
as
well,
and
I
think
all
others
should
be
able
to
comment.
A
Also
with
that,
as
well
as,
like
I
mentioned
before,
how
the
docs
placeholder
pr
all
the
docs
deadlines
itself
around
u.s
holidays.
I
did
make
a
call
for
that,
just
to
start
to
start
work
earlier
as
well,
and
also
made
a
note
that
there's
changed
in
the
first
release.
Retros
now
on
november
3.,
with
that
one,
a
few
other
updates,
the
apac
family
meeting
will
be
scheduled.
I'm
gonna
meet
or
talk
with
the
elite
shadows
as
well
on
what
that
time
should
be.
A
The
doodle
ended
last
friday,
so
that'll
be
scheduled
for
next
week
and
there
we
and
since
this
since
october,
there's
no
release
milestones.
So
this
gives
us
some
time
for
those
who
do
have
time
to
look
back
into
some
action
items
into
the
one
from
the
122
retro.
So
you'll
probably
see
me
paying
certain
people.
A
A
Do
you
want
to
call
to
add
feedback
for
the
release
team
selection
process
in
the
github
discussion
that
james
mentioned
as
well,
and
I
think
this
is
it's
very:
it's
actually
more
beneficial
for
those
for
shadows
to
add
their
feedback
and
for
anyone
who
had
to
go
through
multiple
application
process
to
be
selected
just
to
add
their
feedback
and
to
have
any
suggestions
as
well.
A
Also
at
this
time,
since
we
october
besides
coupon,
it's
kind
of
it's
kind
of
like
the
quiet
before
the
storm,
I
do
ask
for
row
leads
and
foreshadows
to
refine
their
their
respective
handbooks
as
well.
This
is
actually
great
for
for
for
for
shadows,
because
they
give
us
this
new,
fresh
eyes
to
look
at
with
the
handbooks
and,
if
there's
anything,
that's
unclear
or
anything,
that's
missing.
Please
add:
please
make
a
pull
request
to
the
handbook
as
well,
so
yeah.
A
So
that's
it
for
my
updates
and
that's
any
comments
or
questions.