►
From YouTube: 20200520 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).
A
All
right,
hello,
everybody!
This
is
the
kubernetes
architecture,
production
readiness,
sub
project
meeting
for
may,
20th,
2020
and
there's
voice
moving
very
fast,
okay
east
on
my
screen.
So
I
think,
last
time
we
met
we,
we
had
some
we're
supposed
to
pick
a
cap
and
review
the
production
readiness.
A
Retrospective
prr,
he
did
for
certificate,
signing
requests
for
the
certificates
api
and
really
no.
No.
No,
I
mean
you
know,
as
usual,
with
jordan's
work,
no
issues
there.
It
was
good
and
there
was
one
great
thing
that
came
out
of
it.
A
He
said
that
and
going
through
that
and
having
to
answer
that
he
actually
found
that
one
of
the
metrics
in
question
hadn't
been
wired
up,
so
you
know
essentially
going
through
and
having
to
be
sort
of
extra
thorough
about
this
from
found,
an
issue
which
was
nice
but
other
than
that
I
haven't
had
a
chance.
I've
signed
up
for
one
or
two,
but
I
haven't
had
a
chance
to
read
them,
and
I
guess
just
as
a
side
note,
we
did
merge
the
we
didn't
merge.
A
The
related
prs
to
put
the
policy
in
place
yesterday
was
enhancements
freeze,
so
we
should
have
a
bunch
in
the
queue
we
did
not
sort
of
strictly
enforce
that
people
had
to
have
answered
these
questions
for
119,
because
we
came
in
kind
of
late
with
the
merge
of
the
policy,
but
nonetheless
we
encouraged
it
and
a
lot
of
people
did
answer
it.
So
anybody
else
have
any
comments
or
have
a
chance
to
review
any
of
the.
B
I
don't
know
for
sure
that
the
cab
itself
is
actually
going
to
make
it,
but
I
went
through
and
the
answers
are
pretty
good.
B
This
one,
I
think,
might
be
easier
because
it's
focused
on
cluster
operators.
I
think
it
definitely
gave
a
sense
of
like
okay.
I
could
turn
it
on
like
this
and
turn
it
off
like
that.
B
A
A
B
B
The
answers,
refreshing
and
better
answers
than
they
were
before
yeah.
It
definitely
demonstrates
a
scaled
back
design,
which
I
think
is
good.
A
That's
great
yeah,
so
yeah
I'm
definitely
getting
the
sense
that
when
these
are
answered,
they're
done
well,
I
do
still
have
the
same
concern
we
have
before,
which
is
like
you
know
the
number
of
the
review
capacity
of
this
small
team
here
and
but
you
know,
I
think,
we'll
we'll
get
a
better
understanding
of
that
over
the
next.
You
know
over
this,
the
rest
of
the
cycle
and
into
the
next
cycle.
But
how
do
we.
A
B
A
Yeah,
I
think
we
should
be
able
to
get
there
fairly
soon,
so
the
enhancements
no
project
has
jeremy
records
already
put
together
a
little
tool
for,
like
you
know,
creating
new
caps.
We
can
add
some
functionality
that
will
query
github
it's
going
to
create
the
pr's,
not
just
the
chaps,
so
we'll
have
to
see
what
let
me
just
put
a
note
here,
I'll
put
an
ai
for.
A
C
C
Yeah,
I
also
reviewed
like
two
scheduling
related
prrs
and
I'm
reviewing
one
for
like
the
new
events
that
I
was
kind
of
involved
since,
like
the
beginning
of
that
and
and
the
the
events,
one
is
like
still
in
progress.
They're,
like
the
initial
version
wasn't
like,
was
far
from
what
I
would
expect,
but
I
think
we
are
making
progress
there
and
the
scheduling
ones
they
both
both
were
pretty
good
ones.
I
I
had
some
comments,
but
those
were
like
pretty
minor
ones.
A
A
All
right
any
other
thoughts,
any
other
action
items
for
next
time.
I
I
still
have
like
down
relatively
far
on
my
priority
list
to
kind
of
put
together
a
report
for
cigar
treat
out
on
on
our
survey,
but
you
know,
or
at
least
on
the
whole,
on
the
I
don't
know
I
don't
know
if
tomorrow
I
have
to
look
at
who
we're
doing,
which
is
some
project.
B
A
Readouts
tomorrow,
but
put
together
a
more
comprehensive
update
on
that.
But
it's
not.
B
A
To
percolate
up
to
my
top
of
my
list
for
a
little
while,
maybe
for
when
we
do
sig
updates,
which
I
think
the
community
meeting
update,
which
I
think
is
next
month,
that
might
be
a
good
time
to
squeeze.
B
The
the
one
thing
that
I
have
as
a
personal
objective
I
would
like
to
go,
look
through
and
find
some
more
responses
to
the
production,
readiness
answers.
So
I
will
probably
I
have
a
list
of
five
caps.
I
think
I
know
that
are
coming
in
and
landing
for
api
machinery.
I
will
be
going
through
those
in
the
next
couple
weeks
make
sure
they
answered
the
readiness
reviews.
B
I
think
we
actually
declined
the
caps
for
sigoth,
but
I
will
go
back
and
and
double
check
those
as
well,
because
I'm
also
familiar
with
them,
so
I'd
be
able
to
look
and
know
whether
the
answers
were
appropriate
for
the
future.
So
that's
something
that
I
okay,
we'll
do
I'll.
B
A
A
All
right,
excellent,
yeah
I'll
review
some
more
for
next
week.
That's
two
weeks
from
now,
but.
C
B
B
Think,
as
a
group,
we
should
have
a
goal
to
actually
get
through
all
the
ones
that
are
going
great
and
just
I
looking
at
it.
I
think
that
I
can
ap
machinery
is
doing
several.
I
will
see
what
author's
doing
and
then
probably
come
back
and
say
what
other
areas
am
I
closer
to
that.
I
could
help
meaningfully
review,
but
if
we,
if
we
get
really
close
to
actually
being
able
to
do
all
these
reviews,
then
I
think
we
can
have
a
lot
more
confidence.
A
A
All
right,
thanks,
fellows
and
I'll,
see
you
later
sounds
good
right.