►
From YouTube: Kyma Core SIG community meeting 20190814
Description
Meeting notes: https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/edit#heading=h.j6shptlgen22
A
Okay,
thank
you
for
joining
our
bi-weekly
Korsak
meeting
today.
I
will
be
your
moderator,
a
TV.
She
will
help
me
in
taking
the
notes-
and
please
add
yourself
to
the
attendees.
If
you
have
not
already
added
yourself
there
and
at
the
beginning.
Maybe
if
some
of
you
have
any
questions
or
feedback
from
the
previous
core
meeting
or
from
the
previous
activities
taking
place
on
Pima,
you
can
do
it
now
or
after
we
finish
our
agenda
topics.
You
can
also
anytime,
stop
us
and
ask
questions
about
each
of
the
items
there.
A
The
first
topic
we
can
start
with
is
about
female
1.4.
It
was
released
and
last
weekend
you
can
find
recording
on
air.
You
can
find
their
release
re
on
github,
otter,
PK
already
previously,
and
the
previous
course.
It
gave
a
detailed
description
of
what
to
expect
in
this
release.
We
have
a
couple
of
new
interesting
components
like
Oreo
2,
and
we
have
a
as
usual
the
regular
and
enhancements
and
new
feature
that
we
have
added,
which
you
can
all
read
about,
and
either
in
the
release
mall
itself
or
on
our
kima
project.
A
B
Okay,
I
hope
that
you
can
see
it.
I
should
see
the
Akuma
yes
and
that's
okay.
So,
basically,
today
I
want
to
show
you
our
new
feature
that
we
added
for
the
Akuma
1.4
and
that
we
start
with
a
little
bit
of
a
background
for
those
who
don't
know.
In
keema
we
have
a
component
called
Helen
broker
and
that
guy
is
responsible
for
exposing
hunch
art
in
the
Service
Catalog
views.
B
So
if
you
go
to
the
catalog
UI
there
and
you
can
see
some
charts
and
to
do
so,
the
hand
broker
use
the
console
the
add-ons
abstraction
that
abstraction
gives
you
ability
to
add
additional
information
about
request,
information
which
are
used
to
convert
hand,
chart
service
class,
for
example,
the
information
about
the
documentation,
some
plans
and
also
the
input
parameters.
It's
quite
easy
and
at
the
beginning,
those
bundles.
Those
add-ons
was
where
fetched
from
the
remote
repositories.
Don't
remote
repositories
should
be
in
HP
format.
B
So,
basically,
you
have
a
some
HP
server
which
serves
static
content
there.
You
have
floated
your
zip
add-ons
with
additional
index
and
that
you
are
a
URL.
You
registered
in
the
hand
broker,
but
we
have
a
feedback
that
it's
not
too
easy
to
have
a
server
with
that
compressed
bundles
because
mostly
our
user
just
have
a
git
repository
with
add-ons
in
a
archived
form
like
a
directory
where
you
have
your
chart
and
he'll
additional
information
about
it
and
that's
all
they
don't
want
to
take
care
of
raising
that
and
having
a
shop
server.
B
Because
of
that,
we
added
support
directly
for
there
for
any
git
repository
that
you
can
have.
Basically
in
the
git
repository
you
should
have
directory
of
your
bundles
and
simple
index
as
it
was
in
the
previous,
but
when
you're
defining
the
world
for
that,
you
should
specify
additional
traffic's.
In
that
case,
you
should
use
the
geet
prefix.
Then
you
should
provide
URL
to
put
on
your
repository
and
after
double
slashes
secesh.
You
should
provide
path
to
your
index
that
you
want
to
register.
It
is
really
easy.
B
I
can
show
you
that
on
our
climate
cluster,
let
me
just
copy
that
example:
I
can
go
to
the
audence
configuration
view,
add
new
configuration
and
there
in
a
URL
just
provide
the
URL
that
URL
can
be
always
copied
from
your
UI
on
a
github.
You
can
copy
that
then,
after
that
last
flashes
I
provide
the
path
to
the
our
index.
In
my
case,
it
will
be
placing
an
add-on
directory.
I
will
choose
the
index
iam
with
acceptance
test.
So
in
that
case
it
should
add
me,
one
bundle
called
acceptance
test.
Let's
do
it.
B
Besides
the
normal
configuration,
we
have
our
git
repository
when
we
go
back
one
more
time
to
our
catalog
view,
then
I
after
a
couple
seconds,
I
should
see
new
bundle
called
testing
acceptance.
Let
me
give
it
doesn't
few
seconds
before
we
proceed.
I
can
also
mention
that
before
you
can
also
specify
the
reference
you
can
point
for
branch
name
for
tag
and
also
for
some
commit,
but
it's
really
useful.
If
you
have
some
revision
on
your
git
repository
and
let's
check
if
it
was
added,
ok,
let
me
check
if
the
edition
was
correct.
B
One
yeah
I
can
see
I
have
a
typo
here,
so
we
just
remove
it
and
copy
it
one
more
time,
because
the
pub
was
incorrect,
so
basically
one
more
time
copy
that
URL
get
prefix
double
slash
this
one
more
time
the
full
path
to
our
index
IAM.
In
a
previous
example,
I
skipped
the
add-ons
directory
so
once
then
a
full
path,
one
more
time.
Okay,
it
was
added.
So
let's
validate
a
URL
yeah
that
why
it's
a
correct
one
go
to
main
space
and
not
a
couple
of
seconds.
It
should
be
visible
here.
B
What's
more,
I
can
also
spoiler
that
we
add
the
support
for
additional
protocols
like
as
free
DCs
and
so
on.
So
besides
the
get
prefix,
you
will
be
able
to
specify
the
as
free
get
taste
and
stuff
like
that
and
then
provide
the
URL
for
your
others
and
also
in
the
future.
You
will
be
able
to
also
provide
Europe
for
your
private
repository
right
now.
We
don't
have.
We
do
not
support
any
authorization,
but
probably
in
the
next
milestone
or
in
the
next
release.
B
A
A
For
that
specific
target
and
on
the
next
release,
we
are
combining
forces
with
the
rest
of
the
community
on
Canada
of
0.9
and
specifically
for
the
eventing
part.
We
started
discussing
what
are
our
main
targets
that
we
want
to
achieve
in
order
to
have
what
can
be
replacing
our
currently
even
bus,
which
is
a
new
model
and
eventing
that
is
called
the
broker
trigger
and
to
have
a
production
ready
broker
ticker.
A
Okay,
the
next
agenda
item
is
about
a
new
feature
that
we
added
in
kima,
which
we
wanted
to
give
you
a
small
demo
about
which
is
supporting
cloud
events
specifically
the
version
0-3
of
the
specs
of
cloud
events,
because
also
we
wanted
to
have
some
feedback
from
the
community
about
the
desire
of
migrating
from
the
our
proprietary
protocol
to
cloud
event
or
our
custom
protocol
to
our
cloud
events
protocol
and
based
on
that.
Let
me
give
you
a
brief
overview
about
currently
this
used
to
be
our
protocol
for
publishing
events
from
an
external
solution.
A
We
had
our
own
headers.
Where
that
are,
we
can,
you
can
say,
cloud
event
inspired,
but
they
are
not
strictly
a
cloud
event
compliant,
and
this
was
all
under
v1
path,
as
what
we
did
is
that
we
added
a
v2
API,
which
you
can
use
to
publish
your
own
cloud
events
compatible.
That
also
gives
you
the
whole
freedom
to
use
whatever
client
you
want,
for
example,
cloud
event:
has
its
own
go
and
Java
SDKs
that
you
can
use
to
send
cloud
events,
and,
among
other,
is
the
case
that
you
can
find
under
the
cloud
events.
A
Let's
see
yeah
there
I'm
just
showing
the
list
of
the
list
of
logs
from
this
lambda
and
I'm,
using
a
very
simple
go
application
which
you
can
see
on
the
right
on
the
left.
This
go.
Application
basically
uses
the
certificate
that
is
generated
and
paired
with
the
application
to
send
cloud
event
to
this
cluster,
and
it
is
using
the
is.
The
go
is
decay.
Cloud
event.
Go
is
decay,
this
is
provided
by
them
and
it
says
very
simply
just
creating
an
event
object.