►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220810
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220810
A
This
meeting
is
being
recorded,
hi
everyone
good
morning,
welcome
to
our
kubernetes
1.25
release
meeting
and
we
are
currently
at
week.
12.
today
is
wednesday,
10th
august
and
right
now,
during
our
daily
burn
down
meetings,
things
is
towards
the
end
of
the
release
and
as
euro,
this
meeting
is
under
the
same
safe
code
of
contact
which
could
be
boiled
down
to.
Please
be
nice
and
respectful
to
each
other,
and
I
have
the
meeting
notes
link
pasted
in
the
chat,
so
please
feel
free
to
register
your
attendees
and
I
just
registered
mine.
A
Let's
move
to
the
open
discussion,
I
do
have
one
topic
which
confused
me
a
little
bit
regarding
with
the
object,
storage
support.
This
enhancement
is
not
been
tracking
ever
our
enhancement
spreadsheet,
but
the
author
is
registered
for
a
feature
blog.
So
I'm
not
sure
if
anyone
has
an
idea
of
about
the
enhancement
status,
because
this
enhancement
announced
to
go
into
alpha
in
the
current
release,
but
it
seems
like
they
were
just
trying
to
kind
of
advertise
this
instead
of
having
any
and
the
user.
Viewed
as
alpha
feature.
A
So
anime
has
an
idea.
B
I'm
I'm
inclined
to
just
pull
that
feature
blog
just
like
just
reach
out
to
them
and
and
pull
it
if
it's
not
tracked,
and
they
are
just
kind
of
like
trying
to
sneak
it
in
as
an
advertisement,
then
I'm
inclined
to
just
pull
it.
We
have
a
lot
of
feature
blogs
this
release
like
a
lot
of
them,
so
it's
not
going
to
hurt
us
to
lose
one
of
them.
A
Thank
you
so
much
for
the
input
cat
and
I'm
also
trying
to
reach
out
to
the
sig
storage
lead,
because
the
six
storage
lead
also
proposed
this
as
a
part
of
the
major
theme
which
confused
me
a
little
bit
so
I'll,
keep
reaching
out
to
the
sig
storage,
lead
together
with
the
author
as
well
and
I'll.
Give
the
update
hopefully
tomorrow.
Does
that
sound
good.
E
Got
it
it
does
say
on
the
issue
in
the
enhancements
repository
that
this
is
tracked
out
of
tree.
So
I'm
a
little
bit
surprised
that
they're
pairing
that
to
a
kubernetes
like
the
release
of
this
to
a
specific
kubernetes
release.
A
Yeah,
thank
you
for
adding
that
mark
yes
like,
if
it's
out
of
a
tree,
it's
it
makes
total
sense
that
we
didn't
track
it
and
in
the
meanwhile,
it
shouldn't
be
a
kind
of
feature
blog
or
like
a
major
theme
announced
together
with
community.
So
I'm
not
sure
if
I'll
double
check
with
sig
storage
on
this
one
again.
Thank
you
so
much
for
the
information-
and
I
hopefully
will
get
back
tomorrow
with
updated
info.
E
And
it
oh,
I
I
do
see
on
the
pull
request
for
the
cap
too
I'll
I'll
link
it
into
the
chat.
But
it
looks
like
one
of
the
leads
did
also
have
a
question
saying
they
don't
know
how
to
track
this
because
it
is
out
of
tree
and
they
don't
know
which
milestone
to
target.
A
Yes,
exactly
and
also
like,
I
guess
it
also
confused
the
sig
dogs
a
little
bit,
because
if
we
want
to
add
any
like
feature
blog
or
anything
introduced
into
kubernetes
official
website,
it
also
caused
some
kind
of
confusion
there.
A
E
I
was
before
that
agenda
item.
I
was
going
to
say
it's
green.
I
think
we
need
to
figure
that
out,
but
other
than
that
enhancement
that
you
just
mentioned.
There's
no
update
since
the
last
meeting.
A
C
Yeah,
hello,
everyone,
our
current
status,
is
yellow
on
master
blocking.
We
had
one
feeling,
but
a
few
minutes
ago
we
had
a
few
minutes
ago.
The
pr
has
been
merged,
so
it
will
take
a
time
to
display
on
the
test
script
and
on
mustang
forming.
We
have
two
failing
in
which
the
second
one
is
just
started
today,
so
we
will
observe
for
one
and
another
day
and
we
will
open
up
towards
the
issue
so
yeah
next,
one.
A
Thank
you
so
much,
hopefully,
the
master
block
and
failure
will
be
going
together
with
our
fix
and
thank
you
for
the
updates.
Any
questions
for
the
ci
signal
team.
F
Yes,
hello,
everyone,
so
nothing
has
changed
that
much
since
yesterday
we
are
still
green,
but
just
something
popped
popped
up
since
yeah
12
hours
ago.
There
is
a
one
priority:
critical,
urgent
pr.
I
just
looked
in
it's
regarding
you
know,
creating
release
branch.
125,
yeah
jeremy
opened
his
pr
and
yes
deems
and
him
they
are
continuing.
I
thought
that's
nothing
serious.
I
think
it's
just
about
you
know
creating
a
branch,
that's
it
from
our
set.
G
Hi,
so
our
current
status
is
yellow.
We
just
passed
the
docs
ready
for
review
deadline,
which
was
yesterday.
We
do
have
a
branch
sync
pr
in
review.
Right
now,
it
looks
like
there
might
be
some
failures
on
that.
I've
pinged
some
folks
for
review
on
that.
As
far
as
our
stats,
we
have
five
docs
prs
merged,
33,
ready
for
review
and
one
with
no
pr
and
then
another
with
no
docs
required,
so
we're
following
up
on
some
loose
ends
and
hopefully
get
that
status
back
to
green.
Soon,
thanks.
C
So
our
current
status
is
green
and
we
have
created
a
linux
vr
for
1.25
beta0
and
the
deluxe
pr
and
website
pr
for
1.25
alpha
3
is
most
and
next
the
team
will
be
working
on
1.25
release,
candidates,
notes.
A
Thank
you
so
much
and
hello.
Let's
thank
you
for
reading
the
pr
I'll,
take
a
look,
and
it
looks
all
good
and
what
about
just
one
more
question
before
we
move
forward
what
would
be
the
status
of
major
themes
if
you
have
any
idea.
C
Yeah
we
have
collected
it
and
we
will
look
over
which
are
the
like.
If
any
updates
are
missing
from
other
six
and
we
will
update
it
there
cool.
Thank
you.
Yeah.
A
I
know
the
deadline
for
the
major
seams
is
the
coming
tuesday,
but
the
maybe
the
feature
blog
draft.
We
also
need
to
add
the
major
sims,
so
if
like
by
any
chance,
you
could
get
a
draft
pr
out
earlier.
That
would
be
awesome.
Thank
you.
Okay
and
comms
cat.
B
Hi
hey
good
morning,
so
the
psp
historical
context
blog
draft
is
available.
This
is
a
very
rough,
very
early
draft
from
mahe,
but
this
is
something
that
we
are
aiming
to
get
out
before.
Release
like
as
soon
as
possible,
I'm
gonna
go
in
at
mahe's
request
and
make
some
edits
to
it
for
like
for
clarity
and
for
grammar
and
he's
still
working
on
a
couple
of
expansions
too,
like
like
psp,
specifically
needed
to
be
removed
after
all
of
this
time
and
how
its
replacement
is
better,
similar
to
docker
shim.
B
This
is
pairing
with
a
blog
article
about
pod
security
admission,
which
is
being
written
by
tim
alclair,
but
we
are
still
on
track
to
have
the
feature
blog
schedule
ready
this
week
and
we're
gonna
stay
synced
with
sig
docs.
With
this
I
met
with
them.
Yesterday
we
agreed
to
aim
for
three
blogs
a
week,
ish
with
currently
16
blogs,
total
that
that
is
a
lot.
That
is
a
long
time
for
the
kubernetes
blog
to
stay
like
dedicated
to
feature
blogs.
B
So
if
we
don't
hit
all
of
those,
if,
if
not
all
of
the
blog
authors
manage
to
like
complete
their
blogs
on
time,
it
really
is
not
a
big
deal.
We
can
lose
like
five
of
these
and
it's
still
be
fine
honestly.
So
the
shadows
really
hustled
on
finding
us
blogs
for
this
and
then
the
only
question
I
I
really
have
is
like
do
we
have
a
release
theme
yet
so
I
can
include
like
any
pieces
of
that
in
the
release
blog
draft
before.
A
A
I'll
pin
you
maybe
later
I
do
have
a
sim
and
also
I'm
currently
working
with
tim
on
getting
the
design
ready
and
yeah,
hopefully
at
least
by
maybe
tomorrow
or
the
day
after
tomorrow.
Okay,
perfect
yeah.
A
A
A
Yeah
appreciate
that,
let's
move
to
release
branch
management,
jeremy.
D
Hey
everybody.
So
yesterday
we
cut
the
rc
zero
that
went
pretty
well,
there
should
be
a
branch
now
and
the
only
kind
of
hiccups
we
hit
were
when
we
were
creating
the
the
new
test
jobs
to
update
test
grid.
There
was
some
failures
with
the
generation
script
that
we
used
so
shout
out
to
where
go
for
helping
triage
that
and
dims
for
helping
to
triage
that,
and
we
got
that
fixed
because
we
spent
a
little
bit
of
time
on
that.
D
We
missed
doing
the
pr
to
update
the
publishing
bot
rules,
so
that
was
the
pr
that
was
mentioned
earlier.
Hopefully,
that'll
go
in
today,
dems
just
lgtmed
it,
and
then
that
should
make
sure
that
all
the
tags
are
in
the
various
repos
and
we
should
be
good
to
go
there.
A
And
thank
you
for
getting
the
rc
there
out
and
let's
move
to
ray
is
on
vacation,
maybe
for
the
rest
of
the
week
as
well.
So,
let's
directly
move
to
updates,
I
don't
have
much
and
congratulations
for
passing
the
deck
line.
Yesterday.
It
went
great,
I
saw
only
one
dog
hasn't
been
tracked,
placeholder
hasn't
been
tracked,
but
other
are
pretty
much
or
either
merged
or
already
ready
for
review,
and
we
had
the
rc
the
error
released
yesterday.
Thank
you
for
jeremy
and
also
the
branch
card.
A
Pr
is
in
progress,
hopefully
gonna
be
completed
today
and
just
feel
like
milestones.
Sorry,
I
forgot
to
put
it
here,
like
you
feel
as
a
reminder
of
like
the
future
big
milestones,
we
will
have
like
the
release
blog
ready
to
review
next
week.
We
will
have
the
major
sim
completed,
also
the
same
date
as
tuesday
16th
august
and
the
dogs
ready
to
merge
is
also
on
tuesday,
so
seems
like
the
coming.
Tuesday
is
a
big
day
and,
together
with
the
future,
blocks
ready
to
review
deadline.
A
So,
after
all
those
past
all
those
deadlines.
Also,
we
scheduled
the
rc1
released
on
the
same
tuesday,
16th
august,
which
will
be
the
last
rc
release
before
the
formal
release.
So
just
keep
the
days
in
mind
and
that's
all
I
have
and
thank
you
so
much
for
everyone's
great
work
on
this,
and
hopefully
all
of
us
enjoyed
the
release
so
far
and
we
get
the
update
from
sig
scalability.
Today
the
status
is
green,
that's
awesome
and
I
don't
think
we
use
project
board,
but
it's
worth
a
check.
A
Cool
we'll,
definitely
need
to
figure
out
how
to
like
leverage
the
power
of
project
board,
maybe
in
next
release
yeah
and
anyone
has
any
questions
or
comments.
Before
I
end
the
recording.