►
From YouTube: Kyma Core SIG community meeting 20190731
Description
Meeting notes: https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/edit#heading=h.c6h3wzeefpg4
9:20 - Kyma Birthday and t-shirt contest
11:06 - Intro to 1.4 release scope that is scheduled for next week
15:34 - Intro of new Google Service Broker that brings more value than the previous one
22:26 - Our guys are going to present on a few conferences in September
A
Okay,
hello,
welcome
on
our
Korsak
meeting,
I'm
mukesh
and
I
will
be
over
monday
or
not
the
writer
today,
and
also
write
notes,
interesting
topics
on
the
agenda,
but,
as
usual,
we
want
to
first
start
with
questions
and
feedback,
but
because
they
we
have
only
john
on
the
call.
So
I
will
be
even
direct
here
Johnse
any
questions
or
feedback.
B
I
think
a
lot
of
commerce
developers
from
partners
and
customers
are
used
to
running
almost
cloud
locally,
so
one
to
try
to
connect
kima
locally
as
well,
because
otherwise
they
have
to
find
somewhere
to
run
kima
in
the
cloud
and
that
cost
money-
and
it's
not
always
the
easiest
thing
so
I
think
with
the
release
of
1.3
there's
now
all
the
pieces
in
place
to
be
able
to
run
it
locally
fairly
easily.
So
we
have
some
instructions
documented
on
how
to
do
it.
B
A
A
B
A
B
A
A
A
Long-Term
maintenance
of
instruction
is
also
easy
because
you
have
commenting
section
and
then
you
can
also
share
it
in
our
slack,
one
of
the
slack
channels
may
be
general
or
application
connects
or
for
others
to
read
it.
That
would
be
my
recommendation.
I
guess
that's
the
best,
because
it's
close
to
a
say,
P,
so
sa
pinlock
seems,
like
the
best
place
sure.
A
A
B
B
A
C
A
B
Yeah
I
think,
once
once
you
talk
to
customers
and
partners
about
especially
the
sort
of
canary
deployment
stuff
that
you
could
do
with
sto.
That's
they
suddenly
see
the
value
in
that.
Yes,
I
know
that
you
could
do
it
by
you
know
just
altering
the
ISTE
oak
iterations,
but
I
was
just
wondering
if
there
were
any
plans
to
sort
of
have
some
sort
of
UI
in
kheema
to
do
that.
C
B
A
C
More
or
less
that's
the
thing
right,
if
probably
they
will
that's
the
question,
what
will
be
the
abstraction,
for
example,
for
routing
right,
if
in
anything
or
something
the
abstraction
over
the
service
message,
mass
instances
right,
the
eastern
and
other
things,
as
you
said,
then
a
sec
John.
It's
that's
also
the
reason
right.
We
didn't
order
to
client,
but.
A
C
B
A
So,
let's
go
into
the
first
topic
of
the
agenda
so
just
to
remind
we
had
birthday
last
week,
last
Wednesday
one
year
already
of
project
on
the
open
source,
and
there
are
two
really
nice
blog
posts,
especially
one
is
especially
nice
because
I
wrote
it
I,
which
is
about
like
kind
of
kind
of
summarizing
the
last
year,
but
also
there's
a
something,
maybe
even
interesting
for
you
John.
Regarding
any
questions
around
in
native
and
what
Peter
said.
A
So
we
were
kind
of
summarizing
what
we
did
during
last
year,
where
we
failed
to
not
deliver
what
we
planned
and
how
we
won't
want
to
solve
it
in
the
future.
So
this
birthday
posts
about
Kim
and
Kim.
A
dish
is
also
interesting
in
this
in
the
subject,
but
the
most
important
here.
What
I,
also
wanted
to
point
out
is
that
we
have
this
t-shirt
contest,
so
any
contributor
like
Philippa,
and
that
we
mentioned
in
the
beginning.
He
already
contributed
during
the
last
five
days
and
because
of
that
he
will
get
a
t-shirt.
A
So
I
already
had
discussion
with
Anna
from
our
team
and
we
will
extend
the
contest
by
one
week,
so
it's
gonna
run
until
the
almost
the
end
of
next
week.
So
yeah
just
a
reminder
here
and.
C
Topics
and
our
team
helping
the
ori
organization,
even
with
writing,
some
of
that
Qbert
is
controllers
and
so
on,
to
make
it
available
and
kima
much
easier
and
in
the
same
way,
let's
say
in
the
cuber
and
the
equivalent
a
style
that
you
will
be
able
to
to
play
with
that
and
already
do
some
add
some
authorization
scopes
to
your
endpoints
in
the
application
and
so
on.
The
next
big
thing
is:
we
will
release
in
preview
mode,
a
new
component
called
compass,
and
if
you
will
go
blog
post
I
will
send
it
later.
C
You
can
go
to
the
command
Cobra
incubator
project
in
github,
where
the
compass
repository
exists
and
right
now
is
the
incubator,
because
we
just
started
but
more
or
less.
We
already
want
to
expose
the
facility
of
that
thing,
which
is
components,
number
of
components
that
allowed
to
register
manage
applications.
C
C
It's
that
feature
for
hand
broker
where
we
can
extend
service
catalog
with
additional,
offering
that
could
be
installed
in
the
kheema
itself
and
then
the
other
thing
is
some
improvements
in
the
namespace
view
that
much
better
user
experience
Kali
will
be
upgraded
and
will
have
the
single
sign-on
enabled
that
it
will
be
the
same
finish
with
graph
Anna
Jaeger.
Then
we
will
upgrade
the
east,
eon
and
other
stuff
is
the
backup
procedure
will
be
configured
as
a
part
of
the
installation
process.
C
The
new
things
for
the
ascend
KPI
specifications
and
conversion
and
validation
service
will
be
provided
and
as
well
in
the
canadian
for
yeah
we'll
have
that
experimental
function,
controller
that
will
expose
lambdas
from
kennedy
and
that's
the
the
way
we
are
going
to
to
have
a
Kennedy's
serving
as
a
function
component
and
not
go
away
with
with
cublas
in
the
future,
and
that's
it.
You
can
of
course
find
all
of
those
epochs
in
the
Zen
hub.
C
C
C
There
was
a
way
that
they
would
discontinue
the
work
on
that
and,
to
be
honest,
they
they
decided
to
discontinue
who
work
on
that
and
all
of
the
users
that
ready
provision
such
a
broker.
They
got
the
emails
that,
on
the
november
thing
will
stop.
They
will
not
operate
that,
of
course,
all
of
the
classes
that
are
spin,
they
are
there
and
there
is
instruction
what
to
do
with
them,
but,
on
the
other
hand,
I've.
C
That
means
you
can
already
try
it
and
how
it
looks
like
I'm
just
enabled
that's
a
Don
in
one
of
the
namespace,
and
you
can
see
that
we
have
that
that
guy
here,
it's
the
old
one
and
that's
the
new
one
Markus
preview
and
it's
the
same
way
how
to
provide
credentials
for
the
broker
as
before.
But
at
the
end
we
need
to
provide
a
secret
and
during
the
provisioning
of
that,
and
we
need
to
provide
the
name
of
that
secret.
The
details
that
the
add-on
documentation
is
the
same
was
different.
C
They
we
have
really
nice
examples
about
all
of
the
plans
where,
when
to
use
them,
what's
the
use
case
and
so
on
and
even
in
the
details,
we
see
the
detailed
description
for
all
of
the
input
parameters
and
even
for
the
binding
part,
the
response
parameters.
That
means
what
we
watch,
what
we
real
and
in
the
secret
and
then
when
spinning
such
for
example,
Google
storage,
I
will
just
do
that
and
you
see
there
is
a
lot
of
plans
available.
C
C
B
C
A
A
So
it's
yeah
the
link,
I
posted
I
pasted
in
the
in
the
meeting
notes,
but
also
of
course,
you
can
find
it
directly
on
our
project
and
yellows
topic
just
to
show
off
I
hope
you
know
or
not.
We
have
a
on
public
slug.
We
have
open
channel
called
kima
squad
where
we
ya
gather
people
that
want
to
talk
on
public
conferences
around
kima
and
we
finally
have
three
kima
squad
members
going
to
different
conferences.
A
Native
council
members
will
talk
there
or
trigger
mesh.
Founder
will
talk
there,
so
it's
a
pretty
important
event
where
we
will
have
two
to
presentations
and
also
yeah
beautiful.
As
you
can
see
here
on
the
call,
he
will
have
a
presentation
around
hand,
broker
and
service
management
on
a
Holland
summit.