►
From YouTube: Kubernetes SIG Service Catalog 20171018
Description
- Determine time/location for Raleigh F2F
- Discussion of ServiceInstance field names for selecting service/plan
A
You
know
all
right:
welcome
everybody
to
the
Wednesday
October
18th
2017,
medium
kubernetes,
6,
Service
Catalog.
We
have
recorded
after
five
minutes
on
recording
time.
I
assure
you
nothing
untoward
happened.
However.
We
have
decided
that
the
next
sig
will
be
in
Red
Hat
tower
NX
and
Raleigh
North
Carolina
on
Monday
November,
27th
2017.
There
will
be
a
meeting
request
sent
out
for
this
later
on
this
week,
so
I
think
Doug.
It's
you
now.
B
Okay,
I
pasted
a
link
to
the
poor
request.
1350
for
this
one
is
renaming
a
resource
or
a
set
of
properties.
I
should
say
inside
of
actually
one
site,
several
different
resources.
We
use
the
word
external
in
front
of
things
like
service
class,
name,
service
plan,
name
and
I.
Don't
think
that's
really
useful
to
end-users
because
they
really
don't
know
what
external
refers
to
most
people
probably
should
not
need
to
know
that.
B
To
put
the
word
external
in
front,
it
made
more
sense
to
try
to
actually
name
the
property
like
cluster
service
class
name,
to
be
the
same
name
as
the
property
within
the
the
service
class
itself,
and
so
after
going
back
and
forth
a
little
with
I
think
null.
We
kind
of
landed
on
the
word
clients
instead
of
external.
That
way,
it
doesn't
conflict
with
the
community's
quote
name,
but
it's
sort
of
by
using
the
word
client
sort
of
implies.
B
The
name
appears
like
that's
for
service
class,
name,
I'm,
sorry
for
search
plan,
name,
it's
now
server
this
plan,
client
name
or
cluster
in
this
case
in
front
of
it
anyway.
I
think
it's
a
big
discussion
about
what
we
wanted.
What
name
we
want
to
use
or
word
we
might
use
in
there.
So
Paul
your
hands
up.
B
A
Become
very
distracted
by
an
epic
failure
to
share
my
screen
properly.
I
wonder
why
you're
laughing
yeah
I
mean
I
thought
it
was
bad
and
then
Jessica
showed
me
when
she
had
on
her
screen,
and
it
was
worse
than
what
I
thought
was
bad.
So
sounds
like
a
really
good
story:
Doug,
don't
make
me
repeat
it
please!
So
here
is
it
my
own,
my
own
preference
I,
really
like
external
name,
because
I
think
it
is
the
right
amount
of
descriptive
that
it's
a
name
that
is
from
something
else.
B
B
B
Let's
put
this
thing
up:
first,
there's:
where
does
the
word
extra,
an
old
client
or
whatever
word
we
come
up
with?
Where
does
that
appear?
I
think
what
I'm
hearing
from
from
both
you
and
me
is
we'd
like
to
it
to
appear
not
at
the
beginning.
That
is
a
prefix
right.
We
want
it
to
appear
so
it
matches
the
property
named
clustering
front
right.
B
If
you
look
at
the
files,
the
very
first
change
so
there's
what
we're
talking
about
there
moves
the
wording,
question
to
be
you're
the
middle
and
it
matches
the
part.
The
real
property
name
right,
I
think
I,
think
Nell
pointed
that
out
and
it
makes
more
sense
because
I
am
used
to
defective
it.
The
proper
name
is
the
same
word
or
string.
That's
using
both
places.
So
then
the
real
question
is:
what
word
do
we
want
to
use
there
and
the
pot
like
I,
said
the
problem
I
had
with
the
word
external?
B
C
Are
you
saying
Doug,
sorry,
no
one's
hands
up
feel
I
go
for
it.
Okay,
sorry,
yeah,
so
I
think
what
you're
saying
is
that
the
external
could
imply
to
the
users
or
that
it
says
where
the
service
is
running
instead
of
the
fact
that
the
name
is
the
external
bit,
cuz
I
think
Bob
basically
says
this
is
nothing
to
do
with
kubernetes
names,
so
I
mean
the
obvious
name
would
be
non
Kate's
name.
C
B
D
So
I
like
something-something
client,
name
or
something
something
external
name
or
whatever
other
word,
I
like
it,
not
as
a
prefix
and
like
good
in
the
middle
as
far
as
external
versus
client
goes
I,
don't
think
either.
One
is
great.
I
don't
have
a
better
idea,
so
different
I
think
the
name
in
the
game
is
just
gonna,
be
we
have
to
document
what
it
really
means.
You
know
that
it's
a
human,
readable
name
otherwise
I
mean
external
client.
There.
You
could
make
the
argument
for
hours
over.
You
know
what
is
external
mean
to
a
user.
B
So
actually
I
think
you're
you're
on
a
very
good.
My
hands
up
next
I
think
you're
on
a
very
good
point
there.
It's
like
what
does
this
name
actually
represent
and
I
think
Aaron.
The
way
you
described
it
is
probably
a
fairly
good
description
of
it.
It's
the
human
readable
name,
if
not
really
meant
it
represents
location
right,
something
like
that.
B
I'm
the
person
I
be
okay
with
the
word
human,
although
I,
don't
think
that's
quite
the
right
phrase.
It
sound
a
little
bit
weird
client
was
the
next
best
thing
I.
Just
the
word
external,
though,
is
gonna
imply
other
meanings
other
than
what
we
think
we
intend,
which
I
think
is
with
you
described,
which
is
it's
just
a
human
friendly
name.
B
C
C
Okay,
no
I,
so
so
so
III
guess
what
I
would
like
is
I
grieve
it
there
and
in
the
sense
that
it's
just
all
of
these
are
kind
of
wonky.
We
should
also
go
ahead
and
and
choose
one
soon
so
that
we
can
ship
this
thing,
I
think
the
cost
of
of
choosing
a
not
so
terrible
name
is
not
the
worst
thing
ever
as
long
as
we
document
it.
A
It's
it's
a
name
that
is
given
to
us,
but
that
we
can't
use
right
now
or
that
we
might
not
use
I,
don't
know
I,
like
honestly,
I,
think
that
this
might
be
one
of
those
cases
where
it's
like
it's
it's
subjective
at
the
end,
and
there
are
probably
many
different
choices
that
would
be
equally
equally
terrible,
like
that
would
make
sense
to
some
people
and
other
people
think
this
is
really
bad.
The.
A
E
About
that,
though,
I
agree,
100%
with
Aaron
I
think,
ultimately,
it's
we're
not
gonna
have
a
perfect
name,
and
we
just
need
to
settle
on
something
I
do
like
it,
with
the
adjectives
being
closer
in
I
worry
about
client
name,
because
that
sounds
to
me
like
the
name
of
a
client,
as
like
external
name,
sounds
like
it's.
The
external
name
of
something
client
name
sounds
like
its
clients
name,
so
I
think.
There's
just
ambiguity
there,
so
I
perfect,
personally
preferred
external
or
maybe
alias.
B
C
B
B
B
B
B
D
B
D
D
We've
got
cluster
service
class,
external
nikuman
cluster
service
class,
alias
and
same
thing
for
cluster
service
plan.
Those
will
be
the
two
options.
Anyone
disagree
want
to
add
other
options
going
once
all
right,
so
all
those
in
favor
for
the
first
one
cluster
service
class
external
name.
Please
put
a
plus
vote
into
the
chat
right
now.
That
was
not
me
voting
for
it
by
the
way,
one
for
external
two
for
external
three
for
four
external
five
or
external,
going
once
anybody
else
for
external
name.
D
C
D
B
D
A
C
I,
don't
know
if
there's
others
I
was
just
going
through
the
code
for
some
other
reason,
I
saw
then
I
was
like
oh
crap.
We
should
probably
at
least
take
up.
I
mean
it's
easy
enough
to
grab
through
to
dues,
but
I
don't
know
if
there's
anything
else
in
the
types
that
we
should
basically
change,
but
this
one
is
gonna
be
exposed.
So
I
would
say
that
we
yank
it
before
we
shipped
beta
one
I.
A
A
A
A
A
Although
we'll
talk
about
that
one
later
so
Service
Catalog
API
server
needs
to
return
proper
values.
For
our
version
end
point,
we
originally
thought
this
could
be
a
1.0
thing.
Apparently
it
is
super
important
to
a
Red,
Hat
QE,
so
Jeff
peelers
working
on
this.
Now,
it's
like
like
incredibly
important
for
us
for
this
one
to
go
into
Oh
dot,
100,
but
just
working
on
it
at
the
moment.
A
D
D
C
D
So
I
I
just
finished
doing
this
for
another
repo.
Basically,
I
did
it.
The
same
way
is
communities
charts,
basically,
the
upstream
charts
repo.
Does
it
and
I
believe
I
can
get
a
I
can
get
Microsoft
to
donate
blob
storage.
For
this
we
can
use
GCS.
If
someone
disagrees
with
that,
I,
don't
care
honestly
bottom
line,
though
it's
not
that
hard
I'm
happy
to
do
it
if
they
want
stood
or
think,
doesn't
want
to
do
it
or
can't
or
whatever.
A
A
A
new
instance
I
broke
this
1420
out
of
this,
so
there's
another
one
which
what
I'm
curious
about
is
if
people
think,
since
this
is
like
the
last
remaining
piece
of
801,
if
we
should
break
it
into
its
own,
which
is
that
we
need
to
have
a
reconciler
loop,
that
when
a
service
class
or
plan
that's
been
removed
from
the
a
log,
has
zero
instances
of
it
left
that
that
we
need
to
delete
it
out.
We
need
to
delete
them
resource
for
that
thing.
I've
got
it
in
progress.