►
From YouTube: Kubernetes SIG Service Catalog 2018-01-29
Description
- solicit participation in kubecon eu intro or deep dive
- publishing svcat
- installing svcat
- restart weekly release cadence and decide to release on Wednesdays
A
Yet
do
it
alright,
it
should
be
started
all
right
cool.
Thank
you.
Morgan
all
right!
Welcome
everybody
to
the
what
is
it
January
29th
version
of
the
it
was
catalogues
sig
meeting
today,
let's
see
already
at
the
recording
started
it,
so
we
can
erase
that
so
small
agenda
today,
but
let's
go
to
put
into
it
so
at
the
coupe
con
Benton
EU.
A
A
So
anyway
we
were
thinking
of
doing
was
offering
it
up
to
you
guys
see
if
there's
somebody
on
the
COG
would
like
the
volunteer,
be
part
of
the
group
is
going
to
be
presenting
this
I
think
you're,
maybe
two
or
three
people
max
might
be
good
for
AMS
session.
Maybe
two
I
don't
know,
but
it's
up
to
you
guys
anyway.
Let
me
sort
of
pause
there
and
see
if
there's
an
interest
from
you
guys
on
the
call
to
sign
up
for
this
thing.
B
B
We
definitely
had
that
was
deaf
for
those
sessions
and
the
last
cube
thing
we're
definitely
worthwhile
for
people
attending
I,
don't
mind
doing
like
the
API
server
stuff,
but
I
don't
know
a
lot
about
the
internals
of
the
controller
beyond
you
know,
interacting
with
it
and
that
it
uses
the
client.
So,
okay,.
A
A
We
were
thinking
of
a
brief
intro
into
the
open
service
broker
API
and
then
a
deep
dive
into
the
Service
Catalog
work
with
the
hopes
of
presenting
it
to
people,
so
they
can
sort
of
jump,
start
their
education
and
possibly
even
learn
more
about
what
we're
doing
so
that
they
can
contribute
code
itself.
It's
not
meant
to
be
just
a
high-level
here's
how
you
use
it,
but
rather
what
we
did
under
the
covers.
A
So,
as
I
mentioned
earlier,
some
of
the
things
like
you
know
the
trailblazing
stuff
we
did
relative
to
avi
or
Gatien
that
kind
of
stuff
or
some
of
the
things
we
had
to
make
tough
choices
on
like,
for
example,
the
naming
scheme
history
age
doesn't
allow
you
to
change
name
stuff
like
that.
We're
looking
for
some
volunteers,
really
hoping
to
get
non
cig
leads
to
do
this
presentation,
so
Morgan
has
volunteered
to
be
part
of
the
organisms
part
of
the
group
doing
this.
A
A
Want
to
pee
I,
don't
want
to
put
you
guys
to
it
so
well.
Actually
we
don't
have
too
much
time
because
they
yeah
if
you're
gonna
do
it.
We
need
to
reserve
a
room
by
tomorrow,
so
I
do
need
to
know
relatively
quickly
so
I'll
ping,
some
people
offline,
who
I
thought,
might
be
good
candidates,
both
Bulls
I,
don't
want
to
embarrass
you
guys
or
put
you
on
the
spot
on
the
phone
here
so
we'll
play
it
by
ear.
Okay,
all
right!
Moving
on
Morgan!
The
next
issue
is
yours:
we're
at
a
publish
service
cap.
B
B
I'm,
not
sure
what
the
suggestion
is
for
how
to
do
that
other
than
you
know.
We
can
copy
I,
guess
this,
and
then
we
need
to
have
the
the
azure
clients,
whatever
that
is
configured
and
in
the
build,
and
then
we
don't
publish
anything
to
releases
I,
don't
think
any
any.
Do
we
I,
don't
recall,
but
I
do
know.
We
publish
images,
so
I
just
wanted
to
raise
this
for
Carolyn
and
solicit
opinions
and
move
on
pretty
quickly.
If
we
don't
feel
like
we're
making
progress,
that's
all
right.
A
So
I
know,
since
you
mentioned,
are
the
releases
that
I
know
be.
As
you
said,
we
don't
actually
use
the
releases
feature
of
github.
I
was
wondering
whether
that
would
make
sense
to
use
here.
I
know,
I
mean
I'm
use
it
in
the
past.
For
other
things
like
tar,
balls
and
stuff
I,
don't
know
how
convenient
it
is
for
executables,
though
that's
my
reason,
I'm
a
little,
hesitant
I
guess
all
we
do
have
assets
yeah.
B
A
B
D
A
D
A
If
you
look
at
the
thank
you
for
look
at
some
of
the
test
cases
or
the
setup
of
the
test
cases,
you
could
see
how
it's
how
it's
done
and
in
fact
you
can
even
get
more
advanced
and
like
mounts
some
of
your
file
system
into
the
container.
So
we
can
have
access
to
local
files
stuff
like
that,
it
is
possible
to
do
it
just
check
the
shell
scripts
in
there.
A
E
Is
it?
Is
it
weird
that
we
wouldn't
have
all
the
binaries
or
the
binders
you
gonna,
be
in
different
spots
or
I
mean
I
realize
that
I
guess
currently
the
service
catalog
is
what
it's
a
downloadable
docker
image
right,
yeah
yeah,
maybe
maybe
it
makes
sense?
Maybe
it's
maybe
it's
good
idea.
I
just
think
it.
You
know
where
we're
putting
service
catalog
binary,
where
there's
no
other
presently
know
where
the
binaries
but
I
guess
they're
already
going
to
be
separated
because
of
the
way
they're
distributed
so
I.
Guess
it's
fine
I,
don't
yeah.
A
So
it
seems
to
me
if
we
create
two
different
versions:
one
is
a
docker
image,
so
people
could
use
it
the
same
way,
so
they
could
run
it
through
docker
they
wanted
to.
But
then,
if
we
make
the
executables
and
stand-alones
available
through
the
release
process
as
well
at
least
there's
a
consistent
spot
to
download
it.
D
D
D
A
D
So
assuming
you
get
the
binary
somehow
now,
if
for
those
of
you
who
were
here
when
I
demoed,
my
previous
plugins,
those
required
you
to
download
and
stick
them
in
the
right
place
manually,
and
they
were
two
parts
that
was
the
actual
plug-in
binary
and
there
was
the
accompanying
Amal
file
that
was
like
showed
coop
CTL
how
to
use
it
so
for
the
new
SP
cat
Carolyn
has
done
some
work
to
make
it
have
a
self
installation
process.
So
here,
I
have
luckily
I
have
a
compiled
binary
for
SV
cat.
D
So
yeah
not
really
much
to
see,
but
what
that's
doing
is.
Is
it's
extract?
It's
copying
itself
into
that
directory
and
it's
extracting
it's
the
plug-in
ham
and
while
we
have
it
in
the
code
in
the
source,
so
it
can
just
deposit
that
right
there.
So
then,
when
I
go
into
CTL,
it's
available
for
use
as
a
plug-in
and
then
just
it's
once
I'm
there,
it's
the
same
thing
as
the
standard
load
version.
Well,
assuming
you
can
get
the
binary
to
the
user.
It's
easier
to
install
now.
A
D
D
D
A
A
On
the
agenda
Morgan,
you
crossed
this
one
out
so
I'm
assuming
we
can
skip
it,
but
you
do
have
the
next
one
after
that,
squashing
makes
you
sad.
Would
you
care
to
talk
about
that?
One
you
I'm,
sorry,
is
it
presenting
again
yeah?
Did
you
want
to
defer
this
one
to
next
week
is
realize
you
said
defer
next
week
you
want
to
skip
this
one
or
not
yeah.
A
A
E
We
needed
to
refund
her
into
open
shifts
so,
and
we
won
pick
up
some
changes
that
Paul
got
this
weekend.
It
was
an
API
change
on
a
rename
and
just
kind
of
guys,
the
guys,
the
point
that
we
should
probably
be
vending
on
a
not
been
during
but
released
on
a
regular
cadence
again
right
was
there
I,
don't
don't
think,
there's
a
reason
we
stopped
in
December
yeah.
A
C
A
E
A
Actually,
if
you
actually
be
great,
if
you
did
it
there,
there
is
a
wiki
page
that
describes
it.
It's
fairly
well
documented
and
fairly
straightforward.
First
time,
I
went
through
it
was
amazingly
simple:
I
was
I,
was
very
impressed
with
the
docket
in
the
air
and
put
together
so
yeah.
If
you
wanted,
if
you
want
to
go
for
it,
go
ahead
and
do
it
but
hold
on
a
sec,
kibbles
your
hands
up,
yeah.
F
Well,
I
was
gonna,
say
mostly
what
you
just
said
and
also
was
gonna
ask:
do
we
want
to
so
the
doc
says
that
we
do
it
every
Friday
and
last
time
I
was
gonna,
do
it
on
Friday
and
people
were
like?
Oh
maybe
we
should
do
Monday
instead,
because
just
so
you
don't
have
to
deal
with
issues
and
stuff
late
in
the
week.
So
do
we
want
to
change
our
release
like
day?
We
could
just
do
Mondays
and
then
cut
it.
B
C
A
C
F
A
I,
don't
think
we
want
to
encourage
Fridays,
obviously
to
AP's
from
what
I
heard
so
I
like
to
make
him
behave
even
more
formal
and
say:
let's
go
back
to
a
Wednesday
cadence,
but
leave
it
up
to
Jay
decide
whether
he
wants
to
wait
till
Wednesday
or
do
it
sooner
based
upon
their
needs,
since
he
expressed
need
for
getting
something
out.
Paul's
recent
changes.
A
A
D
A
I'm
sorry,
coop
Khan,
what
I
say:
Decker
come
yeah,
it's
all
the
same.
If
you're
planning
going
to
coop,
Khan
and
you're
a
part
of
the
education
deep
dive
session,
please
let
me
know
I
do
need
to
let
Dan
Khan
know
I
believe
it's
by
tomorrow,
and
my
hope
is
that
we
grab
an
80-minute
session
or
maybe
it's
a
to
five-minute
session.