►
From YouTube: Kubernetes SIG Release Bi-Weekly Meeting for 20220628
Description
Kubernetes SIG Release Bi-Weekly Meeting for 20220628
A
Hey
everyone
welcome
to
the
june
28th
bi-weekly
sig
release
meeting.
My
name
is
jeremy
I'll,
be
the
host
today.
Just
a
quick
reminder
before
we
get
started.
This
meeting
is
covered
under
the
kubernetes
code
of
conduct.
So
please
be
mindful
of
the
things
that
you
say.
This
will
also
be
recorded
and
available
on
youtube.
A
A
If
you
are
attending
the
meeting,
please
add
your
name
to
the
attendees
list,
so
we
have
a
list
of
who
is
here
and
with
that
we
will
go
ahead
and
get
started.
We'll
start
off
just
by
opening
the
floor
up
for
anybody.
That's
never
attended
a
sig
release
meeting
before
to
introduce
themselves
say
hello,
say
what
you're
interested
in
see
release
for.
B
A
Okay,
with
that,
out
of
the
way,
do
you
want
to
unmute
yourself
and
say
hello
or
anything
else,
you
good
or
we'll,
give
you
a
chance
to
do
that
if
you'd
like
to
okay
well,
welcome
anyway,
to
the
meeting
happy
to
have
you
here
hope
to
see
you
again
at
future
meetings
too:
okay,
we'll
jump
down
to
sub
project
updates.
Next,
first
up
we'll
do
release
engineering.
C
Well,
I
was
out
last
week
and
there
are
a
couple
of
of
things
that
are
interesting,
so
the
first
one
is
we
were.
We
were
allowed
to
go
the
new
release
of
one
our
one.
It
is
built
materials
tool,
but
it
had
a
pretty
nasty
regression
due
to
an
code
change
of
stream
and
it
has
been
fixed
now
and
so
we
should
be
able
to
cut.
One
really
soon
should
be
version.
0.40.
C
Which
comes
with
a
number
of
features
which
include
json
output
and
a
new
mini
querying
language
into
the
build
materials
to
to
extract
the
information
from
them.
The
other
interesting
one
is
that
I
had
a
chance
to
meet
with
some
of
the
spvx
maintainers
during
open
source
summits,
and
one
of
the
things
that
came
up
was
that
they
they
are
reshifting.
C
The
maintainers
of
the
official
spdx
libraries
in
go
spdx
is
a
language
to
the
the
the
specification
to
generate
the
the
s
bonds
with
the
materials
from
the
union
foundation,
and
so
the
the
the
go
implementation
of
the
libraries
will
be.
I
was
asked
to
go
and
help
be
a
part
of
the
new
manchester,
and
so,
if
anyone
is
interested
in
collaborating
in
that
project,
please
let
me
know
and
there's
lots
to
do
there,
because
there
will
be.
C
D
D
F
E
G
Sure
we
had
the
enhancement
phrase
last
thursday
and
it
went,
went
super
well
and
so
far
we
only
received
one
exception
request
and
they
have
approved
that
and
it's
already
merged.
So
currently,
I
believe
we
have
56.
He
has
been
tracked
out
of
76
enhancement,
opt-in
and
that
should
be
good
for
this
release
cycle
and
yeah.
That's
it
we're
looking
forward
to
today's
alpha
2
card
as
well,
and
the
release
notes
team
already
for
that
yeah
thanks
for
taking
care
of
that.
A
H
H
I
think
a
lot
of
us
conflate
them
or
we
end
up
kind
of
discussing
items
at
both
of
them
just
because
of
timing,
and
so
I
think
this
proposal
was
thrown
out
after
a
discussion
about
you
know,
potentially
aligning
these
meetings
so
one
we
could
get
broader
reach
with
our
asia
pac
eu
and
as
well
as
I'd,
make
me
another
meeting
that
is
probably
more
friendly
to
more
of
the
you
know:
north
america.
You
know
that
that
kind
of
time
zones,
as
well
as
maybe
even
potentially
even
the
far
pacific.
H
A
Okay,
sorry
yeah,
so
I
don't
think
we
got
a
lot
of
feedback
on
the
the
issue
in
github,
so
I
think
we
need
to
broadcast
it
more
widely
and
to
do
that,
I
started
crafting
an
email
in
hackmd
and
I'll
drop.
The
links
into
the
chat
so
folks
can
feel
free
to
edit
just
make
suggestions
if
you'd
like
to
and
included
with
that,
I
made
two
doodle
polls
and
I
thought
this
would
be
a
good
opportunity
to
look
at
those
times.
A
I
just
took
a
stab
at
like
picking,
sometimes
on
same
day,
tuesday,
just
to
kind
of
keep
that
consistency,
but
things
that
were
shifted
a
little
bit
more
friendly
for
folks
in
europe,
and
things
were
shifted
a
little
bit
better
for
our
folks
in
the
us.
So
for
the
apac
eu
kind
of
centric
times.
These
are
all
in
gmt,
plus
two,
so
berlin
time,
twelve
one,
two
three
and
four.
If
anybody
is
in
europe
on
the
call
right
now
are
there
times
it
would
be
better
yeah.
A
I
see
james
and
I
see
rob
anybody
else.
Are
there
times
it
would
be
better
for
folks.
Obviously,
this
was
just
like.
I
I
looked
at
the
times
and
did
some
math
and
thought
like
this
is
a
kind
of
a
block
in
the
middle
of
the
day.
Maybe
it
will
work
happy
to
add
or
remove
any
suggested
times
here
before
we
send
the
doodle
out.
J
A
H
Sure,
I
guess
the
the
one
caller
I
was
going
to
ask
is
for
the
release
leads.
Specifically,
you
know
you,
you
have
your
schedules,
you
have
your
things
you
have
to
take
care
of.
You
know,
so
that
was
one
of
the
questions
I
did
was
kind
of
you
know
was
thinking
about
when
he's
looking
at
these
times.
Was
you
know?
How
does
this
work
for
the
team
as
well?
H
You
know,
and
you
know
that
was
one
thing
when
I
was
the
past
emergency
advisor
and
trying
to
recruit
into
zones
that,
like
like
new
zealand's
areas
that
gets
challenging,
but
was
this
part
of
some
of
the
decision
making
in
regards
to
times
proposed?
You
know,
is
that
something
that
we
have
to
kind
of
be
mindful
of
because
that's
the
other
thing
is
just
there's
only
so
many
people
who
can
run
the
meeting.
You
know
yeah.
A
K
A
Okay,
so
I'll
send
this
this
out
later
and
I
can
add
times
to
it
as
it
goes
on
if
we
need
to
to
make
any
changes
and
then
corresponding
to
that
one
I
picked
sometimes
in
the
u.s
same
same
deal.
Kind
of
aligned
with
these
are
there
mountain
times,
because
I
forgot
to
change
it
to
pacific
time
when
I
made
it
so
shift
them
an
hour.
I
guess
so.
8,
pacific
9,
pacific,
10
pacific.
Can
I
edit
this
now
and
just
do
that?
Let's.
E
A
Okay,
8
pacific
9,
pacific
10,
pacific
11,
pacific
12,
pacific.
These
mostly
work
for
me,
so
I
just
tried
to
pick
a
block
in
the
day
that
was
mostly
free
for
me
adolfo.
I
don't
know
how
these
work
for
you
or
for
steven
kind
of
aligned
with
what
we're
doing
now,
but
I
think
there's
also
some
overlap
here
with
other
open
source
meetings
like
in
the
open,
ssf
similar
things.
So
maybe
we
need
to
deconflict
that
a
little
bit.
C
A
A
A
A
L
Yeah,
so
that
one
from
that
one
is
from
me,
I
just
wanted
to
understand
like
if
there
is
a
process
to
show
interest.
I
have
been
reading
the
documents
that
are
already
there
and
the
sig
release
repository
and
live
whatever
are
the
requirements,
and
there
is
specifically
something
I
read
there
that
show
your
interest,
so
I
am
just
trying
to
understand
like
what
is
the
way
right
way.
Is
there
something
some
areas
where
I
need
to
contribute?
C
Until
now,
the
process
have
been
well
somewhat
discretional,
in
the
sense
that
some
of
the
leads
would
hear
from
people
who
had
interest
like
you're
expressing
now
and
try
to
offer
those
people
an
opportunity
to
become
part
of
the
release
managers
management,
managing
team.
But
the
problem
is
that
the
process
hasn't
been
like
really
established,
and
it's
not
written
like
anywhere
and
the
idea
we-
and
so
this
has
led
to
some
problems
for,
for
example,
right
now.
C
They
are
a
lot
of
names
in
there
are
not
active,
and
so
this
being
a
mostly
trust
problem,
we
had
expected
some
of
those
people
to
off-board
themselves
if
they
weren't
able
to
continue
in
their
release
managing
duties.
So
right
now
we
are
going
through
some
discussions
on
how
to
make
the
process
better
and
more
open
to
actually
define
the.
J
C
C
Yeah-
and
I
I've
also
done
two
and
everyone
I
think
that
has
been
also
like.
So
it's
the
same
people
all
over
and
and
it
doesn't
match
with
the
expectation
that
you
see
a
list
of
folks
in
the
in
the
list
and
you
would
you
would
guess
that
there's
lots
of
help,
but
in
reality
there's
not.
So
we
need
to
make
sure
that
people
can
come
on
and
off
and
off
that
list,
but
with
the
appropriate
checks
and
and
trust
that
that
need
to
be.
C
H
So
I
think
that's
that's
good.
I
know
we've
talked
about
this
in
the
past
and
I'm
glad
we're
kind
of
raising
this
and
finding
out
the
one
thing
I
always
think
about
too,
as
well
is
just
kind
of
like
you
know.
How
do
we
do
this
in
a
way
that
is
not
a
cognitive
burden
because,
like
there's,
you
know
like
we
have
veronica
here
she
stepped
in,
and
there
was
some
challenges
with
getting
somebody
to
be
a
release
manager.
H
You
all
have
roles
that
you're
doing
you
know
outside
of
sig
release,
but
you
know
and
we're
trying
to
onboard
people.
Will
this
as
you
kind
of
go
in
and
kind
of
codify
this
is
there
going
to
be
thought
to
how
to
do
this
in
a
way
that
I
mean?
Ideally,
you
know
you
can
do
this
training
that
could
be
repeated
or
like
some
framework.
C
It's
it's
most
likely.
It's
gonna
be
in
improving
the
the
branch
manager
shadowing
program
and
especially
so,
for
example,
I
was
discussing
I
I
I
met
stephen
at
some
point
and
we
were
discussing
so
at
one
point
at
what
point
do
people
so
do
we
want
to
allow,
for
example,
folks
from
from
not
just
from
the
release
team
into
the
branch
managing
program
or
not,
but
if
we
allow
all
sorts
of
contributors
should
they
get
that
training
before
that
or
not?
C
D
Aside
from
the
formal
processes,
what
I
have
noted
at
least
for
the
past
six
months,
let's
say-
and
this
is
my
experience-
is
that
for
being
a
branch
manager
specifically
for
specific
kubernetes
releases,
but
also
for
being
a
general
release,
manager
or
release
manager,
associate
is
like.
Sometimes
you
have
to
like
people
from
acro
all
across
the
release.
D
That
requires
to
do
something
else
or
that
I
don't
know
that
that
has
been
my
experience
in
many
different
tasks
and
you
have
to
at
least
be
able
to
communicate
that
you're
going
to
follow
up
at
a
certain
time
or
that
you're
not
going
to
be
able
to
follow
up
at
a
certain
time
and
like
arrange
with
someone
else
to
follow.
You
know
it's.
So
it's
a
lot
of
things
like
that.
D
That
is,
in
my
opinion,
not
that
much
in
the
technical
part,
because
you
are
supposed
to
already
have
proven
that
at
some
point,
but
in
the
day-to-day
task.
The
difficulty
that
I
have
found
is
that
I
mean
the
difficulty
of
the
role,
not
not
for
me
personally
or
for
anyone
specifically,
but
that
sometimes
like
a
task
has
to
be
specifically
handed
off
or
or
or
taken
by
yourself,
but
then
you
have
to
have
that
availability
in
in
weird
times.
You
know.
D
So
it's
not
like
there
are
no
tasks
that
can
be
sometimes
completed
like
in
two
hours,
or
there
are
many
variables,
because
some
some
things
are
still
in
development,
unfortunately
or
unfortunately,
so
it's
I
don't
want
to
to
judge
it.
I'm
just
saying
that
it
is
what
it
is
right
now
and
that
can
be
a
complication
of
the
role
in
any
of
the
degrees
yeah
and
from
as
a
ca
to
not
to
normal
release,
manager
or
branch
manager.
C
No,
it's
yeah,
it's
a
it's!
It's
one
of
the
one
of
the
things
that
we
need
in
order
to
know
not
to
expect
people
to
to
over
work
is
that
we
need
more
more
more
helping
hands
because
we
need
to
better
cover
the
world
and
have
basically
always
an
option
of
people
to
hand
things
over,
except
instead
of
always
the
same
person
and
putting
the
burden
on
that
particular
individual.
A
F
I
I
think,
to
have
a
very
small
thing:
fedorfo,
as
I've
mentioned
in
the
past,
I'm
trying
to
change
how
the
release
team
is
selected
as
well.
I
have
a
kept
in
progress
for
that
when
I
have
any
spare
time
in
my
life
at
all
to
write
it
and
I
am
still
working
on
it,
which
of
course
follows
many
of
the
same
themes.
F
It's
like
how
do
you
select
a
team
that
you
can
trust
so
those
two
processes
don't
necessarily
need
to
be
the
same
or
aligned,
but
they
should
probably
be
aware
of
each
other.
So
when
I
have
something
I'll
share
it
with
you
and
I'd
love
to
read
your
document
when
you
have
it
as
well,
just
definitely.
A
M
M
C
Yeah,
I
can
take
a
look
I
haven't.
I
haven't
been
able
to
look
at
many
prs
this
week,
but
I
will
take
a
look
one
thing
to
note
about
file
signing
and
why
I
have
purposely
left
that
on
up
to
the
last
minute
of
the
signing
effort,
this
there's
there's
still
a
disconnect
between
how
contouring
images
are
signed,
keylessly
and
the
verification
that
can
happen
to
the
on
them
and
the
the
the
way
files
are
assigned.
C
So
there
is,
there
is
a
currently
an
effort
going
on
to
to
of
a
project
called
as
get
within
sixer.
I
don't
know
if
you
familiar
with
it
and
so
esg
did
it's
basically
the
equivalent
of
say
curl
when
you
curl
that,
from
from
a
url
sgt
will
do
the
same
for
you,
pull
the
file
down
and
ensure
that
it
has
been
signed
but
not
only
signed
but
signed
by
the
person.
That's
supposed
to
sign
that
url.
C
So
there's
some
overarching
work
to
make
that
happen,
which
is
I
I
haven't
checked
in
with
them
lately.
But
the
idea
is
to
basically
top
the
entire
internet
so
delegate
to
trust
and
find
out
who's
entitled
to
sign
which
url
and
they
were
doing
quite
some
progress
recently.
So
I,
if
they
managed
to
get
it
working
just
one
ish.
C
M
Yeah
currently,
the
implementation
that
I
have
is
based
on
the
on
a
known,
public
and
private
key,
and
but
I
don't
know
if
that
is
the
way
that
it
currently
works,
or
that
we
already
with
the
file
with
the
container
signing.
Are
we
already
doing
it?
Keyless,
okay,
yeah
yeah?
Then
I
understand
the
disconnect.
Is
there
a
known
key
currently
that
that
could
be
used
for
file
signing
or.
C
No,
that's
that's
one
of
the
problems
with
the
rpms
and
devs
that
game
management
is
well
a
touchy
subject,
so
we
need
to.
We
need
to
get
that
organized
before
we
before
we
do
it.
But
if
we
can
do
something
like
hillary
signing
for
the
files,
it
would
be
a
great
thing
to
have,
but
I'll
take
a
look
at
the
vr
and
we
can
discuss
the
conversation
later.
M
A
J
Hi,
I'm
sorry.
I
just
want
to
ask
if
I
can
use
the
slot
of
the
next
release
engineering
meeting
next
week
to
talk
about
this,
because
I
think
it's
different
requests.
We
have
a
separate
and
dedicated
conversation
about.
Are
we
the
simulator
mechanisms
for
system
packages?
So
before
we
shift
and
merge
meetings?
A
C
J
J
J
N
J
We
get
our
own
that,
but
I
think
it's
really
really
early
to
work
on
this
because
we
need
to
know
we
need
to
have
a
full
agreement
about
how
we
modify
the
image
promotion
process.
Okay,
so
there's
gonna
be
something
we
need
to
change
during
the
promotion
process.
That
was
not
done.
That
is
not
done
with
gcr.
So
before
we
even
talk
about
setup
container
artifact
registry
repository,
we
need
to
have
a
conversation
with
release
engineering
about
how
we,
what's
the
real
impact
on
the
image
promotion
process.
J
Yeah
and
both
are
oci
compliant.
The
problem
is
how
the
problem
is,
how
both
servers
handle
the
image
blob,
because
simply
because
basically
gcr
do
replication
between
continental
repository
asphalt
registry
is
not
handling
that,
so
we
need
to
be
able
to
for
each
image
promotion.
Do
the
replication
between
multiple,
multiple
artifact
registries?
J
Okay,
okay,
okay,
sounds
good,
it's
that's
one
problem
we
need
to
talk
about
and
they
also
order
from
related
permission
and
stuff
like
that.
So
I
feel
like
I
don't
want
to
push
on
rush
about
this,
so
I
kind
of
want
to
have
a
proper
conversation
about
this.
With
use
different,
I
mean
various
engineering
yeah.
C
Awesome
yeah
take
a
look
at
well
the
the
promoter
already
those
replication
of
blobs.
I
did
that
for
the
for
the
signature.
So
it's
simply
a
matter
of
maybe
moving
that
code
back
in
the
process,
but
yeah
we
can
take
it
up
and
I
I
think
I
saw
a
an
issue
or
or
a
comment
from
ben
somewhere
I'll
take
a
deep
dive.
Yeah.
A
All
right,
I
think
that
brings
us
to
the
end
of
the
meeting.
If
anybody
has
any
other
topics
feel
free
to
add
them
to
the
the
next
agenda
or
come
to
release
on
slack
and
you
can
take
it
from
there.
This
was
an
awesome
meeting
thanks
to
everybody
for
attending.
I
hope
you
have
a
great
rest
of
your
tuesday
and
see
you
on
the
internet.