►
From YouTube: Kubernetes SIG Service Catalog 2019-06-03
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
Okay,
we
are
recording
hello,
everyone
and
welcome
to
the
June
3rd
edition
of
cigs
service
catalog.
It
looks
like
we
have
some
new
faces
here,
so
how
about
we
go
around
the
table
and
introduce
ourselves
I'll
start
off.
I'm
Jonathan
Brooklyn
I
work
for
IBM.
Most
of
you
pretty
much
already
know
me.
I'm
the
remaining
chair,
I
work
on
Service
Catalog
all
day.
That's
what
I
do.
B
E
A
A
Trying
to
remember
what
you
have
to
do
to
get
access
to
the
stock:
it's
not
publicly
accessible!
You
have
to
join
the
Service
Catalog
google
group,
which
you
should
be
able
to
find
by
googling,
but
I
think
that's
what
you
have
to
do
in
order
to
be
able
to
edit
this
once
you
sign
up
for
that.
You
here
forever!
So
really
it's
a
trick.
Okay,
so
I'm
just
thinking
on
the
list,
and
then
we
can
feel
free
to
talk
about
stuff
later
so
first
step
0
to
1.
A
So
like
I
told
some
of
us
at
cube,
con
I
broke
the
corrosion
command
and
the
CLI
when
we
cut
0
to
0.
So
that's
the
major
impetus
on
when
you
get
zero
to
line
out
it's
a
couple.
Other
thing
I
want
to
merge
first,
so
I'm
hoping
to
get
that
done
today.
So
just
you
worry
more
organizational
stuff
future!
Okay.
A
F
E
E
A
D
A
A
If
I
can
remember
where
I
did
this,
so
the
thing
you
actually
want,
and
membership
and
kubernetes
incubator,
which
you
should
be
able
to
submit
a
PR
phone
now
now
that
you're,
a
member
of
kubernetes,
you
should
just
be
able
to
open
up
yar
like
I,
did
here
and
add
yourself
to
this
file,
not
a
number
one.
So
this
is.
This
is
what
you
actually
want.
Now
he
remembers
varieties
and.
F
A
Who
no
longer
work
on
Service
Catalog?
Oh
yeah,
that's
my
next
step.
I
could
do
that
and
then
once
that's
done,
I
can
send
another
PR
or
request
I
supposed
to
actually
publicly
and
then
that
should
happen,
but
I'm
expecting
that
to
break
everything.
So
I
want
to
cut
0
to
1
before
I
move
the
repository,
because
I
have
got
a
release
for
a
while.
A
A
Yeah
X
build
test
Lakes,
so
I
don't
know
if
people
have
been
paying
attention,
but
at
the
end
of
last
week
we
were
having
hello
flakes
in
our
pipeline,
specifically
on
the
X,
build
thing
and
I
really
couldn't
figure
out.
Why
I
don't
know
some
of
these
are
actual
failures.
People
need
to
fix
their
tests.
Let
me
see
if
I
can
find
one
that
was.
A
So
I
took
a
look
into
it
and
it
seemed
like
there
was
two
instances
or
two
things
that
were
causing
the
test
to
fail.
Some
of
them
were,
it
was
just
timing
out
and,
like
that's
a
flake,
obviously
I,
don't
really
know
what
we
can
do
to
fix
that
and
then
some
of
them
were
it
looked
like
it
was
an
actual
error.
A
A
F
And
basically,
it's
constantly
failing,
because
on
our
on
my
pro
request,
I
will
just
retest
that
and
it
passed.
So
the
question
is
because
in
previous
week
there
was
also
a
lot
of
issues
on
the
views
from
different.
It's
all
right
under
the
acquaintances
organization.
I
know
they
had
some
problems
with
infrastructure,
so
maybe
somehow
connected
yeah.
A
We're
talking
about
doing
some
things
like
format
error
when
it
tries
to
what
is
it
doing
it's
trying
to
be
picky,
it's
trying
to
update
stuff
on
the
mend
itself,
but
like
when
I
run
this
this
locally
I.
It
never
fails
like
I,
haven't
gotten
it
to
fail
locally
at
all,
and
I
ran
a
bunch
of
times
so
like.
F
A
F
That
it
could
be
somehow
connected
what
so
VD
downtime
on
the
infrastructure
layer
under
the
current
ID.
So
because
I
know
that
they're
just
under
the
seek
testing
channel,
they
just
discussed
something
like
that
before
releasing
the
new
version
of
the
apprentice
1.15.
So
maybe
it's
somehow
connected
you
can
just
try
to
retest
that
and
observe
that
ability
it's
still
finding
or
not.
A
Okay,
I
don't
understand
how
they
could
have
some
sort
of
test
researcher
adage
that
would
cause
us
to
fail
like
this,
like
I
mean
not
run
sure.
Maybe
the
time
out.
Can
you
do
that,
but
I
don't
see
how
this
execs
lot?
My
error
could
be
that,
but
okay,
we
can
see
it
was
right.
It
was
kept
failing.
We
can
take
this
again
and
see
if
things
are
better
this
week,
mm-hmm.
A
C
D
A
A
E
Try
to
do
the
trash
somehow
across
the
the
tickets,
because
we
we
saw
that
both
already
start
to
do
closing
stuff
about
the
tickets,
but
at
first
I
think
we
need
to
clarify
that
thing
with
prowl
and
then
we
can
focus
on
that
custom
resource
definitions
right
as
the
as
a
first-class
citizen
for
that
project.
But
first
we
need
to
have
a
new
structure
right
and
that's.
The
task
will
be
on
your
right.
E
A
Just
for
the
identification
of
Sam
and
Ed
and
Florian
so
right
before
could
common
cut
a
major
feature:
release
their
2-0
with
GA
based
resources.
So
this
is
0-3
serious.
This
is
the
stuff
we
plan
on
doing
in
the
future,
like
I
said,
there's
a
lot
of
infrastructure
work
that
has
to
happen
before
we
get
started
on
this,
but
the
major
thing
is
we're
going
to
be
transitions.
You
know
these.
A
The
SAPT
mo
guys
have
already
done
most
of
the
work
for
that
they
have
a
branch
up
that
already
contains
the
code,
but
there's
a
lot
of
footwork
I,
guess
that
we
have
to
do
before.
We
can
actually
merge
it,
especially
because
we
have
to
support
API
servers
for
nine
months
past
release
to
see
IDs.
So
that's
the
majority
of
what
zero
three
zero
is
going
to
be
is
going
to
be
the
infrastructure
work
to
allow
that
to
happen
and
then
finally
merging
to
see
IDs
themselves.
B
So
just
to
clarify
so
zero
three
see
there
I
won't.
Have
it
wouldn't
be
like
a
little
feature
between
cities
or
the
API
aggregate,
so
it
will
be
all
C
IDs
and
then
the
code
is
it
was
before,
will
just
be
on
a
branch
somewhere
and
then
support
it
for
the
next
nine
months.
It's
all
right,
correct,
correct.
E
And
then
we
also
discussed
a
bit
cleanup
for
the
pod
Prasad
stuff,
because
it's
mentioned
in
the
configuration
of
the
Service
Catalog,
but
it's
not
implemented
and
we
find
out
that
it's
maybe
a
way
to
do
a
cleanup
for
that
story
and
really
think
what
to
do
with
foot
presses.
Then
what
are
they?
Should
we
land
this
project
or
another
one?
We
think
right,
yeah.
A
You
talks
it:
when
did
you
talk
to
them
on
keep
calm
and
I?
Still
don't?
Okay.
So
what
are
pod
presets
so
currently
in
Cuban
Air,
Service
Catalog,
when
you
bind
an
instance,
the
outcome
of
that
operation
is
a
secret,
that's
created
and
what
name
space
you're
working
in
it
is
not
automatically
injected
into
your
running.
Pods
like
it
is
in
cloud
foundry
where
it's
it's
automatically
added
to
your
apps.
We
cap
services,
pod
preset,
is
a
feature.
A
We've
been
sort
of
bandying
about
a
long
time
that
would
allow
that
to
happen
now
the
problem
is:
is
it's
not
really
accomplishable
just
from
one
service
catalog,
a
new
controller
has
to
be
created
that
we
kind
of
have
been
hoping
for
a
long
time
now
would
be
part
of
mainline
kubernetes,
because
it's
it's
really
it's
a
controller
that
allows
you
to
automatically
inject
any
environment.
Variable
it's
not
really
specific
to
service,
but
it
sounds
like
they.
F
Don't
want
it
yeah
and
they've
told
me
that
they
want
to
use
for
that.
The
impatiens
webhooks
instead
of
input
press
it
but
write
the
patristic
generic
solution,
and
maybe
we
can
that's
one
more
time
talk
with
them.
Just
show
them
the
end-to-end
story
about
it
and
maybe
also
discuss
abilities,
seek
architecture
and
have
a
finite
decision.
What
to
do
that
they
want
to
use
an
engineering
work,
server
yeah.
F
So
for
each
your
use
case,
you
should
write
your
own
web
hooks
to
inject
the
to
modify
the
deployment
right,
yeah,
but
I
think
that
they
just
don't
get
the
idea
behind
it,
but
press
that,
because
it's
just
redundant,
if
you
will
do
that
for
each
of
your
deployment
rights
and
if
each
of
the
community
member
we
implemented
their
own
web
hooks.
It's
it's
not
not
a
good
approach
right.
So
maybe
you
can
just
show
them
and
turn
story
about
it,
and
maybe
one
more
time
decide
what
you
do
with
it.
Once.
F
E
Maybe
what
we
did
in
the
project,
because
we
have
that
automatic,
binding
injection
that
we
just
forked,
they
put
Prasad's
two
to
the
chemo
organization
and
we
are
used.
We
we
created
the
controller
over
they
put
creatively
with
restarting
of
the
applications,
one
and
yeah.
It's
just
a
matter
where
that
put
press
it
will
land.
Maybe
we'll
need
to
make
a
decision
by
ourselves
if
we
want
to
have
it
in
the
Service
Catalog
to
somehow
keep
their
functionality
like
it
is
in
the
cloud
funds
right.
Let's.
C
E
A
E
I,
think
is,
we
need
to
know
something
about
the
application
right
as
well.
It's
then
it
it's
also
I,
think
a
bit
more
and
Service
Catalog
has
right
now
and
yeah,
but
maybe
we
should
leave
that
discussion
for
next
meetings
when
we'll
start
the
cleanup
of
that,
maybe
will
be
after
the
sick
architecture.
Meeting
already,
let's
see,
yeah.
F
E
A
Cool
well,
that's
it
for
today,
then
so
then
you
guys
I,
don't
think
any
of
these
stuff
is
really
actionable.
Yet
we
haven't
really
build
built
out
these
stories,
but
yeah
I.
Suppose
I
probably
should
have
done
this
a
little
interesting
when
you
guys
showed
up
anyways.
Let
me
just
stop
the
recording.
This
isn't
really
relevant.