►
From YouTube: Kyma Core SIG community meeting 20181121
Description
Meeting notes https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/
A
Hello
guys
and
welcome
to
our
regular
kima
course
meeting
your
moderator
today
is
ahmed
abdullah
and
lucas.
Cranach
is
helping
me
in
taking
notes
today.
Our
agenda
is
starting
with
a
very
exciting
topic
about
releasing
kima
0.5
and
we
have
Jose
Medina
to
tell
us
more
about
it.
Jose
you
didn't
take
it
from
here.
Yeah.
B
Thanks
it
so
really
excited
to
have
a
new
release
available
in
github
since
yesterday
afternoon.
So
this
is
our
release.
Zero
point:
five
point:
zero
still
on
our
initial
phase
of
development,
but
it
has
a
very
large
amount
of
changes
which
have
been
included
and
we
have,
as
usual,
our
change
lock
in
github,
with
together
with
the
release,
and
we
have
old,
also
posted
a
new
blog
post
in
our
team,
a
project
dial
page
which
gives
you
all
the
details
about
the
changes
that
we
have
included
in
this
release.
B
So
it's
been
a
while
since
the
release
before
that
which
was
in
October
and
and
we've
been
very
busy,
so
it's
really
difficult
to
pick
out
things
out
of
this
whole
large
amount
of
changes,
so
I
invite
you
to
have
a
look
I,
invite
you
to
read
through
our
blog
post
and
find
out
what
you
can
benefit
from
the
most.
A
D
A
C
C
Okay,
then,
let's
back
the
next
piece
view
to
the
catalog,
as
you
can
see,
we
already
changed
the
main
view
of
the
Service
Catalog,
where
we
see
all
of
the
service
classes
available
for
the
to
provision
and
right
now
you
see,
for
example,
readies
from
the
home
broker
and
classes
from
the
Google
mgcp
a
broker
and
also
as
well
some
service
classes.
There
are
coming
from
the
external
applications
and
they
just
register
the
api's
and
they
are
exposed
api's
or
events,
and
they
are
exposed
Food
Service
Catalog.
C
C
We
introduce
that
to
really
mark
some
of
the
classes
that,
for
example,
if
they
are
from
the
home
broker,
they
are
clearly
marked
that
service
instance
will
be
created
in
the
kubernetes
in
where
the
Kim
is
installed
and
on
the
other
hand,
we
have
the
special
labels
like
the
connected
applications,
where
we
can
see
that
that
application
came
from
the
application
called
EC
pass.
That
service
cast
came
from
the
come
from
the
application
called
EC
brought.
Of
course,
we
we
have
allowed
a
bunch
of
tax
and
the
brokers.
C
We
provide
some
of
the
brokers
providing
a
lot
of
tax
and
we
didn't.
We
don't
want
to
display
that
them.
In
that
view,
that's
the
reason
we
implemented
those
labels
and,
of
course,
we
can
filter
for
the
only
the
connected
applications
or
the
local
service
classes
and,
of
course,
the
default
filtering
like
seeing
the
classes
from
the
Google
or
I
need
to
unassign
that
label
from
the
SCP
or
GCP.
C
That's
very
nice,
nice
feature,
then.
Let's
just
I
can
also
show
you
some
of
the
classes
like
the
MySQL
from
the
GCB,
where
we
can
start
the
wizard
for
the
provisioning.
We,
of
course,
have
some
additional.
Besides
the
link
to
the
documentation
from
the
google,
we
see
the
overview
of
that
service
class.
C
We
also
see
the
details
where
we
can
find
what
are
the
plans
parameters
for
the
provisioning
there,
and
even
the
information
also
the
input
parameters
for
the
bindings
when
the
instance
is
already
provisioned
and
at
the
end
also
the
credentials
that
the
service
bindings
will
contain
and
those
environment
variables
can
be
used
in
the
end
application
where
that
binding
will
be
injected.
Ok,
then,
let's
go
with
the
next
features.
Then,
let's
go
to
them.
I
will
take
the
Redis
from
the
home
broker.
C
I
will
just
install
the
Redis
instance
in
the
given
cuber
notice,
and
you
just
do
that.
What
we
did
next,
we
just
simplified
all
of
the
wizards
for
the
creation
of
the
service
instances
and
service
binding
service,
binding,
usages
I
will
go
in
details
right
now
and
you
can
see
that
we
can
decide
what
type
of
plan
I
will
use.
I
will
use
micro
because
it
will
use
the
in-memory
database.
C
It
will
give
us
much
shorter
time
totally
provision,
that's
instance,
and
of
course
we
already
see
the
input
parameters
that
are
required
or
optional
to
create
such
an
instance.
If
the
class
has
empty
list
of
those
input
parameters
that
you
will
see
nothing
here
and
let
just
create
it,
of
course,
you
also
see
that
we
are
generating
the
names.
Of
course
it
could
be
changed
in
case
of
service
instance,
but
let's
just
take
that
one
and
create
the
instance.
The
next
thing
we
see
the
nice
link
that
can
point
us
to
the
service
instance
itself.
C
You
see
that
I'm
ready
navigate
to
the
instances
view
also,
as
you
can
see,
that
we
have
full
URL
that
you
can
reach
the
service
instance.
That's
it's
also
has
changed
since
last.
Release,
and
also
one
of
the
nice
nicest
feature
is,
is
that
we
have
the
WebSockets.
That
means
all
of
the
things
or
like
you
see,
the
status
is
already
automatically
updated
through
the
WebSockets,
and
we
almost
added
them
everywhere,
were
we
creating
the
bindings
and
and
so
on.
C
The
next
feature
is
also
that,
under
the
plan,
we
can
see
what
parameters
were
provided
for
the
service
instance
provisioning
in
that
case
it's
that
guy
and
that's
also
a
new
thing,
and
we
split
it.
In
the
service
instance
view
we
can
create
a
pure
credentials,
it's
really
a
service
binding
from
the
Service
Catalog,
or
we
can
already
bound
to
the
application
the
credentials
and,
let's
just
show
we
right
now,
the
transfer,
as
you
can
see,
also
that
there
is
a
nice
tool
tips
that
we
see
also
the
description.
C
What's
under
those,
let's
say,
business
names,
what
are
the
customer
resource
definition
used
to
provide
such
a
functional
team?
Of
course,
it's
also
worth
to
mention
that
all
of
those
things
I
presenting
right
now
it
could
be
done
from
the
CLI
and
it's
one
to
one.
Then,
let's
just
create
a
credential,
as
you
can
see
the
service
binding
for
that
Redis
doesn't
have
any
input.
Parameters
required.
That's,
as
you
see,
there's
is
auto
created
for
us
without
any
wizard,
then
we
can
go
to
the
secret.
C
We
see
what
environment
variables
are,
what
are
the
key
value
in
the
secret
and
that
thing
could
be
addicted
to
the
application.
We
can,
of
course,
decode
it
to
see
the
values
and,
in
the
bound
application,
instill
nothing.
That
means
I
didn't
inject
it
to
anywhere.
Then
let
us
prepare
the
end
application
I
will
use
for
that.
The
lambda,
let's
just
create
one,
let's
call
it
already
s.
Client
I
will
just
leave
the
empty
body
because
it's
not
really
important
so
how
it
works
together,
but
just
how
the
injection
works.
Let's
just
create
that.
C
Okay,
it's
just
deploying
the
lambda
q
blasts
and,
let's
back
to
the
instances
view
that
was
that
guy
with
one
credential
and
rates
right
now
bind
the
radius
instance
to
that
application.
Then
also
that
wizard
is
much
simplified.
We
don't
need
to
provide
any
names,
they
will
be
prisoner
ated
for
us
and
also
we
change
the
way
how
we
are
picking
up
and
application
where
we
want
to
inject
the
credentials
you
can
see
right
now.
We
support
deployment
and
function
in
a
minute.
C
I
will
show
how
to
extend
the
types
of
the
end
application
during
the
runtime.
Let's
just
pick
up
them,
readies
client,
the
next
thing
we
introduce
we
can
provide
the
prefix
for
the
service
binding.
That
means
every
and
each
environment
variable
will
be,
will
contain
the
prefixed
and
let
just
name
it
read
this
one.
C
Okay,
then
I've
just
click
to
do
a
job
to
bind
to
the
application.
We
see
the.
Of
course.
We
also
see
the
statuses
that
were
that's
a
new
feature
that
we
see
what's
going
on,
if
really
the
binding
to
the
application
really
works
in
the
secret
view.
We
also
have
additional
information
that
the
prefix
is
used
and
every
environment
variable
will
have
such
an
either,
and
you
see
also
that.
B
C
Credential
is
created,
and
it's
really
related
to
that
service.
Binding
usage,
let's
back
to
lambda
view,
and
of
course
it's
really
also
supported
from
the
lambda
view,
and
you
see
the
name
of
the
Redis
instance
and
also
already
indirectly,
the
environment
variables
that
we
can
use
in
the
body
of
the
function.
The
led
just
I
will
show
you
now
how
to
delete
those
stuff.
We
introduced
the
cascading
delete.
C
That
means
if
the
service
bind,
if
you
want
to
create
a
delete,
the
credentials
that
could
be
shared
across
many
applications,
we
can
right
now
do
that
and,
for
example,
that
one
which
is
not
used
through
the
any
service
binding
usage.
We
can
just
delete
it
and
it
still
want
one
and
right
now,
when
I
will
deal,
I
want
to
delete
the
credentials
that
I,
that
is
used
by
the
application,
I
clearly
see
that
that
it
will
be
used
and
it
will
just
stop
working
and
if
I
will
do
that.
C
I
have
also
Auto
deletion
of
the
service,
binding
usage.
I,
don't
know
why,
but
I
need
to
in
that
one
case.
I
need
to
refresh
that,
and
you
see
also
this
binding
usage
is
deleted.
We
need
to
check
it,
ok
and
then
that's
what
I
wanted
to
show
you
in
that
area.
Of
course,
the
next
thing
I
won't
show
you
some
error
case
then,
for
that
I
will
just
create
one
more
time.
I
will
just
speed
up
a
bit.
C
The
new
service,
binding
usage
and
I
will
just
use
the
name
of
the
service
binding
to
just
simulate
that
the
service
binding
usage
is
in
the
failed
state
and
for
that
I
will
just
show
you
how
to
I
will
do
that
from
the
CLI,
because,
from
the
UI
point
point
of
view,
I'm
not
able
to
break
it
really,
because
I
am
only
able
to
pick
up
the
existing
functions
and
right
now,
I
will
pick
up
not
existing
one.
Then
I
will
go
to
the
CLI
and.
C
Missed
something
once
they
can
throw
his
binding
growth.
Okay,
excuse
me:
I
made
a
mistake.
Probably
I
pick
up
the
wrong
service
instance,
but
overall
we
have
also
the
indicators
in
the
tops
that,
for
example,
when
I
see
I'm.
In
that
context,
I
will
see
that
some
credentials
I'll
failed.
That
means
their
statuses
and
are
in
the
error
state.
Okay,
that's
about
the
Service
Catalog
call
things.
The
last
thing
I
want
to
show
you
it's
about
the
namespace
catalog.
C
Then
right
now,
as
you
can
see
in
the
production,
namespace
I
have
just
easy,
prod
service
classes
from
the
remote
application.
When
I
will
go
to
this
stage,
there
is
one
service
class
from
the
different
application,
which
is
called
EC
stage.
I
will
just
show
you
how
I
did
it
in
the
administration?
We
can
go
to
the
remote
environments.
C
A
E
E
My
presentation
can
use
C
first
light.
Yes,
okay,
thank
you.
I
would
like
to
give
you
a
new
status
update
about
the
immigration
to
grow.
So,
first
of
all,
we
have
up
and
running
cluster
with
the
pro
you
can
access
it
using
address
status,
build
team,
a
project
I
all
already
we
have
21
jobs
defined.
We
have
some
jobs
defined
for
the
testing
for
repository,
for
example,
in
the
testing
for
our
we
create
some
docker
images.
So
we
have.
We
have
some
jobs
that
evaluated
them
and
publish
them.
E
We
have
also
jobs
that
validate
jobs,
the
definition
itself
in
the
kima
for
the
common
repository
we
might
get
so
far,
two
components,
binding
usage
controller
and
he
eiope
layer.
Also,
we
already
have
two
integration
jobs.
First,
one
run
me
keep
on
visual
machine
and
then
run
integration
test.
The
second
one
provision
a
cluster
on
the
cluster
installed
crema
and
there
in
run
integration
tests.
E
Additionally,
we
migrated
some
components
from
the
kima
console
and
we
already
have
prepared
migration
guide.
You
can
find
it
in
the
test.
Infrared
apposite,
Dori
and
our
migration
plan
is
following
at
the
beginning.
We
want
to
have
deprecated
jobs,
so
one
job
will
be
for
component
will
be
in
a
Jenkins,
the
second
one
it
will
be
in
a
pro.
Only
after
we
migrate
all
components,
we
disable
jobs
on
the
Jenkins.
E
So
far,
we
also
do
not
send
any
events
from
the
pro
to
the
github
to
do
not
confuse
developers
but
later
when
we
disable
jobs
on
Jenkins.
We
also
start
sending
that
event,
and
so
probably
here
right
now,
you
can
propagate
that.
Our
next
goal
is
to
migrate
all
our
components.
We
already
have
defined
epoch
when
you
can
watch
the
progress
of
that
death
tasks
and
besides
emigration
of
all
components,
we
also
need
to
spend
some
time
on
making
that
cluster
production
ready.
E
C
A
C
I
forgot
to
show
you
the
runtime
definition
of
the
new
types
of
the
ant
applications
and
I
just
want
to
share
it.
Then
I
also
found
the
reason
that
I
will
not
able
to
simulate
that
error.
I've.
Just
that's
not
saved
my
change
in
the
then,
as
you
can
see
that
that's
what
I
meant
that
we
can
see,
although
when
we
you
have
a
lot
of
bound
applications,
then
if
some
of
them
are
but
what
I
wanted
to
show
you
that
bind
application.
C
And
let's
say
we
like
now
on
the
fully
on
the
clean
ativ
and
we
want
to
support
the
configuration
custom
resource
as
a
application
where
we
want
to
inject
something,
then
I
will
just
simulate
that
we
provided
a
function
T
that
we
can
do
that
in
the
runtime.
We
are
doing
that
for
the
usage
kind
custom
resource
which
is
under
him.
C
A
Service,
Catalog,
API
and
I
just
can
provide
the
name
and
also
the
resource
where
I
am
providing
a
group
kind
of
version
right
now,
I
don't
have
a
native
into
my
cluster,
then
I
will
just
map
it
to
them
cubic
functions,
but
I
will
just
show
you
how
it
works.
Then,
right
now
I'm
just
adding
a
new
definition.
C
C
Example,
we
had
the
conference
for
the
cloud
next
when
we
are
asked
to
provide
the
automatic
injection
to
the
configuration
of
like
a
native,
and
we
needed
to
relieve.
I
meant
that
in
the
controller
and
right
now
we
can
just
add
it
in
the
runtime,
but
it
could
be.
You
can
define
the
pot
even
as
your
end
application,
not
a
deployment
and
right
now
a
lot
of
open
source
projects,
just
wrapping
deployments
around
yeah.