►
From YouTube: Kyma Core SIG community meeting 20190508
Description
Meeting notes: https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/edit#heading=h.rp8p1aj24szr
A
A
Hello,
hey,
I'm
mukesh.
I
welcome
to
our
karthik
meeting
yet
another
one
hard
to
say
which
one
in
row,
but
we
will
not
stop
with
this
one
for
sure.
I'm
your
moderator
today,
I'm
replacing
one
of
our
guys
from
the
sick
because
he's
attending
quite
important
workshops
and
I'm
supported
by
mattel
who
had
a
dentist
visit
today,
so
he
cannot
say
too
much,
but
at
least
he
can
type
with
his
fingers.
A
A
B
A
So
1
1
it's
coming
out
next
week
and
with
1
1
I'm,
not
able
to
give
you
a
precise
reply,
but
I
can
point
you
to
release
notes
that
are
being
prepared
and
they
are
public
leaders.
A
public
PR
opened
for
the
release
notes.
So
you
can
see
what,
in
one
one
so
I'm
gonna,
send
you
a
link
to
a
chat
window
if
I
know
how
to
do
that.
A
100%
sure,
what's
changing
for
sure,
we
are
upgrading
to
the
latest
PNA
TV
venting
and
for
sure
there
are
no
changes
in
the
key
native
if
it
comes
to
the
in
server
less
integration,
so
but
you're
probably
the
most
interested
with
the
server
list,
because
we
still
are
using
cublas
as
a
engine
for
several
s.
We
did
not
switch
to
key
native
yet
because
we
yeah
we
lost
several
weeks.
We
are
most
focused
on
releasing
one
zero.
A
Preview
of
what's
gonna
go
come
in
one
to
really
scope,
but
I
know
from
the
slack
channel
in
this
public
slack
channel
that
Johannes,
that
is
owning
the
server
less
topic
he
wants
to
now
work
with
for
one
to
release
on
yet
a
CR
D
for
functions
that
is
using
key
native,
but
more
details
will
come
once
we
finalize
this
code
that
will
announce
next
week.
What
the
even
think
point
of
view
it's
you're
already
using
key
native
eventing,
it's
not
hidden
behind
the
feature,
flag
and
I,
say
channel.
A
Okay,
let
me
go
back
to
the
agenda
and
anyone
any
questions.
A
A
It's
we're
gonna,
cancel
it
because
major
ET
of
actually
all
chairs
from
the
Korsak
we're
all
going
to
keep
on
Barcelona,
and
we
are
not
the
only
ones.
There
are
many
other
product
owners
going
and
developers
so
Andy.
Of
course
the
core
seek
should
happen
during
the
cube
con,
so
we
will
cancel
it
because
we're
you
can
imagine
that
he
wants
to
meet
with
our
users
directly
at
Krypton
and
not
do
it
through
zoom.
A
But
of
course,
if
you
see
that
there
are
some
important
topics
that
we
should
discuss,
you
would
like
to
discuss
with
us,
then
we
can
do
some
ad
hoc
core
meeting
next
week
or
in
or
a
week
following
after
the
and
the
cube
come.
But
the
most
important
is
we're
not
moving
at
the
meeting
were
simply
cancelling
it
and
the
next
one
is
going
to
be
two
weeks
after
keep
calm.
A
Stuff
about
cute
Khan
interesting
is
that
there
are
many
owners
of
different
quemic
up
abilities,
going
from
like
Jake
from
Sarah,
less
Gaara
from
inventing
even
I'm
going,
and
there
are
also
awesome
engineers
going
with
us
like
Mattel,
that
is
taking
notes.
That
is
not
rewriting
service
catalog
to
use
custom
resources
or
poco
sheets.
That
is
a
brain
behind
the
graphical
layer
that
we
have
in
keema.
So
in
case
you
have
some
branch
or
entire
company
based
in
Barcelona.
A
A
So
that's
it
if
it
comes
to
keep
calm
and
next
topic
from
our
agenda,
we
want
to
do
two
features
preview
for
you.
The
both
of
them
can
be
done
by
me.
One
of
the
features
it's
had
a
CMS
and
that's
a
component.
That's
a
functionality
that
is
I
will
available
already
with
1.0
release.
We
just
did
some
few
bug
fixes
for
this
release,
so
the
whole
functionality
that
I'm
gonna
show
to
you
is
already
now
is
gonna,
be
for
sure
available
with
one
one
and
the
other
feature
I'm
going
to
show.
A
A
You
should
not
be
worried
because,
as
you
know,
in
kimahri
value
to
an
installation,
according
to
local
installation,
to
have
seamless
development
process
and
in
place
as
well
on
your
local
machines,
so
I'm
gonna
have
everything,
of
course,
on
my
opened
on
my
local,
but
on
latest
master.
So
wherever
I'm
showing
is
already
going
to
be
in
the
release
and
yeah
I,
guess
that's
it
if
it
comes
to
the
disclaimer.
So
let
me
jump
to
the
first
topic
so
headless
CMS.
A
So,
of
course,
you
need
to
have
some
background
to
the
topic.
What
has
the
CMS
is,
so
it's
AI
CMS
that
enables
you
to
provide
content
independently
from
the
presentation
layer,
which
basically
means
that
you
can
provide
content
independently
and
then
consume
it
in
any
application
through
the
API.
So
it's
pretty
known
concept.
A
So
it's
a
Service,
Catalog
and
home
broker
that
is
using
headless
CMS
to
provide
documentation
for
services
which
are
shirts
through
the
Service
Catalog
application,
connector
that
you
probably
also
know
that
is
used
to
expose
external
applications
inside
the
quemic
raster
and
yeah
application
connector
during
the
registration
also
uses
headless
CMS
to
save
all
these
specifications
and
documentation
for
the
applications
and
last
but
not
least,
is
our,
of
course,
console
UI,
where
we
consume
through
the
API.
This
content,
in
the
context
of
the
Service
Catalog
and
also
in
our
standalone
documentation
UI.
A
So
that's
if
it
comes
to
the
dependencies.
The
architecture
is
the
most
interesting
I
think,
because
this
headless
CMS
component
is
I,
would
say:
kubernetes
native,
it's
based
on
custom
resources
in
the
backend.
We're
using
another
component
of
ours,
which
is
assets
or
I,
will
not
spend
any
time
on
explaining
what
assets
store
is
I
can
just
tell
you
that
at
the
end,
it's
a
kind
of
file
storage
based
on
you
know.
The
most
important
is
the
headless
CMS.
A
A
Like
we
do
with
the
application
that
the
content
describes,
so
in
other
words,
we
wanted
to
be
able
to
provide
a
description
of
the
deployment
together
with
the
documentation
in
the
same
way
with
just
one
single
cube,
CTL
applied,
so
in
other
words
explaining
what
was
the
motivation
to
do
this
component
and
work
on
it
and
that's
a
core
sick.
So
let
me
just
now
really
jump
into
the
quick
demo
and
not
talk
about
just
theory,
so
quick
walkthrough,
where
the
headless
TMS
is
consumed.
As
I
mentioned,
it's
a
Service
Catalog.
A
A
You
can
see
the
whole
documentation
for
keema
inside
console
for
a
given
version
of
the
console,
and
here
at
the
bottom
you
can
already
see
that,
right
before
this
quick
demo,
I
modified
the
view
a
bit
I
added
additional
topic
to
the
headless
EMS,
which
is
the
sto
documentation
that
I
could
I.
Could
basically
take
the
official
sto
markdown
files
and
add
them
inside
keema
and
embed
them
in
this
documentation
UI
but
yeah?
Let
me
quickly
show
you:
how
I
did
it
so
short
break,
so
I
can
share
a
terminal.
A
A
A
D
A
C
A
Ui
is
loaded
through
the
custom
users,
and
you
can
see
the
two
new
resources
from
it
to
use
concepts
and
previous
guides,
which
are
still
pending
and
I
can
tell
you
in
the
meantime,
while
they
are
pending,
I
can
tell
you
how
do
I
actually
know
what's
created
under
the
hood
and
how
do
I
know
if
everything
works
fine
and
how
come
we
know?
What
is
the
exact
location
of
the
files
after
and
the
the
resource
changes
the
estate
to
ready?
A
So
what
I
do
now,
as
I
mentioned
at
the
beginning
and
at
the
end,
cluster
Docs
topics
and
they
are
reflected
as
the
resources
in
our
dependency
called
asset
store
in
this
case.
In
case
of
this,
this
examples,
its
cluster
asset
and
I,
know
what
cluster
acid
was
created
for
my
specific
topic
in
this
case.
It's
it's
your
security.
A
A
A
A
A
Perfect,
so
you
could
not
see
the
refresh
operation
but,
as
you
can
see,
after
I
did
the
refresh
in
the
UI
I
got
a
new
section
called
for
me
to
use
and
guides
in
concept,
as
I
mentioned,
what
I
expected
before
and
all
the
documents
that
were
in
a
given
source
package
with
the
markdown
files
and
the
issue
that
I
created
344.
It's
also
here.
So
it's
pretty
easy
to
really
build
documentation,
but
of
course
one
disclaimer
I'm,
just
showing
it
basing
on
Eastern
and
Prometheus
example.
A
C
A
But
of
course
the
headless
image
supports
a
way.
The
the
asset
store
supports
a
way
of
adding
custom
custom
parsers,
let's
say
of
the
of
the
content,
so
you
can
even
modify
it
work
through
the
markdown
files
and
remove,
for
example,
the
the
content
that
is
not
nice.
Not
everything
is
out
of
the
book,
supported
and
well
documented,
but
that's
technically
possible.
A
You
can
play
with
it,
and
especially
yes,
please
play
with
it
and
give
us
feedback,
because
there
are
totally
mixing
different
ideas
in
our
heads
how
to
go
forward,
especially
with
Doc's
UI.
If
we
maybe
should
make
it
available
for
you
in
the
way
that
you
can
build
your
own
standalone
and
documentation
page
like
this
one.
So
yeah,
that's
one
of
the
features,
any
questions.
A
A
A
So
you
can
see
there
say
this
is
an
example
that
is
officially
published
by
us.
It's
not
an
example.
It's
actually
official
bundle
repository
that
is
sharing
ready,
service
and
Google
cloud
service
broker
and
the
our
Joe
service
broker.
So
at
the
end,
you
can
configure
helm
to
fetch
those
informations,
those
those
bundles
from
several
different
repositories.
A
So
not
only
the
official
report
that
we
have
when
you
get
email,
but
you
can
provide
your
own
repos
with
your
own
bundles
and
that's
why
we
work
on
working
on
the
UI,
so
you
can
all
say
class
sir
kima
kima's
operator.
We
have
one
unified
UI
when
you
can
see
the
list
of
all
the
configured
repositories.
So
you
know
exactly
what
is
registered
and
available
for
your
users
in
kima
in
the
service
catalog.
A
So
this
view,
as
you
can
see,
that's
a
at
the
end
list
of
the
configurations
with
the
repository
URLs
the
default
one
is
that
I
already
mentioned
to
you,
so
the
one
that
brings
those
three
services
like
readies
or
the
edger
or
service
broker,
and
now
I
can
show
it
to
location
where
it's
taking
taken
from.
At
the
end,
it's
any
HTTP
server,
HTTP
server,
but
here
you
can
see
how
we
solved
it
for
our
kima
bundles,
and
so
we
simply
release
them
and
make
them
available
through
the
release
feature
in
github.
A
That's
the
one
that
is
registered
now
by
default
with
every
installation,
and
you
should
never
remove
it
from
the
configuration.
But
I
can
show
you
how
I
can
reduce
their
additional
bundle.
Repo
I
can
tell
you
that
this
one
consists
just
one
bundle.
It's
called
test
bond
test
service
and
I
can
show
you
how
I
do
it
and
under
the
hood
it
were
config
maps
at
the
moment.
A
As
you
can
see,
the
whole
view
is
based
on
WebSockets,
so
the
feedback
is
pretty
quick.
All
works.
Fine.
Let
me
now
go
to
the
catalog
before
I
showed
you,
three
services
were
available
in
the
catalog
now,
if
there
should
be
four
okay,
so
we
can
see
this
testing
bundle
and
the
showcase
bundle
is
quickly
available
through
just
simple
configuration,
and
these
are
all
the
add-ons
that
I
have
currently
and
configured.
A
You
can
see
now
that
the
catalog,
if
you
got
kind
of
split
it
between
two
different
services
that
you
can
get
in
the
catalog,
so
the
add-ons
coming
from
the
service
broker
and
the
services
coming
from
any
arrest.
Third,
certain
third-party
service
provider,
so
in
K,
for
example,
if
I
would
provision
a
sure
service
broker
and
so
to
register
at
the
end
additional
service
broker
in
kheema,
that
would
provide
services
from
air
pager.
A
A
Just
additional
note
for
you
Krista,
so
that's
the
that's
the
way,
for
example.
How
we
want
to
in
the
future
share
examples
so
then
provide
a
bundle
of
a
repository
with
bundle
of
different
examples.
We
can
share
them
between
different
instances
easily
anybody
can
provision
them
quickly,
so
he
doesn't
have
to
go
through
the
example
and
do
keep
CTL
I'd
like
you
to
do
apply
several
times,
but
you
just
install
everything
which
is
yeah
yeah
looks,
looks
very
promising.
Really,
it's
really
cool.
A
A
A
Okay,
so
we
can
see
that
we
don't
have
anything
really
in
the
pipeline.
There
are
just
two
things
to
accept:
one
is
the
proposal
to
improve
the
development
process
that
is
already
improved
by
several
people.
I
think
it's
even
already
merged,
so
we
just
need
to
check
why
it
still
into
the
and
to
accept
that's,
probably
waiting
for
pickup
from
some
product
owner
rights
module.
It's
probably
waiting
for
final
approval
from
2k
exactly.
C
A
Cool
and
the
other
proposal,
it's
a
pro
request
that
it's
hanging
for
some
time
already,
I
guess
it's
because
we're
all
a
bit
afraid
of
what
it's
what
it
brings.
What
just
brings
in
the
structure
of
the
repos.
Nevertheless,
all
those
and
those
both
PR
such
really
important
topic,
which
is
paying
for
us,
which
is
releasing
of
kimmm.
It's
not
really
easy.
We
want
to
solve
it.