►
From YouTube: 🌱 Kyma Community Meetup 03.06.2020
Description
This virtual event is designed for end users, a space for our community to meet, get to know each other, and learn more about Kyma. We plan to have at least one demo in every meeting, with allocated time to discuss this in small groups.
Agenda:
🌱Where we go with Kyma (Piotr Bochynski) 4:24
- Installation improvements - new working group wg-installation
- Lightweight Kyma
- Externalize application connectivity
🌱New Kyma Elevator Pitch (Maja Kurcius) 14:52
- https://github.com/kyma-project/community/pull/474 check this out and leave a comment about New Kyma Elevator Pitch
🌱Kyma target Personas ( Krzysztof Kwiatosz) 23:16
- https://github.com/kyma-project/community/issues/461
- https://github.com/kyma-project/community/pull/475
🌱New Functions (Michal Hudy) - 27:39
- Architecture: https://kyma-project.io/docs/components/serverless/#architecture-architecture
- Tutorials: https://kyma-project.io/docs/components/serverless/#tutorials-tutorials
- Demo - how to hook your github org to a Kyma Function
🌱Tracing in Kyma Eventing (Sayan Hazra) - 38:36
- Introduction to the Kyma Eventing: https://kyma-project.io/docs/components/serverless/#tutorials-tutorials
Get the meeting agenda to find out what topics are planned for the meeting.
https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/edit
Find out more about our meetup at : https://kyma-project.io/community/collaboration/#kyma-community-meetup-kyma-community-meetup
A
Hello,
everyone
and
welcome
to
our
Kimmel
community
Meetup
I'm
Valentina
I'm,
the
new
community
manager
joining
on
the
months
ago
or
even
less
than
a
month.
So
it's
my
first
time,
I'm
running
this
Meetup,
so
be
gentle
with
me.
We
have
we
try
a
new
format.
We
already
had
a
little
bit
of
debates
regarding
you
know.
If
this
is
the
right
one
or
not,
we
try
to
find
ourselves
also,
while
we
move
forward,
so
we
rename
it
in
the
in
Kimmel
community
meet
up
before
this.
A
A
A
Can
people
propose
the
topics
and
then
there
will
be
Q&A
and
that's
that's
going
to
be
the
format
we
we
plan
to
to
make
it
every
two
weeks,
so
make
it
a
bit
more
lightweight
and
make
it
more
engaging
with
the
community
and
allowing
also
other
people
from
from
different
which
are.
It
could
be
also
not
part
of
the
project
to
present
something
if
they
day,
if
it's
closely
related
to
to
the
keema
project.
A
A
First
topic
is
basically
one
beautiful
proposal
was
to
ask
if
this
meeting
can
be
like
a
webinar
style,
where
you
know,
people
can
be
more
relaxed
and
just
watch
it
or
would
be
a
very
interactive
where
everybody
can
speak
so
I
think
that
a
lot
of
people
already
express
them,
but
I
would
ask
you
at
the
end
of
them
the
meetup,
how
it
goes
sorry
long
introduction
we
have
an
agenda
today.
I
explain
a
little
bit
why
we
reorganize.
A
We
try
to
be
a
little
more
open
and
have
different
type
of
topics
and
make
it
more
of
a
meetup.
But
we
have
couple
of
important
topics
today.
First
of
all,
theatres
will
cut.
Pb
column
will
pick
up
a
little
bit
and
touch
some
points
regarding
where
do
we
want
to
go
with
Kiva
and
somehow
related
to
that?
We
will
touch
then
a
little
bit
of
some
work
with
done
regarding
a
new
chemo
elevator
pitch
and
maybe
some
work
we
have
done
with
chemo
target
personas.
A
So
we
try
to
identify,
maybe
a
new
type
of
persona
that
we
want
to
address.
That
should
be
some
short
ones.
Then
we
have
a
short
presentation
from
akahl
regarding
the
new
functions
that
we
introduced
very
recently,
we
beat
up
the
demo
and
I
think
we
can
take
maybe
Q&A
immediately
after
the
presentation
and
then
the
presentation
regard
of
Sion
regarding
tracing
and
keep
my
eventing
also
something
that
we
introduced
recently
and
a
short
then
a
Q&A
session.
After
that,
as
we
do
have
the
webinar
format.
A
C
B
Good,
so
four
main
topics
for
today
I
will
try
to
make
it
short
you.
You
can
see
that
the
preview
here
ya
understand
better
what
I'm
saying
so
I
will
start
with
the
first
topic,
what
we
already
started,
its
installation
area
improvements.
We
already
started
being
a
previous
release
with
better
retries,
more
resilient
kima
operator.
We
know
from
feedback
from
different
customers,
users
that
it's
one
of
the
biggest
pain
points
currently
in
kima,
and
we
want
to
address
that,
and
it
is
our
focus
for
this
release.
B
Also,
so
in
this
release
we
will
migrate
to
helm
free
to
remove
tiller
component
and
get
rid
of
couple
of
problems,
but
we-
but
maybe
this
is
not
them
the
most
important.
The
most
important
thing
is
that
we
also
do
some
cleanup
in
their
hand
charts.
So
the
installation
should
be
much
much
smoother
and
and
quick
process.
It
started.
It's
not.
It
will
not
be
finished
in
this
release,
but
we
will
see
the
bigger
improvements,
also
in
the
next
releases,
and
also
we
started
some
preparation
to
make
installation
quicker
with
parallel
installation
of
some
components.
B
Right
now
we
have
a
lot
of
waiting
in
the
installation
process.
The
first
thing
we
will
do
is
to
install
custom
resources
definition.
First,
then,
we
can
have
also
parallel
installation,
and
this
dependence
between
components
will
be
much
more
easier
to
maintain,
and,
last
but
not
least
in
data
area,
we
created
new
working
groups
working
group
installation
which
utilize
existing
installations
like
channel
in
our
open,
open
slack,
and
we
encourage
everyone
to
for
dissipate
in
this
working
group.
B
Work
yeah.
The
first
meeting
happened
yesterday
and
we
meet
every
week
Tuesday
afternoon.
So
please
join
us
and
let's
and
help
us
to
improve
that
area.
So
that
was
the
first
point.
The
second
is
more
lightweight
keema,
so
we
also
see
that
we
collected
a
lot
of
nice
open
source,
the
ncf
landscape
projects
in
keema,
but
we
see
that
for
some
cases
it's
also
too
much
and
we
have
now
two
directions.
So
we
have
some
key
map
projects
in
introduction
and
for
production
installation.
B
Some
of
the
components
we
installed
together
with
keema
are
usually
replaced
by
external
services,
so,
for
example,
logging
or
or
a
message
bus.
We
used
something
that
is
provided
by
the
hyper
scalar
with
proper
eyes.
Delays
and
customers
do
not
want
to
maintain
that
solution
on
their
own
in
that
inside
the
cluster
and
so
for
production
use
cases.
We
move
a
little
bit
responsibility
for
some
components
to
external
services
and
for
development
and
Rocco
installation.
B
This
component,
as
we
have
already
in
Hema,
seems
to
be
too
heavy,
and
we
also
think
about
in
that
case,
when
we
offer
batteries
included
scenario,
so
everything
is
already
prepared
that
it
should
be
a
little
bit
more
lightweight,
so
we
go
into
their
directions
for
production
scenarios.
We
simplify
using
external
solutions,
and
for
that
we
will
focus
in
several
areas
to
move
production.
B
Utilization
utilization
of
services
to
the
external
services
and
for
local,
develop
or
for
development
clusters
or
for
local
developments.
We
provide
more
lightweight
alternatives,
so
there
are
areas
we
and
rabbit
now
focus
on
or
even
the
bus
service
and
application
connectivity.
In
these
areas
we
will
have
some
bigger
refactorings
and
you
will
see
that
some
of
them
even
today,
so
that's
the
direction
and
the
last
point
from
this
lightweight
came
up
is
application
connectivity,
and
here
we
will
have
bigger
refactoring
and
we
already
started
that
with
that
movement
with
externalization
of
application
connectivity.
B
So
so
we
want
to
manage
more
kima,
runtimes
and
group,
these
different
applications
and
different
runtimes
some
scenarios.
Some
time
ago,
we
started
in
the
kima
incubator
project
compost
project.
So
this
is
something
that
you
already
heard.
Probably
it's
evolving
and
we
are
ready
right
now,
so
the
compost
project
is
available
also
in
the
commercial
offering
and
as
management
plain
solution
and
we
keep
it
open
source.
But
we
want
to
get
kima
itself
lighter.
B
So
we've
moved
the
functionality
of
application
broker
and
application
operator
from
kima
runtime
to
this
external
project,
and
we
will
have
something
like
system
broker
that
is
outside
of
the
kima
application,
I'll
kima
runtime,
and
this
is
the
direction
we
are
going
to.
So
what
you
can
expect
in
the
near
future
and
the
application
operate.
Your
application
broker
will
be
removed
from
from
the
random
replaced
by
more
lightweight
system
connectivity
in
the
service.
B
Probably
some
of
you
have
spot
different
strange
milestones
in
our
repository,
so
we
had
hundreds
of
milestones
like
strained
xx,
backlog
whatever,
and
we
got
rid
of
that
milestones
and
right
now,
kima
repository
is
more
clean.
If
you
see
the
milestones
in
the
in
the
projects
in
the
Kimmel
repository
there
right
now,
my
stands
created
for
them
upcoming
releases
114
up
to
117,
and
we
have
also
future
milestone.
B
That
shows
and
the
issues
that
we
do
not
for
the
next
three
months,
but
we
still
see
it
as
important
and
we
planned
that
for
the
next
for
a
further
future,
but
we
want
to
keep
these
transparency.
So
if
you
see
that
the
issue
you
are
waiting
for,
it's
not
scheduled
in
the
near
future.
You
can
also
add,
vote
it
and
and
try
to
contact
to
comment
in
the
issue
and
try
to
influence
the
order
with
the
river
and,
of
course,
contributions
are
also
welcomed.
B
C
Okay,
maybe
I
have
maybe
one
comment
about
that
externalization
of
the
application
connectivity
that's
right
now.
What
we
are
focusing
on
is
right
now
compacts
could
be
installed
from
the
composite
repository
from
that
chart
or
could
be
stole
from
the
kima
itself,
because
there
is
older
than
the
child.
The
young,
which
allows
to
do
that
and
chart
is
copied
there
and
right
now
we
are
separating
that
that
means
compose
repository
will
be
fully
available
to
be
installed
on
a
given
kima
runtime.
C
A
Thank
you
for
for
mentioning
that,
because,
in
a
way
it's
it
is
related
with
the
next
topic.
As
we
are
splitting,
you
know
these
two
components
and
we
concentrate
a
little
bit
more
kima,
focusing
as
a
as
a
runtime
application
runtime.
We
we
explored
also
the
idea
of
maybe
trying
to
rephrase
the
elevator
pitch
that
we
have
for
for
kima.
As
we
now
go
on
the
home
page.
A
You
know
we
talk
a
lot
about
extension,
extensibility
and
so
on
now
we
we
try
to
focus
it
more
on
the
on
the
application
runtime,
and
we
have
a
couple
of
issues
in
the
github
where
we
know
a
couple
of
people
contributed
in
Maya
here,
she's
one
of
our
technical
writers.
She
picked
this
up
and
she
we
started
the
initiative
to
kind
of
rephrase
it.
Obviously
we
do
this
in
open
source
way,
with
a
pull
request,
and
maybe
Maya
can
can
pick
it
up
and
present
a
little
bit.
B
D
D
C
D
He
thought
we
could
just
reserve
that
folder
and
it
for
the
to
pitch
and
personas,
which
actually
start
going
to
talk
about
in
a
minute
I
believe.
But
you
know,
and
so
here's
they
like
this
micro
position,
which
is
a
draft
it
might
change
a
bit
after
someone
has
feedback
or
other
technical
writers.
Take
a
look,
and
yes
so
you're
welcome
to
have
a
look
and
share
your
opinions
or,
like
maybe
try.
A
D
C
A
Kimye's
and
flower
native
application
runtime
that
gives
you
the
power
of
kubernetes,
but
without
the
hassle
of
worrying
about
security,
configuration
and
integration
of
tools,
kima
does
it
for
you
as
it.
It
is
not.
It
combines
various
components.
Yeah!
Thank
you.
Maybe
we'll
leave
everyone
to
read
it,
but
it
would
be
a
bit
weird
in
in
the
video
registration.
It
would
be
a
silent.
A
D
D
D
E
C
C
D
D
D
A
F
Sure
sure,
hello,
everybody
and
we've
heard
from
PB.
He
explained
the
directions
were
how
Kamala
should
evolve
and
and
going
into
more
lightweight
one
time
and
we've
seen
the
rephrased
the
proposition
for
the
rephrased
and
punch
line,
saying
what
keema
is
and
what
kind
of
problems
it
can
solve.
And
now
we
can.
F
We
need
to
also
a
bit
redefine
the
personas
Pokemon,
because
we'll
also
want
to
focus
and
also
keep
in
mind
for
whose
problems
are
we
solving
and
what
we
need
to
have
a
common
and
imagination
common
core
understanding
about
the
about
the
personas
regardless.
If
you
are
contributing
and
writing
documentation
or
if
you
are
writing
and
contributing
and
developing
new
features,
we
all
have
to
make
sure
that
we
share
the
same
personas
in
mind
and
sovereignty
already
created
an
ticket
and
issue
and
github
to
define
the
target
personas
for
keema
and
to
document
and
them.
F
So
they
need
to
be
and
publicly
available
and
visible
in
the
community.
Those
customers
are
not
yet
defined,
but
I
would
like
to
just
say
that
that
this
is
a
work
in
progress
right
now
and
describe
you
a
little
bit
the
process.
How
we
are
getting
there
to
define
those
personas,
so
we
have
started
with
a
and
brainstorming
exercise,
trying
to
define
personas
for
camera
and
try
to
orientate
the
needs
and
the
pain
points
along
two
axes.
F
F
We
have
the
level
of
how
easy,
how
small
apps
are
you
developing
some
smaller
applications,
or
are
you
interested
in
more
enterprise,
great
cloud
systems,
so
we
have
tons
this
brainstorming
and
now
we
are
in
the
face
of
moving
this
input
into
a
pull
request,
and
now
this
is
the
place
where
we
want
to
invite
you
to
contribute
and
to
reflect
your
opinions
about
the
personas
both
into
in
this
ticket.
So
please
comment
this
ticket,
but
also
there
is
already
a
very
draft
pull
request.
It
will
be.
F
We
will
continue
working
on
it
and
we
want
to
prove
the
let's
say
the
format,
and
this
is
something
that
you
can
expect
in
the
in
the
github.
Soon,
in
the
documentation
on
the
community
github
so
to
have
real
faces
names
and
a
little
bit
of
description
characteristic
slogans
for
people
that
might
find
kima
interesting
and
that
will
use
it
to
solve
their
problems.
I.
F
F
A
Thank
you,
stuff,
I
think
we
are
a
little
bit
slightly
behind,
though,
let's
see
me,
Hal
I
don't
know
if
there
are
any
questions
right
now,
I
was
just
regarding
those
two
topics.
It
was
more
presentation.
Obviously
we
have
pull
requests.
You
can
be
encouraged
to
contribute
there
if
they
are,
but
if
they
are
not,
then
we
could
just
go
to
to
me
Hal.
He
wants
to
present
a
little
bit
the
the
work
that
his
team
was
doing
been
doing
in
the
last
considerable
amount
of
time.
E
E
Solution
that
is
no
longer
based
on
the
cube
less
it's.
Rather,
we
have
completely
new
solution
that,
worse
than
our
own
survivalist
controller,
where
we
orchestrate
all
steps
and
here
in
the
new
documentation
that
was
also
update,
that
you
can
find
a
new
architecture,
and
so
you,
as
the
user,
you
create
only
one
function,
custom,
resource
and
based
on
that
aptitude
is
orchestrated
for
you,
so
we
click
clip
recreate
proper
configuration.
We
also
create
a
job
that
is
responsible
for
building
the
image.
E
What
is
important
in
practice
solution
everything
was
built
in
the
runtime,
so
when
your
function
was
scaled
up
and
down
every
time
when
the
new
put
stars,
your
function
was
built
in
there
on
type
this
time
we
first
beat
the
image,
and
then
we
just
thought
this
time
is
based
on
Kennedy
serving
we
start
the
new
functions,
so
we
improve
the
time
to
start
new
function
to
heavy
deployed
and
also
into
the
common
technical
details.
Regarding
that
functionality,
as
you
can
see,
we
have
also
internal
data
stream.
E
The
feature
will
also
support
external
dock
registries
and
what
is
more
important
here,
you
can
also
find
night
to
nice
tutorials
how
to
create
factions,
how
to
expose
how
to
point
service
also
how
to
assign
some
triggers
to
it,
and
this
is
the
documentation,
but
let's
see
how
it
works.
On
the
when
you
go
to
the
king.
A
E
So
in
the
competing
new
I
have
a
create,
we
can
create
a
function
which,
let's
say
test
as
a
name,
and
you
can
add
some
rubble
right
then,
when
it
will
create
the
lung
function.
You
will
see
you
a
completely
a
new
structure
of
this,
so
we
are
mostly
focused
on
the
source
code
and
the
dependencies
and
query
also
can
find
the
environment
fire
address.
In
the
configuration
section
you
can
find
that
you
are
able
to
convey.
E
E
I
have
some
internal
problems,
so,
okay
and,
as
you
can
see,
you
have
also
sample
payload
for
your
tickers,
so
you
don't
have
to
go
to
the
specification.
Everything
is
here,
and
next
thing
is,
when
you
add,
some
self
is
binding
to
your
function.
For
example,
Reddy's
with
preface
right,
it
is
visible
here.
Also,
your
environment
variables
that
will
be
injected
to
your
functions
are
also
still
visible
and,
let's
add
another
one
and.
E
Go
back
to
the
code,
as
you
can
see
in
the
code
in
the
environment,
variable
sections:
you
also
see
the
list
of
the
variables
that
will
be
injected
to
your
functions,
so
you
don't
have
to
go
to
the
configuration
tab
and
to
look
into
for
the
names
everything
is
here,
so
you
can
focus
on
your
development
and
you
can
also
add
your
own
variables.
Let's
call
it
test
name
right
and,
as
you
can
see,
it
is
also
visible
here.
What's
more
important,
we
also
validating
if
you
are
adding
exactly
the
same
test
variable.
E
Right
the
save
button
is
here:
you
don't
have
to
save
hold
function,
just
we
are
changing
the
source
code
of
dependencies.
So
we
want
to
save
here
everything
every
other
configurations
added
immediately.
So
you
don't
need
to
have
to
save
your
function
and,
as
you
can
see,
it
is
already
running.
But
what
is
important?
Let's
go
back
to
the
architecture
and
the
diagram
see.
We
have
three
steps.
We
are
configuring
we
are
building,
then
we
are
deploying
the
function.
E
So
if
your
changes,
for
example,
you
are
adding
your
Axel
and
viability
or
something
like
that,
then
we
don't
build
your
function
again.
We
just
change
the
deployment
when
you
change
their
something
related
to
the
image
that
will
be
created
so,
for
example,
the
source
code
of
dependencies.
Then
we
are
bringing
the
new
image
and
when
the
build
is
finished
with
success,
then
we
change
that
your
deployment.
Otherwise
its
is.
The
old
version,
is
a
variable
here.
E
E
And
here
you
just
need
to
add
new,
a
pl/I,
a
gay
rule
with
some
name
test
test
and
choose
your
therapist.
That's
right
and
I
will
expose
with
everything
right
and
we
need
to
let
wait
a
little
bit
and
it
will
be
available
yeah
it
works
here.
As
you
can
see,
we
have
hello
world
and
the
functions
when
we
go
to
the
function
interlocks
as
I
added
to
console.log
tests.
It
also
is
visible
okay,
but
it
was
really
simple.
Example
of
how
the
service
works.
E
Let's
go
to
the
some
people
connected
service
connected
system,
so
I
created
a
small
demo
to
that
to
do
that
and
I
connected
github.
My
test
organization.
Look
at
the
student
to
Kemah
and
I
prepared
two
functions
before
I
will
go
to
the
functions.
Let's
see
how
it
works.
My
functions
are
monetary
issues
created
into
the
whole
organization
and,
for
example,
I,
can
assign
someone
to
the
issue
already
quest.
E
And
when
I
typed
assigned
or
art,
then
my
boat
is
assigning
it
and
is
created
by
function
specifically
for
assigning
people.
I
also
created
another
board,
but
we'll
send
a
blob
emoji,
because
we
recently
we
are
a
big
fan
of
emojis,
so
I
have
to
create
some,
but
right
and
as
you
can
see,
it
sends
the
emoji
so
how
it
works.
I
created
the
two
functions,
as
I
said.
The
first
part
first
function
is
supposed
to
be
only
for
assigning
and
I
had
to
environment
variables
once
my
good
name.
E
The
second
one
is
a
big
upgrade
to
a
well,
and
this
is
connected
by
service
binding,
because
my
github
is
connected
from
the
syrup.
Thanks
of
sales,
catalog
and
application
connector
to
crema
and
also
I,
have
some
acid
assign
some
triggers
to
my
function,
and
he
is
just
the
source
code
of
this
button.
I
am
NOT
the
JavaScript
developer,
so
probably
it's
really
ugly
and
the
next
one
is
just
the
emoji
blob.
It
has
two
more
environment
Barabbas.
A
Thanks
we
heard
that
was
a
that
was
fast
and
a
lot
are
just
wonder
if
there
are
any
other
questions,
we
are
slightly
running
behind
time.
We
have
another
presentation
from
cyan,
so
maybe
we
can
try
to
let's
and
present
and
then
at
the
end,
if
we
have
the
time
we
pick
up
the
questions
if
no
problem
cool.
Thank
you
very
much
Michal
my
pleasure.
A
G
No,
actually,
it
was
there
since
the
beginning.
Tracing
is
an
important
part
where
you,
there
are
many
moving
parts
and
you
want
to
debug.
Where
did
your
event
pass
through
and
what
actually
went
wrong
if
your
function,
which
Michelle
showed
us
is
not
triggered
per
se,
so
tracing
is
really
critical
and
we
have
brought
it
back
because
it
was
broken.
Few
releases
back,
I'm
gonna
share
my
screen.
Is
it
visible
game.
G
Looks
good
yeah
great,
so
yeah
I
have
an
application
which
is
not
for
ten,
and
this
function
is
basically
listening
to
this
particular
event,
and
this
function
basically
does
nothing,
but
some
console.log,
that's
the
thing.
So
if
an
event
is
triggered
from
the
application,
we
want
to
see
like
the
touch
points
of
the
event,
basically
which
components
it
passed
through.
G
So
I
will
go
over
the
configuration
in
a
bit.
But
let
me
explain
the
outcome
first,
because
we
have
a
configuration
which
says
like
we
want
to
have
one
percent
of
all
the
tracing
samples
reaching
jäger,
which
is
the
backbone
of
the
tracing,
but
it
could
be
changed,
but
it
will
obviously
take
more
resources.
Hence
I
won't
do
like
a
bunch
of
calls
to
make
sure
I
have
a
trace.
I
do
have
a
trace
here,
which
starts
from
like
the
issue
increase
gateway,
followed
by
few
components:
connectivity
validator
to
even
service.
G
This
is
part
of
the
application
connector,
which
then
reaches
the
first
channel
here,
which
is
like
this
part,
and
each
channel
means
a
persistence
in
your
event.
Bus
configuration,
for
instance,
as
your
Nats.
What
have
you
followed
by
the
username
space,
the
brokers
which
I
showed
him
back
there
and
then?
Finally,
the
Tanakh
Martin?
Oh-
and
this
has
the
various
fans
here.
So
obviously
we
could
check
even
the
agency
or
how
are
between
which
part
is
going
crazy,
which
part
is
really
fast
and
stuff
like
that.
G
G
G
Don't
see
it
for
some
reason,
but
yeah
I'd
like
to
mention
that
we
exhaustively
use
the
sto
configurations
where
they
co-pilot
has
a
sampling
rate
of
1%
and
it
could
be
changed
based
on
the
need,
meaning
you
would
get
more
traces,
basically
meaning
more
resources
as
well,
so
the
tracing
is
back
with
the
new,
even
mesh,
and
so
this
is
a
good
thing.
That's
basically
it!
Thank
you.
Any
questions.
G
A
You
fan
sorry
for
this
screen
sharing.
We
will
try
to
figure
out
later
why
you
know
and
screen
sharing
an
entire
screen
is
not
possible.
So
but
I'm
you
know
I'm
new
to
the
project
so
when
I've
seen
it
in
the
demo
last
time
we
seemed
like
a
new
feature.
That's
why
I
mentioned
it's
new.
So
thank
you
for
mentioning
that
it
was
already
there.
Are
there
any
any
questions
for
cyan
or
for
for
cyan
first
and
then,
if
not
maybe
there
for
me.
B
Name
then
I
have
a
question
might
be
or
prepare
just
for
me
how?
Because
you
showed
that
there
is
no
direct
exposure
of
observable
dysfunction
for
the
API
gateway.
Maybe
it
would
be
nice
to
have
some
link,
maybe
this
structure
stuff
more
because
this
is
why
that
that
navigates
from
the
function
editor
to
API
roles
directly.
So
people
should
not
guess
that
where
to
go,
you.
E
Are
not
the
first
person
that
is
mentioning
that,
and
this
is
really
the
50,
that
something
needs
to
be
improved,
so
something
like
expose
and
then
should
be
the
direct
to
the
API
roles.
We
film
already
filter
for
me
and
will
create
and
improve
that
in
the
future.
Maybe
in
the
stage
Aristo
will
see.
E
F
B
B
A
Cool
so
well,
I
think
if
there
are
no
any
other
questions,
I
take
it
as
a
feedback
that
we
change
it'll
be
the
format.
Then
we
allow
everyone
to
share
and
share
this
screen.
So
I'll
take
it
by
myself
to
try
it
out
the
set
up
next
time,
and
thank
you
all
for
for
joining,
and
we
see
each
other
in
two
weeks:
I
guess
right
and
anyone
please
join
and
propose
some
topics.
I
said
they
can
be
keema
related.
That's
that's.
Nice
can
also
be
things
that
are
interested
to
Kemah.