►
From YouTube: Kubernetes SIG API Machinery 20190508
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
A
A
C
A
A
D
C
A
F
A
E
A
E
This
at
the
end
that
says,
if
we
run
into
compelling
use
cases
that
require
like
for
details,
we
could
enhance
the
response
from
the
web
hook
to
like
give
us
information
about
run
me
again.
If
some
field
selector
thing
and
wave
hand
waved
the
fact
that
all
the
use
cases
we
have
today
would
be
covered
by
a
run
them.
One
more
time
makes
me
think
that
we
probably
won't
get
for,
at
least
for
a
long
time,
yeah.
A
E
The
gist
is,
we
should
be
able
to
do
this
for
all
web
hooks.
The
fact
that
we
can't
means
is
because
there
are
bugs
in
some
web
books
today
so
be
1.
Beta
1
will
be
opt-in,
but
my
goal
is
to
make
this
opt-in
only
for
big
ones,
beta
1
and
once
what
books
go
to
stable,
this
should
just
be
part
of
getting
called
as
a
web.
You
should
be
prepared
to
be.
A
E
A
G
G
Oh,
this
is
for
the
scalp
area,
so
the
cap
itself
is,
is
it
needs
this
and
then
it
needs
some
test
coverage
I
are
current
thinking
is
to
send
out
a
little
survey
to
some
people
to
try
and
get
some
more
data
on
scale
needs,
so
I'll
send
something
in
the
swatch
panel
later
today
and
if
anybody
would
like
to
themselves
or
know
somebody
who
has
good
CRT
use
cases,
please
try,
and
if
that
survey
filled
out
and
we'll
make
use
of
that.
Okay,
it
looks
like
this
has
had
a
lot
of.
F
A
C
Looked
at
that
in
a
long
while
did
the.
H
A
C
A
It
seems
like
I,
think
I
know
where
check
was
out
of
office
for
a
week
or
two,
so
he
had
a
example
PR,
which
I
love.
Some
comments
on
yeah,
yeah,
I,
think
where
we
left
it
is
is
I
was
like
it
seems,
like
most
of
the
benefit
was
Watchers.
When,
when
you
get
an
object,
it
makes
sense
to
like
serialize
at
once
before
sending
it
to
all
Watchers.
So
I
I
wondered
it.
Maybe
that
would
give
us
like
90%
of
the
benefit
with
less
complexity
and
I
think
he
was
looking
into
that
still.
B
I
E
I
E
I
A
H
As
well,
I
haven't
all
weekend
stories,
my
great
aunt
just
happiest
it's
making
the
storage
migrated
not
doing
anything
and
kill
all
the
HTTP
server
has
agreed
on
the
storage
version
at
this
solution
in
this
camp
is
very
specific
to
the
storage
migrated
and
we
believe
it's
a
common
problem.
You
know
it's
a
setup,
so
I
think
we
need
to
look
at
this
camp
now.
I
will
challenge
every
camper
solution
together.
A
Thank
you
proposal
for
dry
run
authorizations.
Yeah
I
meant
one
and
talked
to
me
a
little
bit
like
the
basic
problem
as
I
understand.
It
is
the
system
that
the
system
that,
like
you,
maybe
you
want
some
sort
of
pre
submit
system
to
check
your
files
when
they're
checked
into
a
to
it,
get
rapport
or
whatever.
But
you
don't
want
that
system
to
necessarily
be
able
to
push
those
files
or
have
the
have
the
permission
to
actually
make
production
changes.
E
I
E
E
So
in
the
simplest
case,
where
you
had
a
manifest
that
I
created
a
namespace
and
then
created
some
stuff
inside
the
namespace
yeah,
it
doesn't
help
that
dry
run
would
give
you
a
thumbs
up
on
the
namespace
and
then
fail
on
all
the
other
creates
because
the
namespace
didn't
exist,
and
it's
also
like
exercising
CI
against
production
with
dry
run
is
not
yet
a
use
case.
I've
seen
CI
typically
operates
on
an
actual
ghoster,
where
it
can
actually
exercise
things.
Yeah.
I
A
G
F
A
H
A
A
It's
try
to
try
that
again
on
the
right,
all
right,
Dave
I'm,
just
assuming
that
we're
going
to
cancel
next
week
because
Q
Khan
or
two
weeks
from
now
rather
a.
H
A
J
J
But
there
are
some
implications
around
how
to
handle
how
the
components
should
handle
losing
leader
election,
because
right
now,
I
think
most
components,
just
panic
if
they
lose
election.
But
if
you
lose
the
cloud
election,
then
should
you
panic
or
should
you
do
nothing
so
Daniel?
You
mentioned
that
the
complexity
might
not
be
worth
it
and
I'm
totally.
Okay,
with
just
saying
here's
a
page
that
documents
how
to
migrate,
even
though
it
might
be
a
little
bit
more
complex
that
if
we're
not
adding
that
complexity
to
the
yeah.
A
A
It
also
yeah
yeah.
It's
also
like
better
redundancy
characteristics
like
if
one
of
your
controller
manager
fails.
Like
you
don't
need
all
of
your
controllers.
You
just
lose
some
of
them.
The
other
thing
I
was
I
was
thinking
about
the
like
the
shutdown
like.
If
you
lose
the
lock,
how
do
you
fix
that
problem?
I've
been
toying
with
the
idea
of
maybe
maybe
we
can
have
a
like
an
admission
control,
an
admission
control
plugin.
That
is
like
a
lock
assertion,
checker.
So
like
every
time
you
send
it
like.
A
The
controller
has
some
lock
somewhere,
and
it
includes,
along
with
its
request,
a
what
I'm
calling
it
like.
Some
sort
of
a
some
sort
of
a
attestation-
that's
like
I,
a
I'm
making.
This
change
and
I
hold
this
lock
and
if
I
don't
actually
hold
this
lock
than
I,
do
a
board
has
change
and
we
can
have
a
plug-in
which
notices
these
things
looks
at
the
resource
that
the
controller
asserts
it
has
locked
and
like
fails,
the
request.
If
that
lock
has
been
invalidated.
A
The
I
think
everything
I
just
described
can
be
done
with
today's
tools,
with
one
exception,
which
is
there's
no
way
in
a
delete
request
to
add
some
sort
of
data
that
would
get
threaded
to
like.
You
can't
thread
arbitrary
data
in
a
delete
request
to
admission
control
plugins
because,
like
like
with
with
a
post
or
a
put,
you
can
include
an
annotation
with
a
delete.
There's
no,
like
you,
can't
you
Tate
and
delete
that's,
not
a
thing.
You
can't
pass
a
random
query,
parameter
so
I'm
not
sure
how
that
would
work.
I'm.
A
C
A
C
A
Yeah
exactly,
and
so
maybe
maybe
the
sort
of
general
way
to
do
this
is
to
just
give
the
controller
like
a
primary
and
secondary
lock
like
as
like
a
flag,
and
then
you
can,
you
can
have
if
you
can
programmatically
determine
what
those
what
those
locks
are
then
that's
enough
to
like
move
arbitrary
sets
of
controllers
into
their
own
their
own
process.
Well,.
K
J
K
C
Which
is
the
unfortunate
but
not
the
end
of
the
world?
It's
not
great,
but
it's
not
awful
either
right,
like
the
lease
you'll
compete
on
it
again
and
see
it
again.
Yeah.