►
From YouTube: Kubernetes SIG Service Catalog 2018-03-05
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
A
A
A
C
Yep
great
so
Matt
suggested
that
we
had
a
new
condition,
two
instances
which
is
all
for
mediation
to
help
with
resolving
timeouts
and
some
other
coordinate
case
issues
with
orientation.
I
got
started
already
working
on
that
and
actually,
once
I
started
working
out
that
I
actually
marked
the
in
progress.
Awesome
th
any
progress
flag
has
duplicated
and
Matt
says
it's
like
it
should
be
kept.
There
is
a
teacher
in
the
Cole.
C
D
Yeah,
the
only
thing
I
really
have
to
say
about
that
I
guess
is
that
it
looks
coming
down
from
from
cube.
Is
that
the
preference
is
to
use
fields
instead
of
conditions,
so
I
think
we
should
still
keep
that
that
field
in
place
and
actually
use
that
for
your
logic,
checks
and
whatnot.
The
condition
is
really
useful
only
to
show
the
reason
why
we're
in
or
for
mitigation,
if
something
else
comes
along
and
clears
out
all
right.
These.
C
C
This
was
what
this
was
part
of
the
one
of
the
other
PRS,
where
Matthews
suggested
that
we,
it
would
probably
be
nice
I,
think
the
issue
was
that
currently
we
we
erase
the
reason
and
message
with
and
the
varieties
with
the
message
saying
that
we
will
start
off
unification
or
something
like
that,
and
with
all
the
latest
changes
we
will
lose.
The
original
error
message
completely
and
that's.
C
C
B
Is
there
anything
if
there
any
did
you
did
you
run
through
the
options?
I
see,
that's
the
big
topic.
If
you
run
through
the
options
in
a
previous
call,
that
I
can
go
refer
to,
or
would
it
be
useful
to
spend
the
time
and
go
over
these
options
right
now
or
should
we
just
wait
until
there's
more
people
I,
don't
waste
any.
C
B
E
So
I
was
a
Paul
asked
me
to
work
on
that,
and
so
I
took
a
took
a
look
around
kubernetes
and
see
what
was
it
being
used
or
it's
something
like
this
and
I
really
wanted
to
reuse.
The
logic
of
parsing
query
statements
like
select
name
in
and
then
give
a
list,
so
I
took
a
look
at
seeing
if
I
could
reuse
label
selectors
from
the
labels,
dot
selector
package
and
I
did
it
in
a
PR.
So
you
go
check
it
out,
there's
a
link
there
and
it
I.
So
I've
got
it
working.
E
What
happens
is
on
grocery
lists
when
it
pulls
the
data
from
the
catalog
from
the
broker
in
the
service
catalog
before
the
objects
get
ingested
into
kubernetes
resources,
I've
applied
a
label
selector
on
them.
So
there's
a
bunch
of
unit
tests
of
examples
of
like
how
this
could
be
used
and
the
question
I
wanted
to
bring
to
everybody
is:
how
would
we
like
to
consume
this
on
the
API
side?
So
there's
there's
a
couple
different
options.
E
E
Well,
no,
no,
not
at
all,
so
this
I
need
a
document
a
little
bit
about
what
the
what's
supported,
but
basically
what's
happening
is
I'm
not
actually
using
like
the
label.
Selector
mechanics
inside
of
kubernetes
I'm,
just
using
the
classes
that
do
that
behavior
for
Watchers
and
Lister's.
But
it's
all
in
memory
in
the
reconciliation
lube
for
the
cluster
service
broker.
So
I
take
newly
converted
object
from
the
JSON
payload.
E
It
gets
turned
into
the
broker,
client
resource
type
object,
and
then
that
gets
turned
into
the
in-memory
version
of
kubernetes
resource
before
it
gets
persisted
and
before
that
happens,
I
convert
it
to
a
simple
map
of
name
and
external
name
is
set
to
and
then
their
values.
So
it
only
has
those
two,
because
that
was
all
that's
really
required,
but
it
it's
setting
up
the
mechanics
for
how
we
could
do
like
say
filtering
on.
E
E
E
Yep
and
then
let's
say
the
the
broker
has
already
been
listed
once
and
has
been
turned
into:
kubernetes
objects:
it'll,
look
like
they've
been
removed
from
the
catalog
on
after
you've
applied
the
filter.
So
why
would
you
want
this?
Maybe
you
have
a
broker
that
has
a
bunch
of
beta
things
that
you
want
to
share
with
a
client
or
something,
and
you
could
set
them
up
with
the
service
service.
Catalog
object
in
kubernetes
that
has
a
predetermined,
white
or
black
list,
and
then
they
only
get
to
play
with
what
you
approve.
E
E
Anyway,
I
I
don't
know
if
maybe
people
want
to
take
a
look,
and
so
I
haven't
I'm
at
the
point,
where
I'm
finishing
up
the
interface
between
how
we
talk
to
kubernetes
and
the
admittance
controllers.
So
if
they're,
if
anyone
has
an
opinion
about
what
we
should
do
or
anything
like
that
or
take
a
look
at
what
the
unit
tests
are
doing,
feel
free
to
take
a
look
now.
You
know
also
I
put
this
behind
a
feature
flag.
A
A
F
I'm
sure
it'll
be
life,
changing
I
just
want
to
report.
Back
last
week
we
did
a
doodle
poll
for
kind
of
combining
forces
with
the
OSB
API
face
to
face,
and
we
selected
November
12
and
we'll
be
at
the
same
place
at
the
Microsoft
conference
center
and
time
Square
I'll
figure
out
what
the
address
is
and
post
that
so
we
know
for
sure,
but
it's
basically
the
square.
E
F
Yeah,
that's
all
I
had
to
say
about
that.
Just
want
to
make
people
aware
that
everyone's
welcome
awesome.
F
G
G
It
was
just
like
the
outcome
of
the
face
to
face
the
last
face-to-face
meeting
where
we
documented,
like
a
bunch
of
documentation,
was
needed
so
we're
trying
to
decompose
that
and
some
discreet
issues
and
we're
going
to
use
the
needs
doc
tag
so
that
people
can
filter
on
it
pretty
easily
and
track
them,
and
then
we're
gonna
tag
them
with
help
on
it.
So
we
can
solicit
more
people
to
contribute
to
this
thing.
A
G
So
we're
starting
off
with
some
high-level
stuff
that
seemed
like
easy
targets
out
of
the
list
that
was
in
that
big
issue:
that's
Paul!
If
you
had
any
priorities
and
Aaron
if
they
had
any
priorities
of
things,
so
it
kind
of
fed
it
into
this.
So
we'll
start
working
on
that
justin
is
on
the
line.
I
think
he's
gonna
help
us
out.