►
From YouTube: Kyma Core SIG community meeting 20190605
Description
Meeting Notes: https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/edit#heading=h.bw9ezmfz6nv4
1:43 - Kyma 1.2 Release
5:06 - KubeCon Barcelona Summary
11:55 - Kyma on the GCP Marketplace
14:48 - Varkes - Mocking Kyma's application connectivity for a faster development cycle
29:04 - Testing Lambda
35:55 - Kyma Community - Decision record template simplification
B
Okay,
welcome
everyone
in
our
like
sick
or
meeting
today
we
have
some
things
to
to
discuss
and
I'm
sure,
and
first
we
have
acute
questions
and
feedback
at
the
beginning.
At
the
end,
that's
if
we,
if
you
have
any
questions,
not
related
to
the
agenda,
we
can.
You
can
already
ask
them
now
when
I
finish
summary,
then
we
talked
a
bit
about
the
release
communities
then
the
short
summary
about
Barcelona
and
then
we'll
show
the
features.
B
The
first
one
is
the
kima
on
the
DCP
marketplace
and
both
all
of
those
three
points
will
be
presented
by
guru.
Bhai
scheme,
then
under
a
scholar,
will
show
us
how
to
do
mocking
the
keema
applications,
connectivity
and
somehow
improve
the
foster
development
cycle
and
the
product
is
called
variks.
Then
first
of
Kitaj
will
show
us
testing
capabilities
in
the
lambda
after
the
features
previous
will
go
to
the
committee
slot
and
on
ago
of
scam
will
show
us
the
simplification
of
the
decision
record
template.
B
D
B
D
Need
to
stop
sharing
and
now
I
will
show
my
screen,
and
you
should
see
the
Kim
approach
a
guy
up
page,
so
the
the
kheema
1.2
release
is
already
announced.
In
the
blog
section
you
see
the
kima
1.2
his
wrist
is
scheduled
on
14
of
June,
and
if
you
click
here,
you
can
see
what
will
happen,
and
so
first
big
feature
we
will
announce,
is
testing
lambdas
in
console
UI.
D
A
lot
of
developers
asked
for
that
so
to
make
it
really
easier
to
test
lambda
so
put
some
payload
and
see
what
will
happen
with
your
code
changes.
This
will
happen
soon.
The
next
feature
is
possibility
to
only
bind
selected
service
classes
of
application.
So
right
now
you
can
have
multiple
API
is
registered
to
the
application
and
if
you
want
to
just
pick
a
couple
of
them
and
make
it
available
in
the
given
name
space,
you
can
do
that
and
it
was
requested
mainly
for
the
security
reason.
D
So
we
can
imagine
that
you
have
admin
ID,
I
and
some
other
API,
and
you
do
not
want
to
put
admin
API
to
any
namespace
to
any
developer.
Next
thing
that
we
will
come
is
improvement
in
installations.
First
of
all,
we
will
have
kima
CLI
as
a
first-class
citizen,
and
we
graduated
silly
CLI
from
incubator
project
into
default
method
to
installing
kima,
and
we
will
also
have
a
couple
of
other
improvements
in
the
installation.
So
right
now
you
know
you
need
to
change
couple
of
configuration
files
to
adjust
them
to
your
settings.
D
We
will
make
it
simpler,
so
default
configuration
will
be
ready
to
use
and
we
will
remove
all
these
set
comments
to
replace
some
placeholders.
It
will
be
really
straightforward.
Another
thing
that
will
come
in
the
next
release
is
support
for
Google
cloud
platform
marketplace
it's
already
there
as
a
preview.
I
will
show
it
one
second
later
so
yeah.
Please
wait
a
bit
a
bit
and
a
couple
of
other
things,
so
we
will
improve
in
the
UI,
creating
namespaces
and
quotas.
D
We
will
have
also
some
nice
links
to
the
api's
and
a
couple
of
improvements
in
eventing,
possibility
to
pass
custom,
headers
and
possibility
to
configure
our
messaging
to
use
something
else
than
our
built-in
nuts.
All
of
the
features
all
the
features
we
plan
for
one
are
linked
here
in
the
and
then
hub,
so
we
can
see
and
explore,
and
yet
just
in
a
week
or
you
will
see
the
new
version,
that's
it
about
first
point
second
thing:
I
wanted
to
share
is
about
cucumber
serrano,
so
I
have
some
short
presentation
about
that.
D
So
keema
team
actually
went
to
cube
con.
We
had
the
booth
there
and
we
had
a
lot
of
interested
interesting
meetings
with
the
kubernetes
community.
This
is
the
location
of
Kim,
of
cubic
on
Barcelona
in
2019,
really
big
nice
venue
and
it
started
they
they.
Before
official
conference,
we
had
a
couple
of
free
conference
events
I
attended
several
as
practitioners
summit
together
with
Ahmed,
and
we
had
nice
meetings
with
key
Native
community,
which
was
also
involved
in
that
summit.
They
had
a
lot
of
trucks
there
other
things
we
did
during
this
cube
con.
D
We
met
a
lot
of
people.
Ackman
and
Lukasz,
had
interesting
meeting
with
creative
and
asking
api
leaders.
Pavel
had
nice
meeting
with
with
kubernetes
dashboard
maintainers
about
our
solutioning
clock
console
and
we
had
also
interesting
meeting
with
jonas
from
light
vent
about
stateful
serverless
and
our
cooperation
inside
akima.
So
a
lot
of
interesting
meeting
we
in
the
community
and
couple
of
others
also
happened.
D
What
also
happened
during
the
cube
con?
What
is
important
for
kima
project
motto,
got
to
sponsors
and
is
now
currencies
or
in
organization
member,
our
first
official
contributor
and
yeah
we've
DK.
They
will
be
the
maintainer
of
service
catalog,
six,
so
yeah
we
have
our
people
in
the
kubernetes
and
yeah.
The
most
important
thing
for
us
was
presenting
c'mon
kima
boof.
D
There
was
a
lot
of
people,
as
you
see,
a
couple
of
pictures
from
the
place
where
the
books
will
were
located
a
lot
of
visitors
and
we
were
doing
well
and
we
had
nice
socks
with
lego
guys
on
the
booth,
a
couple
of
important
things
we
also
took
from
from
sessions
from
keynotes
yeah,
so
just
highlights
from
my
perspective,
during
the
keynotes.
The
most
interesting
one
I
attended
was
from
sermon
guys
that
they
reproduced
Higgs
particle
discovery
on
google
kubernetes
engine
life,
and
they
did
some
nice
processing
of
70
terabytes
of
data
on
the
stage.
D
So
they
did
it
in
five
minutes.
It
was
really
impressive,
but
this
is
here
just
nice
to
see.
This
is
what
what
I
found
the
most
interesting
but
other
things
that
are
hitting
directly
kima.
So
a
couple
of
announcement
and
movements
that
we
will
consider
on
our
roadmaps.
First
of
all,
the
Humphreys
and
was
announced
alpha
1
is
already
available,
and
what
is
the
most
important
thing?
D
Another
thing
which
is
interesting
in
service
mesh
interface,
which
is
another
standard
to
unify
several
service
meshes
right
now,
is
your
console
link
earth
and
they
try
to
put
some
abstraction
layer
on
top
of
service
mesh
with
different
service
meshes
to
simplify
the
Vella
pers
experience.
I
think
this
is
a
good
movement.
Nevertheless,
I
seen
that
Google
and
lyft,
which
are
founders
of
issue,
are
not
active.
Post
participants
but
I
think
maybe
this
will
change
later
on,
but
we
should
keep
eye
on
on
that
thing.
D
Another
thing
that
was
mentioned
many
times
in
many
talks
were
open
policy
agents.
This
is
the
screenshot
from
the
open
police
agent
gatekeeper
project
with
this,
which
is
some
controller
that
is
applying
rules
on
kubernetes
resources,
really
interesting,
I
think
that
which
we
have
some
plans
to
apply
open
police
agents
in
our
in
hema
and
yeah.
This
is
something
that
is
interesting
and
another
point
from
from
from
COO
Burnett
from
cube
con.
D
That
operator
framework
is
right
now,
buzzwords
number
one
and
a
lot
of
people
are
talking
about
that
and
I
think
we
should
also
have
a
look
and
operator
lifecycle,
and
maybe
our
human
installer,
which
is
also
operator
but
not
compliant
with
operator
framework.
We
should
maybe
adjust
it
to
that.
So
that's
my
thoughts
and
yeah
party
was
also
good.
D
E
D
Platform
project
I'm
logged
in-
if
you
do
not
have
this
DCP
project
and
Google
account,
you
can
create
one
and
Google
gives
you
300
bucks
and
credit
for
your
first
project.
So
the
easiest
way
to
start
with
kima
is
really
go
here,
search
for
for
kima,
and
there
is
just
one
result
and
when
you
configure
kima,
you
need
to
just
hit
two
buttons
literally.
So
first
one
is
to
select
the
cluster
you
want
to
want
to
use.
D
You
can
create
new
one,
but
yeah
I
have
already
one
created
and
then
just
click
deploy
button
and
then
installation
of
kima
starts.
And
after
about
15
minutes,
you
will
have
the
cluster
ready.
Of
course,
I
do
not
want
to
keep
you
waiting
and
I
have
already
created
a
nother
installation
created.
So
in
the
end
this
screen
will
look
likes
like
this.
D
You
will
see
the
URL
of
your
kima
console,
email
and
password
for
your
user,
how
you
can
login
and
the
certificate
you
need
to
add
to
your
trusted
certificate
store,
because
yet
in
this
default
installation
we
and
generate
certificates
for
you,
so
you
need
to
trust
them.
So
this
is
just
one
comment
you
should
follow,
which
is
actually
pasted
here.
D
This
comment:
you
need
to
paste
to
the
terminal
and
paste
a
certificate,
and
after
that
you
can
just
navigate
to
this
URL
and
you
see
the
kheema
console
ready
and
you
have
the
cluster,
which
has
such
nice
URL,
which
is
generated
from
your
IP
address
of
your
ingress
gateway.
That's
it.
If
you
were,
there
is
a
video
on
YouTube
channel.
So
in
kheema
channel
you
see
the
schema
installation
on
google
kubernetes
engine.
There
is
a
video
you
can.
You
can
really
check
and
I
talked
here
how
to
how
to
do
that.
Yeah.
B
E
And
thanks
for
the
impressions
from
the
Barcelona
cube
Quan,
it
was
really
a
nice
summary
but
yeah
getting
to
my
topic.
One
key
feature
of
keema
is
that
whole
application
connectivity
so
connecting
enterprise
applications
to
make
them
sadness.
I,
extend
side
by
side,
extendable
and
kheema,
harmonized
interfaces
like
open,
API,
IO
as
an
API
and
then
having
them
consumable
by
our
service.
Catalog,
there's
one
big
key
feature,
and
while
the
development
of
that
functionality,
we
need
to
demo
and
test
that
stuff
from
the
point
or
from
the
FEMA
point
of
view.
E
And
so
we
are
not
so
much
interested
now
in
in
functionality
connected
to
Kemah.
But
so
we
want
to
demonstrate
that
functionality
and
at
the
end
we
have.
We
are
just
missing
a
lightweight
replacement
of
such
enterprise
applications
which
I
can
easily
configure
together,
so
that
I
have
my
very
defined
interfaces
from
that
application.
E
That
I
would
consume
and
kheema
at
the
end,
to
make
tests
and
demos
and
and
to
fill
that
gap
of
we,
we
created
a
small
framework
which
is
located
in
the
incubator
of
kheema
called
Vox,
which
is
a
Greek
for
a
small
ship.
Here
substituting
the
big
ship,
so
the
enterprise
application,
and
so
when
we
are
taking
a
look
on
such
an
enterprise
application.
What
are
the
touch
points
from
kheema
perspective?
E
That
is
mainly
the
the
pairing
logic,
so
the
application
needs
to
pair
with
kima
and
registering
its
API,
so
open
API
as
an
API
IO
a
to
data
specifications,
and
it
also
needs
once
to
send
event
so
the
D
which
you
can
consume
in
your
lambda.
Furthermore,
the
touch
bonds
are
that
in
kima,
I'm
writing
application
logic,
which
wants
to
call
a
pis
on
the
enterprise
enterprise
application
side,
and
so
that
aspects
we
tried
to
mark
in
a
smart
way,
and
so
in
that
framework
here
we
have
five
modules.
Now
it's
based
on
on
node.js.
E
So
one
is
really
this
node
library
just
covering
that
three
aspects
of
pairing
registering
a
pis
and
sending
event.
So
this
you
can
also
use
10
too
low
in
the
library
and
that's
banded
y
is
used
as
a
dependency
in
the
api
server
module
of
Arc's
and
which,
at
the
end,
now
serves
a
REST
API,
which
also
can
be
then
via
a
UI.
So
there's
also
a
cockpit
module
and
we
also
ship
two
modules
to
mark
typical
API
use
cases
or
based
on
open,
API
and
OData
specifications.
E
You
will
get
out
of
a
book
out
and
mark
running
for
that
API
specifications
out-of-the-box
trying
to
mark
as
smart
as
possible
so
for
the
open
API
we
are
using
at
the
end,
an
existing
library,
note
Express
swagger
as
Express
library,
which
is
an
active
project,
and
it's
really
quite
smart,
and
so
really
it
tries
to
a
return.
Smart
responses
when
you
are
doing
a
read
fest,
so
it's
doing
the
full
Rick
fest
meditation.
E
It
tries
to
correlate
to
the
post
and
get
em
methods
for
examples.
When
you
post
data,
then
we'll
return
the
date
on
the
get
endpoint.
If
that
correlation
is
not
possible,
it
tries
to
return
then
static
responses
coming
from
the
example,
definition
in
the
open,
API
or-
and
if
that
is
not
possible,
then
it
just
returns
a
for
the
before
and
for
the
old
data.
We
are
using
the
end
who
data
server
project,
which
is
not
really
active
and
a
bit
sad.
E
E
Let's
take
a
look
at
the
combined
API
mock,
so
that
example
is
serving
a
nope,
maybe
I'm
not
bundling
it
all
together
and
serving
really
the
stuff,
with
a
UI
bundle
and
a
connection
logic
and
to
get
that
functionality.
You
mainly
have
your
food.
Our
API
is
where
you
put
all
your
interfaces,
so
I
have
here
two
of
the
courses
and
schools
yeah.
Well,
it's
just
an
simple
Sega
definition
of
an
API
and
I.
E
E
Takes
a
while
and
just
specifying
where
my
api's
are
located,
which
I
want
to
expose
in
my
mock
and
I
can
provide
here,
the
name
and
descriptions
and
other
information
for
the
keemal
registration
logic.
Nurse
with
that
name
now,
scoots
API
will
be
just
used
for
the
name
of
the
API
when
registering
it
Okemah
site.
E
So
I
have
my
API
definitions.
I
have
my
configuration
and
now
I
have
just
a
very
simple
node
application
and
mainly
create
an
Express
server,
I
instantiate,
the
variks
modules,
which
I
want
to
use
and
I
adjusted
the
modules
MST's
Express
middle
layer
on
my
Express
app
and
then
I'm
starting
the
express
up,
and
that's
it
now.
Let's
have
a
quick
live
demo
for
that.
Let's
go
to
the
readme
of
that
example.
So
of
course,
I
can
just
run
it
locally.
E
Using
NPM
I
can
run
it
locally
using
the
released
docker
image,
but
I
also
can
just
deploy
it
into
a
kubernetes
cluster
and
accidentally
I
have
kima
cluster
running
and
I
will
just
deploy
it
into
my
team,
a
cluster
with
which
I
want
to
connect.
To
so
I
mean
at
the
end,
I'm
here
representing
and
standalone
application
which
I
want
to
connect
to
a
key
map
cluster,
but
my
mock.
Of
course,
I
can
also
run
on
that
kheema
cluster,
so
I
will
just
create
here.
E
That
contains
also
an
API
resource,
akima
API
resource
definition,
with
the
effect
of
that
it's
getting
automatically
exposed
and
accessible.
So
I
see
now
here
my
mocks
namespace
I'm,
going
inside
and
I'm,
seeing
as
well.
First
open
the
pod
running
with
my
excel
with
my
exam,
we
mock
an
API
definition
and
if
I'm,
just
going
now
to
that
which
I
prepared
already
I,
should
get
to
the
UI
of
that
nice
mock
and
what
I
can
see
is
now
here.
The
listing
of
the
defined
API,
so
the
two
to
swagger
definitions
and
so
on.
E
As
an
API
definition,
I
can
browse
inside
I
see
at
the
end
the
the
the
payload
how
it
really
is
getting
registered
on
Chema's,
hired
on
the
application,
connect
or
API
side.
So
I
can
take
really
that
payload
and
executed
directly
to
registered
manually
and
also
I,
have
here
a
link
now
to
the
meta
data
which
is
really
served
by
the
mock
functionality.
And
so
that's
really
know
the
swagger
definition
itself
and
I.
Also
have
you
a
link
to
a
nice
swagger
UI
to
just
visualize
that
API.
E
But
so
now
I
want
to,
of
course,
connected
to
my
kima
cluster,
and
so
let's
go
back
to
the
chemo
cluster.
What
we,
of
course
need
is
an
application,
so
I
have
no
application
at
all
here.
So
I
just
will
create
one
quickly
and
yeah
to
connect
an
application
to
Kim
I.
Need
that
connection
token,
which
I'm
getting
here
from
the
connect
button
I'm
going
to
my
application
clicking
here,
the
connect
button
and
I'm
connected
what
is
now
changing
in
the
UI
is
that
I
can
now
download
the
client
certificate
to
do
the
now.
E
The
same
things
in
a
manual
way.
So
I
can
now
continue
us
to
just
with
curl
and
talk
through
the
application
connectivity
using
the
client
certificate,
and
what
also
happened
is
now
I.
Have
you
register
buttons
to
just
register?
My
API
is
on
keema
side
and
yeah
if
I'm
just
doing
it
going
back
to
keema.
E
It
is
now
popping
up
here
so
now,
I
keep
its
registered
and
what
is
really
nice
now
I
can
and
I
get
a
new
tab
called
remote
API,
and
that's
now
really
representing
the
view
on
keema
sides.
You
know
only
the
two
two
things
which
I
registered,
because
that's
really
the
source
is
coming
from
keema
side
and
I
can
now
you
can
start
modifying
you
and
really
modifying
the
entries
on
keema
side
and
also
deleting
the
things
again
I'm.
E
So
here's
the
delete
button,
so
that's
missing
in
keema
itself,
so
that's
also
not
able
to
manipulate
the
things.
But
so
the
main
point
is
now
I
want
to
just
make
a
half
way
end
to
end
demonstration
of
now.
Let's
really
find
it
to
my
name
space.
Let's
call
it:
let's
take
production
namespace
you
go
to
the
production
namespace,
and
here
now
my
API
is
popping
up
in
the
Service
Catalog
I
can
go
inside
I,
see
again,
my
I
open
API
definition
here
can
play
around
I
can
instantiate
it.
E
Let's
do
it
quickly
with
events,
and
so
here
also
the
I
think
API
gets
rendered
nicely.
I
see
that
there
are
two
events
now
supported
by
my
application:
let's
create
one
instance
quick
and
make
it
consumed
by
lambda.
So
let's
create
chords
test
and
the
body
I
prepared,
of
course,
is
just
printing
the
event
payload.
So
I
want
to
now
just
listen
for
an
event.
E
I'm
just
waiting
a
few
seconds.
Oh
it's
already
running
that
was
fast
because
now
one
feature
as
well
is
what
you
always
need
for
testing
and
demoing
from
the
kima
point
of
view.
Is
that
you
really
want
to
easily
trigger
an
event
from
that
application
side
and
that's
also
supported.
She
ended
Mach
framework.
E
So,
when
I'm
going
to
the
as
an
API
definition
itself,
yeah
I
have
a
section
where
I
can
just
select
an
event
and
the
example
payload
gets
rendered
and
I
can
just
say,
send
event,
and
now
going
back
to
my
lambda
I,
hopefully
can
see
here.
Oh
that
lock
message
so
that
event
arrived
by
the
way
I
can
just
recommend
here.
The
in
line
in
console
looks
really
nice
now
and
will
be
improved
in
the
next
release
as
well
to
have
it
even
more.
E
B
B
C
Some
extends
from
some
stories.
Commerce
stories
based
on
those
events,
and
let's
assume
that
I
would
like
to
build
a
lambda.
That
would
be
me
extending
the
functionality
around
new
customer
creation
in
the
commerce
system,
so
I
will
be
interested
in
this
particular
event.
You
can
see
the
specification
here
customer
created
and
you
can
always
follow
this.
You
can
you,
can
utilize
variks
and
really
mock
the
multi
events
on
the
worker
site
in
order
to
push
events
into
kheema
and
test
lambdas.
C
This
way
we
are
also
planning
to
release
with
1.2
a
feature
that
will
allow
you
to
test
lambdas
without
really
connecting
it
to
today.
Real
events,
so,
as
you
can
see,
I
have
prepared
here
a
short
code,
a
short
lambda
that
will
pick
up
some
events,
data
from
the
customer
created
event
and
but
I
don't
know
if
it
would
be.
If
this
logic
is
correct,
right,
I'm
doing
something
here,
but
I'm
not
really
sure.
C
C
So,
as
you
can
see,
the
only
thing
you
need
to
do
is
to
expose
this
lambda
via
HTTP
I
should
provide
an
HTTP
endpoint
for
sulfur
for
this
function
and
I
will
do
it
right
now,
save
it,
and
now
this
testing
option
is
available
for
me.
So,
as
you
can
see,
my
lambda
is
not
yet
connected
to
any
event,
yet
it's
not
being
triggered
by
any
event
it's
just
exposed
by
HTTP
and
now,
and
what
I
can
see
here?
I
can
see
an
editor
for
the
payload.
So
how
can
I
really
trigger
this
lambda?
C
So
you
can
really
test
some
corner
cases
and
some
malformed
monofin
payloads.
You
can
also
choose
any
of
any
even
from
the
selection
of
events
that
are
available
in
your
namespace,
so
I
can
see
here
all
events
coming
from
the
commerce
system,
because
I
have
a
an
application
bound
to
my
name
space
that
provides
such
such
events.
So,
if
I,
if
I
try
to
find
a
customer
created
event
and
I,
see
I
generated
example
for
event,
so
you
can
you
can
just
use
this
payload
on
or
freely
modify
it
and
send
it
to
the
lambda.
C
C
D
C
B
B
A
We
don't
okay,
perfect,
okay,
so
a
quick
update,
fantastic
community
site.
So,
as
mentioned,
we
simplified
the
decision
record
so
previously
so
far.
If
you
would
like
to
create
an
issue
or
for
request,
and
it
would
require
a
decision,
so
they
separate
decision
record
had
to
be
created
at
the
moment
it
has
been
merged.
So
if
you
would
need
the
decision,
you
just
create
a
new
issue
with
a
type
of
decision
record
and
the
preview.
So
all
the
parameters
are
there.
The
parameters
also
has
been
shortened.
A
So
we
basically
simplified
that
template
and
also
if
you
would
like
to
create
the
pull
request,
there
is
no
no
such
a
template
for
the
full
request,
because
it
was
not
able
to
create
it
in
the
github
itself,
but
in
that
case
you
would
need
to
just
copy
this
table
into
the
pull
request
and
proceed
with
that.
Of
course,
please
remember
that
always
you
need
to
assign
the
label
decision
to
process
your
decision
and
that's
it
for
my
site.
B
B
We
need
to
look
into
our
board
to
do
a
star.
Trash
I
already
know
that
there
is
nothing
right
now,
but
to
be
honest,
we
have
upcoming
planning
soon,
and
we
also
need
to
organize
a
bit
better.
Our
road
map
and,
as
you
already
know,
that
in
the
quadric
IO
there
is
a
road
map
and
some
things
will
arrive
to
the
seeker
as
well
and
III
think
that
next
time
we'll
have
more
items
to
talk
about,
but
that
step.