►
From YouTube: Kubernetes Release Team Meeting (1.26) for 20221114
Description
Kubernetes Release Team Meeting (1.26) for 20221114
A
Okay,
I
think
recording
is
in
progress.
Yes,
okay,
all
right,
hello,
everyone,
it
is
Monday
the
14th
and
week
11
of
the
release.
I
am
grease
and
just
a
reminder
that
we
are
under
the
cncm
cncf
code
of
conduct,
which
boils
down
to
please
be
nice
and
kind
to
each
other.
A
All
right
that
doesn't
seems
like
there
are
enhancement
folks
in
the
crowd,
Leo
and
the
release
has
been
working
through
some
exceptions.
So
that's
still
ongoing
a
little
bit.
Let's
hop
over
to
CI
signal.
B
A
Can
you
hear
me
yeah?
We
are
good
okay
good,
so
we
agree
so
just
a
new
PR.
C
Just
popped
up
a
few
minutes
ago,
but
beside
that
we
are
doing
good
and
yeah.
We
can
give
a
green
light
or
release
candidates.
D
Hi
well,
tomorrow,
is
our
deadline
for
the
dogs
were
ready
for
review.
Currently,
I
will
only
copy
the
insights
that
it
were
help.
D
We
only
have
like
four
no
pull
requests
for
this
cap,
and
already
we
have
like
nine
married
and
the
others
are
draft
and
ready
for
review.
Don't
I
think
we
are.
We
only
try
to
push
this
for
caps
that
we
don't
have
a
step.
We
don't
have
a
still
pull
request
for,
for
the
documentations
and
I
also
have
a
pull
request
to
keep
update
the
branch,
126
and
I
think
will
be.
E
E
A
All
right,
thank
you
for
that
comes
with
Federico.
F
Yes,
hello,
so
we're
back
to
green.
We
have
some
some
issues
with
the
with
the
board
that
were
already
mostly
clarified.
We
already
have
all
the
PRS
there.
F
We
are
now
adding
everyone
for
the
next
deadline,
which
is
around
the
ready
for
review
of
the
of
the
draft
of
the
blogs
the
deprecation
removed
blocks
that
we
rescheduled.
For
the
end
of
this
week.
We
have
been
adding
all
the
instances
of
changes
and
removals
that
we
found
in
the
in
the
PRS,
and
but
there
are
quite
a
few
and
we
will
share
that
information
so
that
we
can
select
the
most
obvious
ones
and
submit
a
draft
for
publication
in
the
next
following
days.
G
Can
give
an
update
on
that
one
I
I,
it's
just
the
one
line.
It's
yeah
we're
gonna
cut
the
RC
0
tomorrow,
so
yeah,
hopefully
all
goes
well.
There
and
yeah
we'll
have
the
first
release
candidate
out
the
door.
A
All
right,
that's
exciting,
I,
don't
see
any
updates
from
navaroon,
so
Leo.
C
Hello,
everyone
so
my
updates,
so
we
have
currently
everything
so
all
the
Caps
are
in
in
the
release.
All
the
exception
requests
have
been
resolved
so
either
they
passed
past
the
deadline
or
they
are
pushed
to
the
next
one.
C
So
that's
that's
good
for
rc0
we
should
have
all
the
major
changes
in
and
just
maybe
some
bug,
fixing
and
so
on
on
the
way.
So
right
now,
if
we
see,
as
we
already
heard
from
CS
quite
a
few
message,
informing
failings
and
also
a
few
flakes
Maybe,
so
we
should
focus
on
that.
C
C
There
was
a
discussion
in
the
CIA
signal
Channel
about
flag
detection
quite
some
time
ago,
and
Antonio
also
jumped
on
this
point,
I
think
on
Friday
or
Thursday,
and
we
have
tomorrow
at
in
the
sick
testing
meeting
like
a
30
minutes,
time
start
or
so
Antonio
will
will
show
a
test
grid
and
how
he
works
with
test
grid,
to
detect
Flakes
and
everything.
So
this
is
hopefully
exciting
for
the
CIA
signal
folks
and
everyone
else,
who's
interested.
C
So
there's
I,
I,
think
the
sick
testing
meeting
notes.
So,
if
you're
interested
you
can
jump
on
the
call
I
think
it's
around
this
time
tomorrow,
if
I'm
not
mistaken
and
right
for
code
freeze,
we
received
I,
think
eight
in
total
and
six
past
past
all
got
accepted
six
past
the
the
new
set
deadline
and
two
did
not.
C
There
was
a
one,
bigger
discussion
which
you
might
have
followed,
not
sure
and
with
one
of
the
exception
requests
basically
right
now,
it's
kind
of
difficult
to
review,
all
the
major
changes
or
the
bigger
changes
in
a
very
short
period
of
time,
so
for
the
maintainers
and
reviewers
it's
it's
challenging.
So
this
is
like
a
new
topic
for
the
Retro.
C
Maybe
there's
like
some
some
ideas
that
we
have
to
improve
this
process,
so
we
can
make
sure
that
these
big
changes
do
not
miss
the
deadline
over
and
over
again,
because
this
happened
now
for
yes,
so
we
should
improve
the
process
and
yeah
we're
in
the
home
stretch.
I
would
say
so
far,
so
good
everybody
is
doing
a
great
job
and
that's
it.
Thank
you.