►
From YouTube: Kubernetes SIG Release Bi-Weekly meeting for 20220111
Description
Kubernetes SIG Release Bi-Weekly meeting for 20220111
A
Hello:
everyone
welcome
to
the
january
11th
sig
release
bi-weekly
meeting.
This
is
the
first
one
of
the
new
year,
so
welcome
back.
I
hope
everybody
had
a
good
good
end
of
2021
and
a
good
beginning
to
2022.
So
far,
this
meeting
is
covered
by
the
kubernetes
code
of
conduct,
so
that
essentially
boils
down
to
please
be
excellent
to
one
another.
This
meeting
will
also
be
recorded
and
will
be
available
on
youtube.
A
A
We
we
have
a
couple
of
time
box
topics
that
we
always
have
get
sub
project
updates
and
then
turn
it
over
to
open
discussion.
But
the
first
thing
we
like
to
do
is
always
welcome
anybody.
That's
a
new
attendee
you're
you're
free
to
not
introduce
yourself,
but
this
is
a
chance
for
you
to
introduce
yourselves
to
the
rest
of
sig
release.
Let
us
know
what
you're
here
for
what
you're
interested
in
doing
and
and
and
just
to
say
hello.
So
we'll
give
folks
a
chance
to
do
that.
If
they'd
like
to.
B
C
D
G
Everyone
yeah,
okay,
go
for
it,
yeah,
I'm
ganesha
and
I'm
basically
from
india.
I'm
a
student
right
now
and
I've
been
a
part
of
the
sikh
it's
not
a
thick,
but
it's
a
part
of
the
sick
architecture.
It's
called
the
sick,
kept
writing
club
and
also
in
a
part
of
the
quantity
channel
and
recently,
when
I'm
being
involved
in
the
sig
network,
k-pinch
group
that
is
being
formed
right
now.
E
A
A
I
Yeah,
I
can
so
last
the
last
teachers,
the
the
last
tasks
we
did
last
year,
we're
finally
measuring
the
caps
for
signing
the
the
artifacts
in
the
kubernetes
releases
and
also
for
trying
to
achieve
salsa
three
compliance.
So
the
artifact
signing
is
like
the
framework
we're
going
to
be
following
for
signing
from
container
images
to
documentation
to
all
sorts
of
binaries
artifacts
whatever,
and
I
think
we
will
be
starting
the
efforts.
I
I
think
sasha
opened
a
call
for
participation
on
on
the
release
management
channel
for
everyone
who
wants
to
get
involved
into
the
into
the
signing
effort
and
we
will
be
I'll
taking
operating
those
projects
during
the
next
release
engineering
meeting
and
I
think,
if
I'm
not
mistaken,
that's
that's
kind
of
the
only
update
this.
For
now.
A
That's
that's
awesome!
Thank
you
for
that
update
for
anyone,
that's
new,
if
you're
interested
in
any
of
those
topics
on
the
off
week
from
this
week.
So
next
week
we
have
a
sub
project
meeting
for
the
release.
Engineering,
part
of
sig
release
and
a
lot
of
those
topics
are
discussed
in
more
depth
and
more
detail.
There
same
same
time,
just
alternating
weeks
so
feel
free
to
drop
into
those
beatings
as
well.
G
I
Yeah,
so
we
we
take
care
of
all
the
software
that
powers
and
releases
the
kubernetes
artifacts
that
people
downstream
consume.
So
whenever
you
pull
one
of
the
images
use
one
of
your
cube,
ctrl
binary,
even
the
documentation
that
goes
out
as
part
of
a
release
like
the
release,
notes
that
those
things
are
produced
by
some
tools
that
we
manage
and
write
and
keep
maintaining.
I
So
some
of
it
has
already
been
running
for
several
years,
but
we
keep
improving
it
right
now.
The
focus
is
on
making
building
more
security
into
the
release
process,
so
the
the
the
main
goals
for
this
cycle
will
be
digitally
signing
the
artifacts
and
and
not
not
only
the
artifacts,
but
also
the
information
that
travels
through
the
release
process.
I
I
So
you
can
think
about
an
artifact
of
the
cube
cdl
binary
that
you
run,
or
even
the
container
images
of
the
several
components
of
a
kubernetes
system
and
documentation
and
the
several
technical
files
that
we
produce
out,
like
the
build
of
materials
at
the
stations
of
about
the
province
of
their
of
those
artifacts.
That
sort
of
thing.
A
Yeah,
anytime,
those
are
great
questions.
Thank
you
for
asking.
I
think
it
gives
excellent
context
for
everybody
else,
and
I
don't
know
if
we
do
that
enough.
So
thanks
for
asking
that
yeah
all
right,
so
the
other
sub
project
that
makes
up
sig
release
sub
projects,
are,
you
know,
kind
of
encapsulations
of
certain
responsibilities
or
delegations
of
the
overall
charter,
so
release
engineering
handles
kind
of
those
mechanics
and
the
the
tools
and
the
next
one
is
actually
the
release
team.
J
Yeah
hello,
so
my
name
is
james.
I
am
the
release
lead
to
124..
This
is
the
first
week
of
release.
We
kicked
off
on
monday.
We
so
far
have,
I
believe,
a
full
release.
Team
of
37
members
there's
been
quite
a
lot
of
shadows
because
four
pair
four
pair
area,
which
is
pretty
pretty
good,
we're
progressing
with
onboarding,
of
course,
all
membership
for
those
needed
doing
various
onboarding
tasks.
J
J
Utc,
tomorrow,
if
you're
interested
and
we'll
be
posting
in
in
sig
release
kind
of
ahead
of
the
meeting
going
on
anyway,
yeah
the
we
opened
for
enhancements
on
monday,
I
haven't
looked
at,
what's
been
opted
in
so
far,
but
I
think
there's
at
least
a
couple
on
there
there'll
be
a
bigger
update
about
that
tomorrow.
I'm
sure
yeah,
I
think
that's
the
main
thing
in
the
first
big
deadline
is
enhancements.
J
Soft
freeze
deadline
the
week
before
from
the
thursday
27th
I
want
to
say
of
january,
so
we
have
a
few
weeks
of
of
kept
collection
and
then
we'll
we'll
be
going
into
kind
of
just
the
implementation
phase
ahead
of
code
reads
so
yeah
all
looking
good.
So
far,
I
think
anyone
got
any
questions
about
the
release
team.
J
A
It
is
it's
challenging
too
getting
through
all
the
applications
for
anyone
that
applied
and
wasn't
selected
it
is.
It
is
tough
to
to
select.
You
know
the
small
like
james
mentioned.
It's
that's
way
less,
that
that
includes
the
leads
too,
but
like
it's
way
less
than
the
the
total
number
of
applicants
that
we
receive
and
it's
it's
always
a
challenge
to
yeah.
J
We
we
so
in
previous
releases.
We
had
an
informal
suggestion
that
most
role
leads
should
take
on
about
two
new
people
or
so
and
that's
been
replicated
here.
It's
now
kind
of
a
formal
recommendation,
so
in
reality
there's
only
about
six
areas
and
two
two
pairs
only
about
11
or
12
spaces
actually
available.
If
you
see
what
I
mean
to
new
applicants,
so
not
counting
kind
of
kind
of
people
who
have
returned
so
it's
yeah,
it's
quite
challenging.
A
All
right
thanks
james
and
good
luck
to
you
and
the
release
team.
This
cycle,
it's
going
to
be
exciting,
a
lot
of
a
lot
of
challenges
for
folks
this
time
around.
Okay.
Next,
let's
jump
to
the
open
discussion
items
and
then
we
can
come
back
to
walk
through
the
board.
Since
we
have
a
few
things
on
the
the
open
discussion.
First
up,
our
node.
Do
you
want
to
discuss
this
one.
L
L
L
L
A
A
A
M
It
hi
so
yeah
two
items
from
me
so,
as
most
of
you
know,
last
release
cycle,
we
started
working
on
the
new
ci
signal
report
platform
and
also
tool,
so
the
ci
signal
report
cli,
has
already
merged
and
basically
the
platform
is
now
basically
waiting
for
merging
and
we
already
have
an
issue
open.
I
think,
from
november
and
yeah
the
question
is
like
who's,
the
owner
for
the
project
or
for
the
platform
and
yeah.
I
think
it's.
The
platform
itself
is
quite
finished.
M
A
Yeah
all
right,
so
I
think
the
the
first
question
you
you're
looking
for
an
answer
for
is
really
like
who's,
who
will
be
the
owner
for
this,
and
I
think
there
was
a
question
from
arno,
because
ci
signal
is
subject
to
people
rotating
through.
How
does
that?
How
does
that
end
up
being
like
owned
by
someone?
M
Yeah
yeah
yeah,
so
for
this
ci
signal
cli,
for
example,
we
have
the
only
reviewer
ownership
for
the
current
ci
signal
team,
but
basically
they
are
not
approvers.
I'm
not
sure
if
this
is
like
a
bit
different
for
the
platform,
because
it's
like
infrastructure,
so
I
guess
that
this
would
not
be
suited
for
rotation.
So
basically,
what
not
commented
so.
I
L
Can
I
I
put
a
link
describing
how
anyone
can
basically
run
a
workload
inside
the
community
infrastructure,
so
you
basically
have
a
dedicated
namespace
and
you
run
your
everything
you
want
to
run
on
this
separate
next
place.
My
question
was
more
about.
It
was
about
ownership,
but
especially,
I
don't
want
to
say
on
call,
but.
L
I
I
I
M
M
Where
are
they
from
time
zones
and
affiliation
and
stuff
like
that,
because
there
was
also
a
discussion
a
couple
of
months
ago,
I
think
james
james
started
that
regarding
getting
a
bit
more
transparency
who
is
who
applied
and
building
a
better
team,
so
I'm
creating
those
diagrams
giving
a
bit
more
transparency,
basically
how
the
current
situation
looks
like
could
be
like
basically
a
foundation
or
something
to
get
started
on.
I
don't
know.
M
Would
this
be
something
which
we
could,
I
don't
know
include
in
into
our
into
the
release
cycle,
so
at
the
start
of
the
release
cycle
after
we
receive
the
applicants,
we
create
basically
the
diagrams
and
show
okay,
those
are
those
applicants.
We
received
this
release
cycle,
it
looks
like
we
are
more
diverse
this
or
something
like
that.
I
don't
know
and
yeah.
So
this
is
like
the
first
question.
M
So,
for
example,
this
would
be
also
possible
that
this
is
b
that
we
use
this
tool
for
also
building
a
bit
the
team
that
that,
for
example,
we
select
a
couple
of
applicants
and
then
we
get
some
applicants
proposed
because
we
want
to
have
like
a
diverse
team.
So
we
don't
want
to
accept
for
guys
from.
I
don't
know
whatever
company
we
want
to
spread
it
out.
So
maybe
this
could
also
help
in
the
selection
process,
but
yeah.
J
One
thing
I've
been
wondering
about
recently,
which
I'm
a
little
bit
concerned
about
is
when
we
do
the
survey,
I'm
not
sure
if
we
actually
ask
people
for
permission
to
use
their
data
in
this
way.
I
don't
know
if
that,
how
much
that
is
required,
I
don't
know
if
there's
a
gdpr
implication
there
like.
I
am
not
an
expert
on
these
things.
J
This
kind
of
you
know
anonymized
data
about
the
applicants,
the
kind
of
applicants
we
get
and
use
abstract
decisions,
and
that
would
be
really
interesting
as
a
topic
of
discussion
and
transparency,
but
I
don't
know
if
we've
asked
permission
to
do
that.
I'm
not
sure
what
the
process
would
be.
I
mean,
like
you
know,
for
future
applicants
we
could.
We
could
work
to
draft
some
language
to
put
on
the
application
process
or
some
check
box
to
say
that
people
are
happy
being
their
data
being
used
in
this
way.
A
Thoughts
yeah,
I
don't
know
if
this
is
a
question
that
we
can
answer.
This
is
probably
something
that
we
would
need
to
get
clarification
from
contributor
experience
or
steering
about.
I
think
it's
like
a
yeah.
We
might
need
to
go
to
the
cncf.
If
it's
more
of
a
meta
question
that
you
know
probably
isn't
going
to
be
answered
by
by
our
group.
A
I
think
that
it's
interesting
to
see
that
kind
of
data
like
any
kind
of
visualization,
I
think,
helps
kind
of
make,
especially
when
there
are
hundreds
of
of
these
rows
and
like
for
anybody
that
hasn't
gone
through
this
process
like
when
we
select
the
applicants.
You
know
you
fill
out
that
form.
It
goes
to
a
spreadsheet.
Basically,
there's
a
google
sheet
that
has
a
row
for
each
person
that
has
submitted
an
entry
with
a
column
for
every
question.
A
I
have
the
same
questions
as
james
like
what?
What
of
this
can
we
share?
I'm
like?
Obviously
we
have
the
data
and
like
we
can
do
this
internally
and
it's
not
shared.
We
can
just
use
this
for
ourselves.
I
do
think
it
would
be
interesting
to
kind
of
report
or
to
make
available
for
folks.
I
guess
just
the
general
shape
of
the
app
like
we're
getting
more
from
release
release.
A
We
get
more
applicants
from
europe
and
india
than
we
do
from
the
us,
or
we
get
more
applicants
from
large
companies
versus
small
companies
or
we're
getting
a
very
small
number
of
applicants
who
identify
as
something
other
than
a
man.
It
would
be
interesting
to
see
that
kind
of
thing
I
think
to
to
just
to
know
for
us
might
be
interesting
for
folks
outside
of
outside
of
sick
release,
to
know
just
like
for
what
we're
doing,
but
I
don't
know
if
this
is
something
that
we
can
commit
to
to
going.
A
K
I
was
gonna
say
so
I
I
can
so
definitely
I
I
appreciate
everybody's
perspective
on
the
privacy,
like
the
usefulness
of
it.
So
so
one
thing
I
I
didn't
get
a
chance
learned
to
reply
back,
because
I
I
actually
am
more
like
a
visual
learner
myself,
and
so
I
didn't
discovered
within
our
survey
that
we
could
go
in
and
actually
grab
some
similar
kind
of
like
reportings,
which
I
didn't
know
existed
in
there.
So
it
was
kind
of
good
to
see
what
you
kind
of
did
there.
K
I
would
definitely
say
the
the
formatting
of
the
applicants
was,
I
think,
was
helpful.
I
think
nate
commented,
and
you
know
about
that.
That
kind
of
would
have
been
helpful
for
him
in
in
selecting,
and
I
think
that
was
kind
of
good.
One
thing,
though,
because-
and
I
was
going
to
put
this
into
the
retrospective
retrospective
was
more
around
like
you're
kind
of
hitting
around
some
of
the
issues
that
are
very
challenging,
and
that
is
diversity.
K
I
probably
went
through
that
list
about
five
times
rereading
everybody
trying
to
glean
anything
I
could
about
that
person
so
that
I
could
meet
the
selection
criteria
and
make
sure
the
composition
of
teams
were
very
representative,
and
so
I
don't
think
we
have
a
really
good
way
to
get
there,
but
I
think
definitely
addressing
you
know.
Can
we
use
this
to
date
in
that
certain
way,
and
I
feel
like
you
know,
we
are
also
not
collecting
the
right
amount
of
information.
If
we're
saying
you
know,
nationality
ethnicities
are
important.
K
I
don't
think
we're
asking
things
in
the
right
way,
and
I
mean
we
think
we
need
to
fix
those
inputs
going
into
the
next
release
cycle.
I
think
there
could
be
some
revisions
to
help
improve
and
now
that
I've
had
that
experience,
I
really
kind
of
feel
it.
The
other
thing
I
was
going
to
mention
is
from
our
last
cycle.
We
had
concerns
about.
K
You
know,
individuals
that
have
repeatedly
applied
that
just
kind
of
get
lost
and
you
know
going
through
the
last
re-release
cycles.
I
was
looking
at
shadows
and
I
saw
a
lot
of
the
same
names
and
I
feel
for
it
because
I
see
these
individuals
really
trying
and
I
definitely
feel
like
previous
cycle.
We
had
this
discussion
and
I
think
we
still
have
an
open
issue
where
james
and
xander
we
all
talked
about
like.
Could
we
have
a
way
to
better
manage
this,
and
so
I
kind
of
feel
like.
K
K
We
know
we're
grabbing
a
great
selection
and
I
was
really
trying
to
find
certain
areas
and
it
was
really
hard
with
a
spreadsheet
and
then
when
you
gave
me
with
that,
it
was
kind
of
helpful,
because
then
I
was
able
to
go
back
and
forth
and
really
try
to
find
these
individuals
that
we
don't
see
a
lot
of
representation
from.
So
I
would
say
this
may
take
a
little
effort
if
you're
persistent,
you
know
it's
not
an
overnight
decision
that
we
could
just
make,
because
I
think
there's
a
lot
that
we
have
to
consider.
K
M
Okay
sounds
good,
so
yeah,
so
what
I
didn't
mention
in
the
first
first
place
is
that
basically
the
tool
is
separate
into
two
things,
so
one
part
is
to
create
the
diagrams
to
get
an
overview
we
applied
and
the
other
part
is
basically
get
a
like
print
out
for
each
team
separate
into
newcomers
and
returners,
so
that
you
don't
have
to
walk
through
the
entire
spreadsheet.
You
can
basically
just
read
the
markdown
file
and
it's
highlighted,
and
you
can
see.
M
Basically
the
applicants
like
you
would
probably
normally
you
would
read
applicants
so,
like
a
text
text
form.
So
this.
This
is
basically
the
two
parts
yeah
and
I
think
the
first
part
I
can.
I
can
also
open
up
on
contribute
to
x,
select
channel
another
thread
to
discuss
this
and
the
other
part
would
not
be
shared
anyways.
So
I
don't
know
if
we
need
to
to
discuss
this,
but
this
would
be
the
first
step.
Maybe.
J
Thank
you
grouped
data
about
applicants,
or
do
we
need
permission
to
do
that
and
if
we
do
need
permission
then
I
think
we
should
add
a
checkbox
for
permission
to
be
included
in
in
that
analysis
or
or
something
like
that
in
the
future
125
and
forward,
because
I
think
that
would
be
a
good
thing.
It's
just
a
question
of
whether
it's
you
know
legally
and
morally
correct
to
do
so
with
the
current
data,
and
we
can't
answer
that
and
I
think
that's
a
steering
question
is
my
feeling.
A
I
think
that
it's
cool
you
did
that,
though,
I
think
having
that
extra
ability
to
go
over
the
data
is
super
useful
without
also
without
it
being
like
in
a
spreadsheet,
because
you
could
totally
do
this
with
like
pivot
tables
and
all
kinds
of
bananas.
Things
inside
of
the
google
sheet,
like
we
do
for
the
enhancement
stuff,
and
that
stuff
is
not
easy
to
maintain
so
good
for
not.
J
A
I
also
think
back
to
joseph's
point:
are
we
asking
the
right
questions
for
what
we're
looking
for,
because
I
think
we've
largely
just
we've
taken
the
same
survey
from
release
to
release
and
release.
I
think
we
added
a
question
about
company
affiliation,
but
other
than
that.
It's
been
largely
the
same
for
a
while,
and
it's
probably
time
to
evaluate
whether
it's
asking
the
right
questions.
We
know
if
we
have
the
right
data
or
not
to
begin
with.
B
B
Add
it
would
be
really
nice
to
have
an
examples
of
what
other
contributors
have
done
in
the
past
to
get
them
there
right,
because
I
applied
for
the
release
shadow
myself
and
it
was
pretty
much
everything
was
happening
right
on
the
spot
dynamic
when
it
performs
like.
Oh,
you
must
sign
the
sla
like
I.
B
I
have
to
go
and
do
the
signing,
but
I
had
to
read
about
all
the
different
types
of
teams,
which
is
a
good
thing,
because
it
gives
me
a
heads
up,
but
the
google
sheet
experience
is
really
tough
and
it
doesn't
give
anybody
the
chance
to
know
me
because,
like
why
do
you
want
to
join
like,
let's
say
the
enhancement
team
right?
I'm
like
okay?
I
literally
just
learned
about
that.