►
From YouTube: 20200923 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,
architecture,
production,
readiness,
subproject
meeting,
it's
a
mouthful
for
september,
23rd,
2020.,
so
david.
You
were
saying
something.
B
Yeah
there
are
a
few
features
that
people
have
noticed
have
been
in
beta
for
a
long
time
and
are
looking
to
move.
Ga
and
among
them
are
pbs
pod
disruption
budgets.
B
I
suspect
that
most
people
who
would
attend
this
call
actually
know
what
those
are,
but
they
basically
keep
a
certain
number
of
pods
from
stopping
at
the
same
time,
at
least
unintentionally,
and
that's
really
useful
for
certain
kinds
of
workloads
to
make
sure
like
you,
don't
bring
down
two
out
of
three
seds
at
the
same
time
as
a
for
instance,
it's
been
there
in
beta
since
one
five,
and
I
think
our
production
survey
has
shown
us
that
basically,
everyone
runs
with
the
beta
features
turned
on,
and
so
I'm
wondering
if
that
is
a
strong
enough
reason
to
just
go
ahead
and
say
like
for
pdbs.
B
B
A
I
know
that's
a
good
question.
I
guess
it'll
kind
of
depend
on
how
much
effort
we're
talking
about
like.
If
do
we
have
a
list
of
do
we
have
a
punch
list
of
what
people
think
needs
to
be
done
yet
or
done
still?
Why.
B
B
Five,
you
said:
yes,
wait,
what
yeah
that's
right
about
after
the
one
nine
refactor,
so
I
think
we
just
didn't
even
think
about
it.
I
just
don't
even
know
if
we
have
a
kept
for
it.
A
Yeah
I
mean
the
other
well
yeah,
so
I
think
we
need
to
put
together
a
punch
list.
I
don't
know
that
we
need
to
go
retroactively,
write
a
cap
that
seems
like
way
too
much
paperwork.
A
So
in
my
mind
we
do
need
a
punch
list
I
need.
I
would.
I
think
we
want
to
understand
and
look
at
the
questions
and
see
if
there's
any
gaps,
even
if
we
haven't,
if
we
haven't
needed
them,
there's
probably
nothing
significant.
A
I
wouldn't
imagine
there's
something
stopping
it
from
going
to
beta
up
from
green
to
ga.
Given
it's
been
sitting
there
for
so
long.
We
don't,
I
don't
know
of
any
incidents
or
anything
certainly
could
look
into
it.
Thought
we've
had
incidents.
I
don't
know
if
flightcheck
knows
anything.
C
Yeah
for
pdb,
I
I'm
not
aware
of
any
like
issues
that,
like
we,
we
have
to
solve
like
before
ga
like
there
is
also
like
crunch
of
that
we
were
david
for
that.
I
actually
think
there
is
a
bunch
of
work
to
do,
but
for
pdb
I
I
wasn't
also
like
deeply
following
what
is
happening
there,
but
I'm
not
aware
of
anything
that,
like
really
has
to
be
done
to
ga,
like
I've
heard
about
like
feature
requests
for
that,
but
I
don't
think
these
are
really
blocking
ga
in
it.
As
this.
B
Okay,
so
I
guess
we
would
probably
be
the
people
who
also
were
involved
in
the
conversation
about
how
to
get
at
the
ga,
so
that'll
make
that'll
make
it
easy.
I
agree
that
cron
jobs
in
particular
come
from
the
list
and
we
do
have
a
list
of
things
that
are
impacted,
although
we
didn't
assess
all
of
them.
Cron
jobs
definitely
have
more
work
to
do,
but
I
think
we're
doing
actually
pretty
good
on
the
list
of
existing
beta
apis.
B
B
A
Okay,
so
definitely.
A
B
I
think
we're
doing
pretty
well
on
the
other
enhancements
in
the
list.
Right
I
know,
monche
is
looking
at
cron
jobs.
There's
a
guy
named
ali.
He
was
actually
trying
to
look
at
code.
I
don't
know
he
made
progress.
We
got
csrs
done.
Pod
security
policies
are
just
going
to
die.
Events
move
to
v1
last
release.
I
think
ingress
has
moved
last
release
as
well,
either
better
than
moving
at
120..
B
I
think
they
might
have
to
last
one
month,
runtime
class.
I
thought
google
was
working
on
that.
I
guess
I
don't
know
for
sure.
That
was
the
one
that
tim
all
clear
was
working
on,
but
he
just
moved
didn't.
He
went
down
okay,.
B
A
Yeah
yeah,
I'm
sure
that
yeah
I'll
follow
up
on
that
make
sure
that
that's
moving
forward.
I
think
I
think
the
note
team's
on
that,
but
not
I'm
not
concerned.
B
I
guess
if
we
have
to
prioritize
readiness
reviews,
I
would
probably
prioritize
readiness
reviews
for
these
apis
if
they're
trying
to
graduate,
if
they're
just
trying
to
shift
to
another
beta,
I
think
they
can
stay
as
they
are.
B
But
there
is,
but
some
things
like
the
changes
for
cron
jobs
are
actually
pretty
significant.
A
A
B
Yeah
yeah,
so
he
works
right,
he's
looking
at
it
and
then
there
was
another
developer
who
was
interested
named
ali,
but
I
don't
know
the
current
status
there.
Mache
probably
would.
C
There
is
a
pr
I
didn't
yet
look
into
the
pr
itself,
but
like
what
he
said
to
me
is
that
it
seems
to
be
roughly
working
already,
I'm
not
sure
like
in
how,
with
what
shape
it
is
whether
it
has
tests
and
stuff
like
that,
or
it
seems
that
there's
at
least
something
here
in
terms
of
code
already
also-
and
the
cap
I
think,
is
in
pretty
good
shape,
so
I
mean
it
doesn't
have
like
pr
file,
for
example,
but
I
think
it's
also
quite
it's
not
super
sophisticated.
In
this
case.
B
Had
a
couple
production
downs
over
that
yeah,
I'm
going
to
say
I'm
going
to
pressure
mache
to
go
ahead
and
fill
that
section
in.
C
B
A
Are
ready
for
that,
but
I
don't
have
anything
else
right
now.
I
think.
B
B
A
Yeah,
I'm
gonna
check
in
one
small
change
to
it
that
I
tried,
because
before
this
meeting
I'm
like
I'll
go
see.
If
I
have
any
and
then
I
found
it
like,
if
people
messed
their
caps
under
under
directories,
then
it
was
puking
on
that.
So
I
had
to
fix
it,
but
that's
fixed
now
and
I
just
have
to
submit
the
pr
but
yeah
anyway.