►
From YouTube: Kubernetes SIG Service Catalog 20180122
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
B
Thanks
everyone
thanks
Paul
we're
going
to
do
the
normal
Q
speaker,
Q
process.
I've
got
my
fancy
technology
equipment
as
usual.
For
those
who
don't
know
just
put
a
hand
up
in
the
chat,
not
like
the
spill
there
and
I'll
put
you
on
the
list,
I'll
a
queue
and
then
we'll
do
the
discussion
like
that,
and
with
that
we'll
start
with.
Did
someone
say
something
looks
good,
okay,.
B
D
Can
show
the
one
that
we
have
if
you
want
or
I
could
just
push
the
video
I
was
I
was
having
discussions
with
Doug
and
I
wanted
to
do
something
else
until
now,
otherwise
I
would
have
sent
it
out
the
email
already
so.
Okay.
A
B
A
A
B
D
I,
just
if,
if
it
sounds
like
Aaron,
it
sounds
like
you
have
people
who
actually
want
to
do
something
if
you
get
them
to
actually
I
would
like
to.
You
know
at
least
pretend
to
have
the
discussion
in
the
the
email.
So
we
can
like
say:
hey.
You
know
we're
trying
to
get
your
attention
so
that
you
can
actually
contribute
I,
don't
want
to
set
a
random
time
that
you
know
fine,
we
have
the
meeting
and
then
you
know,
half
of
us
can't
make
it
and
nobody
shows
up
who
benefits
from
the
meeting
time.
D
B
B
And
then
Paul
to
answer
your
question.
I
was
thinking
probably
having
a
regular
meeting
times
for
us
once
a
week
plus
a
second
one
once
every
three
weeks
to
accommodate
the
APAC
times,
and
that
was
to
keep
our
current
cadence
plus
either
having
a
summary
for
a
pack
people
or
to
obviously
solicit
their
feedback
without
requiring
them
to
wake
up
at
5:00
or
4:00
a.m.
yeah.
A
B
B
Cronuts:
okay
I'll
write
that
ái
for
myself
AI
air
to
write
proposal
and
Google
Groups
thread.
Okay,
next
up
is
J
with
some
o2
milestone
review.
You
want
to
go
ahead.
J
yeah.
E
Sure
so
we've
got
the
zero
to
zero
milestone
coming
up.
Next
I
did
a
review
of
the
face
to
face
action
items
we
had
from
November
and
there
were
a
bunch
of
that
was
a
tired
timeframe
with
Thanksgiving
and
then
Kristin
Thanksgiving
break
just
before
the
meeting,
and
then
you
know
start
of
December
and
Christmas
holiday
coming
up
a
lot
of
stuff.
E
We
had
good
notes
on
Doug
captured
some
great
minutes,
but
we
didn't
get
action
items
on
things,
so
I
ran
through
there
and
tried
to
make
sure
that
everything
was
captured
and
I
ended
up,
adding
a
bunch
of
things
today
and
I
believe
now
that
all
action
items
for
that
were
captured
and
I've
tagged
him
with
the
zero
to
zero
milestone.
But
we
got
about
thirty
seven
items
on
here
that
are
marked
for
zero
to
zero.
I
can
post
the
length
of
the
milestone.
What
should
I
go?
Look
at
there.
You
know,
okay,.
B
B
A
For
it,
so
I
think
it
would
be
really
cool.
If-
and
you
know
when
we
talk
about
these,
two
themes
like
if
folks
are
paying,
you
know
giving
some
thought
to
what
they
would
personally
like
to
work
on
and
I
think
it
would
be
awesome
if
we
could
kind
of
fan
out
the
the
the
actions.
You
know
capturing
proposals
that
we
can
talk
about
and
getting
consensus
on
things
like
individuals
that
have
an
interest
in
a
particular
thing
like
going
through
that
experience
and
getting
used
to
doing.
A
That
is
something
that
is
a
really
valuable
skill.
So
if
you
haven't
done
it
before,
like
it's
a
wonderful
time
to
start
right
now
doing
that
kind
of
thing
and
I
think
that
would
that
would
be
awesome
to
help.
You
know,
like
level
up
people
that
are
interested
in
in
doing
that
kind
of
thing,
and
also
make
sure
that
we
don't
like
have
hacked
a
single
thread
on
you
know
like
three
or
four
people
having
to
sort
it
all
out.
So
I
would
just
encourage
everybody
to
be
thinking
about
that.
E
A
E
B
I
put
my
hand
up,
so
what
I
would
suggest
here
is
we
put
a
time
box
on
this
and
then
do
the
rest?
A
synchronously,
so
I'll
propose
a
time
box
which
is
30
minutes,
so
we'd
be
done
at
45.
With
this
you
have
minutes
to
go
over
Morgan's
item
and
then
we've
got
Carolyn's
I
as
well.
So
well,
that's
my
suggestion
and
I
can
help
facilitate.
E
E
The
next
item
I
was
thinking
about.
We
ought
to
make
everyone
write,
not
everyone
that
each
maybe
we
get
one
person
from
each
company
to
volunteer
and
put
their
names
down
under
assignee.
This
item
get
duck,
write
your
support
for
zero
to
zero
documentation,
we're
going
to
see
if
we
get
professional
doc
writers
to
you
know,
or
at
least
get
the
companies
to
volunteer
some
time
from
doc
writers
and
get
some
help
with
pulling
the
docs
together.
E
E
E
A
small
working
group
and
determine
you
know
prioritize
what
to
do
here
or
break
this
out
individual
items
because
there's
just
there's
a
ton
of
items
on
here
and
if
we
have
anyone
that
wants
to
volunteer
to
lead
this
off
and
actually
why
don't?
We
come
back
to
it,
we'll
just
plan
on
running
through
the
zero
to
zero
items.
So
that's
certainly
a
big
one.
E
B
E
A
A
E
As
an
action
item
for
their
note
in
there
okay,
this
next
one
1604
is
API
surface,
which
service
plan,
their
brokers,
catalog,
have
covered
entities,
objects
created
for
them.
I
think
this
was
the
whitelist
and
blacklist
for
what
items
actually
gets
surfaced
out
of
a
service
catalog
out
of
a
broker.
Excuse
me-
and
we
don't
have
anyone
assigned
on
that.
So
it's
another
open
item.
E
E
14:34
there
should
be
an
etsy,
D
storage
path.
Test.
Matt
has
a
pull
request.
That's
outstanding!
That
I
think
closes
this
off,
but
last
I
saw
it
was
in
review
still
I,
don't
I,
don't
know
if
that
got
hung
up.
It's
probably
a
good
reminder
that
maybe
we
take
a
look
through
the
pleura.
Quite
outstanding
poll
requests
because
I
it
looks
to
me
like
it
was
done
and
probably
white,
not
a
little
final
review.
E
E
13:09
make
purge
generated,
make
target
friendly
two
expansions
there's
a
couple
items
that
are
could
clean
up
around
around
building
who
make
certainly
one
of
them.
Actually
this
mate
right,
there's
there's
a
work.
I
know
a
call
requested
outstanding
on
this.
One
again,
I
think
it's
standing
in
one
of
those
states
where
it's
looking
for
some
final
review.
D
D
E
D
B
E
A
I
added
that
one
I
think
that
was
like
something
I
added
while
I
was
like
brainstorming
I'm,
not
sure
that
we
need
to
do
that,
one
anymore,
because
we
have
the
CLI
that
can
give
us
a
good
experience
for
like
seeing
all
the
details
of
a
service
tied
together
like
that.
So
we
that
one
that
one
might
not
be
like
a
huge
deal
or
something
that
we
want
to
do
right
now
make
sense
to
me.
D
Also
need
to
keep
you
know
during
our
sort
of
API
views
and
whatever
that
you
know
the
API
doesn't
need
to
be
the
be-all
end-all
of
interaction.
You
know
it
just
needs
to
be
possible
to
get
the
information,
and
you
know
we
can.
We
can
wrap
a
client
around
it
so
anyway,
good
Daniels
continue.
Sorry
good.
E
E
E
F
E
Next
one
is
1198
what
should
happen
when
you
update
a
service
instance
credential
for
a
deleted
service
instance.
I
know,
we've
got
a
lot
of
work
around
cleaning
up
for
deletion
I,
don't
this
isn't
indicated
now
anyone's
no
one's
putting
notes
on
here,
so
I
guess
we'll
have
to
review
it
and
see
where
we
stand
with.
This
call
yet
notes
on
here
what
happens
when
you
tried
to
update
a
service
in
substantial
when
the
service
instance
is
deleted?
All
this
is
spec
lacks
updating
for
bindings,
but
update
also
comes
as
labeling.
E
A
Go
to
handle
not
yet
I
understand
from
talking
to
Derek
Carr,
who
is
like
the
owner
of
quota
at
least
historically
and
kubernetes
that
this
one
should
actually
be
very
easy,
with
the
caveat
that
what
what
you
have
to
do
is
basically
lifting
in
an
emission
controller
from
kubernetes.
So
I'm
not
sure,
if
there's
a
better
way
to
do
that,
but
the
the
generic
quota
is
already
there
in
kubernetes
for
us
to
use.
We
just
need
to
enforce
it.
E
E
D
E
E
E
A
E
G
B
A
E
E
A
B
E
E
B
B
H
D
E
A
I
E
E
B
I
E
D
A
E
B
D
It
was
that's
actually
a
lot
like
what
Jay
was
doing
so
I
think
we
can
do.
I
only
have
a
list
of
a
couple
of
things
to
talk
about
so
I'll
just
type
some
numbers
in
and
if
we
can
just
sort
of
continue
in
the
same
fashion
as
we
were
I
think
that's
the
most
effective
thing
it
shouldn't
take
more
than
a
couple
minutes
and
then
Caroline
he
go
first
is
778.
Oh,
did
you
know
this
was
a
pushing
a
build
image
thing.
Do
we
push
that
now
or
is
it
still
still
a
thing?
D
Oops,
okay:
next
is
three
I'll,
come
back
and
fix
that
three
3d,
three,
eight
nine,
three,
eight
nine
is
this
something
that
we
still
need
to
document.
This
is
the
SSL
strategy
for
I
assume
everything
also
besides
the
the
API
server.
But
everything
else
is
this:
taken
care
of
by
the
helm,
chart
and
Jen
CA,
or
is
this
something
that
we
need
to
either
document
or
point
to
the
the
upstream
documentation.
D
B
D
B
D
A
D
B
F
F
F
Okay,
we
kind
of
ran
into
weirdness
with
how
that
works,
and
what
I
was
trying
to
figure
out
was
is
the
bug
with
glog,
something
that
would
impact
someone
who
is
using
service
catalog
as
a
library,
because,
basically,
a
lot
of
these
come
down
to
like
we
can
make
a
reproducible
built
using
article
package
and
tamil
that
you
see
here
and
a
lock,
but
if
someone's
using
us
as
a
library,
Depp
treats
some
of
these
things
differently
and
people
would
end
up
with
a
different
revision.
So,
for
example,
easy
JSON.
F
We
had
a
specific
revision
pinned
go
open-open
api
swag
made
a
specific
revision
pins.
Those
are
in
the
lock.
If
you
do
a
build,
you'll
get
those
revisions.
But
if
someone
used
up,
for
example,
in
reference
service
catalog,
it's
not
guaranteed,
they
would
get
these
exact
revisions.
So
there's
workarounds
but
I
wasn't
sure
if
we
needed
those
workarounds
or
it's
the
looser
constraint
would
work.
A
F
When
you
run
DEP
ensure
inside
of
the
root
of
our
Service
Catalog
repository
DEP,
looks
at
go
package
tamil
and
go
packages
that
lock
and
it
basically
regenerates
exactly
what's
in
our
vendor,
we
check
in
vendor
anyway,
so
it
doesn't
really
matter
we're
gonna
get
the
versions
we
want.
That's
not
the
part
that
I'm
trying
to
bring
up
I'm,
trying
to
ask
that
if
someone
else
uses
Service
Catalog
as
a
library,
maybe
or
something
really
cool
that
we
did,
they
want
to
be
able
to
use
it
interact
with
like
generated
client
things
like
that.
F
A
F
For
the
ones
that
I've
commented,
transit
constraints
or
their
dependencies
of
service
catalogs
dependencies,
we
don't
directly
import
open,
API,
swag
or
easy
JSON
anywhere,
and
that
gives
us
honest
control
or
exact
origin.
In
that
case,
unless
we
do
something
to
kind
of
say,
we
really
need
to
to
pin
those
revisions,
god
well.
F
Get
everything
that's
in
the
tamil,
but
not
what's
in
the
lock.
So
if
you
look
at
the
lockers
explicit
revisions
and
things
like
that,
but
when
you
use
someone
as
a
library,
DEP
ignores
the
lock
and
just
goes
by
in
this
tamil
file,
so
they'll
get
at
CDE
3
to
13
they'll,
definitely
get
co-branding
s-191
things
like
that.
F
F
It
makes
it
easier
for
people
to
consume
you
as
a
library.
If
you
don't
heart,
pinned
revisions,
that's
all
because
if
they
rely
on
somebody
else,
who
also
relies
on
easy
JSON
and
we
both
have
conflicting
revisions
in
makes
people's
lives
difficult.
So
we
try
to
limit
that
in
general,
if
you
anticipate
being
used
as
a
library.
D
D
The
things
that
people
might
want
to
use
would
be
the
generated.
Clients
would
be
my
guess,
that's
that's
about
it
and
whatever
we
need
to
do
to
get
that
build
depends
on
all
the
API
machinery
stuff.
Now
we've
switched
from,
depending
on
directly
upstream
kubernetes
he's
the
giant
one
to
these
individual
libraries.
D
If
the
individual
libraries
have
a
constraint,
I
would
be
inclined
to
stick
with
that
constraint
because
you
know,
but
if
I
don't
see
how
the
client
would
have
any
dependencies
on
stuff
like
API
server
or
you
know,
the
API
machinery
type
stuff
beyond
client
go
and
beyond
I.
Think
it's
Cates
API
or
something
like
that,
and
so
I
don't
see
that
these
two
dependencies
specifically
need
to
be
tied
to
anything
for
the
client
to
work.
F
D
F
Yeah,
it
does
I
will
add
something
that
we'll
be
able
to
test
our
build
off
of
a
sample.
That,
like
would
be
a
representative
of
what
someone
who
is
consuming
our
library,
would
look
like
and
then
maybe
we
can
just
do
a
test
build
and
go
okay.
Does
that
work
and
then
just
check
that
during
our
build
so
that
we
know
if
we've
broken
someone
I
mean
bugs
are
bugs,
but
you
know
it
should
be
able
to
compile.
If
you
use
us
season
up
that.
B
Cool
so
I
had
a
quick
piece
there
to
add
a
little
bit
of
proof
to
what
you
said.
Morgan
I
recall
putting
this
swag
important
because
the
bill
was
failing
when
we
are
on
the
cou
1.7
code
base
before
we
were
checking
in
our
vendor
directory
and
obviously
after
we
had
checked
in
our
sorry
while
we
were
still
using
Glide,
obviously,
and
while
we
had
our
vendor
directory
checked
in,
but
we
were
doing
the
upgrade
to
1/7
so
I
highly
suspect.
This
is
not
an
issue
anymore,
as
Morgan
said
just
adding
on
to
that
point.
B
B
Well,
any
other
comments,
questions
anything
else
in
here
that
we
needed
to
talk
through
about
DEP,
going
once
all
right,
all
right,
any
other
business.
Anyone
wants
to
talk
about
today,
discussions
comments,
questions
going
once
all
right,
I
hereby
grant
you
six
more
minutes
today,
so
use
them
wisely
and
enjoy
the
rest
of
your
day.