►
From YouTube: Kubernetes SIG Service Catalog 2018-04-16
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).
B
A
Hello:
everyone:
this
is
the
kubernetes
service,
catalog
sig
meeting.
We
post
a
link
to
our
agenda
for
anybody
who's
new
this
time
around
trying
to
see
if
we
have
new
people
yeah,
we
do
okay
cool,
so
the
ideas
that
we'll
walk
through,
if
you,
if
you
put
your
name
in
here,
so
that
we
know
who
all
attended.
That's
super
helpful
if
you
wanna
put
something
on
the
agenda
feel
free
to
type
in
and
just
slap
your
name
on
it.
So
we
know
who
wants
to
bring
up
what?
A
So
first
on
the
agenda
is
the
working
group
updates.
I
think
really
have
one
working
group
at
this
point,
and
hopefully
we
can
dissolve
it
soon.
So
obviously,
the
doc
working
group,
real
quick.
If
you
go
to
SVC
cat,
that
I
owe
you
can
see
the
whole
ripoff
of
the
kubernetes
website.
But
this
is
just
not
everything's
like
live,
but
it's
a
framework
for
us
to
start
tagging.
The
existing
markdown
files
that
we
have
and
then
having
them
sucked
into
this
website
and
looking
pretty
and
that
just
gives
a
spot
start
building
out
more
stuff.
A
So
if
you
click
on
like
say,
try
our
walkthrough,
that's
existing
content
that
we
already
had
that
you
know
just
throw
a
little
bit
of
a
frontmatter
on
and
then
it
all
looks
nice
and
it
looks
way
more
official
than
telling
people
to
read
a
markdown
file
and
get
help.
So
if
you
would
like
to
be
that
special
someone
to
give
it
that
second
looks
good
to
me,
the
agenda
has
a
link
to
the
pull
request
there.
A
B
Yeah
I
didn't
want
to
actually
do
it.
I
just
wanted
to
walk
either,
walk
through
that
the
agenda
document
and
either
you
know,
make
sure
we're
all
on
the
same
page
or
write
a
list
in
here
of
what
of
what
we
discovered
or
we
could
not
I.
Don't
know
I
just
wanted
to
it's
the
thing
that
we
immediately
had.
B
A
B
First
thing
that
we
discussed
was:
what
do
we
want
to
have
for
a
ga
release
and
part
of
that
was
figuring
out
two
things:
basically
what
I
want
in
it
and
then
when
do,
we
want
to
say
we're
releasing
it
as
well
as
the
sort
of
the
time
frame
that
we
can
say
that?
Yes,
these
are
the
final
GA
items
that
we
want
to
have
and
I
don't
know
if
that
was
in
here
somewhere.
A
Sorry
I
don't
mean
interrupt,
but
just
for
this
one
I
know
we
put
a
whole
bunch
of
stuff
in
this
dock,
but
it
may
be
helpful
to
maybe
start
updating
milestones
like
I.
Think
we,
everyone,
oh,
is
that
sound
good,
okay
I
can
take
that
as
an
action
mom
to
just
start
finding
those
years
ago
with
these
or
making
placeholder
ones
and
the
people
as
you're
hashing
on
this
can
comment
on
them
or
if
that's
a.
B
B
B
I
and
Doug
and
Jonathan
a
little
bit
discussed
the
sort
of
the
fact
that,
as
the
platform
we're
supposed
to
be
the
source
of
state
source
of
the
true
state,
and
yet
the
broker
can
can
really
be
the
source
of
true
state
and
that
keeping
those
things
in
sync
through
authentication
and
updates
is
difficult.
When
sort
of
the
are
back
comes
into
firms
in
the
show
and
that
the
layering
of
changes
needs
to
be
either.
B
You
know
they
have
to
have
a
cue
or
something,
and
the
big
thing
that
came
out
of
that
I
think
was
the
fact
that
we're
going
to
put
a
delete
flag
on
the
instance
and
the
broker
the
instance
and
the
binding
so
that,
instead
of
directly
issuing
to
delete
you
say,
okay,
go
delete
this
in
the
background,
and
then
we
can
undelete
it
if,
if
we're
rejected,
so
everything
can
fail
at
every
point
in
time,
and
that's
really,
we
have
to
work
around
all
that.
So
to
do
I
guess
lunch
is
in
there
twice.
B
B
Action
items,
sort
of
a
thing
and
I
mean
I
guess
since
IBM
is
interested
in
this
one
will
fly.
Take
that
one
at
some
point,
I,
don't
know
about
the
rollback
command.
If
there's
a
specific
person
who
wants
to
do
that
and
the
locking
flag,
we
already
have
a
PR
for
basically
I
think
and
it
probably
needs
to
be
updated
to
some
of
the
new
recent
changes
and
that
ends
that
topic
pretty
good,
Paul
and
Red,
Hat
and
I.
B
Think
it's
J
has
a
nice
health
checker
tool
that
seems
to
be
everybody
seems
to
once
they
finally
understood
it,
be
interested
in
bringing
that
open
and
we're
going
to
probably
merge
it
into
the
interest,
entry
and
I
guess
we
do
want
a
demo
of
the
thing,
but
I
don't
know
if
J's
ready
to
demo
it
today,
maybe
maybe
next
week
at
an
apple,
see
any
comments
on
that.
One.
D
B
B
B
B
'we
user
experience
for
first-time
users
and
possibly
combined
with
some
depending
on
how
v3
for
OS
b
goes.
It
might
be
more
more
achievable
or
more
easier
to
do
with
the
pram,
whereas
things
memorize
arguments
that
we
talked
about
this
for
a
lot,
but
there's
no
so
notes
in
here.
Carol
do
you
have
anything
you
would
like
to
add,
particularly
oh
I,.
B
B
B
A
B
B
A
A
Yeah
I
just
thought:
if
there
was
it's
hard
to
track
like
what
we're
even
trying
to
commit
to,
if
we
don't
have
at
least
something
to
reference,
you
know
and
editing
the
doc
can
get
a
little
awkward
cuz.
You
can't
always
tell
who
who
said
what
or
anything.
So
if
you're,
all
ok
with
that,
if
we
could
at
least
just
do
comments
or
arguing
about
if
something
should
be
in
or
out
or
negotiating
or
whatever
it
is.
However,
the
sausage
is
made
and
get
help.
A
Then
I
just
had
a
question
for
you
all
because
I'm
you
know
I'm
very
new
and
I,
don't
quite
know
how
the
proposal
stuff
works.
You
know
like
I,
got
some
feedback
on
the
proposal
and
I
can
keep
playing
with
it.
But
I'm
you
know
it's
getting
to
be
a
big
doc.
I
was
just
wondering
you
have
suggestions
for
like
what
would
be
a
good
next
step
for
us
to
do.
A
C
D
D
While
we're
waiting
for
that
I
guess,
I
can
I
can
give
a
little
background
within
RedHat.
We
have
a
multiple
deployments,
but
there
are
online
deployments.
We
have
a
central
Prometheus
monitoring
solution,
which
you
know
doesn't
monitoring
cache
metrics
all
that
stuff
and
we
also
generate
alerts
off
the
Atheist
alerts
framework
and
for
service
catalog.
We've
got
bare-bones
metrics
that
were
introduced
in
what
I
think
November
December
timeframe
and
actually
I've
been
meaning
to
talk
everybody
about
that.
For
some
time
we
don't
have
much
in
there
for
metrics
I'll.
D
Give
you
a
demo
of
what
we
do.
Have
it's
just
some
basic
counts
right
now
and
I
think
it'd
be
great
if
we
could
add
some
additional
metrics
as
we
get
moving
through
here.
You
know,
I,
don't
know
if
it
makes
sense
to
do
such
like
number
of
instances
that
are
in
an
error
state.
You
know
same
thing
for
bindings,
etc,
but
in
general
I
need
some
help.
Taking
a
look
at
metrics
and
exposing
more
metrics
where
I
was
headed
with
this
was
right
at
Red
Hat.
We
monitor
everything
with
Prometheus.
D
D
Stuff
we'd
have
a
end-to-end
job
that
runs
and
again
exposes
metrics
to
Prometheus,
so
Prometheus,
it's
out
there,
integration
metrics
from
various
components
and
you
can
go
to
do
alerts
and
whether
those
alerts
go
to
a
pager
or
go
dashboard
or
whatever
it's
all
pretty
flexible
and
very
generic.
If
you're,
all
just
exposing
that
file
Prometheus,
metrics
and
Morgan
you're
still
sharing
in
chance,
we
can
stop
sharing
that
and
I'll
share.
My
screen.
D
C
D
D
D
A
B
A
C
Ask
you,
as
it
is
I,
don't
think
it's
really
that
descriptive
to
be
honest,
but
I,
don't
know
get
out
of
your
Doug
I'm
sorry
I
mean
I'm,
alright,
to
be
honest,
I'm
already
bothered
that
we're
exposing
people
to
a
different
command
line
instead
of
coupe
control
at
least
servants
cat
is
a
little
bit
meaningful.
Whatever.
A
We
do
the
name
of
the
binary
would
be
the
same
as
the
name
of
the
plugin.
So
to
be
clear,
if
we
change
the
name-
oh
gosh,
no,
no,
not
Scott!
If
we,
if
we
take
the
name
of
the
binary
to
k80,
that
would
for
UX
perspective,
I
think
they
would
have
to
necessary
change
in
the
name
of
the
plug-in
so
be
cube.
Ctl
plug-in
Katie,
but
I
think
I
kind
of
read
a
dog
that,
like
it's
really
funny
and
I,
would
totally
love
to
do
it
just
from
that
perspective.
C
At
some
point
that
the
plug-in
infrastructure
will
fix
itself
and
we'll
stop
having
to
get
the
plug-in
name,
and
then
this
won't
be
an
issue,
and
people
can
just
use
qu
control,
get
services
or
you
know,
crate
binding
whatever
you
want
to
call
it
and
not
have
to
put
the
plug-in
name
in
there
at
all.
So
yeah.
A
Gosh
I
hope
so
I
feel,
like
I,
don't
know,
there's
still
hammering
out
6
Eli
what
they
want
to
do,
but
yeah
I
owe
them
an
experience
report
about
how
we've
been
making
the
plug-in,
because
I
think
we're
like
the
biggest
plug-in
honestly
for
kubernetes.
So
hopefully,
mostly
our
opinions
and
thoughts
may
carry
a
bit
more
weight,
so
I'm
gonna,
just
in
my
heart,
rename
it
to
Katie
unless
anyone
else
has
an
alias
it
to
that.
But
I
just
think
from
a
UX
perspective.