►
From YouTube: Kubernetes 1.24 Release Team Meeting 20220216
Description
For more info, see https://git.k8s.io/community/sig-release
A
Hello,
everyone
welcome
to
the
sick
release
weekly
meeting
we
are
currently
at
week.
Six
today
is
february
16
2022
and
this
meeting
is
under
sincere
code
of
conduct,
which
boiled
down
to
just
place
be
kind
to
each
other,
and
we
generally
use
this
meeting
to
get
the
general
updates
on
the
release
schedule
so
I'll
be
the
host.
Today,
I'm
cece,
currently
the
lead,
the
release,
lead
shadow
and,
let's
move
to
the
open
discussion
thanks
james.
A
B
A
C
Hi,
yes,
this
is
laura.
I
am
a
ci
signal,
shadow
reporting
today
that
our
status
is
yellow,
so
we've
had
kind
of
a
lot
of
intermittent
flakes.
Over
the
past
week
there
was
one
set
that
was
kind
of
widespread,
based
on
like
a
key
rotation
issue
that
was
quickly
resolved
by
testing
ops,
and
then
there
were
some
others
that
we
followed
up
on,
including
listed
here,
a
failing
on
master
blocking
and
a
failing
on
master
informing.
C
But
we
did
give
the
go
signal
for
the
release
branch
cut
yesterday
for
these
two
failing
ones,
the
master
blocking
one.
We
got
some
input
from
sig
network.
It
was
like
a
gce
like
timeout
thing
that
they
gave
the
input
that
it
was
okay
to
not
block
the
release
on
and
then
for
the
master
informing
one.
There
was
really
quick
triage.
It
was
seen
by
cuba
dm
faster
than
us,
so
great
job
to
qadm
so
yeah.
C
A
D
Hi
hi
everyone,
so
currently
the
status
from
background
is
green.
We
have
one
blocking
issue,
that
is
the
docker
shim,
which
we'll
keep
track
until
the
middle
of
the
release.
As
per
the
discussion
in
the
last
team
last
release
meeting,
we
have
zero
blocking
prs,
zero,
critical
and
urgent
issues
and
zero,
critical
and
urgent
prs
as
well.
So
we
are,
we
look
green
for
this
side
and
our
team
is
continuing
to
follow
up
with
the
different
owners
of
the
issues
and
the
pr's.
E
Hello,
everyone.
So,
yes,
the
current
status
of
the
dog's
team
is
green.
The
integration
branch
is
healthy
and
currently
we
are
tracking
66
enhancements
from
which
57
don't
have
pr
three
drafts.
One
ready
for
review,
one
completely
merged
and
four
doesn't
need,
doesn't
need
dogs
as
for
now
so,
yes,
the
dog's
team
is
continuing
to
ping
for
the
placeholder
prs,
with
a
note
that
when
the
open
placeholder
pr
deadline
is-
and
so
yes
that's
it.
Thank
you.
A
F
G
So
on
our
ends,
everything's
still
green,
we're
reviewing
the
enhancements
tracking
page
to
try
to
figure
out
which
topics
are
appropriate
for
the
deprecations
and
removals
blog.
We
have
a
few
identified,
so
the
next
step
is
just
you
know,
confirming
the
right
topics
and
then
actually,
starting
on
the
blog.
A
H
H
Sure
so,
as
people
have
said,
as
we
deliver
quite
a
week,
we've
had
a
couple
of
things
go
off.
Of
course,
the
patch
release
went
off
off
yesterday,
which
is
pretty
good.
On
one
note,
there
is
the
kubernetes
community
meeting
at
1800
utc
tomorrow,
it's
the
first
time
we've
had
one
of
these
in
a
while,
and
part
of
my
job
is
to
go,
give
a
general
update.
H
So
I've
been
speaking
to
nigel,
who
is
the
person
sharing
that
meeting
and
I'm
going
to
be
along
to
give
just
a
brief
overview,
update
of
how
things
are
going
largely
for
community
members
who
may
not
be
too
connected
to
what
we're
doing,
which
is
nice
one.
Other
thing
I'm
going
to
try
to
get
better
at
is
setting
the
meets
sorry
setting
the
notes
for
this
meeting
up
early
as
it
is.
We
need
to
do
it
a
few
hours
before
I'm
going
to
try
to
do
it
after
every
meeting.
H
A
Nice,
thank
you
look
forward
to
the
mid
cycle
virtual
and
thanks
for
the
sixth
scalability
they
already
updated
before
this
meeting
seems
like
the
status
is
green,
that's
great,
and
maybe
we
should
take
a
look
at
the
project
board
as
well.
I
took
a
brief
look.
It
looks
like
everything
is
under
control
and
works
fine.
H
B
H
B
H
A
H
So
I'm
thinking,
if
I
just
open
that
I'll
repost
that
and
you
know,
I'm
certainly
supportive
of
adding
a
release
in
the
formal
cycle.
We
don't
add
an
apac
friendly
one
until
we
add
additional
meetings
kind
of
later
in
the
cycle
like
week,
11
or
something,
but
I
think
we've
always
added
one
part
way
through
the
cycle,
but
I
don't
think
it's
ever
been
formalized
in
any
schedule
anywhere.