►
From YouTube: 20210505 SIG Arch Prod Readiness
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).
B
Cinco
de
mayo
may
5th
2021,
and
it
is
this-
is
the
kubernetes
production
readiness
subproject
meeting?
Thank
you
all
for
joining
us.
Let's
get
started
alana.
Do
we
have
any
action
items
to
review?
I
do
think.
A
B
Was
just
yeah,
I
did
mine
and
we
did
start
getting.
We
have
it
here.
We
started
getting
responsible.
We
only
have
26
responses,
which
is
not
very
many.
We
had
like
75
or
something
last
year
last
year
when
we
did
it.
So
this
is
probably
reflects
me
not
going
out
and
posting
stuff
on
slack
and
like
really
like
last
time
I
was
a
little
more
aggressive
with
it.
B
We
did
get
bob
after
the
cncf
bob
kill
and
talk
to
the
cncf
and
had
them
put
it
out
to
the
end
user
community,
which
is
really
good.
So
we
maybe
have
you
know
some
good
results
in
here,
but
we-
I
don't
want
to
close
it
yet
and
probably
after
cuba.
B
So
next
week
maybe
take
some
time
and
try
and
drum
up
some
more
responses
and
see
see
how
that
goes,
so
that
that
would
be,
I
guess,
the
only
action
it
was
to
check
on
the
status
of
that
and
that
that's
where
we
are
right
now.
B
B
Yeah
and
then
looks
like
the
rest
of
the
agenda
items.
Oh
well.
The
next
two
are
yours.
Well,
I
know
so.
A
I'll
take
it
away,
then
so
this
has
been
approved
already,
but
I
wanted
to
just
raise
this
as
a
topic,
so
we
had
it
on
the
record.
My
question
was:
is
prr
applicable
when
there
are
no
entry
changes,
so
there
was
a
cap
from
sig
cluster
life
cycle
and
they
wanted
to
make
some
changes
to
cube
adm
and
they
said.
Oh
we've
got
this
feature
flag
and
I
said
on
these
various
control
plane,
components,
I'm
like.
Okay,
what
changes
are
you
making
to
those
control
plane?
Components
like
that's.
A
You
know,
potentially
a
lot
of
things.
You're
gonna
have
to
talk
to
they're
like
no,
no
we're
not
actually
making
any
changes
in
tree.
It's
just
in
cube.
Adm
and
the
author
didn't
really
understand
the
question.
I
guess
so
once
I
confirmed
that
it
was
kind
of
like
well,
it's
just
in
cube
adm,
so
there's
not
really
anything
to
coordinate,
so
I'm
not
sure
prr
is
applicable,
so
I
approved
it
and
I
guess
in
the
future
it's
like.
B
A
B
B
The
understanding
so
far
is
that
the
whole
release
tracking
process,
so
so
it
comes
down
to
the
the
capped
process
is
actually
only
necessary
for
things
that
are
in
tree
and
it's
optional
for
things
that
are
out
of
tree.
But
I
would
think,
if
you
choose
to
do
the
kep
process,
then
you
know
you
may
want
to
have
production
readiness
review,
but
that
you
know
a
lot
of
our
questions.
Just
don't
apply.
B
And
then
you
just
say
for
anything
that
doesn't
apply,
you
just
say
any
and
that
maybe
we
need
to
put
a
little
node
in
the
template.
Anything
that
does
not
apply.
You
can
put
n
a,
but
we're
still
going
to
look
at
those
and
say
no.
No.
That
actually
applies
because
that
happens.
People
put
in
m
a
oh,
yes,
oh.
A
C
D
C
Be
reviewing
those
but
but
yes,
I
think
it's
such
cases
will
be
happening.
Yes,.
B
Yeah
and
enhancements
team
was
working
on
sort
of
a
flowchart
to
help
people
and
like
a
way
to
sort
of
like
potentially
bypass
like
to
people
again
to
answer
the
question:
do
I
need
a
cap
and
then
you
know
whether
there's
further
refinement
beyond
that
of
when
I
need
a
cap.
Do
I
need
this
section
and
that
section
is
a
different
question,
but
even
to
just
answer,
the
question
do
I
need.
A
cap
is
not
always
clear
to
people,
and
so
the
enhancement
sub
team
is
working
on
that,
but
I
haven't
attended.
B
A
Planning
on
attending
next
week,
and
I'm
not
sure
either.
I
think
that
we're
seeing
a
lot
of
this
where
people
they
want
a
design
doc
and
they
want
review
from
their
sig
chairs
and
they
want
to
follow
the
standard
review
cycle
and
the
only
way
that
we
have
to
do
that
right
now
is
a
cap,
so
you
know,
and,
and
the
folks
get
very
concerned
they're
like
well,
I
need
pr
of
you.
I
can't
work
on
this
until
I
get
this
pr
for
if
it's
like
well.
A
B
Right:
okay:
next
item.
A
Next
item,
so
I
was
just
we
might
want
to
come
back
to
this
one
or
I
don't
know
what
order
we
want
to
do
this
in.
But
okay,
mostly
I
was
concerned.
C
C
I
mean
I
added
first
round
of
comments,
and
hopefully
the
last
one
but
yeah
it's
still
six
out
of
out
of
64
that
we
have
now
but
like
the
interesting
point,
is
that
when
I
was
looking
into
this
spreadsheet
today
morning,
my
time
there
were
like
46
or
some
or
44
or
something
so
like
20
of
them
were
added
like
today.
Wow
I
expect
another
like
30
or
something
will
be
added
like
I.
I
think
we
may
reach
hundreds
out
of
this.
C
Related
to
pr
but
yeah.
A
Well,
so
I
will
say
at
least
so
I
was
one
of
the
people
who
was
adding
a
bunch
of
kept
to
the
spreadsheet.
I
added,
I
think,
like
17
yesterday
for
node
a
bunch
of
them
were
no
no
granted
like
not
all
of
them
are
necessarily
in
shape
to
make
it
for
this
release.
A
bunch
of
them
were
just
like.
Oh
this
slipped
from
last
release.
We
already
did
prr.
We
don't
have
to
do
it
again
right,
so
there
are
at
least
a
decent
chunk
of
them
in
that
camp.
A
Like
another
example,
would
be
api
server
tracing
that
one
has
been
prred
to
death
like
it's
just
it
just
keeps
slipping
so
some
of
them
there's.
No
pr.
I
don't
know
that
the
release
team
has
gone
through
and
like
actually
labeled,
which
things
already
had
prr
done
versus
what
needs
it
for
this
release
and
so
on.
Maybe
we
can
ask
them
to
do
that,
and
that
way
we
can
then
we
can
see
who's
assigned
and
then
split
them
if
they're
not
yeah,.
B
B
C
B
B
B
Cool
okay,
yeah,
so
I
I
think
definitely
we
need
to
keep
our
eye
on
this
and
tomorrow
I
will
go
through
mine
and
see
how
many
I
have
assigned
and
we'll
try-
and
I
guess
this
is
the
last
ball
point.
I
will
try
and
identify
any
that
that
haven't
been
flagged
that
are
in
the
spreadsheet,
but
are
missing
from
any
kind
of
pr
reviewer
assigned
and
probably
go
through
and
assign
them.
C
I
think
okay
there's
another,
there's
next
point
about
it.
Yes,
I
think
john,
if
you
could
take
a
look
into
elana's
pr
that
is
linked
below,
because
that
will
force
us.
I
wanted
to
do
that
for
quite
some
time
also,
and
so
thanks
for
doing
that,
I.
A
Just
started
getting
really
mad.
I
was
like.
I
am
furious
that
I
have
to
every
single,
like
I
think,
I've
reviewed
five
caps
thus
far
and
every
single
one
I've
had
to
comment
this
on
there
because
it
wasn't
pulling
in
the
pr
review
because
they
didn't
update
the
metadata.
So
I
made
it
required.
So
I
went
through
about
like
20
of
these
and
I
actually
like
checked
the
issue
and
figured
out
the
stage
and
the
last
milestone
and
then
some
of
them.
A
I
gave
up
zero,
zero
and
alpha
because
there
aren't
them,
don't
have
it
set.
B
A
Much
so
so.
A
C
Okay,
so
I
also
responded
to
the
email
thread
from
release
team,
where
they
were
mentioning
describing
what
what
is
required
to
have
a
cap
target
a
feature,
and
I
think
we
we
need
to
actually
start
checking.
If,
if
there
is
like
an
appropriate
latest
milestone
in
the
capian,
because
that
will,
for
example,
automatically
will
let
us
know
if
we
have
a
pr
or
not.
C
A
Yeah,
I
think
one
of
the
things
I'm
struggling
with
right
now
in
reviewing
these
things
is
there's
a
ton
of
metadata
in
the
cap.eml
file
and,
frankly,
like
I
only
really
care
about
maybe
three
or
four
things
like
I
care
about
the
title,
the
number
the
current
stage,
the
latest
milestone
and
like
maybe
the
reviewers
and
the
approvers.
I
don't
care
about
anything
else
and
like
there's
a
bunch
of
data
in
there,
and
I
think
the
problem
is
people
see
that
and
they're
like
oh
there's
too
much
to
fill
in
here.
B
A
But
this
one,
I
really
want
these
to
be
required
so
because
it
is
causing
me
misery.
So
I
think
at
least
having
the
like
zero
zero
indicates
that
it's
wrong
and
somebody
needs
to
go
and
update
it.
There
was
a
question
about
whether
or
not
we
should
have
like
an
unknown
stage
instead
of
setting
them
all
back
to
alpha
for
the
ones
that
we
don't
know,
but
I
I
think
it
might
be.
B
D
A
And
I'm
hoping
to
so
for
my
mentoring
cohort
right
now,
I'm
hoping
to
try
to
get
through,
at
least
for,
like
the
people
in
my
group,
to
get
them
to
review
all
of
their
six
caps
and
update
this
metadata
for
us
as
part
of
some
of
the
enhancement
stuff
that
we're
working
on.
So
then,
maybe
I
have
like
a
group
of
people
who's
willing
to
do
this,
but
that
won't
cover
every
sig.
So.
B
B
D
A
So
I
explained
like
line
by
line
every
change
that
I
made
here,
which
was
adding
the
file
name
to
the
data
structure,
fixing
this
error,
because
this
map
never
gets
initialized
and
actually
making
the
things
required.
B
B
So
we
had
a
warning
before
it's
still.
A
A
warning,
but
now
it
fails
because
it's.
A
Yeah
I
spent
like
two
hours
on
this
last
night,
so
I
hope
it
was
appreciated.
I
hope
it'll
save
us
pain,
because
I've
already
spent
like
so
much
back
and
forth,
telling
people
they
need
to
set
this
and
them
not
setting
it.
Oh
yeah
somebody
else
submitted
the
same
initialization
there's
now.
Three
people
who've
submitted
this
and
I
closed
some
duplicates.
This
is
just
the
same
code
change.
D
C
Yeah,
so
I
was
wondering
whether
we
shouldn't
have
like
a
special
marker
for
that,
but
on
the
other
hand
like
I
see
much
value
of
like
committing
it
now
and
yeah.
B
A
A
C
Can
you
find
caps
by
milestone
using
capsteel?
I
can't
remember.
A
B
B
I
I
run
it
through
to
like
put
it
into
a
little
spreadsheet,
and
then
I
just
and
then
I
work
the
spreadsheet
right
like
I
run
it
once
I
put
it
in
a
spreadsheet
and
then
I
that
way
I
can
keep
track
of
did.
I
did
I
look
at
this
one.
Did
I
look
at
this
one
like
keep
notes
on
them.
You
know,
and
then
I
run
it
again
later
and
see
if
stuff's
been
added-
and
you
know
it's
it's
kind
of
panty
ass,
but
we'll
refine
the
process
over
time.
A
D
Well,
it
is
required,
though,
for
the
actual
yeah
for
the
review
so
like
it's
not
like.
It's
not
like
the
automation
is
adding
an
extra
requirement,
because
the
shadows
would
just
be
looking
for
it
anyway.
So.
A
A
It'll
make
everyone's
life
easier,
because
I
don't
have
to
have
the
conversation
with
every
single
person
who
submits
a
thing
to
please
update
the
metadata.
My
only
concern
is,
if
you
don't
update
the
metadata
at
all
and
it's
already
in
an
implementable
state.
It's
really
easy
for
people
to
miss.
It.
B
A
D
No,
it's
not
it's
not
happening
in
122..
I
I
think
that,
especially
given
the
opt-in
process,
which
kind
of
changed
the
game
anyway,
like
the
research
process
kind
of
has
to
be,
I
think,
just
reconsidered
to
see
like
what
problem
they're
solving,
and
I
know
that
people
are
still
working
on
that,
but.