►
From YouTube: Kubernetes SIG Service Catalog 2018-10-01
Description
Agenda: https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM/
* Review how k8s members, reviewers and approvers work
* End to End tests aren’t running anymore
* Discuss intro/deep dive sessions for KubeCon
A
A
If
you
are
new,
feel
free
to
write
your
name
on
the
attendees
list
and
if
you
like,
introduce
yourself
and
say
why
you
should
of
today
and
what
you're
just
interning
about
it,
anyone
absolutely
anyone
you're
looking
for
the
project
is
allowed
to
just
throw
something
on
our
agenda
here
and
we'll
get
to
it.
Basically
a
top-down
order.
If
you
just
want
to
lurk
and
not
say
anything,
that's
totally!
Ok,.
A
A
A
Think
if
you
join
that,
you
should
be
able
to
to
throw
stuff
in
there,
so
we
used
to
do
manual
merges
and
now
we've
switched
over
to
what
main
kubernetes
does,
which
is
proud,
and
it
does
things
a
little
differently.
We've
just
been
kind
of
feeling
it
out
and
I
think
we
were
all
a
little
bit
surprised
by
how
it
works.
So
I
want
to
do
a
review
based
on
what
we've
seen
and
just
make
sure
everyone
understands
how
it
works
and
how
it
is
configured
like
right
now.
A
A
If
you
want
to
interrupt
me
or
anyone
who's
talking,
you
can
type
a
plus
hand
or
hand
or
something
like
that
to
chat,
and
then
we
will
give
you
an
app
and
I'll
make
sure
to
be
quiet
and
call
on
you
and
give
you
a
chance
to
talk
by
the
way
so
I'm
wearing
some
documentation
on
what
it
looks
like
to
be.
In
part
of
the
project,
so
users
is
people
who
use
service.
Catalog
numbers
are
people
who
are
users
catalog
and
they
are
in
the
kubernetes
incubator
organization.
A
So,
if
you
go
to
this,
you
would
people
who
are
here
are
considered
members
of
our
organization
and
they
have
the
ability
to
do
a
couple
things
you
can
have
issues
assigned
to
you
of
like
officially,
instead
of
kind
to
leave
a
comment,
and
the
other
thing
you're
able
to
do
is
look
over
a
pull
request
that
came
from
someone
who
is
not
a
member
and
go
yes
that
looks
safe
to
run.
By
default,
our
tests,
our
CI
tests,
don't
run
automatically
to
prevent
basically
people
from
like
mining
bitcoins
with
our
CI
cycles.
A
So
github
has
its
own
review
system
and
I
like
to
do
both
I
like
to
actually
use
the
official
github
review
system
and
then
apply
the
extra
comment
at
the
end
that
says
LG
TM
and
that
just
gives
it
a
little
green
checkmark
and
it
also
applies
a
label
to
the
four
across
it
says:
LG
TM
and
that
doesn't
get
it
merged.
It
just
says:
I'm
a
person
I'm,
somehow
associate
with
the
project
and
I've
gone
through
a
pull
request,
review
and
I
feel
this
is
good
if
you
are
already
in
the
kubernetes
organization.
A
C
A
Have
to
be
part
of
the
organization
that
Service
Catalog
is
inside,
so
that
keeps
you
in
key
thanks,
but
but
the
rules
that
they
have
told
me
is
that
for
people
who
are
already
members
of
the
kubernetes
organization,
it's
just
a
formality
for
them
to
open
an
issue
and
get
access
to
the
incubator
as
well.
Essentially,
these
people
are
trusted
to
not
do
malicious
things
in
our
CI.
That's
yes,
that's
piece
of
like
the
level
of
responsibility
there
I
mean
we
also
have
an
owner's
file,
though
in
our
repository.
A
Everyone
who
used
to
be
basically
whoever
used
to
have
write
access
to
our
repository
when
we
moved
to
prowl
became
an
approver.
There
is
actually
another
level
here
that
we
could
have
had
called
reviewers.
That
would
be
people
suggested
to
do
the
reviews.
That
way,
you
can
have
someone
who
is
a
member
of
the
kubernetes
incubator,
org,
okay,
and
they
may
not
be
in
a
position
where
they
can
merge
pr's,
but
they
may
have
done
enough
commits
in
a
certain
area,
for
example,
SV
cat
CLI,
where
we
were
like
it'd,
be
really
helpful.
A
A
So
here
we
go.
This
is
a
good
example
of
this.
So,
for
example,
Kirsten
is
not
a
maintainer
but
she's
a
reviewer
in
here,
and
that
just
automatically
tags
her
for
reviews
when
someone
opens
a
pull
request
in
that
directory,
and
it
helps
avoid
the
the
maintainer
x'
who
are
at
the
root
owners
from
always
being
pinged
for.
Basically
every
review.
A
So
that's
how
reviewers
work
yeah!
If
he
is
that
as
a
reviewer,
you
don't
need
to
have
commitment
essentially,
and
you
can
still
just
share
the
load
and
help
review
things
and
it's
always
safe
to
apply
lgt
em,
because
you
still
have
the
responsibility
of
a
maintainer
doing
the
final
approve.
So
we
call
people
maintainer
x'
in
kubernetes.
A
A
Previously,
in
the
sig
we
had
a
rule
where
you
need
to
separate
people
to
review
something
to
get
it
merged,
and
we
have
been
following
this
so
far,
but
I
wanted
me.
People
aware
that
in
the
rest
of
kubernetes,
that's
not
always
a
requirement
and-
and
in
fact
there's
nothing
in
proud.
That
prevents
say
like
me,
who
is
an
approver
from
applying
both
labels
applying
both
commands
again
it
merged.
This
is
helpful
at
times,
for
example,
fixing
the
type
I
want
to
read
me
fixing
a
dock
page.
A
It's
not
a
it's,
not
an
interesting,
controversial
change,
and
it
just
helps
if
I'm,
an
approver
and
I
have
time
to
do
the
review
and
like
I'm,
basically
the
owner
for
that
area
anyway.
I
can
help
get
something
through
quickly.
You
can't
do
it
for
your
own
things
but
say
like
Jay
submitted
something
and
fix
some
horrible
typos
in
this
dock,
then
maybe
I
just
submitted
I
could
help
get
it
through.
A
You
know
quickly
or
something
like
that,
but
so
I
just
want
to
make
people
aware
that,
like
if
you
see
this
happen,
it's
not
a
fault
and
how
we're
configured.
This
is
how
car
works
and
I
wasn't
aware
of
this,
and
then
also
our
repository
is
configured
to
need
both
LG,
TM
and
approved.
This
is
not
true
for
other
repos,
and
people
are
actively
talking
about
this
right
now.
So
I
just
wanted
to
make
it
like
super
clear
and
then
tears,
don't
have
any
special
abilities
when
it
comes
to
crowd.
C
A
That's
another
thing
that
is
currently
up
for
debate
about
making
this
configurable
or
maybe
changing
the
default
behavior
of
prowl.
If
you
go
into
the
kubernetes
sig
contributor
experience
mailing
list,
people
are
actively
talking
about
that
right
now,
but
yeah.
The
way
we're
set
up
currently
is
LG.
Tm
means
I've
done
the
code
review.
So
every
time
the
code
changes
that
gets
wiped
away,
a
prove
says
the
right
person
has
reviewed
it.
We've
made
all
the
changes,
needn't
need
to
be
in
there.
You
know
you
didn't
like
forget
something
off
somewhere
else.
A
A
It's
sometimes
useful
when,
like
someone
just
needs
a
rebase,
or
they
just
need
an
it
like
a
small
thing
that
we
don't
really
care
if
they
make
the
change,
if
they
do
great,
if
not
whatever.
That
may
be
something
we're
like.
You
can
put
the
approve
on
knowing
that
whatever
they're
gonna
do
after
that,
isn't
terribly
exciting,
and
it's
okay
for
someone
else
to
lgt
em
in
order
to
get
it
merged.
A
A
A
D
B
F
A
Currently,
in
our
proud,
proud,
config
and
so
they're
rotting
during
this
yeah
I
built,
but
we
have
another
set
of
tests,
they
were
called
e
to
e
that
hit
a
real
cluster,
essentially
yeah.
We
unfortunately
never
figured
out,
and
people
forgot
with
the
transition
of
people
will
be
on
and
off
the
project
and
switching
to
grow.
A
A
B
B
A
D
B
Send
me
I'll,
probably
get
it
cranked
up
a
basic
scaffolding
tonight,
for
if
you
want
cool
one
guarantee
the
test,
but
I'll
just
guarantee
that
infer
the
scaffolding
will
spin
up
and
spin
down
and
get
a
lot
working
first,
and
then
we
can
overlay
the
tests.
The
different
type
of
tests,
I
get
it
done.
A
F
It's
me
so
yeah
Jenkins
for
a
while
I
think
was
starting
around
was
a
June,
or
so
it
was
just
like
freaking
out
like
it
wasn't
responding
to
the
PRS,
like
things
have
gotten
crazy
with
it.
I
tried,
fixing
it
and
like
it
worked
for
a
while,
but
then
it
started
having
the
same
exact
issues,
and
so
that
was
around
the
time
that
yeah
so
proud,
gotten
fully
rolled
up
and
it
seemed
like
it
was
good
to
go
so
yeah
at
that
time.
F
I
kind
of
just
left,
Jenkins
alone
and
then
I
didn't
notice
when
it
had
originally
just
completely
stopped
posting
on
on
PRS.
But
after
about
a
month
or
so,
I
just
took
it
offline
because
it
wasn't
being
contributed
to
nobody
seemed
to
care
at
all.
So
yeah,
it
seems
like
prowl,
had
been
filling
its
use
case.
B
G
A
G
A
F
C
B
Then
you
do
your
plugins,
then
you
put
your
config
in
which
is
pretty
standard
stuff
and
then
run
your
test.
Make
sure
that's
all
work
and
yeah.
That's
pretty
straightforward,
I,
probably
who's
the
best
person
to
talk
to
about
getting
some
of
the
secret
stuff,
like
you
know
the
project,
any
specific
stuff
that
it
means.
B
B
B
A
E
If
they
were,
you
know
things
they
wanted
to
make
sure
you
got
mentioned.
Like
I
said
that
meeting
already
happens.
So
if
you
have
something,
you
really
want
to
make
sure
we
talk
about,
feel
free
to
reach
out
to
one
of
us
yeah.
Theoretically,
at
some
point
we'll
have
the
presentations
ready
for
you
per
two
weeks
before
the
conference.
I
think
was
what
we
decided
so
just
something
happen.
E
C
Was
some
discussion
in
one
of
the
recent
PR
is
about
word
wrapping
column
ad?
That
kind
of
thing
I
know:
I
got
dinged
when
I
first
started
about
doing
word
wraps
on
function,
comments
as
far
as
I
know,
that's
the
only
place
that
we
do
word
wrapping,
but
I
also
don't
think
it's
covered
anywhere
in
our
dog.
So
I
thought
it
was
worth
discussion.
That's
what
people
recollected
I,
don't
know
why
you
need
to
do
word,
wrap
at
column.
Eighty
on
function,
help
or
you
know,
function
go
doc,
but
that's
that's.
C
H
C
A
I'm
trying
to
word
wrap
occasionally,
but
I
won't
hold
up
a
PR
for
you,
I,
like
word
wrapping
in
the
in
the
markdown
for
our
websites,
most
of
because,
if
I'm
suggesting
edits,
if
a
really
large
paragraph
is
a
single
line,
it's
extremely
difficult
to
isolate
and
comment
on
it
great
broken
up
into
hard
lines.
I
can
give
someone
a
comment
about
an
individual
thing.
Yeah
again,
that's
just
something
that
it
makes
my
life
easy,
but
it's
not
something
I,
you
know
I!
Won't.
We
usually
ask
someone
to
do
it.
Yep.
C
There
was
this
milestone
was
already
created.
Perhaps
Carolyn
did
it,
but
in
any
rate
it's
a
good
milestone
to
heaven.
It
helps
us
I
think
identify
exactly
where
we
are
with
the
namespace
broker,
because
it
seems
like
we
kind
of
like
a
leaking
faucet.
We
keep
finding
a
drip
here
there
we
have
missing
functionality.
C
C
A
C
C
C
A
A
B
We
have
a
number
of
on
the
broker
part
of
side
of
it,
I'm
talking
about
how
that
the
OSB,
so
on
OSB,
there's
a
number
of
that
utilizes,
obviously
service,
catalog
and
pre,
and
promoting
them
to
to
preview
so
that
people
can
use
them
more
and
I
noticed
a
lot
of
people.
Are
there
akia
I've
also
been
on
that
throat,
maybe
not
I.