►
From YouTube: Kubernetes SIG Service Catalog 20171002
Description
- Rename cluster-scoped resources
- F2F doodle
- CRD support
- When should we release pod preset stuff?
A
B
In
conjunction
with
the
OSB
face,
the
face
that
is
happening
in
Raleigh
and
I
have
put
together
a
doodle
to
go
and
see
what
dates
work
for
people
and
know
there
has
been
very
little
action
on
it,
so
just
so,
people
can
make
travel
plans
accordingly.
Please,
if
you
are
interested
in
coming,
go,
take
a
look
and
fill
it
in
so
right
now
we
have
four
participants:
I'm,
hoping
there
will
be
more
people
that
would
be
interested
in
joining.
B
A
A
A
D
C
A
A
A
C
Because
I
agree
with
you,
obviously
we're
not
going
to
drop
a
pod
preset
from
core
until
the
next
official
release,
but
it'd
be
nice.
If,
when
we
merge
it
into
ours
there,
the
PR
for
the
core
goes
in
at
the
same
time
just
to
remove
it
so
that
by
the
time
the
next
release
does
go
out.
There
wasn't
confusion
about
which
pod
preset
is
the
one
people
should
use
yeah.
A
A
D
Yeah
I
just
wanted
to
ask
if
we
need
to
merge
CID
support
before
we
do
base
onto
1.8,
and
what
of
what
is
our
plan
to
in?
According
to
beta
release?
Do
we
want
to
rebase
before
we
release
Twitter
and
also
like
when
we
were
based
on
21.8?
We
will
have
to
drop
to
PR
support,
which
is
a
breaking
change,
so
I'm,
not
sure
if
it's
important
for
batteries
or
not.
A
Okay,
I
stuck
my
hand
up
when
I
see
Doug,
says
+1
to
rebase
I'm,
not
sure
what
that
means
exactly
Doug,
maybe
in
a
minute
you
can
articulate
yourself
so
for
me.
I
think
that
we
should
drop
TP
our
support
and
merge
CRD
support
before
before
1:00.
Before
we
release
the
beta
TP.
Our
support
is,
does
not
work
fully
as
far
as
I
know
and
I
would
like
not
to
have
to
carry
that
code
any
longer
than
we
have
to
some
of
the
tests
around.
It
are
flaky.
I.
D
Just
want
to
mention
that
to
Piazza
don't
work
with
AP
so
that
you
all
right
I'm,
not
sure
if
they
like
work
with
other
things.
If
there
are
other
issues
but
with
APA
Grenadier,
they
don't
work
for
sure,
because
posterity's
I
had
to
basically
particular
as
the
resource
names
are
the
same
and
namespace
is
the
same
for
both
GPRS
and
service
katalk
api
server.
So
when
you
try
to
reduce
the
both
of
them
in
api
aggregator,
there
is
a
clashing
between
two.
So
it
doesn't
work
so
for
series.
D
I
had
to
set
up
a
different
name
space
for
series
so
that
they
don't
clash
with
each
other.
So
yeah
you're
right
that
there
is
a
an
issue,
at
least
with
some
things
with
GP.
Our
support,
so
I
would
drop
it
so,
but
I
guess.
We
still
need
to
probably
need
to
merge
series
first
before
dropping
TBR's,
I'm,
not
sure.
Actually,
if
like,
if
the
best
don't
work,
do
we
even
care
about
the
introducing
series?
First.
A
A
So
it
might
be
worth
a
look
before
we
make
a
decision,
but
my
gut
says
it's
probably
better
to
remove
them
first
and
keep
the
accommodations
that
we
made
for
them
around
and
just
remove
them
and
then
add
new
TP
RS.
Instead
of
trying
to
I'm
sorry,
add
CRD
support
in
after
instead
of
trying
to
then
have
three
different
backends
and
remove
one,
but
it's
probably
worth
some
investigation.
C
A
D
So
III
have
already
in
open
CID
a
PR.
It
has
some
comments,
but
I
don't
think
anyone
in
this
call
has
reviewed
it
yet
and
I
mean
I'm,
not
sure.
Actually
it
might
be
actually
easy
to
see
that
most
of
the
stuff
which
I
did
for
theory,
is
basically
copy,
pasting,
QPR,
stuff
and
just
changing
it.
So
if
I
remove
QPR
support
first
I
guess
it
might
be
harder
to
review
to
see
that
like
it's,
it's
a
lot,
it's
something
that
which
has
been
already
reviewed
for
TBR's.
D
Okay,
yeah
I
guess
I
will
just
try
to
look
at
the
CID
support
clean
up
all
the
things.
There
are
also
some
some
issues,
one
at
least
one
issue:
open
footy
PRS
that
I
think
updates
are
working
different
from
dvd/cd,
40,
PRS
and
because
I
copy
pasted
some
stuff
from
DiBiase.
Perhaps
the
same
issue
for
series,
but
I
would
prefer
to
address
some
issues
after
image,
because
it's
already
a
pretty
big
one.
C
D
C
D
We
can
draw
basically
when
we
rebase
on
to
1.8,
we
will
have
to
draw
GPRS
in
the
same
PR.
So
one
of
the
then
like
I
guess,
one
of
the
reasons
to
drop
TP.
Our
support
first
is
to
just
make
the
PR
on
drew
basing
on
to
1.8
smaller,
because
otherwise
we
will
have
to
like
in
there
raising
P
I
will
have
to
drop
all
the
together
stuff
because
there
is
no
API
for
working
with
GPRS
anymore.
A
Okay,
so
I
think
the
there's
one
other
thing
we
haven't
spoken
about
yet,
which
is
also
in
play,
is
rebase
to
176
I.
Think
the
set
of
things
we're
talking
about
is
rebase
to
176,
add
CRD
support,
remove
TPR
support
rebase
to
1.8,
and
the
reason
we
wanted
to
do
a
176
rebase
is
I.
Think
it's
a
much
less
intrusive
change
that
will
pick
up
some
fixes,
there's
already
a
pull
request
for
it.
I
think
the
only
question
on
that
one
is
doesn't
need
to
be
rebased
now.
D
D
The
only
program
I've
had
is
that
because
of
monomaniacal
works
and
sinking
from
an
era,
two
separate
repos,
some
of
the
rapist
climb
go
I
think
is
stale,
so
it's
instinct
when
with
1.7.5
but
for
some
reason
they
didn't
haven't
synced
with
the
latest
release
for
some
reason,
so
it's
it.
It
will
come
files
and
works,
but
basically
communities.
D
One
point,
seven
point
six
is
up
is
in
sync,
with
the
release
and
some
others
are
actually
still
in
there
like
snapshots
snapshots
which
I
I
took
the
latest
commit
from
the
particular
release,
but
it's
not
the
same
as
the
latest
commit
in
the
mainland
or
eco.
Sorry,
I
think
there
were
some
issues
with
API
machinery
syncing
or
something
like
that.
I
have
actually
raised
an
issue.
I
don't
think
it's
been
addressed.
I
will
just
check.
C
D
I
think
that
Paul's
recommendation
was
the
best
one.
The
raising
one
point,
seven
point
six,
then
merging
CID,
then
dropping
TPR
and
then
raising
on
to
one
point
eight.
So
it's
a
it
sounds
good.
The
only
problem
is
that
I
can't
I
guess
like
we
can
merge
the
first
PR,
but
it's
as
I
said.
The
the
dependency
on
client
go
is
not
really
this
one.
It's
just
like
this
to
me.
The
report,
which
has
been
seen.
A
Sync'd
yet,
okay,
so
we
need
somebody
to
take
an
action
item
to
talk
to
API
machinery
and
ensure
that
we
know
one
with
the
timeline
around
Clank,
Oh
being
updated
to
1/8
is
and
then
I
also
seem
to
recall
in
Prior
discussions
with
API
machinery.
We
talked
about
a
need
to
release
tags
for
these
repos
so
that
you
don't
have
to
chase
down
a
bunch
of
random
Shahs
that
you
could
just
have
a
1.80
tag
that
you
could
use
for
all
these
things.
A
D
Yeah
I
guess
I
can
still
just
for
now
just
work.
Work
on
the
CR
DPR
clean
up
some
stuff
and
revise
it
and
see
how
it
goes.
We
can
actually
merge
series
first,
I,
don't
think
they
have
to
be
in
like
in
order
with
one
point,
seven
point
six
and
like
the
rest,
three
issues,
I
guess,
should
be
in
the
in
the
order
which
is
currently
written.
D
C
Well,
is
there
any
objection
to
in
general
this
random
order
or
good,
letting
now
figure
out
the
proper
order?
I,
don't
think
anybody
released,
has
any
opinion
I,
don't
see
anybody
jumping
up
and
down
on
this
topic,
so
it
seems
to
me
as
long
as
you
figure
out
the
best
order
to
get
it
in
there
sooner
rather
than
later,
it
sounds
like
the
best.
The
best
way
to
go.