►
From YouTube: Kuberentes SIG Release Meeting for 20230906
Description
Kuberentes SIG Release Meeting for 20230906
A
Awesome
so
hey
folks,
my
name
is
Mickey
and
I
will
be
the
host
for
today's
kubernetes
1.29
meeting
it's
pretty
exciting.
This
is
the
first
week
of
the
release
and
today
is
September
6th
Please.
Be
aware
that,
since
this
is
a
kubernetes
community
meeting,
it
does
adhere
to
the
kubernetes
code
of
conduct,
which
essentially
boils
down
to
the
excellent
to
one
another,
also
as
I
mentioned
before,
this
meeting
is
being
recorded
and
will
be
posted
to
YouTube.
A
A
B
B
There
was
some
updates
to
the
handbook
if
anyone's
interested,
I
linked
it
there,
but
the
biggest
one
that
might
affect
the
release
team
is
now.
Then
hanselman's
board
is
going
to
track
per
Milestone,
so
the
status
is
going
to
be
like
at
risk
for
the
enhancement
trees
at
risk
for
code
freeze,
instead
of
just
at
risk
or
tracked,
the
enhancement
tracking
sheet
is
linked
there
and
we
currently
have
35
enhancements
on
on
the
board.
B
C
Hi
everyone,
my
name,
is
a
release
cycle
I'm.
Currently,
in
my
final
year,
questioning
computer
science
engineering
and
as
far
as
the
status
for
CI
signal
goes,
we
are
starting
with
the
yellow
status
because
we
have
two
failures
on
the
master.
Blocking
dashboard
and
two
failures
on
the
master
informing
dashboard,
all
of
which
are
under
in
the
folks,
are
looking
into
those
issues,
and
it's
currently
underway,
and
apart
from
that,
I
have
CI
signal
of
meeting
scheduled.
Without
previously,
it
may
have
on
8th.
D
Hello,
everyone
I'm,
miet
I,
will
be
the
lead
for
the
back
to
dash
team
for
this
release
and
I've
been
a
part
of
the
previous
release
of
the
bacteria
Shadow
and
at
my
day,
job
I
worked
as
a
senior
regenerate
detectify,
which,
at
the
time
of
security
company
and
going
into
the
details
of
back
to
realize
uptake.
The
status
is
currently
green.
Now
blocking
issues,
PR
developed
issues
and
eight
PR
were
open
right
now
and
with
further
updates
to
the
shadow
of
selection
is
ongoing
and
I
will
be
updating
to
Port
foreign
for
1.289.
E
E
Stuff
from
the
previous
lead
was
actually
completed,
so
there's
not
cleanup
from
the
last
release
that
I
need
to
do
right
now.
I
do
have
a
couple
of
quick
questions.
While
I
have
Mickey
here
and
Tim,
the
handbook
says
that
you
should
do
an
intro
as
a
GitHub
discussion
that
does
not
appear
to
have
been
done
since
1.22.
Is
that
actually
necessary
or.
E
E
Yeah,
okay,
and
on
setting
up
access
the
handbook
also
explicitly
hands
you
a
reference
PR
made
from
Maine
to
get
ownership
for
yourself,
but
there
is
a
linked
PR
in
discussion
that
calls
out
that
you
should
actually
make
that
PR
from
the
dev
Branch
not
from
Maine.
Was
that
ever
sorted
out
and
what
is
the
actual
answer?
I.
E
F
F
A
A
G
Hello,
nothing
major
to
add
at
this
stage,
so
I've
got
the
shadow
shadow
applications
yesterday
and
I'm
starting
to
go
through
them
in
order
to
select
the
the
four
Shadows
following
the
proposed
guidelines
in
terms
of
diversity
on
all
different
angles,
and
that's
pretty
much
it
for
now.
The
the
next
action
from
release
notes
is
in
the
19th
of
September
I,
think
in
which
we'll
start
with
the
first
draft
PR.
So
we're
good.
A
G
G
H
H
I
I
Yeah,
hello,
everyone,
I'm,
I'm,
Xander,
I
I've,
been
involved
in
the
release
team
in
one
capacity
or
another,
since
version
120,
maybe
119
I'm,
not
sure,
actually
last
release.
One
128
was
the
first
one
since
120
that
I've
I've
not
been
on,
but
it's
it's
good
to
be
back
I
guess
by
day,
I
I
work
on
open
source
at
Microsoft
as
a
product
manager,
yeah
I
think
my
role
through
this
is
to
kind
of
facilitate
the
shadow
program,
and
that
includes
you.
I
I
I
This
is
kind
of
my
my
going
rogue
that
I'm
doing
here,
but
I
I
want
us
to
kind
of
focus
on
returning
members
for
this
cycle,
because
we
have
a
lot
of
folks
that
have
participated
over
several
Cycles.
Now
that
or
even
just
one
cycle
that
want
to
continue
contributing
and
I
think
we
can.
We
can
do
well
to
kind
of
foster
that
that
desire
to
stay
active
and
and
keep
contributing
once
you've
started.
I
I
I
We
want
to
be
building
teams
that
as
much
as
possible
stretch
across
Global
time
zones
so
that
we
have
coverage
across
you
know
across
different
times
and
make
sure
that
the
the
alternate
time
meetings
on
on
Fridays
and
stuff
are,
you
know:
we've
got
representation
at
those
yeah
I
think
that
was
everything.
I
had
yeah
definitely
reach
out
with
any
questions
that
come
up,
selecting,
shadows,
I'm,
happy
to
help
provide
input
and
all
of
the
the
lead
Shadows
have
been
through
this
before
too.
I
G
Yeah
one
just
so
fry
the
I
mean
it's
it's
it's.
We
don't
have
a
lot
of
time,
but
if
we
factor
in
checking
for
previously
checking
for
availability
right,
because
one
thing
is
people
adding
their
name,
the
other
is
to
actually
ask.
Are
you
interested
I'm,
not
I'm,
not
sure
if
this
is
possible
until
Friday,
but
maybe
I'm
overthinking,
it.
I
I
To
be
tight,
I
think
my
goal
is
to
have
things
Locked
In
by
next
Wednesday,
but
that's
where
I
think
you
know.
If
we
can
get
things
if
we
can
have
decisions,
at
least
by
Friday
morning,
that
gives
everyone
Friday
to
send
out
emails
to
the
selected
Shadows
to
check
for
their
availability
and,
failing
that
you
know
Monday,
we
would
start
and
then
hopefully
have
things
ready
by
Wednesday.