►
From YouTube: Kubernetes SIG Service Catalog 2018-09-17
Description
Agenda: https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM
A
It
looks
like
it's
just
the
four
of
us
great
kick
things
off.
First,
the
steering
committee
or
the
release
team
I
forget
who
reached
out
to
us
and
said:
do
we
have
anything
we
want
to
mention
this
part
of
the
1.12
release,
notes
and
I
was
talking
to
Paul.
Like
you
know,
what
are
we
supposed
to
say
about
this,
and
the
consensus
is
that
if
we've
had
major
things,
make
it
into
Service
Catalog
since
one
9/11,
we
can
call
it
out
and
use
this,
that's
just
a
way
to
get
more
eyes
and
people
up-to-date.
A
B
A
A
A
Nope
cool
I
wanted
to
do
a
demo
of
a
feature:
that's
turned
off
by
default,
but
I'll
be
working
on
more
and
I
wanted
to
show
people
because
I
think
it's
kind
of
cool
I.
Don't
if
you
remember
from
like
to
face
two
faces
ago,
we
were
talking
about
how
to
be
able
to
provide
default
provisioning
values
on
stored
on
servers
plans.
So
I
wanted
to
pull
this
up
and
sure.
A
A
A
I'll,
send
a
link
to
the
doc
in
just
a
sec
on
how
to
do
that.
It's
in
the
home
term
how
you
convert
it
on,
but
what
this
does
is
when
I
provision
a
new
service
instance
of
this
plan,
if
I
don't
set
any
parameters
or
no
I
can
choose
to
set
parameters
or
not,
but
if
I
don't
actually
set
a
value
for,
say,
secure
right
here,
I'll
get
it
automatically.
So
if
I
do
I
supervision,
ponies.
B
A
One
of
the
very
first
milestones
was
be
able
to
create
a
custom
class
or
plan
okay,
and
we
made
really
significant
progress
on
that
and
then
the
next
step
was
be
able
to
set
this
on
a
class
or
plan
and
have
it
actually
go
through
to
provision
and
then
one
of
the
later
steps
was
going
to
be.
Brokers
should
be
able
to
provide
hints
for
default,
Peruvian
params,
but
that's
where
I
got
super
murky,
because
we
didn't
really
have
a
concrete
plan
for
how
oh
s
be.
A
Api
should
be
communicating
that
Service
Catalog,
so
that
kind
of
petered
out,
and
it's
like
something
we
were
going
to
try
to
talk
about
later:
okay,
yeah,
so
I
provisioned
an
instance
of
this,
my
sequel
plan
and
called
it
ponies.
This
is
a
UI
problem
that
Jonathan
called
out
so
just
know.
We're
gonna
fix
it,
because
there
were
no
immediate
parameters
specified
it's
not
that
going
back,
but
if
I
do
it
described
now
on
the
instance
ponies
so.
C
I
wanted
to
comment
about
that.
You
know
if
we
wanted
to
populate
that
with
the
default
parameters
as
defined
in
the
server-side
object,
we
would
have
to
issue
a
get
request
to
the
kubernetes
in
order
to
find
out.
If
there
are
any
I,
don't
know
if
that's
necessarily
the
best
decision
like
I,
might
just
change
that
Ruby
age.
So
it
said,
like
you,
didn't
specify
any
parameters
like
no
parameters
provided
on
command
line
or
something
like
that.
A
What
idea
is
we
don't
have
to
echo
everything
back?
You
know
what
I
mean
I
like
cube
CTO,
for
example,
just
created
instance
ponies,
because
so
the
describe
isn't
going
to
happen
immediately.
It
takes
has
to
be
like
resolved
and
by
the
prime
time
its
provision
it'll
be
set,
so
in
an
epic
demo
fail.
This
is
normally
what
it
looks
like
I'm,
not
sure
why
my
machine
is
all
messed
up.
C
A
Yeah,
that's
that's
what
I'm
saying
like
it's
gonna
take
time
for
it
to
get
resolves
because
it
happens
on
the
server
side,
so
yeah.
We
could
change
this
to
be
like
no
parameters
set
on
the
instance
or
like
some.
We
could
simplify
this
and
just
show
like
what
keeps
ECL,
which
Oh,
which
is
created
instance,
my
tv5
and
dot,
try
to
print
all
this
other
stuff
out
yet
I
don't
know.
A
A
A
A
It's
not,
but
you
notice
it's
showing
up
here
the
defaults
and
the
idea
is
that
they
get
merged
together.
So
if
you
see
a
final
set
of
parameters
here,
it
had
like
6
things
and
you're
like
what
came
from
class.
It
would
have
shown
up
here
in
the
status,
but
I
have
to
figure
out
what
I
screwed
up
on
my
machine
cuz.
Obviously
this
didn't
work.
Okay,.
B
A
The
ideas
that
the
defaults
are
just
that
defaults
and
then
whatever
you
specified
on
the
instance,
are
basically
overrides.
So
if
I
had
provisioned
this
instance
and
set
secure
equals
to
false
that's
what
would
have
been
used
if
I
had
provisioned
this
and
said
color
blue
it
would
the
final
parameters
would
be
blue
and
secure
is
true
and
if
I
said
nothing
I'll
just
get
secure
is
true.
I'll,
try
to
repeat
this
demo
next
week.
Sorry
I.
B
A
A
It
allows
you
to
get
all
it's
like,
for
example,
firewall,
filtering
rules
or
things
like
that.
They
need
to
open
up
between
to
be
nuts
or
something
like
that,
while
still
allowing
somebody
to
say
customize,
the
name
of
database
or
I'm,
not
quite
sure
what
you
want
to
customize
and
not
lose
the
value
of
all
those
defaults,
so
they
do
get
merged
in
together.
Yeah.
B
A
Yeah
they
are
stored
on
the
instance,
so
during
the
reconciliation
loop
for
figuring
out
what
the
plan
is
before
you
provision
immediately
after
you
resolve
the
class
in
the
plan,
it
resolves
the
default
parameters,
those
parameters
on
the
status
and
actually
applies
them
to
the
instance.
The
fact
that
this
is
empty,
it's
just
something
screwy
on
my
environment,
I'm.
B
A
Yeah,
because
otherwise
you're
gonna
have
a
permanent
connection
between
the
plan
and
the
instance
and
the
defaults
on
that
plan
and
changing
them
would
would
require
redoing
the
instance
which
isn't
actually
something
that
happens.
I
know
and
service
got
along,
so
this
fits
kind
of
with
the
reconciliation
loop
and
how
we
interact
with
the
broker.
B
Because
there's
something
to
be
said
for
four
things,
not
changing
under
you,
which
is
what
you're
doing
right
here,
which
is
good,
then
there's
also
the
thing
that
says:
well:
yeah
I'm
not
gonna,
nicely
force
all
my
instances
to
get
updated
in
some
way.
However,
if
something
does
cause
them
to
get
recycled
like
they're
an
update
happens
gee.
They
really
should
start
using
as
new
defaults.
It
I
could
see
a
little
bit
of
both
so
interesting
yeah.
A
Yeah
I
drop
me
from
wrong
inserts
catalog,
if
you
say
relist
in
a
plan
or
a
class
is,
is
modified.
Service
Catalog
doesn't
do
anything
to
the
instances
and
bindings
right,
true,
okay,
yeah,
but
it
is
an
interesting
scenario.
It
would
allow
for
more
easier,
like
management
at
the
operator
level,
without
having
to
flex
around
with
everyone's
instances.
Yeah.
B
A
A
C
Does
this
work?
Okay,
so
I
want
to
talk
about
SP,
can't
register
D
register
so
currently,
today,
right
now,
they
support
the
registration
of
the
registration
of
cluster
service
brokers.
Now,
with
the
addition
of
names
based
brokers
and
then
being
the
default
like
sort
of
way,
we
envisioned
the
average
user
using
this
I
believe
Kalyan
and
I.
C
We
had
a
discussion
that
we
wanted
to
make
name
space
brokers,
the
default,
so
when
I
say
SP,
CAD
deregister
its
broker,
it's
assuming
I'm
talking
about
name
space
brokers,
but
I
just
wanted
to
ask
around
because
I'm
at
the
point
where
I'm
actually
an
implement.
This
are
we
still
set
on
that?
Is
that
what
we
think
makes
the
most
sense,
I.
A
Think
for
me,
the
reason
why
I
suggested
that
in
the
first
place
was
that
it
follows
the
behavior
that
we're
using
for
like
say,
referencing
the
name
space
implicitly.
Like
so
say
you
execute
a
SP
cat
or
a
Q
CTL
command
name.
Space
is
kind
of
always
there,
even
if
you
didn't
specify
it
because
it
could
be
coming
from
the
cube
config
right.
So
you
have
this
ambient
name
space
at
all
times.
Well,.
C
I
was
thinking
it
was
Morse
cuz,
the
average
user
can
do
these
things,
whereas
cluster
service
brokers
require
admin
privileges.
So
it's
likely
that
they're
gonna
get
a
lot
more
use
out
of
being
able.
You
know,
without
having
to
type
thanks
for
stuff.
Anyways
implement
I
wanted
to
go
over
what
I
envisioned
this.
These
commands,
looking
like
yeah.
B
C
C
Now,
if
I
was
going
to
make
this
the
namespace
broker,
I
guess
I
could
implicitly
get
the
namespace
out
of
your
context
and
I
have
an
optional
flag
to
specify
your
namespace
than
is.
How
do
we
want
to
retrofit
the
cluster
service
broker
functionality
back
into
this
Kamali
it'd
be
cluster,
so
it
would
just
be
a
binary
flag.
Yeah.
C
C
The
other
thing
is
I,
I
can't
imagine.
Even
if
people
are
scripting
using
s,
you
can't
really
script.
This
particular
bit
of
functionality,
because
I
feel
like
register
and
read
register
is
like
something
an
actual
person
does
like
I.
Don't
think
they
like
automatically
have
a
script
that
like
periodically
D
registers
and
your
registers,
their
brokers
like
that,
isn't
no.
B
A
I
mean
it's
kind
of
weird
in
general,
because
every
time
you
commit
something
to
master
4sv
cat
like
there's,
no
feature
flags
or
anything
like
that.
It
just
goes
in
and
then
the
next
time
you
cut
a
release,
it's
in
there,
so
like
register
and
deregister
fairly
recent
commands.
So
we
you
know,
we
implemented
them
in
an
iterative
fashion
and
just
did
it
for
cluster,
because
that's
what
was
available
at
the
time
and
now
that
brokers
is
like
fully
enabled
we're
going
back
and
fixing
the
commands
to
match
that
I.
A
I
think
once
we
get
one
oh,
this
is
gonna,
be
more
important
to
us
because,
like
I
said
just
it
there's
this
conflict
between
incremental
development,
which
is
what
we've
normally
favored
with
a
big
bang.
As
soon
as
it
hits
master,
it's
gonna
be
released,
and
then
we
can't
break
it
so
with
an
environment
variable
to
let
us
basically
do
our
feature
gating
like
we
do
with
our
home.
Yes,.
B
C
A
C
A
C
C
A
A
Jimmy
did
that
like
four
months
ago
and
I
wanted
just
help,
get
that
push
through
for
him.
So
if
anyone
has
time,
that'd
be
really
helpful
to
give
us
final
lgt
m
and
then
the
other
one
is
not
huge.
I,
don't
really
need
to
beg
for
it,
but
I
want
people
to
be
aware
of
it.
I
added
a
script
that
makes
it
really
easy
to
deploy
to
your
local
cluster,
a
canary
build
of
the
controller
and
the
API
server,
and
so
this
is
the
dock
for
it
and
a
little
script
to
go
with
it.
A
So
people
are
like
working
on
features
and
you
have
your
own
magic
script,
I'd
love
to
like
combine
forces,
and
otherwise
this
is
my
magic
script.
I
just
wanted
everyone
else
to
use,
because
otherwise
it's
kind
of
awkward.
You
have
to
push
an
image
to
a
registry
somewhere,
you
can't
be
named
the
normal
name
that
we
use
for
all
of
our
bills.
You
have
to
be
overriding
values
and
there's
just
kind
of
a
bit
of
a
dance
you
have
to
do
and
if
you
use
helmets
even
more
complicated,
so.
A
A
I'll
take
everyone's
silence
and
head-shaking
as
yeah.
We
can
finish
early
so
thanks
everyone
for
your
time
really
appreciate.
It
have
a
good
one.