►
From YouTube: Kubernetes SIG Release for 20230228
Description
Kubernetes SIG Release for 20230228
A
Welcome
to
the
February
28th
Sig
release
meeting,
my
name
is
Jeremy
and
I'll
be
the
host.
Today
we
have
not
a
huge
agenda
today,
so
we'll
we'll
get
started
with
updates
from
Carlos
and
Adolfo
about
signing
things
that
are
and
blocking
the
releases
a
little
bit
right
now.
So
just
before
we
get
started
remember
this
meeting
is
covered
by
the
kubernetes
code
of
conduct.
A
So
please
be
mindful
of
the
things
you
say
and
we
are
recording,
so
this
will
be
available
on
Zoom
with
that
Carlos
and
Adolfo
to
be
respectful
of
your
time.
Since
you
have
to
go
to
another
meeting,
you
want
to
give
us
an
update
on
where
we
are
with
the
pending
releases.
Yeah.
B
Sure
yeah
I,
I
I,
do
have
like
a
super
brief
context,
background
on
the
problem.
So
during
the
last
patch
releases,
the
promoter
got
grade
limited,
but
when
signing-
and
we
don't
know
exactly
why,
but
it
got
rate
limited
by
six
store,
and
so
we
have
the
fortune
to
be
here
in
person
with
some
of
the
people
who
are
on
call
for
that
stuff,
so
checking
on
the
logs
and
everything.
It
seems
that
for
some
reason,
all
of
our
signing
requests
got
funneled
into
the
same
POD
at
the
same
time.
B
So
we
got
very
limited
and
those
are
that's
another
problem
to
deal
with
later.
But
the
unfortunate
situation
where
this
left
us
is
that
we
have
and
well
this
impacted
only
the
images
during
the
patch
releases,
any
all
of
all
other
images
that
have
been
promoted
after
that
are
signed
correctly
and
should
have
shouldn't
have
any
problems.
Now
the
images
of
the
batch
releases
work
on
in
one
of
three
states:
no
four
states,
the
first
ones,
don't
have
any
signatures
at
all.
B
Then
we
have
another
set
who
have
partial
signatures
in
the
sense
that
maybe
one
image
has
a
signature
and
it
didn't
got
replicated
to
the
other
mirrors.
B
Then
we
have
another
set
of
images
that
have
got
their
signature,
so
we
signed
the
images
twice
wondering
staging
and
the
second
one
at
production
time
when
we
promote
them
and
there's
a
bunch
of
signatures
that
got
the
signature
copied
from
staging.
But
when
the
promoter
broke,
didn't
get
the
the
promoter
signature.
B
So
last
week,
I
wrote
another
supplement
for
the
promoter
to
check
the
status
of
the
signatures
and
try
to
fix
them,
but
we
weren't
accounting
on
the
fact
that
some
images
have
the
signature
from
staging.
B
So
the
way
this
new
sub
command
works
is
it
will
look
for
the
specific
signature
image
stack
because
signatures
are
attached
as
kind
of
image,
so
it
checks
for
the
existence
of
the
tag
and
the
first
iteration
I
wrote
simply
assumes
that
if
it
finds
A.C
it's
signed,
but
then
when
we
were
checking
before
running
the
job,
we
found
this
new
situation
that
somehow
the
signature
from
from
staging.
So
that's
where
we
are-
and
we
already
delayed
the
the
releases
from
last
week
to
this
week,
and
now
we
have
this
new
yeah.
C
And
then
we
came
like
with
some
ideas
and
suggestions
that
we
want
to
share
in
see.
What's
the
decision
from
from
our
site,
one
is
we
one
option
is
we
continue
like
we
need
to
update
this
new
comment
to
check
if
the
signature
have
both
signatures,
or
at
least
the
crowd,
trust
signature?
If
they
don't
have
it,
we
need
like
a
somehow
sign
those
things
now.
C
Yeah
and
if
we
follow
this
path,
we
might
need
to
delay
the
the
battery
releases
again,
maybe
for
the
next
week
or
maybe
even
longer.
We
don't
know
yet
other
option.
Is
we
make
a
patch
in
the
release,
release
stage
part
to
ignore
the
checking
the
signatures,
and
then
we
complete
this
release
and
we,
like
maybe
burn
this
release
and
cut
a
new
one.
C
Week
and
and
then
we
run
the
new
one
and
like
we
reverted
the
change
that
checks
the
signature,
but
then
we
cut
a
new
set
of
patch
releases
and
then,
while
we
do
that,
we
continue
work
on
this
tool
in
this
common
tool.
Then
we
can
validate
these
two
with
the
dead
release.
Then
we
can
sign
the
the
the
current
release
with
the
missing
signatures
to
see
if
everything
works,
but
then
we
not
delay
anything
more
and
then
we
just
cut
a
new
release
and
the
current
one.
C
Yeah,
but
this
problem
we
might
maybe
break
people
down
Downstream
users,
because
they
might
have
already
checking
the
signatures
with
like
this
with
it's
a
I
know
which.
B
B
If
I
had
like
one
more
day
like
a
full
work
day
to
work
on
it,
I
could
get
the
command
down,
but
unfortunately
we're
in
this
thing
and
we're
in
and
out
locked
in
an
auditorium,
so
I'm
I'm,
not
sure
I'm
gonna
get
the
time
to
to
fix
that
part
of
the
of
the
UK
promo
thing.
So
well
that
that's
that's
what
I
have
so
far
so
happy
to
hear
others
I
know.
D
D
B
Just
just
to
have
some
some
yeah
just
to
make
the
context
clear
for
everybody
in
order
to
skip
the
the
patch
release
we
need
to.
B
E
D
No,
the
I
think
permission
but
is
kind
of
we
can
just
basically
refresh
configuration
I'm,
pretty
sure
to
a
state
default
release
and
we
say:
okay,
we
have
to
wish
him,
but
by
120
I.
Think
the
what
of
January
I
think
my
question
is:
do
we
have
GitHub
tags
right
now
existing
in
the
KK
Ripple
matching
batteries.
B
C
C
D
C
E
Me
ask
something:
promoter
did
the
mutual
right,
it
promoted
images
to
all
miracles,
so
images
are
ready
to
use
they're.
Only
not
sign
is
that
correct.
Yeah.
B
E
Basically,
if
we
will
proceed
with
release,
we
get
rid
of
that
checking
in
career
release.
We
will
have
fully
functional
release
only
that
they
are
not
signed
exactly
what
if
we
like
stop
there
I
mean
we
tell
communicate
those
services
are
not
signed.
If
you
depend
on
that
like
we
are
a
bit
sorry,
but
we
will
just
release
a
new
one
in
March,
which
is
like
in
two
weeks
from
now,
so
that
we
avoid
cutting
another
set
of
actually
yeah.
E
Yeah
that
would
be
I
think
that
would
be
a
good
plan
like
I.
Think
not
a
lot
of
folks
really
depend
on
that
right
now,
so
this
is
not
really
going
to
affect
many
folks,
not
nice,
but
something
that
we
can
consider.
C
And
the
idea
is,
we
finished,
this
updated
the
two
and
then
we
signed
the
ending
up
like
in
the
future
yeah.
B
B
Some
all
sorts
of
automated
processes-
Downstream,
right
and
I-
can
bet
my
house
even
that
more
people
are,
depending
on
those
tags
and
artifacts,
getting
released
to
trigger
their
processes
than
the
signatures.
So
they
have
to
make
a
choice.
I
would
rather
say
we
make
we
release
with
other
signatures
and
make
them
consistent,
eventually,
yeah.
B
G
My
other
question
is
I
need
to
do
some
work
in
Cape,
promo
and
a
bunch
of
other
things
in
like
a
week
and
a
bit.
Do
you
think
you'll
have
some
capacity
to
help
me
out
with
that
or
do
I
need
to
consider
adoptions.
G
Yeah
so
I'm
thinking
of
making
some
changes
to
kpromo
in
paper,
it's
trivial,
but
if
it
gets
messy,
it's
gonna
require
All
Hands
back
to
deal
with
it.
So
is
there
capacity
for
both
of
you
to
look
at
over
the
next
two
three
weeks.
B
C
Yeah
Okay,
so
to
summarize,
we
are
like
we
are
agreeing
that
we're
gonna
continue
the
release
but
release
without
the
signatures.
Is
that
correct
assumption.
B
So
that's
the
only
one
and
we
don't
have
other
other
than
that.
We
don't
expect
any
other
yeah
yeah
I
mean
people
verifying
manually
or
whatever,
but
that's
the
only
one.
C
And
CC,
just
to
make
sure
this
is
only
affected.
The
this
patch
release
is
not
gonna
like.
We
hope
that
the
rate
limit
and
stuff
not
affected
the
the
the
current.
C
Yeah,
the
the
127
that
you
want
to
cut.
Maybe
this
week.
B
Exactly
oh
yeah,
maybe
you
missed
that
CC,
but
so
the
the
the
rate
limit
has
not
changed
from
six
or
side
I
mean
now
it's
changed
because
they
increased
it,
but
it
had
not
changed
for
months
and
for
some
reason
when
we
signed,
we
hit
one
pod
with
all
the
requests
at
the
same
time
and
that's
why
it
failed.
But
we
don't
know
why
maybe
bad
luck.
Cluster
was
very
balancing.
Who
knows.
B
And
we
have
like
a
bunch
of
we
have
about
70
other
images
which
have
been
released
promoted
after
the
Patch
releases
were
cut
and
all
of
those
were
signed
correctly.
I
mean
it's
not
the
same
number
of
images,
but
those
are
signed
correctly.
F
I
see,
oh
another
question
is
like
the
the
patch
release
is
already
delayed
for
at
least
the
two
weeks
by
now.
Right,
so
are
we
still
planning
to
like
so
far
as
the
current
plan,
we
still
plan
to
do
the
patch
release
for
like
a
rich
plan
last
month,
like
in
February
patch
release
and
then
do
another
patch
release
in
two
weeks.
B
And
and
the
other
thing
that
we
should
kind
of
communicate
clearly
is
the
patch
releases
were
already
so.
The
releases
were
already
cut
one
week
back.
So
even
if
we
release
tomorrow
next
week
or
whatever
those
changes
correspond
to
the
Viewpoint
one
week
ago,
so
there's
no
so
the
the
actual
artifacts
the
artifact
delivers
is
delayed.
But
this
was
cut
in
time.
I.
F
E
I
just
want
to
mention
something
super
important,
but
we
have
to
make
sure
that
nothing
got
merged
since
starting
the
releases.
Otherwise
we
might
have
issues
with
cutting
those
releases,
and
this
is
also
a
shout
out
to
release
budget.
Please
don't
mention
anything
otherwise,
yeah.
We
will
have
issues
yeah.
C
That's
a
good
point:
yeah
I
was
checking
out
the
Cherry
picks
and
so
far
I
didn't
see
any
any
more
use
of
that.
C
F
E
C
E
F
A
No
I
think
that's
pretty
clear,
we'll
summarize
in
in
the
Sig
release
Channel
just
for
everybody
else.
It's
not
on
the
meeting
right
now.
A
Cool,
does
anybody
have
anything
else
they
wanna
go
over?
The
agenda
was
pretty
empty.
Was
that
was
empty
today,
so
you
didn't
have
anything
else
to
cover.
It's
gonna
end
a
little
early
and
give
folks
time
back
if
they
would
like.
H
I
have
a
just
a
small
question:
go
for
it
new
and
thank
you
all
for
letting
me
join.
Is
there
any
chance
that
maybe
in
the
future,
we
can
separate
out
the
tagging
and
the
artifact
generation
so
that
we
can
get
the
tags
out
even
when
the
artifacts
are
not
generated
yet.
H
B
Well,
the
problem
is
that
yeah
sometimes
we
need
to
to
like
when
we
are
building
and
we
sometimes
need
to
the
stage
fields.
We
need
to
like
run
them
several
times,
and
we
have
the
processes
set
up
as
the
most
complex
parts
of
the
of
the
release
process
happen
during
staging.
So
we
tried
to
aim
for
in
situations
like
this
one,
where
things
may
fail.
We
try
to
catch
them
before
we
publish
the
tags
so
in
order
to
when
we.
B
So
if
we
need
to
go
and
make
any
adjustments
and
we
need
to
like
merge
more
PRS
or
whatever
we
can
still
do
it,
but
because,
if
we
go
to
tag
early,
then
we're
subject
to
always
release
at
that
Viewpoint
and
make,
and
we
have
the
in
the
past.
We
have
like,
like
needed,
to
scrap
releases
entirely,
because
we
didn't
have
a
way
out
when
the
tag
was
already
cut.
H
Okay,
that
sounds
absolutely
reasonable.
Sorry,
yeah.
H
Really
appreciate
it,
you
guys
are
doing
great.
Thank
you
so
much
thank.
B
A
Welcome
by
the
way,
is
it
Matt.
H
H
A
A
G
Yeah,
that's
gonna
run
for
up
to
127
my
disappear
briefly
for
like
a
keep
calm
message,
but
we'll
be
back
on
right
after
that
for
a
little
bit
while
and
it'll
be
gone,
but
yeah.
This
is
happening
after
all,
yes,
but
the
change
will
be
official.
Luckily,
like
two
like
three
weeks.