►
From YouTube: 20210422 SIG Arch Enhancements
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
We're
not
recording
hi.
Everyone
today
is
april
22nd,
and
this
is
in
a
kubernetes
announcements
of
project
meeting.
This
is
the
meeting
rescheduled
from
april
15th
due
to
prior
conflicts,
so
we
will
be
discussing
whatever
is
there
on
the
agenda?
I
also
pasted
the
meeting
link.
Sorry,
the
meeting
notes
link
the
chat,
so
please
feel
free
to
have
a
look
at
it.
Also
before
we
get
started
with
the
meeting
two
housekeeping
items
number
one.
A
We
follow
the
kubernetes
code
of
conduct,
which
essentially
boils
down
to
please
be
nice
to
everyone,
and
this
meeting
is
being
recorded
and
will
be
publicly
posted
to
youtube.
So
please
be
aware
of
what
you
say
and
doing
this
meeting
awesome,
so
we
are
done
with
the
housekeeping
items.
I
see
that
ray
has
volunteered
with
the
note
taker.
Thank
you
ray
with
that.
B
Call,
I
think
it's
first
time
I
joined
this
meeting
today.
Sorry,
I'm
just
kind
of
re-situating
my
cameras
and
everything
I'm
at
a
different
location,
but
I
think
a
few
know
me
from
the
shadowing
with
the
enhancements
previously.
So
I
don't
think
anybody
else
who
doesn't
know
me
here,
maybe,
except
I
don't
know
luke,
but
I'm
just
with
animal
I'm
with
adobe
and
we're
working
with
the
sra
manager,
also
an
operator
kubernetes
and
just
trying
to
get
more
familiar
with
the
overall
enhancement
process.
A
C
Sure
luke
phillips,
maybe
kind
of
like
joseph
I'm
just
kind
of
watching
learning,
trying
to
figure
out
about
the
process
and
see
see
where
someday
help
out
involve
or
something,
but
probably
I've
been
lurking
around
the
release
management
meetings
as
well.
I'm
just
kind
of
looking
to
understand
it
all
so.
C
A
Thanks
everyone
for
those
introductions,
moving
it
to
the
first
discussion
item
that
we
have
for
today.
Can
we
merge
the
kubernetes
announcement?
Pull
request?
Number
I
don't
know
who
added
this
to
the
meeting?
Is
there
someone
who
is
there
in
the
meeting
who,
edit
it.
D
A
Completely
agree
with
that.
Also,
I
see
that
the
last
comment
mentions
that
we
will
discuss
or
review
this
in
the
next
week's
meeting.
It's
supposed
to
be
like
some
meeting
in
december
or
january.
I'm
not
pretty
sure
whether
we
discussed
it
already,
but
what
we
can
do
is
we
can
possibly
like
start
a
slack
thread
on
this
right
after
this
meeting.
E
A
So
that
we
get
more
thoughts
because
clearly
like
whoever
added
this
to
the
notes,
is
not
present
yeah
so
yeah.
Let's
do
that.
D
A
A
Yeah
awesome
doesn't.
A
Cool,
I
guess
none,
okay,
let
moving
ahead!
So
anna
on
behalf
of
me,
at
the
application
level,
add
application
label
to
kubernetes
announcements
issues,
for
example,
stage
duplication.
So
I
guess
this
was
one
of
the
comments
that
was
put
in
when
updating
the
enhancements
handbook.
So.
E
E
Well,
it
was
your
idea
I
can,
but
I
think
it's
a
great
idea,
so
I
can
just
like
add
on
to
what
you
said.
I
guess,
but
we
currently
have
stage
alpha
beta
and
stable
and
we
actually
started
tracking
deprecations,
not
really
like,
maybe
like
starting
few
releases
ago.
So
it's
pretty
new,
but
I
think
it
would
be
really
great
to
have
that
label
and
it
was
not
bruins
idea,
but
I
also
plus
one
on
that
idea
like.
D
Yeah
this
is
like
a
duh
like,
of
course,
we
should
do
it
like
in
this
tracking
sheet.
Like
I
started
tracking
the
deprecations,
I
think
in
120
like
as
deprecation,
so
I
think
that
it
makes
a
lot
of
sense
to
just
have
like
a
visible,
a
ray
actually
wrote
that
I
said
duh
and
then
yeah
I
mean
I.
A
D
A
A
Yeah,
I
know
the
process,
it's
basically
creating
a
pr
in
the
destiny
repository
with
a
config
called
extra
labels,
I'm
not
sure
where
it
exactly
is,
but
I
can
find
it
out
like.
I
can
do
it
if
others.
D
Yeah,
if
you
could
do
it,
but
then
just
like
put
the
put
a
link
to
the
pr
because,
like
I
remember,
I
found
where
you're
supposed
to
add
labels,
and
then
I
lost
it.
So
I
just
like
to
find
it
again.
D
F
A
Yeah
cool,
so
does
anyone
else
have
any
comments
on
this
point.
A
Okay,
fair
enough,
so
let's
go
to
the
next
point.
Next
point
was
added
by
me.
It
was
about.
It
was
also
in
conjunction
with
jeremy.
So
not
just
let
me
read
it
so.
The
thing
is
we
have
been
discussing
on
the
receipt
step
for
some
time
and
there
are.
There
have
been
lots
of
reviews
by
people
and
that's
really
great
to
have
just
that.
A
Externalizing
non
sig
release
non-cigars
community
as
well,
who
are
the
primary
consumers
of
this
as
to
what
they
feel
about
what
is
being
proposed
because,
as
of
now,
I
see
only
comments
from
people
who
have
been
involved
with
release
or
architecture,
and
I
feel
like
there
is
a
lot
of
value
in
getting
reviews
from
people
who
are
consumers
of
what
we
are
proposing.
E
So
we
actually
talked
a
little
bit
about
this.
Maybe
kirsten
can
explain
a
little
better
because
it
was
mostly
her
idea.
I
think
we
talked
about
a
few
weeks
ago
when
no
one
was
here,
but
she
talked
about
like
having
us
review
at
first,
but
then
rolling
out
very
smallly
by
you
know
with
like
maybe
do
a
test
with
like
one
stick
or
something
like
that
right.
I'm
not
sure
if
there
was
like.
D
You
were
talking
about.
No,
my.
I
think
that
my
question.
Well,
I
would
have
two
points
at
this
moment
would
be
one.
I
think
that
you
probably
need
to
like
really
like
think
about
the
receipts
process.
In
light
of
how
successful
the
opt-in
process
has
been
and
whether
or
not
this
receipts
process
is
going
to
add
like
more
heaviness
and
whether
or
not
it's
going
to
give
like
benefit
now,
because
it
was
made
when,
like
the
process,
was
a
lot
more
chaotic.
D
So
that
would
just
be
like
my
number
one
like
overall
thought,
then
my
number
two
thought
would
be
that
I
was
concerned
that,
like
we
can't
just
roll
a
tool
out
to
everyone
in
a
mandatory
way
without
having
some
real
testing,
because
there's
a
potential
that
it
kind
of
imposes
related
to
number
one
imposes
just
like
a
high
burden
on
authors
and
cigs
that,
like
they
just
can't,
really
use
it.
So
like
it's
kind
of
like
the
same
idea,
but
stated
in
two
different
ways.
A
I
I
I
agree
with
both
of
those
ideas,
both
both
counts,
so
I
also
feel
like,
since
we
already
changed
the
process
a
bit
in
the
last
release
cycle
and
people
are
still
like
coming
to
terms
with
what
is
the
new
process.
This
is
like
an
added
thing
on
them,
and
this
was
also
so
so.
The
cap
was
written,
keeping
into
mind
all
constraints
that
we
were
feeling
in
the
previous
process.
D
And
it's
a
lot
harder
to
like
go
into
a
command
line
tool
to
do
that,
and
that
ui
seems
very
like
heavy.
Like
there's
a
directory
structure.
Now
I
have
to
look
in
a
directory
with
a
tool
when
I
could
just
look
at
a
spreadsheet
before,
but
I
think
that
there
could
be
some
value
in
like
having
like
like
we're
now,
organizing
the
repo
better.
D
We
have
this
kept.yaml
artifact
and
we
can
create
a
way
to
like
collect
more
artifacts
for
various
reasons,
and
I
think
that
that
makes
sense
kind
of
as
a
receipt
like
as
a
sort
of
like
a
data
aggregation
tool,
because
we
don't
necessarily
have
a
great
way
to
do.
Some
of
that,
it's
very
manual
to
like
look
at
everything,
but
I.
A
E
A
E
D
Yeah,
it
feels
like
that's
like
the
it
feels
like
that.
Kind
of
thing
is,
like
kind
of
the
true
value
I
mean,
maybe
like
of
the
receipt
or
of
the
tool
is
like
being
able
to
survey
this
vast
reap.
I
mean
the
disaster
repo
to
get
informa
to
get
specific
information,
as
opposed
to
like
this
is
how
I
add
a
cap.
This
is
how
I
move
an
individual
cap
kind
of
along.
D
D
Idea
but
I
lost
it,
but
you
could
definitely
use
that
information
to
like
make
reports
to
make
charts
to
let
cigs
kind
of
use
like
hey.
What
did
we
do?
What
did
we
do
over
the
last
year,
like
how
many
betas
do
we
have
like
they
can
do
all
of
that
like
independently,
without
having
to
go
to
a
spread,
go
to
a
bunch
of
spreadsheets
or
go
to
a
bunch
of
like
emails
and
stuff.
You
know
like
it
could
be
like
a.
F
A
I
agree
and
in
a
way
that
feature
has
already
been
implemented.
I
guess
so.
There
is
a
command
called
capsule
query
where
you
can
specify
minus
one
stage:
minus
minus
sig,
and
it
will
churn
your
metadata
for
all
those
yeps
like
what
is
the
name
who's.
The
author
yeah.
D
F
D
G
Yeah
I
mean
is
the
as,
as
you
say,
with
reporting
is
the
real
value
that
there
is
like
this.
This
defined
structure
of
how
this
data
is
stored,
which
could
be
reported
on,
but
also
fed
into
tools
like
kept
ctl.
If
you
wanted
to
or
even
other
tools
right,
I
mean
you
could
you
could
envision,
I
don't
know
creating
a
slack
bot
or
something
to
let
six
do
whatever
that
way.
There
were
ways
of
making
that
more
ergonomic.
G
D
But
it
wouldn't,
I
think,
if
it's
like,
we
thought
of
it,
I
don't
think
it
would
be
less
ergonomic
like
if
you're
focusing
on
it
as
a
tool
to
facilitate
like
gathering
information,
that's
something
that
we
can't
do
right
now,
really
without
that
tool.
So
I
think
that
if
you
take
away
the
like
this
is
how
I
shepherd
I
kept
through
a
release
and
just
focus
on
it
as
like
this
really
great
information
gathering
tool,
then
it's
like
a
value.
D
Add
like
just
like
right
off
the
bat
you
know,
because
all
of
the
cats
like
is
that
shakar.
I
think
he
he
is
he
the
person
who
was
helping
like
reformat
all
of
the
kept,
like
all
the
texts
are
in
the
proper
form
now
so
like
that
hard
kind
of
onerous
work
has
been,
has
been
done.
So
really,
it's
like
a
value
add
like
once
the
tool
is
shaped
in
a
way
that
people
feel
good
about
like
that.
That
by
itself
would
be
a
value.
D
A
D
D
Yeah,
I
think
I
also
just
think
that,
like
I
think,
often,
process
has
actually
been
pretty
successful,
so
I
think
we
have
to
like
build
on
success,
and
I
think
that,
like
giving
it
more
time,
it's
gonna
also
see
like
what
problems.
There
are
right
because
often,
I
think,
solves
some
problems,
but
it
might
not
solve
all
problems
of
the
like
enhancement
process.
D
D
So
I
think
it's
I
think
it's
cool,
but
I
think
the
tool
itself
has
like
easily
a
lot
of
great
potential
value
like
as
a
data
aggregation
tool
just
right
off
the
bat
and
then
for
process.
Maybe
maybe
it
does
maybe
it
doesn't,
but
I
I
think
that
it's
going
to
be
really
cool
for
the
aggregation
of
information,
because
we
can't
can't
do
that
right
now
without
it.
A
I
plus
one
to
those
points,
so
I
think
we
are
at
a
consensus
here
what
we
need
to
do
with
receipts.
So,
let's
think
on
slack
about
it
and
create
a
thread
mentioning
some
of
the
key
points
that
we
talked
right
now
and
so
that,
like
everyone
who
is
involved,
can
like
give
their
inputs
because
we
don't
have
many
people
on
this
call
right
now.
D
D
A
Okay
cool,
so
let's
hop
on
to
the
next
point
thanks
everyone
for
the
discussion
on
this
really
appreciate
it.
So
it's
from
anna
I
would
hand
over
the
baton
round
to
go
over
the
part.
E
Yeah,
so
I
just
noticed
that
paris
posted
an
issue
that
she
created
for
people
for
enhancements
upgrade
to
take
a
look
at,
but
I
already
I
saw
that
kirsten
actually
made
a
comment,
but
I
think
the
idea
is
that
if
well,
I
don't
know
exactly
I'm
understanding
the
issue,
but
I
think
the
idea
is
like,
if
there's
more
than
one
or
two
six
involved
in
a
cab
like.
Would
it
be
better
to
have
that
kept
discussed
in
a
community
meeting?
Is
that
how
you
understood
that
kirsten?
E
D
D
I
kind
of
couldn't
personally
tell
so
like
my
answer
was
based
on
thinking
that
you
were
presenting
a
cap,
because
I
don't
think
that
I
think
it's
like
how
nabaroon
was
trying
to
get
like
super
like
more
async
to
be
more
inclusive
like
I
don't
know
that,
like
a
sync
meeting
is
a
good
place
to
like
have
that
discussion,
just
given
all
of
the
time
zones,
but
if
it
is
about
like
presenting
a
kep
as
a
way
to
like
talk
about
and
get
async
feedback,
then
I
have
some
ideas
about
it,
but
I
was
just
with
paris
didn't
respond
yet
to
that.
D
So,
like
I
kind
of
just
left
a
question
and
some
thoughts
that
about
that.
E
And
I
think
she's
specifically
looking
for,
can
someone
from
the
release
team,
like
enhancement,
team
or
lead,
I
guess
flag,
which
caps
are.
You
know
good
for
discussion?
I
guess
or
something
like
that.
D
Well,
I
actually
just
had
a
concern
where
it's
like.
I
don't
I.
I
don't
think
that
it
should
be
on
the
release
team
to
flag
these
caps,
like
I
think
that
it
should
be
on
cigs
to
flag
the
caps
by
some
sort
of
criteria
like
I
think
that
the
prr
is
kind
of
like
a
good
starting
point,
because
that
is
those
are
questions
and
information
that
the
general
sort
of
consumer
of
features
is
going
to
like
care
about.
D
But
at
the
same
time
like
I,
I
don't
necessarily
think
that,
like
it's
like
a
oh
release,
team
should
be
like
flagging
flagging
kept
semi
arbitrarily
like.
I
think
that
this
the
community
meeting
is
kind
of
a
burden.
I
think
for
authors
and
cigs,
and
it's
like
a
big
ask.
So
I'm
just
like
a
little
bit
concerned
about
people,
volunteering
people
to.
A
That
yeah,
so
what
I
understood
from
the
issue
is
that
we
have
a
lot
of
different
kind
of
tips
right
and
one
major
one
kind
of
cap
that
we
see
is
which
involves
a
lot
of
six.
Let's
say
one
owning
sick
and
more
than
two
or
like
I
forgot.
B
F
A
Things
so
in
that
case,
it's
usually
like
better
to
have
a
conversation
in
a
common
forum,
and
the
issue
is
basically
suggesting
to
try
to
make
the
community
meeting
that
forum
for
discussion
because
you
can,
if
it
occurs
monthly.
So
let's
say
you
can
possibly
have
a
30
minute
time
slot
where
you
can
discuss
that,
and
I
don't
know
I
think
sigrid
is
stacked
there
because
kept
being
associated
with
the
release.
Otherwise,
I
think
even
an
open
question
on
that
is.
Who
would
be
the
point
of
facilitation?
A
A
The
ask
is
to
find
a
process
to
do
it.
Like
also,
I
see.
The
third
point
is
like:
could
someone
from
the
releasing
flag
which
kept
a
good
or
should
there
be
an
automated
process?
Probably
not,
but
it's
like
a
simple
signal
like,
for
example,
in
the
tracking
sheet.
If
we
see
that
there
are
more
than
two
participating
sigs,
there
may
be
a
flag,
but
I
don't
know
if
we
should
put
time
put
more
time,
investment
into
it
more
than
that,
but
let's
discuss
yeah.
D
Feel
like
this,
this
needs
input
from
ziggs
more
than
it
needs
input
from
us
like.
I
feel
like
it's
more
like
what
is
like:
hey
sick
leads
like
would
this
help
you
and
if
so,
how
would
you
like
to
do
this
because,
like
they're,
the
ones
you
have
to
have
the
discussion
and
also
get
the
value
out
of
the
discussion,
so
I
almost
would
say,
like
I
feel
like
this.
D
This
this
issue
should
be
sent
to
like
sig
leads
for
discussion.
You
know
I
mean
like
like
because
I
just
feel
like
that's
not
it's
almost
like
outside
of
our
expertise,
especially
if
it's
about
groups
of
sigs
collaborating
with
each
other
and
see
what.
D
D
Seems
like
a
lot
of
the
work
where
it's
like
you
want
to
say,
like
the
one
thing
is
to
take
more
ownership
of
kept
and
part
of
that
planning
and
part
of
planning
is
talking
to
the
people
that
you
need
to
talk
to
right
so
presenting
this
as
a
way
to
talk
to
all
of
the
people
that
you
need
to
talk
to
seems
like
the
furthest.
We
can
go
because
once
about
this,
like
you
only
have
four
weeks
for
a
cup
anyway,
so
it's
not
really
going
to
get
you
get
you
there
yeah.
E
E
Sigs
know
right
like
so
that
was
one
of
the
problems
we
had
and
eventually
those
caps
didn't
emerge
or
like
didn't
make
the
enhancement
phrase
but,
like
it
shouldn't
be
really
up
to
us,
like
the
release
team
to
really
like
facilitate
between
the
owning
and
the
participating
stake
right
so
like,
if
there's
a
forum
for
them
to
talk
to
each
other.
If
they
don't
do
that
already,
like,
I
think,
that's
a
really
great
idea.
D
Yeah,
well
maybe
I'll
suggest,
on
the
I'll
I'll
write
something
I
can
write
something
on
the
issue
like
kind
of
suggesting
to
bring
this
to
the
sig
leads
and
see
what
they
think
and
how
they
could
use
this
time
to
facilitate
their
acrostic
communication,
but
also
that's
the
correct.
I
think
that
that's
the
correct
outcome
right.
It's
like,
if
you
don't
talk
to
another
sig,
it's
you're
not
going
to
get
your
work
in
because
you
didn't
talk
to
the
other
six
like.
I
think
that
that's
actually
that's
correct.
I
mean.
D
A
A
F
Yeah
hi,
everyone
hello.
This
is
me
shaker,
hey
yeah,
hi,
hi,
everyone
yeah.
So
in
one
of
the
thread
we
were
discussing
about
capsite
and
release
speeds,
if
you
remember
number
one
yep
yeah,
so
I
I
so
so
right
now
we
have
all
the
metadata
about
the
enhancement,
projects
and
proposals
in
the
repositories,
so
we
want
and
you
and
ui
that
that
will
display
all
these
details
quickly.
A
Yes,
so
we
want
to.
For
starters,
we
want
to
see
like
what
all
caps
have
been
filed
and
from
that
we
can
extend
on
to
the
notion
that
we
can
probably
filter
by
sig
or
filter
by
release
or
filter
by
authors.
Then
like
it
would
be
completely
up
to
the
front
end
on.
How
do
we
do
it?
So
the
one
of
the
asks
there
was
to
have
a
generic
command
on
kfctl,
which
eventually
turned
out
to
be
capacity,
query,
which.
F
A
F
Yeah
yeah
I've
got
it
okay,
I
I
I
will
spend
some
time
to
understand
the
some
commands
and
how
the
jamal
and
jason
jason
generated.
Okay.
B
A
Also
like,
if
you've
seen,
the
thread
tim
banister
from
sick
dogs
had
already
placed
in
with
some
ideas
that
you
can
also
sync
with
him
about
what
work
he
has
done
already,
so
that
you
get
up
to
speed
like
as
soon
as
possible.
If
you.
F
Even
being
him,
okay,
okay,
okay,
got
it
so
yeah
in
release
page
the
current
release
page.
We
can
see
all
the
cap
that
is
completed
or
some
url
that
redirected
to
this
enhancement
proposal
issue.
So
some
any
kind
of
common
thing
in
both
the
pages
or
they
are
both
separate,
totally
different.
F
So
in
kubernetes
release
page,
we
log
everything
right.
F
F
A
F
Yeah
in
changelog
we
we
mark
some
of
the
that
is
completed
right.
A
So
this
was
the
issue
that
started
off
this
conversation
and
thanks
shriker
for
adding
the
slack
traders.
F
A
So
this
also
went
in,
went
in
and
had
like
lots
of
back
and
forth,
so
I
feel
like
we
can
unblock
ourselves
by
starting
with
a
poc
of
how
the
page
would
look
like,
and
maybe
we
can
extend
from
there.
A
I
would
say,
let's
not
bother
about
like
where
we
would
deploy
it
and
which
website
this
will
be
part
of
kdev
or
kubernetes
dot,
io,
basically,
kubernetes
dot,
developer
communities,
dot,
io,
let's
just
build
a
poc
for
others
to
see,
and
maybe
you
can
ask
the
community
directly
that
maybe
just
shoot
an
email
to
sig
release
cigars
and
later
on.
F
D
D
F
Yeah
welcome
my
pleasure
here.
Yeah.
I
will
look
into
the
how
this
command
line
works
and
how
it
gets
generated,
and
we
will.
I
will
explore
how
we
can
disclaim
ui,
and
maybe
I
will
update
in
selection.
A
A
Awesome,
I
think
we
just
have
two
minutes
so
does
anyone
have
anything
else
to
talk
about
on
this
point
or
on
anything.
A
Good
everyone
I'm
going
to
officially
end
the
meeting,
stopping
recording
and
just
thanks
everyone
for
being
there
and
the
awesome
conversations
around
those
points,
try
to
put
up
ai's
on
slack
or
wherever
relevant,
but
for
the
points
that
I
have
taken,
ownership
of
with
that
have
a
nice
day
evening
ahead
with
that
happy
weekend,
bye.