►
From YouTube: Kubernetes Release Team Meeting for 20230927
Description
Kubernetes Release Team Meeting for 20230927
A
A
My
name
is
Priyanka
sagu
and
I
will
be
hosting
this
week
for
129
release
cycle
meeting
today
as
discussed
I.
This
is
week
four
of
the
129
release
cycle
and
this
meeting
abides
by
the
kubernetes
Community
code
of
conduct,
which
pretty
much
comes
down
to.
Please
be
nice
and
excellent
to
each
other.
A
I'm
again,
posting
a
link
to
the
meeting
notes
in
the
chat
so
feel
free
to
add
yourself
as
attendees
there.
Thank
you
another
note.
This
meeting
is
recorded
and
will
be
publicly
posted
on
the
kubernetes
YouTube
channel.
So
if
you
want
to
be
not
recorded
or
anything
that
you
are
going
to
discuss,
please
be
mindful
of
this.
Thank
you
and
you
can
keep
your
cameras
or
audios
turned
off
with
that.
Let's
move
to
the
open
discussions.
A
There
are
no
items
there.
Just
a
reminder:
we
will
be
having
a
129
retrospective
meetings
sometime
in
the
middle
of
the
cycle,
as
well
as
one
around
the
confusion
of
the
cycle.
So
if
you
have
any
feedbacks
comments,
anything
you
would
like
to
discuss
with
the
wider
Community.
Please
add
your
items
there
in
the
agenda
document.
The
link
is
in
the
meeting
notes
before
I
move
forward.
We
do
we
have
anybody
new
on
the
call
and
want
to
introduce
themselves.
B
Checking
I
can
go
I'm,
I'm,
a
D'souza
I.
Just
this
is
the
person
I'm
joining
the
release.
Team
meeting
and
I'm
based
out
of
Australia
I've,
been
in
devops
positions
in
for
the
past
over
a
decade,
I'm
just
trying
to
be
more
active
in
kubernetes
space,
open
source
space.
A
A
If
not,
let's
move
to
our
team
updates
enhancements
with
Ryan.
C
So
we
agreeing
this
week
so
we
have
total
62
enhancements
still
so
far.
So
we
have
completed
a
slack
out
three
to
all
the
six
things
this
week
and
we
are
doing
an
initial
Outreach
for
all
the
enhancements
currently
on
the
tracking
board
and
marking
them.
If
it's
extract
for
enhancement
stream,
enhancement
streams
or
at
risk,
and
just
a
reminder
next
week
is
scheduled,
ET
scheduled
for
6th
of
October,
so
the
that's
all
from
enhancing.
A
Thanks
for
the
update,
Ryan
I,
also
checked,
most
of
the
enhancements
are
already
reached
out
by
the
enhancement
seams.
So
that
is
good
and
yes
reminder
to
everyone.
We
are
approaching
enhancements
freeze
next
week.
So
if
you
want
to
track
your
Kips,
this
is
the
time
to
do
it.
Now.
A
If
not,
let's
move
to
CI
signal
with
vita.
D
Hey
everyone,
my
Emery
depths
and
the
shadow
for
CI
signal.
Our
overall
status
is
green.
The
issue
tracking
Port
is
up
to
date
and
released
1.29
Alpha
this
week.
So
thanks
to
the
release,
identity
and
everyone
involved
in
this.
A
A
If
not,
thanks
for
the
updates,
let's
move
to
bug
triage
with
eager.
A
But
thanks
for
the
update
it
any
questions
for
bakrid.
A
Not
thank
you.
Let's
move
to
docs
with
that
hello.
F
All
of
our
early
release
cycle
weeks,
one
and
two
tasks
are
complete,
so
our
status
is
green.
Shout
out
to
my
lovely
Shadows
for
getting
themselves
scheduled
for
every
single
thing.
They
could
possibly
need
to
deal
with
other
people
on
for
the
rest
of
the
release,
so
everybody
is
scheduled
for
weekly,
Branch,
syncs
and
updates
to
both
here
and
Sig
docs
meetings,
which
is
pretty
cool,
and
so
we
are
ready
to
assign
caps
and
begin
Outreach
as
soon
as
enhancements.
Freeze
is
done.
A
A
Thanks
again
cat:
let's
move
to
release
notes
with
Harsha.
G
Hi
Priyanka
and
hello
everyone
so,
overall
the
release
note
status
is
great
and
the
alpha
one
pair
is
open,
opened
up
and
it
is
up
for
review.
So
we
will
open
a
thread
for
the
major
themes:
discussion,
post,
the
production,
Readiness
phrase
yeah
and
that's
all.
A
Thank
you
Android
also
to
the
pr
for
a
review.
I
would
also,
if
you
are
on
the
call
just
heads
up
for
you,
thank
you
and
thanks
for
raising
the
pr.
Thank
you
any
questions
for
release,
notes.
A
If
not
thanks
again,
let's
move
to
comms
with
Carol.
H
Hi
sure
Carol
lead
from
cons
and
our
updates.
The
team
sent
message
in
the
slack
to
the
six
check,
if
there's
any
British,
blog
or
duplications.
Also,
we
sent
our
stats
to
sick
dog,
a
pack
meeting
that
is
and
another
time
zone
that
we
couldn't
participate,
but
we
sent
the
status.
H
We
update
our
boards
with
people
that
is
assign
it
to
track,
and
we
also
talking
to
to
track
the
major
themes
with
with
the
help
with
the
enhancement,
team
and
I
think
similar
to
the
docs.
We
will
send
a
message
in
the
caps
after
the
freezing,
like
a
docs,
also
sent
a
message
to
track
the
documentations
with
your
life
to
formalize
and
send
a
message
is
any
problem
for
doing
that.
H
Because
this
will
be
like,
if
it's
okay,
like
enhancement
to
to
the
handbook,
to
also
put,
as
example,
to
communicate
with,
to
notify
with
all
the
Caps
if
they
have
any
yeah.
I
F
Yeah
I
thought
I
thought
that
was
documented
honestly,
because
I
I
did
it
every
time
I
was
on
comms.
Did
you
Mickey
yep.
F
J
Same
thing
for
for
me,
I,
mostly
use
slack
after
they
were
selected,
but
I
think
that
there
were
also
a
comment
in
in
the
in
the
cap.
I,
don't
think.
That's
specifically
documented
just
that
we
need
to
to
communicate
and
get
the
analysis
from
the
from
the
owners.
H
J
One
thing
that
I
was
thinking
and
we
can
discuss
this
and
on
a
retro
or
some
someplace
else.
It
might
be
useful
to
think
if
this
kind
of
question
for
the
opt-in
could
be
something
that
could
be
added
as
a
checklist
earlier
earlier
in
the
in
the
process.
Just
just
like
people
answer
about
are
there
is
the
the
cap
ready
is
the
prr
done.
Maybe
answering
are
you
interested
in
in
in
in
in
opting
in
yes
or
no,
but
I
guess
this
is
out.
This
is
not
useful
for
for
this
stage.
A
Good
feedback
actually
I
think
this
is
something
we
can
include
in
the
checklist
work
for
the
role
leads,
so
something
like
three
cycle
or
three
early
weeks
items
but
great
point.
There
you
go.
Let's
discuss
this
dude
during
the
checklist
work
as
well
and
as
well
as
during
retro.
Thank
you
and
thanks
cat
Mickey
for
the
feedback
there.
So
I
think
we
are
good
there
Carol
we
can
send
out
Communications
on
the
PRS
kprs.
A
If
not,
thanks
for
the
updates
again
Carol,
let's
move
to
release
Branch
management
with
Jim.
K
K
I
did
the
I
guess
picture
link
or
a
copy
of
the
table
there.
That
was
in
the
pr
there
for
quick
reference.
I
tried
to
avoid
any
release
Cuts
around
kubecon
North
America,
but
we
still
kind
of
couldn't
avoid
doing
early
November
kind
of
the
mid
late
November
dates
to
kind
of
stay
on
track
for
the
the
release
on
December
5th,
but
yeah
our
net.
We're
all
good
and
looks
like
things
are
rolling.
A
Thank
you
so
much
for
doing
all
the
work
there
for
Alpha
One.
It
was
adventurous
and
thanks
for
the
schedule
as
well
any
questions
for
release.
Branch
management.
A
Not
we
don't
have
Xander
on
the
call,
but
he
has
left
updates
so
on.
All
onboarding
sessions
are
completed
last
week.
I
think
the
recording
is
available
if
any
Shadows
were
not
able
able
to
join
the
calls
due
to
time
zone,
please
ping
Xander
in
sick
release
or
otherwise
for
recordings.
A
Thank
you
and
then
I
have
a
few
updates,
mostly
the
same
updates
from
us
from
Jim.
We
release
129
Alpha
One
on
25th
Monday
after
a
few
blockers
and
the
release
cut
timeline
is
also
updated.
That's
the
link
there.
We
have
a
prr
freeze
coming
up
tomorrow.
A
That's
a
heads
up
for
everyone
and
also
enhancements
please
coming
up
on
October
6th
I.
Think
another
update
is
also
from
the
new,
updated
release
timeline.
We
had
Alpha
2
planned
for
this
week
tentatively,
but
that
is
also
now
moved
to
October
10,
which
would
be
I
believe
the
week
after
coming
one-
and
that's
all
updates
from
me
one
question
to
you
Jim.
This
was
something
that
came
during
the
discussion
ongoing
discussion
on
129
Alpha,
zero
thread.
A
We
wanted
to
document
some
of
the
knowledge
we
have
with
Marco
at
the
moment
regarding
OBS
side
of
things.
So
is
this
something
that
is
relevant
for
our
upcoming
release
Cuts
as
well,
and
we
should
document
it
before.
A
K
We
should
definitely
track
it
for
I,
don't
know
if
we
have
a
retro
deck
already
available
to
use
or
something
like
that.
We
should
track
it
long
term,
but
the
issue
we
ran
into
most
likely
wouldn't
happen
again.
If
it
does
happen
again
until
1
30
or
like
the
alpha
cut
for
130,
so
I
don't
think
we
need
to
do
anything
for
the
next
Alpha
cut,
but
it
is
worth
tracking
long
term.
K
I
think
there's
an
open
issue,
but
it's
kind
of
generic
I'm
happy
to
own
that,
but
again,
I,
don't
think
it's
a
priority
at
the
moment.
A
God
yeah
I
just
wanted
to
cross
check
if
it
is
a
requirement
for
upcoming
129
Cuts,
but
that's
good.
Yes,
we
have
a
retro
deck,
so
I
I
will
take
an
action
item
and
I'll
move
it
there.
Thank
you
and
from
six
scalability
we
also
have
a
green
status,
so
that
is
all
good
there.
Any
last
minute
updates
discussion
items
from
anyone
before
we
close
the
call.
A
If
not
I'll
go
ahead
and
stop
the
recording.