►
From YouTube: Kubernetes SIG Service Catalog 2019-9-16
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,
if
you
hear
going
down
the
list
of
things
home,
striped
version
mixed
up
so
you've
linked
me
to
be
issue
on
that
I
was
unable
to
actually
reproduce
it
like
I
download,
the
newest
version
of
elm
thinners
to
dot
whatever
out
the
3.0
beta
version
and
not
installed
and
reinstall
the
hell
chart
over
and
over
again
and
I
only
ever
got
the
most
recent
version.
So,
like
I,
don't
know,
what's
going
on
there,
I
should
probably
share
my
screen.
Yeah
I
can
look.
A
B
This
is
basically
a
difficulty.
I
have
also
an
ox
night
on
our
agenda,
so
I
wanted
to
talk
about
it
because
of
the
beginning.
There
was
an
assumption
that
when
you
push
something
to
the
home
repository,
then
the
last
pushed
charlie
be
installed
on
your
cluster,
and
that
was
an
issue
and
because
of
that,
we
introduced
that
concept.
We've
additional
entry
dedicated
for
me
to
branch,
but
after
I
sit
here,
I
sing
with
one
of
the
maintain
maintainer
of
hell
and
I
check
it
once
again
and
and
yeah
ham
supports
and
versioning.
B
So
that
was
probably
some
mistake
during
the
investigation.
So
basically
the
current
approach
looks
like
a
back
and
there
is
a
proposition.
What
we
can
do
with
that
and
I
have
two
questions.
You
can
check
them
on
in
agenda
for
today's
meeting.
Okay.
So
basically
the
first
question
is
you
if
we
want
to
remove
that
and
tweak
from
time
repository
I
mean
about
catalog
v2
Brown?
That
was
the
first
question
and
the
second
one
is
about
pushing
hand
charts
to,
as
we
cut
catalog
entry
I
mean
by
the
inquest
one.
A
B
B
The
full
name
service
I
know
that
what's
also
working
good,
so,
as
you
can
see,
you
have
a
to
entry,
catalog
and
catalog.
The
ODOT
to
and
question
is
if
we
want
to
remove
that
new
entry.
There's
the
first
question
and
second
one
is
how
we
want
to
push
new
charts
to
the
old
entry
I.
A
B
A
A
B
B
So
we
can
back
to
documentation
and
I
will
explain
you
that
okay,
so
basically,
as
you
can
see
right
now,
you
have
two
comments
to
install
Service
Catalog
one
is
the
without
any
suffix
right
and
there
is
to
install
the
service
clock
from
the
master
bike
and
the
second
one
was
dedicated
to
install
service
catalogue
from
v2
branch.
Alright,
such
approach
was
introduced
because
we
fought
from
the
beginning
that
if
you
push,
if
you
push
chart
to
the
home
repository
the
latest
post,
so
that
repository
will
be
installed
on
us
as.
B
B
A
separate
day
exactly
exactly
some
things
to
that.
If
you
push
from
master
0.3,
it
won't
want
to
be
overridden
with
the
0.2.
For
example,
we
create
a
new
patch,
but
that
assumption
was
wrong.
I
think
once
again
with
one
of
the
hell
contributor
and
they
supports
sender
sharing.
So
even
if
you
push
old
version
to
your
repository,
it
will
not
be
taken
into
account.
If
you
are
installing
says
Kellogg.
A
B
B
A
B
A
B
B
Basically,
what
you
can
do
is
to,
of
course,
get
all
version
from
six
o'clock
and
you
can
execute
helm,
install
with
that
particle
version
and
also
using
such
comment.
All
late
will
install
service
catalog
with
the
newest
version
used
using
some
versioning.
So,
for
example,
if
you
have
something
like
that,
you
pushed
current
release.
Next,
you
push
something:
we've
both
got
free,
then
you
push
some
patches
for
your
old
branches.
Till
ten
install
will
install
only
the
newest
version
based
on
some
version.
Not
the
latest
pushed
ok.
A
A
B
B
As
you
can
see,
there
is
a
two
entries
and
that
one
is
not
in
sync
with
v2
branch.
Does
it
what
we
want,
and
there
is
a
question,
and
that
was
the
question.
Basically,
we
need
to
decide.
I've
explained
that
why
we
did
it
right,
but
as
Morgan
notice,
we
don't
need
to
do
it.
We've
we
can
do.
We
can
still
have
only
one
entry.
I
I.
B
Yeah
and
that's
the
question:
if
you
want
to
support
I
already,
let
me
check
it.
I
asked
here
a
question
for
both
of
you
me
to
decide
lease
at
approach
the
bugger
feature
in
to
decide.
If
we
want
to
spit
at
that
or
not
if
you
want
to
have
that,
our
users
should
use
such
common.
For
instance,
Arabic
from
v2
branch
or
I
mean
just.
A
B
Okay,
there's
it's
not
a
problem,
we
can
do
it,
but
what
we
need
to
do
before
that?
We
need
to
decide
if
you
want
to
have
two
repositories
or
not.
We
need
to
decide
if
such
approach
we're
splitting.
That
is
a
battle
feature
and
be
instead
stake
that
in
reading
documentation
right
now,
we
have
that
in
documentation.
As
you
can
see,
there
was
an
entry
saying
that
one
second
dogs
install.
B
We
are
saying
that
if
you
want
to
install
the
newest
supported
source
catalog,
you
are
using
that
one.
If
you
want
to
use
older
version,
for
example,
API
server
based
implementation,
then
you
need
to
use
something
like
that
and
first
of
all,
we
need
to
provide
if
we
want
to
have
something
like
that
or
not
as
far
as
I
as
far
as
I
understand,
Morgan
is
against
such
approach.
What
Morgan
wants
to
have
is
only
one
I,
don't.
B
A
A
A
Especially
because,
if
like
we
need
to
fix
a
bug
on
the
feature
branch
and
we
cut
an
easier
to
version,
you're
like
oh
I-
have
to
go.
You
know
the
current
versions
like
0-3,
15
or
whatever,
but
I
have
to
go
backwards,
16,
but
then
up
one
to
get
0
to
17
or
whatever
that
is
nobody's
gonna.
Do
this
yeah.
B
B
Okay,
so
what
maybe
explanation
why
we
choose
0.2?
It
was
just
an
idea
for
for
a
future,
so
it
would
be
easier
to
just
you
know,
use
if
you
have
a
different
breaking
change
for
0.3,
then
we
don't
need
to
find
a
business
business
name
for
that
branch,
but
yeah
for
catalog.
We
can
generate
for
couple
of
my
legacy
API
server,
something
like
that,
but
maybe
even
API
server
will
be
good
enough.
Yeah.
B
A
B
A
A
It
isn't
so
I
guess
just
say
the
API
server
based
version,
but
like
just
make
it
more
explicit
why
this
branch
exists,
legacy
version
that
still
uses
the
API
server.
Don't
don't
focus
on
the
version
numbers
because,
apparently
that's
confusing
just
say:
okay
legacy,
API
version
still
uses
the
API
server
will
be
some
ordered
intelligence.
B
A
B
B
What
like
duplicated?
We
sorry,
sorry
I,
don't
yeah
I
named
it
wrong,
be
I'm,
saying
I'm,
saying
that
our
old
user,
which
still
use
the
API
server,
sure
I'm.
B
A
B
A
B
B
B
A
B
A
B
Because
if
you
creating
attack
check
it
out,
that's
it
for
you,
it's
choose
an
existing
tag
or
create
a
new
tag
on
published.
So
basically
you
just
creating
a
tag.
If
you
don't
have
it
here,
what
we
did,
we
just
created
a
tag
by
our
own
and
then
on
the
github
release.
We
only
really
use
that
tag.
If
you
are
not
doing
that
locally,
then
such
thing
we
did
it
for
you.
Well,
the
minge
updates.
B
B
B
B
Then
what
you
are
doing
is
to
creating
locally
repository
using
your
charts,
so
home
repository
and
then
sinking
those
files
into
your
Google
Storage
bucket,
okay
and
credentials.
There's
an
important
stuff
you
can
see.
There
is
a
statement
out
of
the
k2g
cloud
right.
You
are
using
that
guy
G
cloud
key
file
how
the
guy
is
generated.
Okay,
so
let
me
show
you
an
asset
you
have
that
file,
but
that
guy,
but
is
encrypted
in
Travis
before
that
job
will
be
executed.
I
can
show
you
okay,
it's
here.
B
It
will
be
decrypted
decrypted,
safe
under
that
path.
And
after
that,
this
script
is
executed
right,
and
that
was
the
approach
yeah.
It's
decrypted
using
open
SSL,
but
using
work.
G,
okay
and
those
key
I
think
that
I
can
show
that,
on
on
our
recording,
really
bacon
Travis
yeah
I
birthday,
they
are
defined
under
settings
as
an
environment.
Variable
okay,.
A
B
You
what
you
have
is
you
have
it
there
that
guy
you
decrypt
five
committed
on
our
repository
and
use
that
decrypted
file
to
authenticate
with
G
cloud
is
like
that
right
now
it
was
started
by
Corrine.
Probably
Corrine
had
also
the
power
to
connect
new
secrets
to
share
with
them
with
us
or
no,
it
should
be
checked,
and
what
is
that?
The
other
end.
A
Of
that,
like
a
helm,
I
don't
know,
is
there
a
front-end?
Can
I
go
to
helm
that
whatever
and
look
at
it?
No,
there
is
no
throne
I'm
a
headless
server
on
the
internet.
That
somehow
was
also
a
scanning
at
home.
Chart
update,
published
nope.
B
B
B
There
need
to
have
only
index
iam
with
your
zipped
charts.
Nothing
more
does
it,
so
this,
yes,
is
good
enough
to
go.
You
just
register
that
this.
Yes,
under
that
this
years,
you
have
a
index
yum
file,
saying
okay,
I
have
Satyam
files
and
you
can
download
them
from
that
server.
Does
it?
There
is
a
contract
with
home
repository.
We
don't.
A
A
A
Okay
next
thing
on
the
agenda:
pomorie
lib
migrated.
So
finally
they
got
through
all
the
junk
that
needs
a
nap
in
and
we
now
on
a
proud
owners
of
a
new
kubernetes
cigs
library.
I
did
a
bunch
of
junk
just
looking
at
a
vendor
der,
so
it
would
compile
by
Machine
and
then
bump
the
references
to
and
service
catalog
itself.
That
should
be
good
for
the
time
being,
but
okay
take
a
look
at
it.
Just
know
it's
there
under
our
control
now.
A
So
if
we
need
to
change
something
that
we
talked
to
service
brokers,
that's
where
it's
gonna
be
next
thing
on
the
agenda
leak
and
go
routines
and
test.
So
this
is
something
Morgan
mentioned
when
we
merged
the
latest
SVR
seems
like
there's
a
whole
bunch
of
go
routines
that
get
leaked.
They
get
set
up
and
use
and
test,
and
then
we
don't
get
broken
down
so
not
like
not
like,
like
a
memory
leak
that
they're
just
guru,
teens
being
linked
wholly
within
the
test
process
itself.
A
Okay
me
just
something
to
think
about
on
single
or
denomination,
so
you're,
the
only
other
person
who's
aware
of
this.
There
was
a
random
person
who
came
and
asked
us
to
nominate
someone.
I,
don't
really
know
what
to
deal
with.
That
is
I,
don't
know
who
we
would
nominate.
I
was
thinking
nominating
you.
B
A
A
A
A
A
B
A
B
Didn't
see
that
one
okay,
so
there
is
a
comment:
I
thought
that
you
didn't
look
at
it.
Okay
to
me.
What
I
think
we
need
to
figure
out:
okay,
okay,
so,
and
the
agreement
about
that
chart
is
to
rename
the
entry
for
center
log
legassik
a
server
or
something
like
that,
and
please
that
entry
manually
to
also
D
so
to
push
or.
B
B
Okay,
where
is
connected
I.
B
A
A
B
B
B
And
that's
good:
the
old
entry
will
not
be
removed.
This
is
one
problem.
Second
problem
is
that
we
will
not
update
the
old
entry
service
at
work
right
right
now
we
have
all
dot
2.1
and
if
you
want
to
add
it
that
I
think
that
we
need
to
do
that
manually
or
me.
I
know
what
we
can
do
is
to
change
script
responsible
for
pushing
that
I
mean
that
one.
B
A
A
Know,
I,
don't
know,
I,
think
I,
don't
know,
I
think
our
process
might
still
be
screwed
up,
because
let's
say
this
happens,
we
fix
it.
We
cut
0
to
3
and
then
we
merge
the
CD
requests
and
we
have
3
0
0,
and
then
we
need
to
do
something
on
the
branch
we
need
to
make
0
to
4.
How
does
that
0
to
get
cut?
Where
does
that
come
from.
B
So
if
you
will
create
a
tag,
0.2
dot,
4
on
V,
to
branch
on
that
one,
basically,
images
will
be
pushed
with
the
tag
name,
so
0.2
dot,
4,
that's
good
about
the
chart,
use
that
images
and
we'll
push
to
have
repository
with
chart
named,
as
you
have
right
now
so
new.
You,
you
manually
typing
on
keyboard.
No,
no,
no!
No!
Okay,
build
history!.
B
A
A
B
A
B
A
B
I'm,
saying
only
do
that
on
say
only
ones
and
next
releases
will
be
automated
in
the
same
way
as
I.
Do
this
right
now:
okay,
pink
sink
current
situation.
Right
now
we
have
a
problem,
because
what
we
need
to
do
is
to
somehow
remove
the
old
entry
replace
at
a
pH
with
a
okay,
so
I'm
gonna
talk
to
Carol,
oh
I'm,.
A
A
A
B
A
B
Maybe
we
can
just
say
a
little
bit
about
our
work,
our
current
releasing
process.
We
have
a
dedicated
entry
for
old
API
server
on
our
chart
and
say
what
is
different
between
API
server
and
series
that
you
are.
You
don't
have
API
server.
You
don't
have
an
etcd
anything
like
that
thought,
tal
a
little
bit
about
the
immigration
path
right
that
just
introduced
all
of
them
to
our
new
approach.