►
From YouTube: Kubernetes SIG Service Catalog 2019-8-26
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
B
Yeah
we
created
the
V
zero
point
to
a
branch
and
we
did
some
changes
to
the
release
pipelines
and
we
did
in
fact
every
is
zero
point
two
point:
two:
if
I
remember
correctly,
with
different
I
mean
we
just
tacked
it
so
so
it's
just
attack
not
a
get
robberies.
In
fact,
and
we
have
all
the
artifacts
appended
with
the
V
point:
zero
to
statics
in
place
and
we
tested
it
today
and
it
worked
works.
B
So
I
guess
the
the
the
first
part
is
of
the
transition
is
over
more
or
less
I
would
appreciate
if
you
could
take
a
look
on
what
we
did
and
and
see
if
it
fits
with
us
and
yeah
I
I
hope
that
whatever
she
would
join
us
so
because
I
guess
she
had
some
ideas
about
the
next
steps
like
evaluating
reviewing
this
CR
D
Brown
is
here
before
requests
and
proceeding
with
the
whole
transition,
but
knowing
yeah.
The
point
is
that
the
the
first
step
I
think
was
finished
successfully.
So
so
it
looks
good.
B
C
B
Yeah
yeah
yeah,
sorry
yeah,
we
try
to
I
mean
you
can
see
it
on
Travis.
All
steps
were
finished
successfully
so
and
we've
confirmed
that
way
and
in
a
storage
on
mgcp
and
I
sure
all
those
artifacts
are
in
place
because
there
is
I
guess
as
we
cut
as
this
post
to
se,
cut
is
pushed
to
Azure
and
some
other
artifacts
are
forced
to
them.
B
B
D
B
D
A
D
0,
although
to
the
to-
and
basically
it
went
really
good,
what
we
can
do
right
now
is
to
just
create
a
official
release
on
the
github
just
to
select
the
proper
tag
artifacts
already
in
place.
So
it's
good
to
go.
We
already
tested
that
we've
key
clusters.
We
created
the
commenter's
we've
1.12
version
and
I
execute
the
board
through
steps
just
to
create
an
instance
or
is
a
rocker
creed
instance
binding
and
etc,
and
it
work
we
without
any
problems
and
about
the
next
steps.
D
I
think
that
we
already,
we
already
confirmed
that
we
can
release,
move,
API
and
series
and
right
now,
what
we
can
do
is
to
just
work
on
the
test
that
we
have
one
per
request
about
refactoring
the
test
it
just
this
damn
last
one.
So
we
can
just
review
that
you
already
as
far
as
I
know,
Jonathan.
You
already
give
the
a
proof
level
for
it.
So
I.
A
Don't
know
I,
don't
normally
have
any
insight
how
you
guys
work
on
this
stuff.
Like
did
you
actually,
where
helped
work
on
that
for
quest
at
all,
or
was
it
just
I
forget
you
submitted
it
because,
like
I
would
like
another
a
set
of
eyes
on
it,
but
Morgan
doesn't
have
the
time
to
take
a
look
at
it.
I
don't
know
if
you
want.
D
Problem,
okay,
so
I
take
a
look
on
it
and
basically,
what
you
can
do
is
to
just
review
the
the
main
pre
quest.
I
think
that
we
can
just
check
if
there
is
no
conflict
with
them
with
the
current
files
on
the
master,
because
I
know
that
we
merge-
and
that's
one
thing
I
want
to
talk
about-
is
the
end
to
end
testing.
But
after
after
all,
oh
so
we
can
go
through
that
huge
for
requests
about
changing
back-end,
for
storing
custom
resource
and
I.
D
D
It's
basically
only
only
mentioned
that
current
milestone
will
use
the
admission
webhooks
with
the
Siri
approach.
So
basically
we
can
merge
it
directly
to
the
master
branch,
because
you
can
start
work
with
the
series
on
the
master.
Thanks
to
that,
because
we
have
already
needy
dedicated
v2
branch.
So,
as
you
can
see,
when
you
right
now
register
the
SV
cut
repository,
maybe
I
will
just
show
you
that
normal
view.
D
If
you
register
the
service
network
repository,
then
you
can
select
between
old
version
v2
and
the
new
one
from
current
milestone
this
year
implementation,
but
there
right
now
we
to
work
on
it
to
make
working
so
yeah.
As
you
see,
as
you
can
see,
this
mention
about
instances
katalk
from
the
master
branch
supposed.
D
B
C
B
D
A
D
We
all
I,
said
I
already
tested
that,
if
you
want
to
I
can
even
provide
you
an
instance
about
the
DGK
cluster,
with
the
u.s.
surgical
log
installed
on
it,
yeah
no
problem,
okay
and
okay,
and
basically
because
one
prickers
was
already
merged
about
the
end-to-end
testing.
I,
don't
know
if
you
took
a
look
on
it.
D
So
if
you
check
basically
what
I
did
is
to
create
a
script
just
for
creating
the
commenter's
clusters
in
kind
kindness,
the
kubernetes
in
docker,
then
we
are
just
executing
make
a
suitable
image.
So
we
are
building
circle
up
from
sources.
Then
uploading
that
image
directly
to
our
cluster
using
kind
load
comment.
Then
we
are
installing
service
catalog,
using
the
chart
from
given
source
and
executing
in
2004
ow
rough
plant.
The
pre
quests
with
the
proper
scripts,
was
already
merged
and
collapse
all
that
thing
and
go
directly
to
that
script.
D
So,
as
you
can
see,
we
just
installing
the
kind
home
then
creating
cluster
insane
killer,
deploying
the
latest
catalog
version
from
given
request,
basically
from
sources
preparing
data
for
tests.
Basically,
that
means
that
we
are
creating
the
because
for
end-to-end
test
right
now.
We
are
using
the
UPS
broker,
probably
it
should
be
changed
in
in
future
and
we
are
just
executing
into
n
test
so
scripts
already
match.
What
do
we
should
do
right
now
is
to
merge
pipeline
for
that?
D
It
was
already
reviewed
by
Morgan
and
also
by
our
technical
writer,
because
I
changed
some
markdown
files
and
one
thing
what
I
did
was
that
I
moved
I
removed
the
Jenkins
folder
all
those
scripts,
because
there
was
outdated
those
scripts
and
what
I
did
I
also
merge.
Two
things:
the
Travis,
folder
and
Jenkins
scripts
to
one
single
folder
called
see.
I
already
talked
about
that
with
you
on
slack
and
right
now.
What
we
have
on
the
master
branch
is
to
have
only
one
dedicated.
D
Dedicated
folder
just
for
our
SIA
I
staff.
So
what
do
you
have
here?
We
have
a
public
release,
script
published
on
chart
script
and
executing
entrance
test.
Probably
we
can
we
add.
Next
one
run
regression
test.
We
already
have
app
requests,
not
know
the
request,
but
source
code
prepare
for
that,
and
one
thing
was
only
that
I
renamed
the
one
thing,
because
I
also
didn't
know
why,
but
under
test
folder,
as
you
can
see,
it
was
directly
under
test
folder.
D
There
was
the
script
for
uploading,
our
charts,
so
I
just
move
it
under
CI
and
name
it
publish,
hunt
chart
because
this
is
basically
what
it
is.
It
was
just
for
a
KTVT
cloud
and
publishing
our
chart
so
I
just
clean
up
that
stuff
at
the
in
the
CID
threat,
so
yeah
I
will
just
send
that
request
on
the
slug
and
you
can
take
a
look
on
it.
B
D
Just
enable
the
end-to-end
tests
and
those
end-to-end
test
would
be
executed
both
on
the
master
branch
and
on
the
v2
so
because
it
there
are
just
and
to
Alan
test.
So
they
don't
know
anything
about
internet
implementation,
okay,
yeah,
let's
that's
it
from
from
my
side
and
maybe
the
last
update
from
my
side.
It's
about
the
will
find
it
about
the
committee
meeting
I
attend
that
one
and
I
can
share
with
you
only
wanna
be
recording
and
also
the
slide
deck
that
I
that
I
prepared.
So
everything
really
go
into
that
now.
Okay,.
D
A
D
D
D
A
A
A
D
D
C
D
What
do
we
already
did
on
the
v2
branch?
We
changed
the
chart
to
refer
to
the
newest
version.
We
created
attack
on
that
comet
and
push
it
to
the
upstream.
Thanks
to
that,
the
Travis
execute
that
build,
and
we
have
basically
our
images
on
quay
and
chart
already
in
place
on
G
cloud
DCP
site.
So
what
we
can
do
is
to
just
create
a
github
release
because
part
artifacts
already
in
place.
So
what
we
can
do
right
now
is
to
just
over
the
tag
basically
to
a
new
release
Jabba
just
by
selecting.
A
D
A
D
So
we
didn't
we
right
now
we
didn't
announced
that
release,
so
we
only
did
it
somehow
just
by
creating
attack
and
releasing
the
artifact,
but
we
didn't
create
a
tree.
So
no
one
who
watched
that
repository
didn't
receive
a
notification
and
we
also
didn't
send
any
message
to
to
to
to
Google
group
about
it.
Oh
yeah,
we
can.
We
can
just
so
that
was
my
question
when
we
want
to
do
that,
you
know
sure
way,
so
just
cut
the
Credo
release
and
send
that
out
to
our
mailing
list
mm-hmm.