►
From YouTube: Kubernetes Release Team Meeting for 20221125 (v1.26)
Description
Kubernetes Release Team Meeting for 20221125 (v1.26)
A
A
I
am
adding
the
link
to
the
meeting
agenda
document.
Again,
please
feel
free
to
add
yourself
in
the
attendees
section
also
feel
free
to
add
any
points
that
you
want
to
discuss
as
part
of
the
meeting,
and
with
that
just
a
note,
the
meeting
abides
by
the
cncf
code
of
conduct,
which
boils
down
to
please
be
excellent
and
nice
to
each
other.
Oh
yeah,
thank
you
for
joining.
A
So
there
is
nothing
in
the
open
discussions
again.
I
see
we
have
1.26
retrospective
document
link
there.
So
if
you
have
any
feedback
comments,
anything
that
you
want
to
discuss
that
happened
or
anything
any
improvements
that
you
want
to
suggest
for
the
release.
Cycles,
please
feel
free
to
add
your
suggestions
there
in
the
ink
document.
Thank
you
with
that.
We
can
move
to
the
role
updates,
enhancements,
apparel.
D
Now,
as
we
are
getting
close
to
the
next
release
cut,
that
is
on
29th
November,
we
started
checking
the
job
history
of
all
the
flaky
ones,
to
see
the
pattern
so,
except
everything
looks
good
except
one
like
Ci,
kubernetes,
itoe
Ingress,
and
we
will
keep
an
eye
on
this
like
it
started
feeling
today
and
also
we
are
observing
1.26
blocking
and
informing
test
grids
and
everything
looks
good
as
we
don't
see
any
failing
jobs
on
that.
So,
yes,
that's
all
about
CI
signal.
Thank
you.
D
A
A
Flake
issues,
open
I,
believe
that
is
tracked
by
CI
signal
already,
and
everything
else
also
looks
good,
so
moving
to
docs
I
believe
we
do
not
have
anyone
from
docs
as
well,
so
I'll
just
go
ahead
and
check
the
Wednesday
update
and
from
Wednesday
it's
yellow
and
we
have
one
Gap
without
proper
documentation
and
with
just
placeholder
PR,
so
I
believe
the
team
is
looking
on
that
and
yep
Frederick
wine.
I
I
see
you
typing
there,
but
I.
If
you
want
to
go
ahead
with
release,
notes,
yeah.
A
C
C
Yes,
thank
you
and
apologies
for
the
mix
up
there,
so
we
are
yellow
in
in
comes
essentially
because
of
the
the
number
of
opt-in
feature
blocks
that
we're
tracking
and
the
number
that
are
already
ready
for
review.
So
we
do
have
more
today
compared
to
yesterday
and
as
I
mentioned
in
last
call
it's
very
common
for
the
deadline
to
be
day
where
most
feature
blocks
come
in
still
better
to
put
this
on,
yellow
to
to
to
reflect
the
fact
that
we
have
less
than
half
of
the
feature
blocks
ready
for
review.
C
A
A
You
might
hear,
hear
from
naborum
sometime
earlier
than
last
week
with
a
release
survey
for
the
Shadows.
So
please
give
your
valuable
feedback.
That's
very
much
appreciated
to
improve
the
release,
Cycles
and
I.
Believe
there
is
nothing
from
release
leads
as
well.
We
have
come
up
with
a
release
theme
that
Leo
shared
and
witnessed
their
meeting,
and
more
will
come
on
that
in
the
release
article
thanks
again
Frederick
for
working
on
that
and-
and
we
do
not
have
anyone
from
six
scalability
as
well.