►
From YouTube: Kubernetes 1.24 Release Team Meeting for 20220223
Description
For more info, see https://git.k8s.io/community/sig-release
A
All
right
welcome
to
the
1.24
release
team
meeting.
This
is
wednesday,
the
23rd
of
february.
Please
be
aware
that
this
meeting
does
abide
by
the
kubernetes
code
of
conduct,
which
can
be
summarized
as
please
be
excellent
to
one
another.
A
Don't
see
any
open
discussion
items
today,
but
I
will
loot
back
to
that
at
the
end.
In
case,
anything
gets
added
over
the
course
of
the
meeting
and
why
don't
we
kick
it
off
with
enhancements
team
priyanka?
What
updates
do
you
have
for
us.
B
Hey
everyone,
so
our
overall
status
is
green
and
we
just
received
an
exception
request
this
last
week,
1432,
which
was
approved,
it's
also
implemented.
So
we,
our
total
crack
number,
is
67.
Now,
oh
yeah.
A
All
right
silence
is
golden.
Let's
move
on
to
kristoff
with
ci
signal.
C
Hi,
this
is
christopher,
ci
signal,
so
today
we
have
one
failing
test
in
master
blocking
and
I'm
yet
about
to
look
for
the
issue.
This
test
is
fading.
Since
yesterday
we
have
a
couple
of
more
failing
and
master
informing,
and
apart
from
this,
I
got
pinked
by.
D
C
That
we
have
a
couple
of
issues
that
need
some
close
attention
right
now
we
are
looking
for
yeah
responsible,
so
people
who
can
can
help
out
on
a
couple
of
issues
here
about
flaky
tests
and
even
a
cherry
pack,
and
apart
from
this,
we
have
two
pr's
that
need
to
be
approved
by
yeah
kubernetes
release
managers,
so
also
here
would
be
great
to
get
some
some
help.
A
Sounds
good
if
you
do
need
some
additional
help
finding
folks
to
to
help
out
with
the
flaky
test.
If
you
want
to
maybe
start
a
thread
in
in
sig
release
and
then
james,
maybe
we
can
pull
in
some
folks
that
have
shadowed
or
led
a
ci
signal
in
the
past
to
to
help
out
with
that.
D
Yeah,
I
agree,
I
think
a
thread
in
slack
is
probably
the
best
bet
to
set
that
started
just
for
extra
visibility,
because
then
we
can,
we
can
find
six
chairs
and
all
sorts
and
tag
them
in
this
would
be
great
okay,
cool.
E
A
Cool
cool
I
know
docs
has
been
busy.
Let's
move
on
to
docs
with
me.
F
Hello,
everyone,
so
our
current
status
is
green
and
integration
branch
is
healthy.
We
are
currently
tracking
67
enhancements,
out
of
which
still
there
are
remaining
54
prs.
We
have
four
draft
peers,
four
are
in
review
process
and
one
completely
merged
and
four
don't
require
dogs.
So,
however,
we
don't
have
any
major
changes
since
our
previous
meeting.
Thank
you.
A
All
right,
I
don't
see
an
update
from
release
notes
here.
Do
we
have
lucas
or
anyone
from
the
release,
notes
team?
That's
able
to
speak
to
things
there.
G
Hey
so
it's
me
paul
from
the
release,
notes,
team
and,
I
guess
lucas
isn't
there
in
the
meet
or
probably
visit
with
some
other
work,
and
we
did
not
have
any
major
updates
from
the
previous
meet.
It
says
that
we
would
be
having
another
meeting
set
up
for,
along
with
all
the
release,
notes,
shadows
and
lucas
himself
for
discussing
the
errors
we
were
facing
with
krell,
and
that
would
be
it.
A
H
Yep
hi
everyone
so
with
comms,
we
have
started
with
the
initial
draft
for
removals
and
deprecation
blocks,
so
please
reach
out
to
us.
If
you
have
any
content
and
we
have
a
tracking
sheet
now,
where
we
will
be
reaching
out
to
enhancement
honors,
to
help
us
with
the
removal
and
deprecation
block,
also
the
release
blog
part.
H
As
soon
as
the
deprecation
blog
thing,
the
initial
draft
is
prepared
will
be
starting
up
with
the
release
block
part
and
the
enhancement
seat
is
now
prepared
and
we'll
be
reaching
out
to
people
soon.
Another
thing
we
have
here
is
like
james.
If
you
have
any
message
presented
for
seed
leads,
as
I
got
the
context
from
mickey
like
last
time,
see
the
lead
had
some
content
to
send
out
to
sig
leeds
to
reach
out
for
the
release,
blogs
and
announcement
and
application
blog.
H
So
we
could
merge
all
those
content
and
reach
out
to
sick
leads
if
they
have
anything
for
that
application
or
removable
blogs
or
future
tracking.
You
would
like
to
highlight.
D
Yeah,
I
mean
I'm
more
than
happy
to
reach
out
I'll
I'll
reach
out
to
everyone
with
some
message.
I'll
I'll
start
a
slack
thread
after
this
meeting
to
discuss
how
we're
going
to
do
that
because
it
could
either
be
in
slack
or
via
the
email
list,
we'll
have
to
decide
the
best
way
yeah.
I
think
that
should
be
that's
pretty
straightforward.
I
have
to
do
that.
A
Cool
and
with
that
it
looks
like
I'm
seeing
no
new
updates
for
release
branch
management,
but
nabarun
if
you're
on
the
call
is
there
anything
that
you
wanted
to
wanted
to
share.
Well,
you've
got
the
time.
A
A
I
The
things
to
look
up
for
is
we're
getting
about
to
mid
cycle,
and
I
will
be
sending
out
a
survey
to
all
of
you
to
kind
of
see
how
things
are
going,
as
this
will
also
help
cue
up
things
for
our
upcoming
mid-cycle
retro,
which
also
we
should
try
to
get
some
things
in
there
as
well.
If
you
have
things
that
have
come
up
during
this
release,
make
sure
you
put
some
of
these
things
down,
so
we
can
make
improvements
as
well
as
I
will
be
doing
some
additional
lead
and
shadow
outreach.
I
Is
we've
been
really
trying
to
make
sure
that
our
meeting
times
are
inclusive
of
everybody
around
the
globe,
and
so
I
know
he's
put
a
call
out
for
timing
for
the
friday,
so
I'm
keenly
looking
at
that,
and
hopefully
we
can
make
sure
that
everyone
has
something
that
or
at
times
that
is
convenient
for
them.
I
think
that's
it
so
happy
wednesday
great
to
see
everybody.
A
All
right
with
that,
I
will
pass
it
off
to
james.
D
Hello,
friends,
all
right,
so,
first
up
last
time
I
said
I
was
going
to
be
going
to
speak
on
the
team's
behalf
at
the
community
meeting.
I
turned
out
not
to
be
able
to
make
this
due
to
a
last
minute
conflict,
but
zander
very
very
helpfully
went
for
the
team.
Instead,
I
understand
it
was
was
fine,
no
issues.
D
Excellent,
so
thank
you
very
much.
Xander
next
point.
As
joseph
just
mentioned,
we
are
going
to
add
a
friday
meeting.
This
is
designed
to
be
more
in
an
apac
friendly
time
zone.
I'm
planning
to
close
the
doodle
poll
for
that
in
about
40
50
minutes
and
send
out
invites,
and
with
the
first
meeting
this
friday,
the
25th,
I
think,
looking
at
there's
only
been
two
responses
so
far.
D
I
think
their
consensus
was
around
about
9
or
10
a.m,
utc,
which
is
like
one
or
two
in
the
morning
for
for
you
in
the
us,
I
think
which
is
fine
but
we'll
see.
And
yes,
I
will
share
that
link.
I
will
just
go
and
and
pull
it
out
and
put
it
in
the
chat
in
a
second
other
than
that.
I
don't
think
I
have
any
particular
update
yeah.
D
Oh,
I
will
go
and
one
thing
that
so
this
friday
meeting
was
kind
of
like
a
informal
thing
in
previous
releases,
but
not
done
formally.
So
I
think
what
I'm
going
to
do
is
I'm
going
to
amend
the
schedule
to
say
when
we
introduce
it
and
then
when
the
next
release
lead
comes
along
and
copies
the
124
schedule
to
make
the
125
schedule
they'll
bring
that
with
them,
so
they
can
introduce
it
as
like
an
actual
thing
rather
than
having
to
to
the
way.
A
All
right,
I
don't
see
any
open
discussion
items
that
have
been
added,
so
I
will
end
the
recording
here,
but
yeah
y'all
are
doing
a
fantastic
job.
This
this
release
has
some
pretty
high
impact
items
associated
with
it,
and
so
I
know
that
that
can
be
a
little
stressful
and
y'all
are
doing
just
a
really
amazing
job,
keeping
up
with
everything
and
yeah.
So
thank
you
all
for
your
effort
seriously.