►
From YouTube: 20200729 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
Hello,
everybody:
this
is
the
kubernetes
sig
architecture,
production
readiness,
sub
project
meeting
for
july,
29th
2020..
A
So
I
have
one
thing
I
wanted
to
discuss
or
bring
to
your
attention
at
this
call
so
as
part
of
the
enhancement
sub
project,
we're
working
on
this
kept
control,
and
I
have
a
pr
here
to
add.
Do
you
see
the
the
thing
I
clicked
through
to
now?
You
probably
only
still
see
the
original
one,
because
it's
sharing
the
tab.
A
A
Yeah,
you
can
click
okay,
you
have
clicking
ability
so
yeah,
so
it's
a
little
cli
tool
and
this
particular
pr
adds
a
query
function
so
that
you
can
query
by
sig
and
whatever.
So
what
I'd
like
you
to
give
some
thought
to
what
I
plan
to
do,
I
think
there's
actually
a
document
out
there.
That
starts
to
describe
what
people
want,
and
maybe
people
already
have
feedback
on
that.
But
let
me
let
me
see:
lori
apple
was
asking.
A
But
in
any
case,
so
what
I'm
thinking
is
from
our
point
of
view
in
this
group
like,
wouldn't
it
be
nice
to
have
something
that
says,
show
me
all
the
things
where
I'm
the
pr
approver
show
me
the
things
where
there's
no
prr
approver
sign,
although
the
kept
validation
now
doesn't
let
things
go
through,
but
you
could
find
it
since
it
allows
you
to
include
prs,
not
just
things
in
the
file
system.
You
can
actually
find
any
pr's.
A
For
example,
yet
so
that's
what
I'm
thinking
I
want
to
add
query
parameters
for
that.
If
there's
anything
special
you
want,
I
know
david
you.
This
was
of
interest
to
you
that
we
can
determine
out
of
the
kept
metadata.
You
know,
then,
please.
C
A
B
B
A
Here
this
document
is
where,
if
you
haven't
seen
it
I'll
put
an
agenda
and
requirements.
A
A
So
if
you
want
to
click
through
on
that
too,
if
you
haven't
already
seen
that
document.
A
D
A
Document
was
produced,
but
this
is
where
we
put
in.
D
A
Requirements
around
queries
so
anyway,
that
was
what
I
wanted
to
bring
everybody's
attention
here.
As
far
as
other
topics,
I
have
not
personally
been
diligent
in
going
back
and
finding
my
pr
reviews
and
doing
them,
so
I
I
I
do
need
to
get
on
the
ball
on
that.
But
what
about
the
rest
of
you.
D
D
D
I
think
we
need
to
think
whether
what
we
are
doing,
what
we
will
be
requiring
for
120
and
whether
we
are
going
to
require
more
or
actually
start
really
requiring
it
or
yeah.
What
are
our
plans
here.
A
I
think
we
we
can
probably
I
expect
120
to
be
a
small
release
because
right
what
going
on
the
pool's
not
even
open
yet
really
as
far
as
like
we're
still
in
code
freeze
and
the
holiday
season's
upon
us
very
soon,
black
friday,
cyber
monday,
all
that
business.
So
I
expect
there
won't
be
a
huge
amount
in
that.
So
it's
probably
a
good
time
to
start
to
say:
okay,
but
let's,
let's
enforce
it,
because
the
burden
won't
be
too
much
we'll
get
a
really
clear
idea.
That's
my
opinion.
I
don't
know
david.
B
I'm
willing
to
give
that
a
go.
I
think
in
some
ways
this
interacts
with
the
thread
that
voytech
started
on
big
reliability.
B
For
us
yeah
so.
B
D
Yeah,
I
think
those
are
all
great
questions
like
I,
I'm
not
even
sure
like
secret
reliability
is
the
best
option
or
like
there
are
clear
drawbacks
of
that
and
like
some
of
them
brought
by
team,
I
think
other
people
also
are
bringing
up
some
other
issues.
So
I
I'm
not
I'm
not
yet.
D
Definitely
convinced
that
cigarette
ability
is
is
the
right
way
if,
if
it,
if
it
appears
that
it's
something
we
would
like
to
proceed,
then
I
would
say
that
the
production
readiness
is
actually
part
of
that
other
parts
mentioned
like
other
parts.
There
are
things
that,
like
yeah,
it
would
be
more
like
cross
cutting
like
other
efforts.
More
will
would
be
more
like
cross
cross.
D
Cutting
across
six
like
there
will
be
significant
things
around
testing,
which
it's
unclear
like
the
sig
reliability,
the
the
the
role
of
sig
reliability
in
that,
whether
it's
like
just
driving
it
or
like
really
contributing
or
like
things
like
upgrade
test.
I
think
we
wanted
to
I
ideally.
I
would
like
them
to
be
like
enforced
at
their
like
production
readiness,
but
we
don't
have
infrastructure
really
and
we
don't
have
like
good
examples
to
force
people
to
actually
start
doing
that
now.
D
So
I
think
many
of
the
aspects
of
that
are
actually
related
somehow
to
production,
readiness.
A
A
I
don't
know
if
yeah
I'm
kind
of
like
is
creating
another
separate
sig,
the
right
move
or
trying
to
get
these
things
attention
in
the
existing
cigs.
Creating
another
sig
creates
a
little
more
overhead,
and
would
it
really
recruit
more
people?
I
mean
that's
what
it
comes
down
to
is
like.
A
Are
there
people
who
would
be
attracted
to
that
and
join
in
and
participate
that
aren't
participating
in
sleep
testing
that
aren't
participating
in
this
effort
that
you
know,
and
it's
not
entirely
clear
to
me
and
and
then
the
danger
others
have
mentioned
of
like?
Oh,
that's,
not
my
problem,
but
that
one's
not
as
much
of
a
concern
to
me
because
part
of
like
this
and
other
process,
things
or
automations
that.
B
B
I
guess
ours,
our
our
goal
here
is
small
enough
that
we're
going
to
be
able
to
enforce
many
pieces
of
it
by
bot,
not
all
of
it,
but
many
pieces
of
it.
B
Sig
reliability
seems
broader
to
me
and
I'm
less
sure
that
it's
going
to
be
able
to
enforce
these
things
by
bot
or
at
least
its
goals,
but
but
knowing
that,
like
you,
guys
see
these
as
at
least
in
some
way
related
like
that,
that
makes
makes
it
a
little
bit
more
clear
to
me.
B
I
think
what
what
a
future
direction
would
be,
and
I
don't
know
where
the
sig
reliability
is
going
to
get
approved
or
not
right,
like,
I
think,
that's
a
topic
for
a
separate
call,
but
I
just
want
to
make
sure
I
knew
where
this
went.
D
We
used
to
have
soaked
this
some
time
ago,
like
five
years
or
four
years
or
something
and
nothing
is
happening
in
that,
and
everyone
believes
it's
needed.
No
one
is
like
really
looking
into
that.
So
can
we
really
maybe
sig?
Reliability
is
not
the
best
way
to
achieve
that.
Maybe
there
are
better
it's
probable,
it's
even
more
than
probable,
like
I
I'm
just
wondering
like
what
are
those
ways
to
actually
get
it
and
get
people's
attention
to
to
couple
things
that
seem
to
be
important
from
reliability.
Perspective.
A
Okay,
so
we
probably
don't.
A
A
I
mean
I
think
that
that
the
category
the
questionnaire
already
says
this
is
for
beta.
This
is
only
new
for
ga.
This
is
only
for
alpha,
so
I
would
think
that,
before
the
enhancements
freeze,
people
need
to
fill
out
the
sections
that
are
for
their
stage.
D
We're
really
asking
right
that
that's
yeah,
that
I
agree,
but
are
we
going
are
we?
A
A
Yeah,
I
don't
know
I
I
I
mean
I'm
open
to
taking
you
slower
like
in
being
saying
just
ga
things
for
now
and
that
the
others
that's
not.
C
D
B
Think
seems
like
building
out
the
tool
will
at
least
allow
us
to
issue
the
query,
see
how
many
we
have.
A
B
A
Know
what
I
mean,
what
actually
is
gonna?
You
know
what
the
people
are
actually
gonna
make
forward
motion
on,
but
I
guess
we
get
an
upper
bound
roughly
because
unless
new
people
come
in
with
new
enhancements,
of
course
too,
but
that
aren't
out
there
yet.
But
we
get
some
idea
of
it.
A
In
some
ways
like
alpha
things,
there's
very
minimal
requirements
on
alpha
things.
It's
like.
Basically,
you
can
turn
this
thing
off,
and
so
that's
even
more
important
in
the
sense
of
like
if
somebody
actually
went
through
alpha
with
something
that
they
didn't
have
a
feature
gate
for
that
was,
like
you
know,
feature
gainable.
That
might
be
even
worse,
so
I
don't
believe
that
would
happen
anyway.
I
mean,
I
don't
think
a
sig
would
let
that
through.
A
B
Yeah,
I
think,
given
what
I
anticipate
the
schedule
for
120
looking
like
I
I'll,
be
able
to.
B
Help
in
a
significant
way,
I
think
my
next
four
weeks
are
going
to
be
pretty
pretty
busy
with
downstream
stuff
inside
of
red
hat.
Okay,.
B
C
D
A
D
A
That
just
sign
up
here,
our
approver
like
we
could
actually
have
it
say:
oh
you're,
going
to
beta.
I
think,
there's
a
couple
things
in
there
like
metrics,
that
you
have
to
define
and
you
have
to
define
the
different
components
that
are
affected.
We
probably
can
modify
some
of
those
things.
Yeah.
B
I
need
an
intern.
I
need
an
intern,
a
google
summer,
faux
project
it's
too
late,
but
we
needed
one.
B
One
that
like
could
do
a
social
hack
on
me,
so
that
basically,
every
day
at
I
don't
know
9
30
in
the
morning.
It
sends
me
a
message
and
says
you
should
review
this
one
prr
section
and
so
like
it's
right
there,
there's
no
excuse
it
pops
up
in
slack,
I
click
it.
I
review
the.
C
B
But
I
think
if
we
can
build
it
into
a
tool
with
a
sort
I
can,
I
can
like
have
the
mental
discipline
to
do
one
per
day.
A
Okay,
all
right
all
right,
well
take
a
look
at
that
in
that
those
the
temp
control
tool
and
see,
if
you
you
know
what,
like
I
said,
my
plan
is
already
to
add
a
flag
in
there.
That
says
I
can
look
for
a
particular
pr,
reviewer,
who's
assigned
or
ones
where
nothing
none
is
assigned,
which
could
happen
in
a
in
a
pr.