►
From YouTube: Kubernetes SIG API Machinery 20180328
Description
For more information on this public meeting see this page: https://github.com/kubernetes/community/tree/master/sig-api-machinery
A
A
Like
Phil
is
not
here,
does
anyone
know
what
Phil
wanted
to
say?
I
saw
him
earlier
today,
oh
yeah,
there's
a
question
about
their
working
group
for
admissions
I.
Try
to
share
all
of
my
documents
with
humanities,
announce
communities
dedicate
a
missionary
in
this
case.
I
also
shared
was
the
mailing
list
that
I
made
for
the
Wraiths
group.
A
B
Don't
think
it's
Oh
echo
on
anything
else
for
310
that
we
haven't
already
discussed
things
like
wanting
to
limit
package
imports
for
the
QB
API
server.
Maybe
move
us
out
of
the
master
package
if
we
start
being
able
to
prune
and
pin
down
what
dependences
we
have
and
there's
some
of
the
ongoing
CRD
work
around
versioning.
C
And
so
it's
a
project,
you
know
there
and
we
have.
The
police
is
available
for
anyone
who
wants
to
play
with,
and
it
supports
some
some
nice
functionality
like
docks
duration,
that
unusable
so
if
you've
been
trying
to
figure
out
how
to
generate
thoughts
for
your
place
yeah.
This
is
what
I'm
doing
it
was
people
asking
about.
A
D
A
B
D
B
D
C
Someone
else
was
I,
just
had
a
thing
on
staging
and
the
60
Li
we're
trying
to
build
common,
tooling
libraries
for
clients
that
can
control
would
use
and
but
could
potentially
use
by
other
folks
and
I.
Think
one
thing
we
ran
into
is
that
we
can't
publish
those
outside
of
kubernetes
quarterly,
both
because
the
nothing
outside
nothing
depending
on
equal
in
staging
can
be
vendor.
That
can
be
okay,
shooting
things
in
studio
with
in
staging
right.
C
But
if
we
made
it,
if
we
made
like
kinase
new
repo-
and
we
created
a
library
in
there
and
we'd
and
on
client-
go
for
instance,
the
what
we
were
told
is
you
cannot
bend
their
back
library,
but
it
doesn't
go
back
to
the
kubernetes,
because
the
there
is
maybe
of
Glencoe
rains
backwards.
Compatibility
that
there
is
no
way
to
update
the.
C
That
time
I
mean
so
say,
I
have
like
new
like
food
you're
saying
you
can't
fix
it
because
it
is
vendor
so
yeah
I
can't
you
can't
fix
the
vendor
right
because
it's
been
hurting.
You
can't
fix
the
other
one,
because
you
haven't
submitted
to
change
right.
That
breaks
it
to
be
fixed
right.
Ii
need
to
submit
the
changes.
I,
don't
like
with
things
in
staging
referring
good
things
of
staging.
It's
probably
things
not
in
staging.
Yes,
it's
you
can't
show.
C
That
means
that
we
we
have
to
anymore
like
putting
more
in
staging
or
as
a
it's
necessary
for
us
to
put
more
in
staging.
If
we
want
to
feel
free
to
help
us
like
actually
cut
the
cord
yeah,
that's
one
approach,
I
guess
is
wondering
if
there's
disability
of
those
api's
might
be
coming
to
a
point
where
we
don't
expect
it
to
be
this,
to
be
a
big
issue
or
if
there's
some
subset,
I,
don't
know
if
I'd
go
that
far.
C
C
C
Okay,
so
maybe
there's
like
across
sea
working
group
sort
of
thing
here
right
where
it's
like
the
tooling
for
a
guy
machinery
and
the
tooling
for
fight,
though,
are
going
to
be
tightly
coupled
or
the
to
of
the
premium,
is
doing
that
coop
tooling,
for
the
CL
eyes
would
be
trying
to
come
up.
They
have
to
live
in
the
same
repo
and
then
I.