►
From YouTube: Kubernetes SIG API Machinery 20190227
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
Hi,
everyone
welcome
to
Wednesday
February
27th
2019,
a
memory
meeting.
We
have
a
short
agenda,
just
two
items,
but
one
of
those
items
is
it's
potentially
pretty
open-ended
discussion.
So
let's
kick
it
off
with
the
first
item,
which
I
will
introduce
real,
quick,
some
kind,
contributor,
I,
think
I
filed
an
issue
or
something
or
we
charted
in
slack
or
something
anyway.
We
have
this
DPR
out,
which
adds
a
resource
version
precondition
to
delete
options
which
really
I
think
must
have
been
a
oversight.
A
A
A
A
The
other
reason
is
we
are
the
change
as
it
stands,
doesn't
have
a
any
provision
for
making
sure
that
if
you
set
this
field,
when
you
talk
to
an
old
cluster
that
the
old
cluster
will
basically
just
ignore
it
rather
than
honoring
it,
and
so
I
wanted
to
raise
that
this
is
that
too
bad?
Do
we
have
to
you
have
to
do
this
in
a
two
version
approach?
A
We
did
that
for
dry,
run,
making
sure
that
that
I
create
which
version,
but
one
version,
rejected
all
dry,
run
requests,
and
then
the
next
version
started
honoring
them.
So
at
least
you
had
some
going
some
guarantee
that
an
old
system,
even
if
it
didn't
understand
it,
would
still
reject
the
request.
A
C
Precondition
if
someone
goes
to
the
effort
of
actually
setting
it,
they
probably
really
care
that
it
actually
did
what
it
was
I,
you
think
about
previous
ones.
We've
done
where
say
you
have
list
pagination
and
if
your
list
pagination
request,
is
ignored,
you
really
care
yeah,
it's
not
happy,
but
you
can
understand
it
all.
But
in
this
case,
if
you
explicitly
say
please
don't
believe
me
if
you've
changed,
you
probably
have
a
reason
for
caring.
D
E
A
B
C
C
E
C
C
A
C
C
A
A
A
C
C
B
A
A
A
Okay,
other
thoughts
on
that
so
I
think
the
next
discussion
and,
like
you
can
say
your
piece
in
this
second,
if
it's
doesn't
seem
right,
but
I
think
the
next
discussion
is
going
to
be
open-ended
and
mostly
about
how
do
we?
How
do
we
as
a
group,
make
progress
on
a
complicated
design?
When
are
our
forums
that
we
should
be
using
to
interact
with
yeah
I,
don't
know
the
and
and
and
we
can
also,
we
can
also
like
dive
into
the
design
that
we
have
right
now
or
we
could
focus
on.
A
D
Yeah
I
mean
I,
agree,
I,
don't
think
we
should
have
I,
don't
like
having
a
private
email
conversation,
so
I
would
be
happy
if
we
just
yeah
moved
it
to
sig
list
that
the
mailing
list
I
think
we
do
have
some.
You
know,
high-level
discussion
to
have
so
trying
to
just
you
know,
take
a
draft
and
and
discuss
it
in
the
margin
is
not
we're
not
quite
ready
for
that.
Yet
yeah
so
yeah.
If
yeah
yeah.
A
So
I
yeah,
the
the
the
thread
like
I,
didn't
respond
as
frequently
as
I
would
have
liked,
because
it
is
kind
of
complicated
and
I
wanted
to
write
down
my
response
clearly
and
that
turns
out.
I
have
a
projector
right
now.
I
have
the
I
have
five
pages
of
this
at
the
moment.
What
I
believe
I
will
send
to
the
list
immediately
after
this
I
just
finished
it?
Oh,
maybe
I
want
to
reread
it,
but
I'll
be
I'll,
be
sending
that
with
shortly.
A
C
A
C
A
Yeah
so
I
think
I
think
at
this
point
I'm
a
little
confused
like
we
made
so
many
comments
in
the
margin,
and
we
had.
We
had
a
small
group
meeting
to
discuss
it
and
we
had
some
email
threads
and,
at
this
point,
I'm
confused
about
what
the
proposal
is
so
I
I
think
the
next
thing
is:
is
someone
Kim?
If
he
has
time
needs
to
write
a
second
draft
or
send
a
kept?
It
send
an
actual
kept
the
things
label.
Those
caps
and
the
notes
here
are
actually
documents
not
cast
okay,
so.
D
As
I
said,
I
think
we
still
have
some
kind
of
high-level
discussion
to
that's,
not
finished
yeah.
So
tell
you
what,
if
you
have
a
significant
dump
of
thoughts?
Why
don't
you
send
that
I'll
be
happy
to
read
that
and
respond
with
trying
to
consolidate
the
discussion?
You
know
with
a
summary
of
what
I
think
we've
week
to
the
degree
we
settled
on
some
things.
You
know
what
we
said
one
and
what
I
think
are
the
open
questions
in
a
high
level,
and
you
know
try
to
focus
the
conversation
to
move
it
forward.
Yeah.
E
Already
I
would
actually
like
to
mention
that
I
think
if
we
want
to
keep
this
as
a
public
record,
a
very
lightweight
draft
cap
of
the
basics
that
everyone
then
chimes
in
on
may
not
be
a
bad
way
of
getting
all
of
it
in
a
public
record
and
in
fact,
a
public
record
which
is
the
first
place.
People
are
going
to
look
for
the
record
of
why
things
are
the
way
they
are
yeah.
A
So
that
might
that
might
look
like
starting
a
kept
and
fully
filling
in
the
requirements
and
iterating
on
that
until
we're
happy
and
then
start
starting
because
I
I
guess
the
idea
with
caps
were
supposed
to
merge,
often
and
and
like
so
that
you
can
see
the
history
in
the
commits.
I.
Don't
know
if
I'm
completely
on
board.
With
this
theory.
E
A
D
Lock
in
what
little
progress
we've
made
so
far,
and
and
this
is
a
kept
specifically
again
since
I
think
we
do
still
have
some
open
issues-
a
kept
that
is
a
place
I
guess
I'm
not
quite
sufficiently
familiar
with
kept
so
I'll
see.
If
I
can
look
that
up,
I
understand
it
as
a
way
to
document
the
community's
thinking
about
why
it
is
the
way
what
we
want
and
why
we
want
it
and
not,
and
what
and
don't
want
something
else.
Yeah.
A
A
Yeah
we
can
coordinate
on
the
on
the
email
list.
Okay,
we're
18
minutes
in,
and
this
is
maybe
one
of
our
shortest
meetings
ever.
Does
anybody
have
other
items
that
would
be
good
to
talk
about
in
this
group,
or
should
we
call
this
called
the
chordae
I'm
good,
all
right
going
once
going
twice?
Okay,
thank
you!
Everybody.
This
has
been
a
very
short
meeting.
Super
efficient
I'll,
see
you
all
in
a
couple
weeks.