►
From YouTube: Kubernetes SIG Service Catalog 2019-9-23
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
B
Not
only
basically
the
story
about
the
immigration
tool
guidelines
so
documentation
and
also
script
that
will
be
used
for
CI
pipeline
I'm,
still
working
on
fixing
unit
tests.
I
think
that
there's
some
back
on
our
implementation,
but
basically
there
is
a
lot
of
five,
so
you
can
already
check
it
and
check.
Also
documentation.
I
already
described
this
scenario
that
we
implemented
for
migration
path.
It's
already
optimatus,
when
you're
using
hum
charge,
then
it
will
be
done
basically
by
by
hell.
It's
also.
You
don't
need
to
do
anything,
but
of
course
there
is
also
documentation.
B
Okay,
so
basically
do
that
script
will
create
a
kind
cluster,
so
in
the
same
way
that
we
have
already
fought
it
and
to
interesting,
then
install
service
catalog
from
the
latest
APA
server
release.
So
in
our
case
it
will
be
from
dedicated
entry
on
our
ham.
Shard
then
create
sample
data
I
mean
that
serve
some
service
brokers,
some
service
instances,
every
service
catalog
using
upgrade
and
then
execute
test
check.
B
A
B
A
B
Lot
of
comments
on
that
request,
as
you
can
see,
there
is
11
comets
commits
yeah,
commits
commit
sorry,
I'm,
sorry
and
I'm
thinking.
If
you
are,
if
we
are
able
to
use
rebei,
rebase
and
merge
option
because
right
now,
all
those
comets
will
be
squash.
Squash
squashed
squashed
into
one
commit,
and
you
do.
It
will
be
only
on
me
and
I
think
that
maybe
even
for
others
it'll
be
easier.
If
you
can
check
in
a
blame,
when
you
execute
blame
action,
you
can
check
the
real
outer
of
that
coat.
B
A
B
You
think,
because
I
already
saw
that
on
on
the
last
request,
if
this
year,
this
implementation-
a
lot
of
people
working
on
that.
But
then
there
is
everything
it's
on
me
right
because
ties
basically
use
the
squash
squash
and
merge
strategy.
But
what
we
can
do
is
to
just
maybe
at
whole
trouble
and
maybe.
A
B
B
So
yeah
and
then
one
I've
already
talked
about
it.
Basically,
maybe
you
can
just
finish
that
story.
I
already
show
you
that
guys
from
sick
up
machinery
and
they
created
the
beginning
release
with
additional
suffix,
called
beta
dot,
zero
and
I'm
thinking.
If
we
want
to
do
that,
do
that
the
same
for
us,
so,
for
example,
we
can
merge
the
pull
request
with
the
immigration
tool
and
documentation
so
once
for
and
then
when
we
cut
a
new
release,
we
want
to
do
that
like
at
normal
one
or
we
want
to
do
a
pre
release.
I.
A
B
So
I
think
the
same,
because
it
would
be
quite
safe
for
us
to
just
announce
that
we
have
a
prayer
release,
it's
a
better
release
and
after
testing
that
we
can
cut
the
normal
release,
saying
that
is
a
stable
one
and
everyone
can
use
it
good.
Okay.
So
now
it
maybe
write
it
down
that
we
agree
on
I.
Think.