►
From YouTube: Kubernetes Release Team Meeting (1.28) for 20230607
Description
Kubernetes Release Team Meeting (1.28) for 20230607
A
Hello,
everybody
and
welcome
to
the
June
7th
2023
kubernetes
128
release
team
meeting.
This
is
week
four
and
I've
just
started.
The
recording
I've
got
the
meeting
notes,
Linked
In
the
meeting
chat.
If
everybody
who's
on
the
attendance
list
can
add
themselves
to
the
agenda,
please
do
so
and
as
always,
these
meetings
are
recorded
and
uploaded
to
YouTube
so
be
sure
to
adhere
to
the
cncf
code
of
conduct
for
anybody.
That's
new.
That
mainly
boils
down
to
just
be
nice
to
everybody.
A
Let's
get
started,
I,
don't
see
anything
in
the
open
discussion
today.
So
I
think
we
can
move
right
into
sub
release.
Sub
team
updates
from
enhancements.
B
B
32
announcements,
the
production,
Readiness
reviewed
Praises
tomorrow-
that
is
a
tune
it
will
start
from
tomorrow.
So
for
all
the
announcements
leads
and
announcements
or
not.
Please
try
to
get
in
your
announcements
before
the
prr
freeze.
The
status
of
the
of
our
team
is
currently
green
and
we
have
tracked.
We
have
tracked
three
announcements
successfully
until
now,
but
we
have
reached
out
to
every
almost
every
announcements
on
the
tracking
board,
so
13
of
them
are
will
be
at
stage
Alpha.
B
Seven
of
them
are
targeting
to
Stage
beta,
and
six
of
them
are
targeting
to
Stage
stable,
so
yeah,
that's
kind
of
it.
The
announcements
number
is
still
low,
I
think
but
yeah
I'll,
post
and
follow-up
email,
a
reminder,
email
on
the
channel
on
the
dev
mailing
lists
and
of
the
prr
fees.
So
yeah,
that's
kind
of.
A
Things
yeah
I,
do
remember.
Last
week
we
discussed
about
reaching
out
to
the
Civics
and
I
think
that
was
done,
but
yeah
okay
anyway,
thanks
for
the
updates,
all
right,
CI.
D
Yes,
hello,
everyone,
so
we
are
currently
yellow
as
a
few
hours
back
like
about
one
hour
back.
We
just
got
one
failing
issue
on
Master
informing
and
we
have
a
release
card
scheduled
for
tomorrow,
like
Alpha.
Two
and
yes,
I
have
started
a
thread
for
go
non-go
signal
for
tomorrow's
release,
cut
I
will
be
responsible
for
it
and
yes,
I
am
like.
We
are
trying
to
get
the
fix
for
that.
D
One
failure
I
will
raise
and
GitHub
issue
after
this
meeting
and
yes
I'll
bring
the
Sig
Windows
team
for
looking
into
this.
So,
yes,
I
will
try
to
get
a
fix
for
this
before
the
release
cut.
So
yes,
that's
it.
Thank
you.
A
E
F
A
Yeah
that
that
should
be
okay,
usually
the
segmentation
is,
but
it's
likely
that
it's,
oh
yeah,
yeah
I'll,
take
a
look
at
it
too,
but
we
could
probably
get
an
exception
for
this.
A
All
right
bug,
triage.
G
Yes,
hello,
everyone
back
to
Ash
team
status
is
currently
green,
an
oil
is
blocking
issues
or
pis.
As
of
yet,
we
have
also
started
paying
some
of
the
long
run
against
State
apis
and
issues
to
get
an
early
updates
on
them,
and
everything
is
on
track.
Thank
you.
A
Okay
sounds
good
ducks.
H
A
I
Hey
hi
everyone,
the
status
of
the
release
notes
is
green.
Both
the
release,
notes,
PR
and
the
website.
Pr
for
Alpha
version
has
been
merged
and
yeah
we'll
create
a
discussion
thread
for
major
themes.
After
the
production,
Readiness
freeze.
A
F
Yeah,
so
the
I
would
say
for
tomorrow
the
number
support
things
happening,
the
master
informing
failing
we
currently
bump
to
go
long
dependency
in
the
KK
Ripple.
Hopefully
it
should
be
done
by
end
of
today
and
also
there's
a
change
in
the
with
this
tooling
to
now
use
gosh
sign
V2,
so
that
might
be
impactful
for
tomorrow.
So
I
would
like
to
start
cutting
the
releasing
around
10
A.M
ISD,
if
possible.
For
me
so
I
can
get
some
help
from
European
people
in
Balance
team.
A
A
J
Hello,
so
we
completed
the
shadow
orientation,
one
two
and
three
we
I
think
it
was
quite
nice.
The
slides
are
uploaded
in
slack
if
you
want
to
take
a
look,
also,
if
you
missed
it
or
in
general.
Obviously,
if
you
need
support
during
the
release
cycle,
anything
you
can
always
reach
out.
Let
me
know
other
than
that.
I
think
it
looks
good.
So
no
further
updates.
A
Okay
sounds
good
great.
B
E
A
E
Yeah,
so
we
will
have
our
first
APAC
meeting
on
June
30th.
It
is
not
yet
scheduled
and
a
time
is
not
decided
so
I
linked
there.
A
meeting
time
survey.
So
please
only
fill
this
out
if
you
are
planning
to
attend
those
and
is
in
APAC
slash
each
time
zone
to
make
sure
that
we're
holding
space
for
people
outside
of
North
America
and
then
next
Wednesday
we're
gonna
have
a
meeting
to
discuss
books
reaction.
Ci
signal
merge.
This
is
on
the
release
team
calendar.
E
It
is
not
mandatory,
but
if
you
are
interested
you're
welcome
to
join.
A
I
That
saying
scalability.
A
E
I,
don't
think
so
and
I
think
the
six
Sig
release
is
also
doing
migration
on
the
board.
So
that
might
not
be
the
one
anymore.
A
Okay
does
not
seem
like
it;
that
was
a
nice
and
quick
one
I'm
going
to
stop
the
recording.
Now
then,
thank
you.
Everybody
for
attending.