►
From YouTube: 20220203 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
Okay,
hi
everyone,
it's
thursday
february
3rd
2022..
This
is
the
fig
architecture,
enhancement,
subproject
meeting.
We
abide
by
the
kubernetes
code
of
conduct.
It
would
be
good
to
everybody
and
I
guess
we'll
we'll
get
started.
I'm
kirsten
and
with
me
is
ray
and
I
do
I
need
to
share
my
screen.
I.
B
A
There's
only
two
of
us
we're
both
looking
at
the
same
thing,
so
ray
actually
added
a
github
issue.
It
was
I'll
put
it
in
the
chat,
even
though
he
has
it
for
posterity.
A
Let's
see,
it's
called
kept
stages
and
transitions,
so
I
guess
I'm
just
wondering
what
you
wanted
to
discuss
right.
I
feel
like
you
won
a
radio
show
right
now.
B
So
this
is
just
to
highlight
an
issue
that
was
brought
up
during
the
123
release
cycle,
but
it's
more
of
a
proposition.
I
guess.
If
we
need
a
two-phase
commit
in
the
kep.yaml,
do
we
need
a
do?
Do
we
need
to
distinguish
a
target,
an
action
and
an
actual
release?
I,
I
guess
release
version
dates
of
the
cap.
I
guess
the
background
is
just
like
what,
if
I
kept,
does
they
do
opt-in
for
a
release?
B
Some
folks
believe
that
they
should
not
revert
a
change
on
a
cap
that
said
that
there
should
be
other
fields
another
or
another
fields
or
other
fields
involved
that
that
will
state
and
at
target
versus
and
versus
an
actual.
So
this
is
just
one
that
was
just
brought
up
during
the
123
release.
Just
want
to
bring
it
up
on
this
subproject
call.
A
Yeah,
I
guess
reading
it.
The
thing
that
concerns
me
is
that
it.
A
It
makes
I'm
a
little
bit
worried
about
the
idea
that
people
might
have
to
go
back
and
I
don't
know
like.
A
Maybe
I
should
share
my
screen
so
that
we
can
kind
of
see
one
second
yeah,
because
I
think
that
the
proposal
was
having
a
two-stage
commit
where
it
was
like
target
and
actual,
and
that
seems
like
it
would
require
people
to
do
another
pr
into
the
cap,
which
feels
like
it
would
be
even
harder
to
track
right
like
because
right
now,
what
is
it
we
end
up?
Having
that
the
essentially
like
the
the
release
that
we're
targeting
and
then
if
that
is
incorrect,
you
know,
like
the
release
team.
A
Has
people
go
back
and
say:
okay,
that
was
wrong
like
we
have
to
update
it
or
the
next
time
that
you're
actually
trying
to
do
it.
You
have
to
fix
it,
but
this
would
mean
that
for
everybody
they
would
probably
have
to
do
a
second
pr
to
their
enhancement.
Is
that
what
it
that's
kind
of.
A
We're
adding
more
touches
but
more
touches
feel
like
more
opportunities
to
have
things
stale
or
wrong.
B
A
A
A
A
I
mean
it
feels
like
I
mean
like.
I
think
that
we
always
say
like
in
the
release
like
it's
not
done
until
it's
done
right,
like
it's
not
done
until
everything's
merged
at
the
end,
and
we
are
sure
that
you
know
a
certain
cup
was
and
its
you
know.
Associated
work
was
included
in
the
release.
So
there's
always
that
element,
but
I
feel
like
the
release.
Team
is
also
tracking,
like
who's
getting
booted
out,
and
it
feels
a
little
bit
more
doable
to.
A
So
maybe
that's
something
you
know
ensure
that
the
cap
is,
you
know,
updated,
which
I
don't
know
that
seems
kind
of
difficult,
if
we're
honest
with
ourselves
like
to
force
people
to
go
back
and
make
another
pr,
even
just
to
take
away
the
I'm
wondering
one
thing
that
we
could
do-
and
this
is
a
little
bit
weird,
is
that
because
we
can't
always
get
people
to
do
the
pr
on
the
cat's
update
like
if
it's
dropped,
I
mean,
I
think
most
people
do
do
it,
though,
but
if
they
don't,
we
could
always
just
have
like
potentially
a
label
that
indicates
that
it
was
dropped
from
a
release
like
in
the
issue.
A
A
A
Yeah,
so
I
mean
is
this
like
from
the
perspective
of
the
release
team.
Like
a
big
issue,
I
mean
it
feels
like
you
know,
the
release
team
is
tracking
the
things
to
get
dropped
and
it's
easy
enough
to
write
a
note
on
which
I
think
they
which
I'm
pretty
sure
they
already
do.
They
write
a
note
on
the
issue
that
says
this
was
dropped.
A
B
A
A
Do
we
really
need
more
more
than
that
you
know
like
if
our,
if
it's
not
in
our
official
like
these,
are
the
caps
that
were
in
the
release
list?
If
the
release
team
has
gone
to
the
open
issue,
because
it
kept
still
open
and
said,
hey
it's
the
drop
from
this
release,
I
mean
there
doesn't
really
seem
to
be
that
much
work
to
do.
B
Yeah,
I
agree.
We
could
also
add
this
to
the
survey.
A
Yeah
yeah,
but
I
know
that
there
was
also
like
a
what's
it,
a
web
page
that
somebody
was
working
on
for
caps.
So
there's
also
the
thing
of
like
some,
I
think
right
now.
Maybe
the
list
of
kept
in
a
release
is
a
little
harder
to
access,
but
I
think
that
you
know
if
the
kept
website
goes
live
then
it
also
kind
of
reinforces,
what's
actually
in
the
release
like
in
a
pretty
visual
clickable
way,
as
opposed
to
just
like
a
repo
that
you're
bumbling
around.
A
So
I'd
probably
wait
to
see
like
if
that
clears
up
any
confusion
as
well,
but
I
think,
as
long
as
the
especially
the
release
team
is
unambiguously
saying
things
about
an
issue
and
it's
you
know
properly,
labeled
feels
like
that's
the
lowest
sort
of
touch
thing
that
we
can
do
that's
reasonably
accurate.
B
Yeah,
we
could
add
something
about
even
well
actually
a
more
general
question
like
what
changes
or
what
what
books
like
to
be
in
the.
A
Yeah
yeah,
I
mean
I
just
haven't
really
seen
this
be
like
a
big
issue
in
the
releases
and
I
feel,
like
you
know,
cups
are
reasonably
up
to
date,
so.
A
We'll
see,
I
know
we
could
yeah
I'll
think
about
it.
Do
you
want
to
go
to
the
survey?
Actually
I
just
I
was
just
doing
some
brainstorming
so
I'll
share
my
screen
hold
on.
A
Can
you
see
my
screen
yep
right,
okay,
cool.
I
can't
see
you
now
yeah,
so
I
can
give
you
access
to
this
as
well,
but
I
was
just
thinking
of
like
general
ideas
like.
I
know
that
there
are
certain
ways
to
like
formulate
actual
questions,
so
what
I
wanted
to
do
is
just
like
get
some
areas
that
we
thought.
Generally.
We
were
interested
in
getting
some
information
and
then
like
talking
to.
I
know
there
are
some
people
who
are
really
good
at
making
surveys
to
get
it
formed
into
like
a
proper
survey.
A
So
I
have
instructions
because
I
know
like
at
least
for
me
even
just
personally,
I
find
it
really
hard
to
read
the
instructions
of
the
cats
like
they
don't
exist
anywhere
outside
of
the
markdown,
and
I
think
that
can
be
really
confusing
for
people
like
people
have
said
that
to
me
as
well
like,
oh,
like,
is
there
a
separate
dock
with
the
instructions
or
you
know
like
it's
actually
kind
of
hard
to
view
them
without
being
in
like
a
super
markdown
view,
and
then
I'm
just
wondering
about
like
the
quality
of
the
instructions
you
know
like
do
any
of
them
make
like
sense
or
not?
A
Subject
matter,
I
know
that
we
were
always
talking
about.
You
know.
We
want
people
to
memorialize
their
decision
making.
B
A
But
you
know
like
the
cap
is
very,
is
best
suited
for
like
a
very
technical
kind
of
subject,
but
there
are
process,
caps,
potentially
and
other
types
of
caps
that
maybe
we
haven't
thought
about
that.
You
know
people
want
to
write
a
cap
for,
but
maybe
the
current
template
is
really
heavy
or
doesn't
have
things
that
they
think
are
relevant.
You
know
so,
like
kind
of
getting
that
kind
of
information.
A
I
did
have
this
thing
in
a
section
for
the
test.yaml,
like
I
don't
know
how
people
are
interacting
with
that.
I
feel
like
and
I'm
kind
of
interested,
especially
the
statuses
like
because
we
have
provisional
implementable
implemented,
but
then
we
also
have
these
other
optional.
Things
like
deferred,
rejected,
withdrawn
replaced,
and
I'm
wondering
like
how
often
do
people
actually
use
like
all
of
the
statuses
and-
and
you
know
like-
did
they
find
them
useful
at
all?
A
You
know
just
to
see
I
had
a
user
story,
because
someone
was
actually
asking
for
user
story
guidance
previously
and
now
I'm
just
wondering
like
do
other
people
have
the
same
issue
because
we
can
always
get
you
know
more
guidance
for
this,
and
I
think
it's
I
mean,
I
think
what
I
wrote
was
pretty
self-explanatory.
A
So
I'm
not
gonna
go
too
deep,
but
I
also
wanted
to
flag
just
specific
questions
like
to
sig
leads,
since
they
see
like
a
lot
of
different
authors
like
if
there's
something
that
people
are
always
getting
caught
up
on
something's
missing
if
there's
something
that
they
want
to
require
or
if
there
are
things
that
they
as
like
leads
think
you
know,
isn't
necessarily
that
useful,
because
I
think
they
have
like
a
slightly
different
perspective
than
authors.
B
A
So
I
feel
like
they
have
like
a
sort
of
great
perspective
on
like
the
actual
template
itself,
and
I
just
I
thought
general
usage
would
be
interesting
because
the
one
thing
I
thought
was
like:
do
people
really
read
kept
like
after
they
kept
it
done
or
we
all
just
like.
You
know
trying
to
get
it
like
the
final
stage,
but
then
we
never
like,
like
how
often
are
people
using
the
cap
you
know
like
like?
Is
it
easy
to
find
makeup
that
they
want
etc?
A
And
then,
just
like
general
technical
issues,
like
you
know,
have
you
ever
encountered
like
a
technical
issue
that
prevented
you
from
submitting
your
calf,
whatever
those
were
just
like
the
the
kind
of
sub
sections
that
were
off
the
top
of
my
head?
Some
of
them
were
probably
unnecessary
and
probably
need
other
things,
but
that
was
kind
of
what
I
was
going
for
in
my
first
pass.
So
hey
wait.
I
can't
see
you,
I'm
gonna,
stop
sharing
now.
Oh
there
you
are.
Oh,
I
love
there's
ray
sorry,
so
yeah
like.
A
Is
there
anything
that
you
think
we
should
add
whether
it's
like
a
specific
question
or
like
a
general
area
about
like
the
sort
of
kept
template
with
an
eye
of
like
how
do
we
improve
this
like?
How
do
we
improve
the
usage
or
remove
the
friction
or
something.
B
Yeah,
I
think
we
should
just
have
at
the
end
of
the
survey.
Just
have
a
general
comment
box,
because
what
if
someone
has
a
topic
or
a
point
that
is
not
covered
in
these
questions?
B
I
know
we've
have
a
few
issues
that
people
have
created
and
that
they
wanted
to
talk
about,
and
I
think
we
should
also
see
if
we
can
add
those
not
specifically
like
those
issues
that
we
have
regarding
cups
to
the
survey
in
some
way
or
the
other.
But
not
does
that
be
like
address.
It
specifically
is
like
what
do
you
think
of
issue?
B
You
know
one
two
three
or
something
like
that,
so
just
more
voice,
since
we
now
we
have
a
several.
We
could
also
see
we.
B
No,
I
don't
want
to
link
the
issues
yeah,
just
using
kind
of
like
some
of
the,
not
all
the
issues
like
some
of
the
issues
that
we
might
see
that
other
folks
might
be
interested
or
might
or
might
have
input
on
just
having
it
in
a
general,
a
general
way
to
add
some
feedback
from
those
issues
to
the
survey
yeah.
I
could
add
in
some
some
suggestions
and
yeah.
A
A
B
Because
we
we
kind
of
have
this
this
reach
with
the
survey,
and
so
we
could
leverage
it
with
with
some
more,
I
guess
some
issues
that
might
be.
I
guess
that
might
that
might
have
more
interest,
not
seeing
that
every
issue
will
have
an
interest
but
like
we
could
highlight
a
few
of
those
or
one
one
or
two
of
those.
A
Yeah
yeah,
it's
like
it's
it's
kind
of
like
I
I
in
a
way
I
want
to
get
people's
like
unpainted
opinion
about
the
cat,
and
that's
the
one
thing
that
I
worry
about
is
like
people
who
already
have
an
issue
like
they
know
what
the
issue
is.
So
I
feel
like
we're
aware
of
that.
But
then
there's
like
this
vast
vast,
vast
ocean
of
people
that
haven't
said
anything
you
know,
and
it's.
B
A
Like
I
don't,
I
don't
understand
like
what
this
graduation
criteria
mean
and
we
could
have
like
a
bunch
of
people
who,
like
they
find
friction
and
something
that
you
know
we
don't
find
friction
in
or
that
you
know
louder.
People
don't
necessarily
find
friction
in.
So
that
was
the
one
thing
where
I
I
thought
about
like
really
taking
the
questions
from
other
open
issues,
but
then
I
thought
you
know
like
we
know
about
those
open
issues,
and
so,
if
we're
asking
for
feedback,
if
other
people
you
know
have
that
feedback,
they
can
leave
it.
B
A
They
want
to
say
about
so
probably
letting
the
questions
be.
Most
of
the
questions
be
optional
and,
having
like
a
sort
of
free
form
section
would
also
let
people
like
dip
in
and
leave
their
like
two
cents,
even
if
they
just
want
to
talk
about
like
one
thing,
so
I
really
think
that's
like
a
good
idea,
probably
try
to
keep
it
short,
though
right,
because
people
don't
like
long
surveys.
A
I
know
that
there's
one
or
two
people
in
the
community
that
are
really
good
at
making
surveys,
so
we
can
go
to
them
to
like
get
some
survey
survey
information,
but
do
you
think,
do
you
think
we
should
have
the
same
survey
for
like?
I
was
just
thinking.
It's
one
survey
and
you
know
we
asked
like:
are
you
an
officer?
Are
you
a
reader
or
are
you
a
lead
and
then
for
leads?
It's
like
like?
A
A
I
think
I'm
gonna
I'll
pass
the
links
around
a
little
bit
and,
and
we
can
sort
of
add
a
little
bit
more
ideas
and
then
just
like,
because
these
are
just
ideas
and
then
try
to
just
fill
it
down
to
something
that's
a
little
bit
more
concise
and
then
feel
pretty
good
about
it.
So
I
think,
like
a
page
is
probably
I
mean
it's
not
going
to
be
a
google
doc,
but
like
shorter
is
better
than
longer
and
the
freeform
box,
I
think
you're,
a
thousand
percent
right
is
probably
essential,
so
that'll
be
cool.
B
This
is
something
I
saw
on
the
slack
channel.
I
feel.
A
Like
they
don't
go,
oh
nine,
eight
eight.
A
That
was
one
of
my
questions,
because
that
was
the
one
thing
that
I'm
not
I'm
not
personally
like
sure
what
the
ergonomics
from
the
cap.yaml
are
for.
Users,
like,
I
feel
like
a
lot
of
us,
are
like
more
involved
with
the
actual
readme.mb
like
the
meat
of
the
cap.
You
know
so
maybe
like
we're
like
there's
like
how
how
do
authors
find
the
kept.yaml
with
something
that
I
thought
that
we
should
definitely
ask
about
and
see
like
you
know,
is
this
useful?
Is
it
difficult
to
keep
updated?
A
A
B
A
A
Well
there
he
opened
a
pr,
but
I
know
there's
some
open
comments
on
the
pr
that
weren't
addressed
so
there's
that
one
second.
A
So
there's
that
so
I
mean
that's
that
pr
is
not
ready.
The
one
thing
that
we
talked
about
like
in
the
past
was,
I
mean,
we're
kind
of
limiting
the
changes
that
go
into
the
template
right
now.
So
that's
good.
We
used
to
have
a
lot
of
churn
on
the
template
and
so
like
rejecting
people
for
not
having
the
updates
didn't
quite
make
sense
because,
like
the
template
was
always
changing
and
it
was
like
well,
how
do
you?
How
do.
A
Like,
like
you
know,
how
can
I,
how
can
I
expect
you
to
have
the
most
updated
version
of
something
if
there's
no
version
so
like
there's
kind
of
a
tension
between
arches
pr
and
then
the
general
like
we
don't
have
a
version
to
say
that
you
have
to
be
at,
and
so
that
was
kind
of
a
concern
of
mine
where
we're
just
kind
of
gonna
say
like
yeah,
like
you
don't,
and
I
think
his
pr
mostly
changes
the
it
just
checks
the
title.
So
it's
really
just
like.
A
Does
it
have
the
titles
or
not,
which
I
think,
given
that
the
kept
template
hasn't
had
any
churn
seems
more
reasonable
than
it
did
last
year
when
he
opened
it?
So
you
can
probably
get
this
in
in
some
reasonable
cadence.
But
I
also
do
think
that
this
might
be
a
good
time
to
think
about
versioning.
The
cap
like
to
say
you
know,
maybe
ask
like
to
say,
like
what
we
have
now,
because
it
hasn't
changed
for
quite
a
long
time
is
like
version
zero,
because
you
know
like
we're.
A
Gonna
have
to
actually
like
give
the
cap
some
sort
of
version.
At
some
point
so
that
we
can
actually
track
it
as
we
change
it,
and
it
might
be
a
good
time
to
think
about
it,
since
the
template
has
been
pretty
stable
for
a
long
time.
So
I'm
just
throwing
that
out.
A
A
Yeah
yeah
yeah,
so
I
think
we
could
feel
I
was
just.
I
was
also
concerned
that,
like
running
some
check
on
on
the
pr's,
like
could
block
authors
who
just
want
to
have
something:
that's
more
provisional,
like
in
a
work
in
progress
kept
like
that
was
a
concern
of
mine
with,
but
then
I
guess
it's
like.
If
we're
really
just
checking
for
the
subtopic
titles,
it
doesn't
matter
that
much
like
it's
not
that
big
of
a
burden.
It's
just
like
yeah,
put
back
a
couple
of
the
subtitles
that
you
took
out.
A
A
The
thing
is
like
when
you
start
to
have
like
checks
in
a
linter,
then
you
have
to
always
keep
it
up
to
date
so
like
if
we
actually
let
it
run
now,
and
we
think
we're
gonna
change
the
template
later,
a
bunch
of
things
are
going
to
be
merged.
That
would
have
to
eventually
change
again.
So
I
don't
know
what
the
utility
of
that
is
going
to
be,
but
that's.
A
Yeah,
so
what's
what
we
could
do
is
is
we
could
get
the
pr
kind
of
like
up
to
snuff
and
then
just
kind
of
hold
it
until
we
get
our
results
back
and
decide
what
we're
gonna
do
yeah,
but
but,
as
a
general
matter
like
the
the
linter
is
like
a
good
idea,
and
we
want
to
get
that
in
before
the
next
release,
along
with
whatever
changes
we
wanted
in
the
cab,
so
yeah,
but
then
we'll
have
to
figure
out
well
see.
This
is
the
other
problem.
A
Now
that
I'm
talking
out
loud,
the
problem
is,
is
like,
if
you
change
the
kept
and
you
change
the
like,
let's
say,
there's
a
survey
and
the
survey
makes
some
changes
to
the
kept
template.
Do
we?
Can
we
really,
without
a
lot
of
notice,
start
requiring
people
to
make
non-trivial
changes
to
their
cap
like
potentially
like
right
before
the
release,
like?
I
don't
really
think
so
so
like
having
had
like
that's
that's.
A
That
was
the
problem
that
I
had
with
the
winter,
because
we
don't
have
versions
on
the
cap,
because
if
you
had
versions,
you
could
say
you
know
you
can
be
within
one
version
of
the
current
version.
So
you
don't
necessarily
for
this
release
have
to
be
on
the
newest
version.
You
should
at
least
be
on
the
previous
version,
something
like
that
like
we
could
have
like
a
sort
of
refinement
for
that,
so
that
new
taps
always
use
the
newest
version,
but
older
caps
have
a
little
bit
of
room
to
update
themselves.
A
B
A
I
mean
it's
like
eyeballed
for
the
most
part
like
there
were,
there
were
a
couple
like
major
version
shifts
where,
like
the
version
was
clearly
different,
like
you
were
using
a
completely
different
format.
So
for
like
a
release
team
member
or
someone
else,
it
was
really
easy
to
be
like
you're
on
a
version
from
like
two
years
ago.
You
know,
but
now
it's
like
the
the
form
of
the
test
is
pretty
stable.
A
A
A
B
A
A
Everybody
should
be
up
to
this
version,
and
even
if
we
come
up
with
a
new
kept
template,
you
still
have
to
be
on
this
version
and
then,
when
we
roll
out
whatever
changes,
we
get
from
the
survey
that
can
be
version
one
or
whatever,
and
then
we
can
kind
of
decide
what
we
have
to
do
with
the
winter
and
by
what
date,
people
would
have
to
be
updated
to
that
new
template.
So
it
might
be
good
to
treat
this
as
version
zero,
like
the
stable
base,
like
you,
gotta
have
this
with
the
winter.
A
Yeah,
okay,
so
cool
but
yeah.
I
also
just
for
the
template
changes.
The
one
thing
that
I
wanted
to
be
mindful
of
was
not
changing
the
template
all
the
time
and
like
only
changing
it
like
any
slam,
but
like
once
a
year
or
something
where
then
we
can
really
ensure
with
the
linter
and
the
future
versioning
and
everything
else
that
people
are
well
aware
of
the
changes
that
there
are,
but
they
were
not
making
like
a
lot
of
micro
changes
to
a
template
that
people
just
don't
pick
up
on
like.
A
A
To
do
like
post
survey
would
be
to
like
figure
out
when
to
flow
out
new
template
changes
and
how
versioning
yep,
you
know
what
I
mean
yeah
I
mean
I
think
that
that'll
be
interesting,
like
get
a
good
opportunity
to
finally
like
bring
the
kept
and
then
try
to
like
articulate
that
to
the
community
in
a
meaningful,
easy
way.
It's
just
not
going
to
cause
anybody.
Any
stress.
A
Cool
okay!
Well,
thanks
for
that,
so
yeah
I'll
I'll.
Send
you
the
links
to
this
to
the
idea
stuff
and
I'll
also
send
that
to
the
other
enhancements
leads
and
like
you,
can
either
ask
specific
questions
or
like
just
brain
dump
like
anything,
and
then
we
can
kind
of
just
iterate
to
get
it
down
to
like
a
nice
format.
I
just
want
to
see
if
anybody
has
like
a
specific
area
that
they're
like
oh,
I
know
people
might.
B
A
Yes,
it's
country
backs,
I
think
I
can
ask,
I
think
josh
burkus
might
know.
So
I
was
gonna.
Ask
him
first,
if
he
or
if
he
knows
anybody
or
she's
the
person,
to
try
to
kind
of
get
power
survey
into
sheep
and
can
help
make
that
help
us
figure
out
how
to
actually
make
the
server.
B
A
So
yeah,
since
it's
just
us
and
we're
done
all
right,
we're
done
thanks
ray
I'm
gonna
stop
recording
for
a
second
do
I
do
that.