►
From YouTube: Kubernetes SIG Release for 20230314
Description
Kubernetes SIG Release for 20230314
A
All
right
welcome.
Everybody
today
is
March
14th
2023,
and
this
is
our
weekly
Sig
release.
Meeting
so
remember
we.
This
is
a
meeting
that
is
publicly
regarded
to
the
internet,
and
so
please
be
mindful
of
anything
that
you
say
and
do,
and
this
meeting
is
governed
by
the
kubernetes
code
of
conduct,
which
will
send
to
be
awesome
to
each
other.
A
A
All
right,
we
have
a
pretty
light
agenda
today,
so
we'll
start
with
the
sub-project
updates.
Anybody
wants
to
do
a
an
update
on
release
engineering.
B
Let's
see
the
image
freeze
stuff
is
coming
along.
Is
I
opened
a
number
of
PR
this
morning,
I'm
on
stage
most
of
the
changes
for
the
rest
of
the
week
and
then
hopefully
we
can
start
reviewing
things
next
week
and
try
and
get
all
the
changes.
Nourished
on
like
the
27th
and
team.
A
We
were
waiting
on
the
on
a
patch
that
we
merged
yesterday
to
fix
and
check
the
the
signatures.
So
it's
it's
now
it's
now
in
so
we
should
be
able
to
to
go
move
forward
with
that.
That's
why
Carlos
froze
the
bump
of
the
promoter.
A
A
This
is,
this
is
part
of
the
pr
set
that
you
were
discussing
last
week
right.
A
A
Okay,
just
to
make
sure.
B
So
if
you
go
to
k6
promo
tools,
there's
a
PBR
code
669,
that's
the
main
PR
recorded
the
main
things
I
need
to
do
in
the
tooling
yeah.
Okay,.
A
Yeah
for
sure,
let's
I'll
review
it
and
get
it
merged
afterward
or
with
a
call
I
mean
it's
been.
It's
been
there
like
for
a
couple
of
months
now,
and
so
it
should
be
ready
to
go
and
if,
if
you
need
to
get
any
other
feature
of
the
due
to
the
register
freeze
or
whatever
before
we
got
it
just
let
us
know
this.
B
Is
the
main
one
I
need
to
do
this
and
then
I
update,
testing
Pro
and
make
sure
the
files
in
the
right
place?
That's
it.
B
A
Okay,
Okay
so
I
think
okay,
I'll
I'll
approve
it.
While
someone
continues,
the
the
update
I
see
a
mention
on
the
agenda
narun.
Do
you
want
to
talk
about
the
the
patch
releases
tomorrow.
D
C
Confirmed
their
availability,
but
tomorrow,
as
Google
build
admins,
so
tomorrow,
I
have
created
all
the
tracking
issues
around
10
minutes.
There
I
will
start
with
the
cuts
early
on
in
the
morning
in
India
time
and
then
whatever
is
left,
can
be
taken
over
in
the
U.S
morning
times
so
that
we
have
like
Smooth
transition.
A
A
Anybody
has
any
questions
for
another
one
about
or
the
release
engineering
team.
The
race
managers
in
general.
A
Okay,
so
before
yeah
I,
just
like
wanted
to
give
up
an
update
on
what
I
was
on
the
changes
that
we
wanted
to
get
into
the
promoter,
so
the
the
the
those
changes
that
we
were
waiting
for,
which
that
I
was
telling
Muhammad
about
were,
are
related
to
fixing
the
signatures
that
got
broken
during
the
last
batch
releases.
A
I
sent
the
last
batch
yesterday
to
ensure
that
we
can
check
and
verify
the
signatures
and
resign
whatever
is
missing
and
I
also
opened
up
this
tracking
issue
I'm,
showing
in
the
chat
now
and
to
exactly
yeah
yeah.
It's
two
give
more
context
on
what
we
are
trying
to
do
and
how
to
fix
them.
So
things
like
Muhammad
being
out
of
the
look
of
what
we
were
working
on.
Does
that
do
not
happening
again.
A
So
if
anybody
wants
to
help
fix
those
right
now,
it's
mostly
I'll
personalize.
Those
changes
like
running
them,
ensuring
that
they
work
and
then
basically
letting
setting
up
the
job
to
run
and
constantly
verify
the
signatures.
A
E
I
just
had
one
quick
update
when
we
did
the
branch
cut
for
126.
We
had
a
couple
of
issues
that
we
took
action
items
for
one
was
the
publishing
bot
rules
didn't
get
updated
correctly.
So
we
wanted
to
update
the
handbook
to
use
the
update
rules
tool.
So
I
did
that
I
wrote
a
PR
for
I,
had
changes
for
this
in
a
branch,
but
I
forgot
about
them
and
never
pushed
them.
E
So
I
did
that
today,
I
went
to
make
sure
that
they
were
there
like
oh
they're
out
there,
because
CC
and
Company
will
be
doing
I.
Think
the
127
beta
cut
this
week,
yeah.
C
E
E
So
the
I
updated
the
handbook
for
a
couple
of
more
Branch
cut
related
tasks.
Mostly,
so
we
can
build
improve
a
new
Cube
cross
image
once
Branch
cut
happens.
We
don't
forget
to
do
that
because
we
had
forgotten
to
do
that
before
and
we
agreed
to
do
it
during
Branch
cut
or
after
the
branch
cut.
So
that's
another
post,
Branch
cut
task
and
this
few
steps
that
go
along
with
that
and
then
a
change
to
the
ways.
E
The
publishing
bot
rules
get
updated
to
use
the
Tool
instead
of
hand
crafting
things
so
just.
A
A
Okay,
so
then,
let's
move
on
to
the
release
team
updates,
anybody
wants
to
do
that.
D
Yeah
only
thing
we've
got
for
today
is
code
freeze
at
5,
PM
Pacific
time
tonight.
So
far
things
are
looking
good.
We,
we
did
receive
one
preemptive
exception
request
which
we
approved,
but
yeah
aside
from
that,
we'll
we'll
see
how
things
go
after
freeze
this
evening,
what
exceptions
look
like
and
yeah.
A
A
All
right,
I,
don't
see
any
other
open
items
for
open
discussion.
So
if
anybody
wants
to
bring
something
to
the
table
or
wants
to
discuss,
not
sit
down.
A
Okay,
well,
if
not,
maybe
we
can
give
folks
the
rest
of
the
meeting
minutes
back
and
we
can
continue
chatting
on
slack
on
in
Mid
and
next
Tuesday.