►
From YouTube: SIG Service Catalog 20170320
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
C
So
what
we
have
okay,
so
I,
guess
if
you
aren't
familiar
with
the
pod
preset
whole
thing,
it's
an
admission
controller
and
it
will
allow
you
to
inject
various
resources
into
a
pod
so
like
in
this
example
that
we're
setting
we're
going
to
just
call
it
like
a
lot
of
database.
It's
going
to
be
in
a
specific
namespace.
D
C
And
then
it's
going
to
match
on
looking
at
labels
called
front-end,
so
I'll
show
you
our
pods
next
to
which
is
just
this
engine
X
pod,
that's
called
website.
It
has
this
role
front-end
that
we're
going
to
be
matching
out
with
our
pod
preset
role,
front-end
and
it's
going
to
inject
like
a
environment,
variable
DB,
port
and
volume
amounts
and
volumes.
So
it
basically
just
modifies
the
pause
back
for
any
sort
of
life
label,
selector
that
you
give
it
so
amazing
it
make
sure
because
I
just
gotta
have
another
meeting.
C
D
C
D
B
C
B
C
B
C
C
Okay,
hard,
why
is
it
not
running
with
it
I.
B
B
B
Alright
I'm,
going
to
share
my
screen
and
we
are
going
to
take
a
look
at
MVP
two
so
see
here
share
my
screen.
Amazing.
Absolutely
amazing
that
on
march
20th,
2017
I
was
offered
the
opportunity
to
share
only
the
window
that
I
actually
wanted
to
share
by
doom
Thank
You
sim.
It
is
truly
appreciated,
so
we're
going
to
run
through
all
of
these.
So
first
up
Aaron
found
a
bug
today
where,
if
you
bind
it
to
the
UPS
broker
before
you
have
a
instance
provision,
it
will
panic.
B
B
A
B
B
And
then
there's
a
pull
request
from
Simon
to
fix
some
of
the
flaky
tests
for
TPR
I,
like
fixing
flakes
that's
good
and
in
fact,
in
general,
the
last
several
years
of
my
software
development
career
had
basically
put
me
permanently
off
flake
based
cereals.
For
this
reason,
so
next
one
is
ensure
that
the
OSB
grid
has
never
changed
across
API
server
calls
Aaron.
Do
we
ever
establish
whether
that
was
happening?
B
B
Excuse
me,
and
next
one
appears
to
be
the
issue
that
580
fixes,
which
is
write.
An
integration
test
to
establish
that
OSB
grid
can't
changed,
can't
change
once
assigned
576
we've
already
covered
as
a
TP,
our
storage
integration
tests.
I
can't
have
you
gotten
unstuck
from
that
I
know.
We
were
talking
about
that
one
earlier,
yeah
I'm,
so
close
I
can
taste
it
all
right.
Well,
I
can
taste
it
too
now.
B
Next,
one
is
poor
request
that
I
open
to
make
the
fake
broker
server
like
an
OSD
broker.
So
what
I
found
when
adding
an
integration
test
that
basically
simulates
the
walk
through,
is
that
the
I
was
using
the
broker
client
and
that
is
not
really
suitable
for
use
in
an
integration
test.
It's
fine
it
what
it
does
and
it's
fine
for
unit
tests,
but
since
the
controllers
might
make
calls
again
and
again
what
I
had
started
doing
is
making
a
fake
broker.
That's
an
OSP
compliant
broker.
I
this
is
going
to
get
tabled.
B
I
might
move
this
out
of
MVP
to
now
for
reasons
that
we'll
get
to
momentarily.
So
next
up
is
ad
e
de
walk
through
testing
and
jenkins
from
everybody's
favorite
cereal
base,
nick
kibbles
and
bites.
I
see
this
has
two
LG
cans
on
it,
which
is
good.
I
hope
that
this
one
can
be
merged
soon,
because
this
will
give
us
a
lot
more
confidence
about
what
about
ensuring
that
we
don't
break
the
walkthrough
next
one
is
an
issue
that
aaron
has
opened
to
because
the
controller
was
reprovision
and
rebinding
things.
B
So
a
couple
things
about
this
at
the
protocol
level
at
the
API
spec
level,
it
is
totally
fine
to
resend
the
same
provision
and
same
bind
request
as
you've
already
sent
and
if
you
send,
in
the
exact
same
way,
brokers
are
supposed
to
be
I,
didn't
and
tell
you
awesome.
Great
I
already
did
that
in
practice.
We
have
found
that
surprise.
Surprise,
not
everybody
implements
the
burglar
spec
correctly,
and
so
basically,
the
the
issue
here
was
to
avoid
resending
requests.
B
If
we've
already
reconciled
a
particular
state
and
we
got
into
a
ready
condition,
equals
trip,
do
my
let's
see,
let's
see
Erin,
do
you
know
if
I
pull
the
fix
that
I've
merged
I?
Don't?
Okay,
I
remember
all
right,
so
there's
a
pole
for
that
open.
We
might
come
back
to
that.
One
next
one
is
to
put
to
create
young
charts
for
Service.
Catalog
resources
are
fairly
self-explanatory,
so
you
don't
have
to
do
like
a
cube.
Cgl
creates
all
over
town
on
next.
One
is
to
add
off
secret
fields
to
broker
example.
A
B
B
The
next
one
I
see
separate
the
water
from
the
dev
guide
as
a
proposal
that
sounds
like
it
might
be
a
worthy
goal,
especially
now
that
you
can
demo
and
do
to
walk
through
without
building
anything
and
next
one
is
refactor-
is
a
walk
through
to
work
with
the
helm,
sharks
that
the
other
polls
are
adding
and
after
that
we've
got
the
flaky
tests
for
the
I
believe
this
is
for
third-party
resources
being
installed.
I
think
there's
a
pull
request
that
we've
already
looked
at
for
that
number
574.
B
Next,
one
is
a
poll
for
me
that
adds
a
integration
test
that
does
provision
and
bind
and
basically
is
like
a
integration
test
for
the
walk
through
someone
that
I
referenced
earlier
I
think
after
my
poll
to
avoid
reprovision
and
rebinding
goes
in.
This
can
go
in
with
that
changes,
but
I'll
have
to
follow
up
on
that.
B
Next
one
is
a
poll
to
not
start
the
API
server
when
the
TPR
installation
fails
in
folks
I'm
very
pleased
to
say
that,
like
the
theme
of
we're
tightening
this
stuff
up
and
fixing
documentation
breaks,
it
seems
to
be
very
evident
in
these
issues
as
we
walk
through
them.
That
is
greatly
appreciated
and
you
all
will
appreciate
it
after
tubecon
when
there's
a
bunch
of
people
poking
around
the
repo.
B
So
thank
you
all
for
for
pitching
in
dead
to
get
the
stuff
shaped
up
next
issue:
add
TBR
storage
to
the
test
and
test
integration,
client-side
test
I
know,
Kent
and
Aaron
have
been
working
on
this
I've
been
offering
some
consultations
of
low-to-moderate
help.
Perhaps
what
I'm?
What's
that?
Ultimately.
A
B
Okay,
next
one
is
integration
test
for
the
controller,
as
we
discussed
I
have
some
additional
polls
in
process
now
to
realize
that
one
next
one
is
have
an
e
de
for
the
walkthrough,
which
Michael
key
bays
and
working
on
next
up
is
add
a
health
check
that
fails
in
the
API
server.
If,
until
all
T
PRS
have
been
created,
it
sounds
like
that
ones
in
progress
right
now.
B
Next
one
is
implement
asynchronous
provision
and
deprovision
now,
just
for
the
record
technically,
the
client
already
does
this.
However,
when
you
do
an
async
provision
or
D
provision,
the
go
routine
that
calls
it
blocks
until
it's
finished,
which
is
not
a
really
sustainable
long
term.
I
am
I,
will
be
quite
honest
with
everybody
I'm,
not
certain
that
we
will
get
to
this
one
this
week
and
I.
B
This
one
is
what
conditions
should
we
have
in
the
API.
I
also
think
that
this
should
be
moved
out
to
MVP
three
agreed,
so
what
we've
done
come
on
github?
What
we've
done
for
now
is
that
there's
a
writing
condition
and
that's
basically
it
a
next
one.
Add
continuous
integration
that
runs
the
EE
tests.
I
think
that
Michaels
pull
requests
closes
this
next.
One
is
add:
support
for
pod
preset
make
a
pod
injection
policy
or
the
resource
formerly
known
as
pit
as
I,
sometimes
like
to
call
it.
I
will
be
honest
with
everybody.
B
I
don't
see
this
happening
this
way,
eight
four
reasons
that
I
want
to
get
to
once
I
start
talking
about
good
old
number.
Four
one
three
self
link
for
broker's
is
incorrect.
It's
missing
a
slash.
I
actually
have
a
clue
on
how
to
fix
this.
One
I
had
intended
to
just
fix
it
after
the
rebates,
but
I
think
I
know
how
to
fix
it
now
so
I'm
probably
going
to
go,
try
to
do
that
in
the
next
day
or
so
and
last,
but
certainly
in
no
way
shape
or
form
least.
B
We
have
rebates
on
to
kubernetes.
One
six
candidate
so
last
week,
jeff
peeler
and
I
sat
together
in
raleigh
and
started
this.
I
think
that
we
are
about
85
to
90
percent
done
with
it.
B
In
doing
this,
we
found
a
couple
things
that
need
to
be
fixed
in
kubernetes
before
we
will
be
able
to
consume
pod
presets.
So
as
an
example,
there
is
machinery
that
publishes
from
the
kubernetes
case
that
I
of
kubernetes
repo
in
a
subdirectory
called
the
staging
repo
publishes
the
api
machinery,
an
api
server.
B
Repositories
that
hasn't
been
working
for
some
time
now,
apparently,
and
in
order
for
that
to
in
order
to
complete
the
rebase,
I
really
want
that
to
be
fixed
so
that
we
can
be
on
the
latest
version
of
everything.
I
have
some
assurances
from
hooks
that
work
on
API
machinery
that
we
that
will
be
unblocked
on
this
today,
I
haven't
seen
that
that
has
happened
yet
so
I
am
not
I'm.
B
No
longer
certain
that
we'll
be
able
to
complete
the
rebase
this
week
and
I
would
really
like
for
as
many
testing
pools
to
be
merged
as
we
can
possibly
get
before
the
rebase
lands
and
as
as
a
function
of
all
this
client
go,
does
not
yet
have
the
settings
API
group
that
just
added
for
pod
preset
in
it.
A
D
A
B
A
B
What
we
could
do
is
we
could
we
could
create
an
Adagio,
not
one
candidate
tag
now
and
okay
I
tell
you
what
why
don't
we
do
that
and
we'll
make
an
O
dot
one
tag
after
later
in
the
week
after
more
these
testicles
and
have
merged
everybody?
Okay,
with
that.
A
B
Think
that
would
be
awesome.
If
folks
could
do
that
and
basically
I
think
everybody
that
used
the
MVP
has
found
at
least
one
bug
so
far,
so
the
more
the
merrier
even
em
bugs
alright.
So
that's
what
we
got
for
MVP
thanks
to
everybody,
that's
working
on
fixing
on
working
on
fixing
stuff
and
let's,
let's
check
back
with
Jeff
Jeff
how's
it
going.
C
B
B
Are
we
still
planning
on
meeting
at
cocoon?
We
are
still
planning
on
meeting
Thursday
was
the
day
that
was
selected.
I
still
need
to
reserve
the
space
because
I
suck.
B
B
A
Yards,
so
if
you
have
a
PR
that
needs
to
go
in,
it's
the
bug,
fix
or
documentation,
can
you
either
milestone
it
with
MVP
two
or,
if
you
can't
pinkie
and
I'll,
milestone
it
as
MVP
two
and
then
others
if
you're
looking
for
reviews
go
in
to
the
key
of
the
pull,
slash
pulls.
So
that's
all
the
pull
requests
that
are
currently
open,
select,
MVP,
two
for
the
milestone
and
get
reviewing.
A
A
B
So
I'll
take
a
pass
through
all
the
PRS
and
make
sure
that
everything
is
tagged
with
MVP,
that's
relevant
to
it,
so
that
everything
shows
up
in
this
list
all
right.
Well,
let
me
just
end
this
on
a
note
that
I
think
it's
a
little
ironic
that
we've
been
talking
about
stability
and
tests
when
there
is
a
clearly
smoke,
detector
shaped
hole
to
the
light
screen
right
of
Aaron's
head
in
the
background.