►
From YouTube: Kubernetes SIG Release Bi-Weekly Meeting for 20220906
Description
Kubernetes SIG Release Bi-Weekly Meeting for 20220906
A
Hello,
everyone:
this
is
the
sick
release
weekly
meeting
for
september
6
2022,
and
this
is
our
first
time
on
the
new
schedule
for
the
meeting,
I'm
happy
to
see
that
we
got
a
good
number
of
people
here.
As
a
reminder,
this
meeting
is
under
the
discover
under
the
kubernetes
code
of
conduct,
so
be
mindful
of
what
you
say
and
do
because
we
are
recording
this
meeting
to
the
public
internet
and
remember
to
be
awesome
to
each
other.
A
My
name
is
garcia.
I'm
going
to
be
your
host
today.
We
have
somewhat
backed
agenda
for
today.
So,
let's
start
with
the
giving
so
the
an
opportunity
to
any
new
members
to
say
hello,
and
if
you
want
to
see
state
how
what
your
interest
is
in,
seek
release
and
say
hi.
B
I
can
say
hi,
I'm
new
to
the
sig
release
meeting,
but
I
think
I've
worked
with
pretty
much
everybody
here.
I'm
mark
I'm
a
sig
windows
chair,
but
I've
also
been
working
on
the
enhancements
team
release
team
last
release
and
I've
been
helping
with
the
switch
to
project
boards.
For
that.
So
just
thought.
I'd
show
up
here
too.
A
Awesome
mark
we're
happy
super
happy
to
have
you
here.
First.
C
Okay,
I
can,
I
can
say
hi,
although
I
I'm
also
working
with
most
of
you
outside
of
this,
so
I'm
fresh
and
I'm
I'm
well,
I'm
currently
the
coms
lead
for
version
126,
so
obviously
being
here,
it's
it's
it's
just
another
way
of
catching
up
and
then
trying
to
to
help
it
to
learn.
A
Nice
to
have
you
friend
and
of
course
there's
you
cannot,
you
can
say
hi.
If
you
want
to
again,
we
don't
get
tired
of
friendly
faces.
A
B
B
We're
for
sure
doing
two
three
one,
two
three
one
dot,
two
four
and
1.25
1.22
is
still
conditional
on
the
basis
of
whether
we
have
critical
bug,
fixes
or
cvs
for
that
branch,
and
that's
all.
I
had.
A
C
I
will
take
care
of
the
cherry
picks
as
I
have
done
over
the
past
few
cycles.
So
if
you
want
to
help
me,
that's
great,
but
it'll
be
done
between
today
and
tomorrow
and
the
next
day.
A
Yeah,
thank
you.
So
I
I've
been
doing
some
some
cherry
pick
reviews
over
this
week
and
just
a
reminder
to
all
radius
managers.
This
is
part
of
the
work
we're
supposed
to
do
the
earlier.
We
can
do
the
the
cherry
picks
it's
better
for
gaining
better
signal
in
the
overall
project,
but
also
it's
helpful
for
for
the
authors
to
to
know
that
we
have
their
changes
in
mind,
and
so
I
can
one
thing
I
can
let
out
for
people
doing
the
cherry
picks
is.
A
We
are
probably
we
are
most
likely
going
to
cut
a
122
release.
So
if
you
see
any
patch
releases
that
need
to
be
backported
to
the
122
branch
and
or
are
missing
the
122
backboard,
please
make
it
make
a
note
on
those
cherry
picks
to
to
the
authors
all
right.
Thank
you,
mohammed,
for
letting
me
know
that
my
voice
was
a
little
bit
quiet
all
right.
I
guess
this
also
segues
nicely
to
the
release
team
updates.
If
anybody
wants
to
to
give
one.
D
I
I
can,
I
can
give
an
update,
so
we
are
in
the
first
week.
So
that's
great
the
release
cycle
starts.
D
This
is
this
change.
We
had
a
meeting
on
last
thursday,
so
we
we
discussed
everything
and
sent
out
notification
emails
to
the
community,
so
hopefully
this
change
will
be
will
be
smooth
and
everything
some
some
process
to
automate.
For
example,
the
project
board
is
the
work
in
progress,
but
the
changes
which
are
relevant
for
the
community
or
the
sick
leads.
This
should
not
be
affected,
so
hopefully
we
don't
have
to
adjust
anything
and
all
in
all,
it
looks
fine
ryder.
D
A
Thanks
leo
looks
okay,
I
mean
concerting,
but
it's
still
early
days
a
weekend.
D
Yeah
I'm
right
now
we
don't
have
the
the
shadows
selected.
That's
that's
that's
a
problem,
but
I
guess
we
can.
I
don't
know
number
one.
Do
we
want
to
comment
on
this?
I
think
we
can
send
out
the
the
the
email
informing
the
community
and
everything
so
and
we
also
have
two
previous
leads
in
the
the
shadow
group.
So
maybe
we
can
handle
things
right
now.
It's
not
100
clear
when
he
returns
hopefully
soon
but
yeah.
B
Yeah,
I
think
that's
the
right
way
for
the
shadows,
since
we
have
abstracted
out
the
google
sheets
right
now.
We
don't
need
the
sheets
and
we
will
be
doing
mostly
everything
through
project
boards.
It
should
be
like
less
work
at
the
start
and
since
everything
is
on
github,
it
should
be
much
more
streamlined
and
anyways
like
we
have
like
people
in
the
team
who
have
experience
with
enhancements
to
take
care
of.
So
I
guess
we're
yellowish
green,
but
it
would
be
fine.
A
All
right
any
questions
for
leo
or
another
room.
A
Okay,
all
right,
so,
let's
move
to
our
open
discussion
topics.
The
first
one
is
from
liu
again
a
release:
team
shadow
analysis
report.
D
Yeah,
just
a
short
one,
so
this
release,
we
finally
use
the
shadow
application
tool
so
there's
a
tool
which
generates
diagrams,
which
gives
some
general
information
about
the
shadows
without
revealing
any
any
information
and
also
generating
markdown
files,
which
we
send
out
for
just
ease
the
selection
process
and
the
diagrams
for
1
or
26
are
ready
and
there's
an
issue
open
to
discuss
if
we
can
publish
everything
so
in
the
reporter
community,
if
you
have
like
any
input,
any
concerns
or
any
anything
feel
free
to
add
a
comment,
and
hopefully
we
can
push
the
first
report
out
to
the
community
soon.
A
Okay,
so
well,
my
question
was
more
in
in
on
the
release
infrastructure
for
that
repo.
I,
when
you
opened
the
pr
last
week,
I
completely
missed
it,
because
it's
not
it
wasn't
one
of
the
the
repositories
that
I
usually
I'm
looking
at
I'm
I
now
added
it
to
my
daily
list
of
things
that
I
do,
but
do
you
need
anything
in
terms
of
automation
or
release
tooling
or
anything
on
that
ripple.
D
Yes,
so
right
now,
there's
like
a
one
one.
I
need
to
define
or
document
which
steps
are
needed
before
each
release,
but
since
we
update
the
in
the
application
form
every
time
or
mostly
every
time,
we
also
need
to
make
some
small
adjustments.
So
there's
like
a
one
file
configuration,
so
the
automation
part
of
things
might
be
a
little
bit
tricky,
but
currently
there's
not
much
needed
else
than
defining
how
the
report
should
look
like
if
there
are
any
diagrams
missing.
D
A
All
right
so
next
topic
from
me
just
a
note
that
I
got
the
salsa
provenance
tester,
that
I've
been
working
on
for
like
one
or
two
months
now
to
a
working
state,
and
I
started
running
some
tests
on
the
building
kubernetes
releases
with
it.
I
haven't
yet
tested
it
end-to-end,
because
I
need
some
infrastructure
changes
that
I
have
to
to
do
on
the
on
the
release
project.
But
it's
working
and
I
started
the
donation
process,
and
this
is
one
just
wanted
to.
A
Let
everyone
know
that
the
the
donation
process
is
going
and
the
other
one
is
that
if
anybody
wants
to
be
an
early
tester
of
generating
salsa
provenance
for
their
projects,
we
should
be
able
to
do
it.
The
only
requirements
is
one
that
your
project
builds
on
either
google
cloud
build
or
github
actions,
and
if
that's
the
case,
then
we
most
certainly
can
make
it
work.
A
All
right
and
if
there's
any
questions
whatever
just
let
me
know
it
gained,
I
just
want
to
tell
you
gain
a
lot
of
features
which
weren't
planned
on
the
early
stages.
It
can
now
natively
send
pops
up
message,
messages
to
trigger
itself
on
early
stages.
It
now
can
collect
artifacts
from
the
native,
the
artifacts,
from
the
build
systems
from
buckets
from
it
can
read
s-bombs
and
at
the
stations
to
collect
the
list
of
artifacts.
So
it's
packed
with
a
lot
of
things.
A
I'm
I'm
hoping
to
do
a
demo
real
soon,
all
right,
but
enough
of
that.
So
next
one
jeremy
meeting
at
the
nation.
E
Yeah,
so
thanks
everybody
for
attending
today,
our
new
meeting
time
muhammad
pointed
out
in
slack
that
this
overlaps
with
the
sig
testing
meeting,
and
I
was
going
to
propose
that
we
swap
the
alternations
so
normally
next
week
would
have
been
the
old
meeting
time.
So
what
I'm
proposing
basically
is
just
like
we'll
do
the
next
meeting
at
this
time
and
then
we'll
be
on
the
right
cadence
after
that,
and
it
should
alternate
with
the
sick
testing
meeting.
C
I
think
that
probably
solves
the
conflict
with
the
dots
as
well,
because
docs
is
monthly.
I
believe
no,
it's
bi-weekly
as
well,
so.
E
A
E
So
I'll
send
another
message
to
the
I'm
sorry
to
the
mailing
lists
with
a
summary
of
this
and
then
I'll
update
the
the
calendar
invites
and
get
bombarded
by
a
bunch
of
messages
from
google.
Again,
it's
really
cool
to
like
just
as
an
aside
to
watch
the
history
of
companies.
E
There's
a
whole
lot
of
folks
subscribed
to
the
sig
release
mailing
list
from
heptio,
which
obviously
those
addresses
don't
exist
anymore
and
vmware,
used
to
use
a
weird,
gcp,
subdomain
and
there's
a
whole
lot
of
folks
from
vmware
that
are
subscribed
like
with
gcp
or
gcp.vmware.com,
which
also
doesn't
exist
anymore.
A
Okay
and
so,
and
the
last
our
last
topic
for
in
the
open
discussion
list
is
something
which
just
was
raised
a
few
like
an
hour
or
so
ago,
in
the
in
our
slack,
which
is
around
but
signing
doing
the
mac
code.
Signing
thing
for
the
coordinator
for
the
for
the
kubernetes
organization
binaries.
This
was
specifically
brought
by
the
kcp
folks.
A
So
the
idea
is
that
if
you
want
to
run
binaries
in
your
mac,
they
have
to
be
signed
by
the
authorized
ca
from
apple,
and
this
has
been
an
issue
that
has
been
raised
many
times
by
other
projects.
I
linked
an
issue
from
municu
there
when
I
have
the
kcp
one,
and
since
we
are
working
on
redoing
the
way
we
release
the
artifacts,
I
thought
it
might
be
a
good
time
to
start
discussing
this
and
re
and
ensuring
that
we
consider
this
in
the
road
ahead.
A
This
doesn't
have
to
be
a
like
a
b0
priority
just
now,
but
we
should
start
thinking
about
it
because
it
involves
not
only
doing
the
implementation,
but
we
need
to
get
some
funding
and
we
need
to
unless
we
do
the
my
proposal
to
do
a
chip
in
fundraiser
and
but
it
also
involves
planning
around
access
to
the
credentials.
A
That's
gonna
be
used
to
sign
yeah
mark.
B
A
Yeah,
I
think
it's
a
good
time
because
we're
redoing
the
the
the
signing
of
the
system
packages
we're
moving
we're
planning
on
moving
some
of
the
artifact
builds
to
to
make
them
also
maybe
run
through
promotion
in
in
via
the
file
promoter,
just
as
we
do
with
container
images,
so
it
would
be
a
good
time
I.
A
This
is
not
something,
for
example,
that
I
have
in
mind
constantly,
because
since
I've
never
used
them,
I
it's
not
an
issue
that
comes
to
my
mind
frequently,
so
I
think
it's.
If
you
have
folks
that
are
interested
in
the
project,
it
would
be
a
good
time
to
bring
them
over
to
the
meetings
and
if
you
have
experience
or
people
that
can
help,
I
would
be
mostly
appreciated
both
for
windows
and
mac.
Banners
too.
A
Awesome
that
would
be
super
grateful,
so
some
of
the,
for
example,
arno
linked
an
issue
on
that.
He
already
requested
funding
for
for
an
apple
developer,
account
for
for
us
to
to
have
access
to
the
sign
name
for
a
signing
account
so
yeah,
I
don't
know,
go
ahead.
F
I
just
want
to
say
that
jesus
was
brought
to
steering
in
may
of
this
year
about
basically
how
we
can
handle
binary
sign
nature
for
always
different
than
linux,
and
I
think
there
was
there
was
like
a
conversation
I
put.
I
can
put
the
link
of
the
recording
for
this
meeting.
They
were
like
conversation
about
how
cncf
handled
that,
or
maybe
a
developer
can
pay
for
that
and
we
get
reimbursement.
F
F
A
E
A
Oh,
thank
you
and
also
the
we
need
to
have
some
conversations
with
people
who
know
how
this
stuff
works
and
see
how
we
can
integrate
that
and
just
to
start
drafting
out
design
and
other,
maybe
other
resources
that
me
we
may
require,
like
maybe
apple
hardware,
things
like
that.
So
that's
I
I
say
I
say,
but
it's
a
good
time
to
to
start
organizing
around
a
plan
to
do
it.
A
All
right
so
any
thoughts
or
questions
around
signing
or
specific
binaries.
E
C
Windows
is
slightly
different,
that
one
you
need
to
go
to
a
ca
and
get
a
certificate
from
them
for
code
signing,
and
then
you
just
sign
the
binaries.
F
I
don't,
I
don't
think
we
for
next
month
is
just
about
getting
funding
for
the
microsoft
program
and
the
apple
program
business
like
a
foundation
nation
we
need
to,
we
need
basically
to
address
and
we
have
a
windows
opportunity
we
can.
We
can
do
that
so
mark.
If
you
have
any
talks
about
how
what's
the
pricing
for
this
program,
please
drop
it
in
secretary's,
slack
channel.
A
Yeah
and
as
navern
suggested,
if
they
have
you,
know,
opportunities
for
non-profit
like
the
cncf
to
participate
in
those
would
be
also
great.
A
Okay,
so
thanks
everybody
for
coming
and
we
are
still
going
on
with
the
binary
conversation
on
slack
if
you
are
on
turn.
So
thank
you
and
see
everybody
next
week.