►
From YouTube: Kyma Core SIG community meeting 20181010
A
The
agenda
for
today
is
the
first
topic
is
gonna,
be
a
announcement
of
the
first
release
done
by
Xhosa
and
then
the
next
one
is
going
to
be
a
presentation
and
actually
live
demo
from
pure.
That
will
show
that
it
is
now
doable
in
an
easy
way
to
deploy
kima
to
google
cloud
ng
in
kubernetes
engine,
then
Radu
will
show
our
first
contribution
to
que
native
in
the
eventing
area.
A
You
know
that
we
were
announced,
say
kima
project
together
with
kenny,
if
a
few
months
ago,
so
it
was
kind
of
obvious
that
we
will
work
towards
a
closer
integration.
A
Then
we're
gonna
have
our
usual
community
slot
and
during
this
slot,
adam
will
present
our
first
a
working
group
and
actually
one
of
the
most
important
ones,
not
only
for
us
a
schema,
but
also
for
us
a
contributors
and
then
we're
gonna
have
a
usual
questions
and
feedback.
So
for
now
I
mute
myself
and
Xhosa.
Please
continue
with
the
release
topic.
B
Hello,
everyone,
so
basically
what
I
wanted
to
talk
to
you
today
is
about
our
race,
and
this
is
the
first
official
release
that
we
do
for
kima
since
we
went
live
in
when
we
first
open
sourced
the
project,
so.
B
C
C
C
B
So
yeah,
so
we
have
an
official
release,
also
in
github
as
a
release.
The
number
of
this
release
is
zero.
Point
four
point
one:
why
zero
point
four,
because
we
had
some
internal
releases
that
we
did
before
and
we
follow
semantic
versioning.
So
this
was
pretty
much
the
next
number
that
was
up
for
the
release
and
basically
in
in
the
releases
in
github.
What
you
will
usually
see
is
beside,
of
course,
the
general
information
about
the
release.
B
You
will
have
some
information
about
the
installation
and
you
will
have
also
below
going
further
down
a
change
look.
So
this
is
basically
all
the
changes
that
have
been
included
in
this
release,
and
these
are
all
github
links,
so
typically
pull
requests
that
you
can
link
to
or
that
you
can
follow,
and
you
can
see
further
details
about
everything
that
has
been
included
in
this
release.
If
this
is
a
little
bit
too
technical-
or
this
is
a
little
bit
too
much
to
read-
I
can
understand
that
perfectly
well.
B
So
what
we've
done
is
that
we've
done
a
blog
post
again.
Thank
you,
Luke
rush.
Thank
you,
everybody
who
it
is
and
in
the
kheema
website,
keep
my
project
on
Io.
You
will
happen,
then
the
block
you
always
a
release
to
post
about
the
release,
and
here
you
have
a
bit
more,
let's
say
understandable
and
easily
readable
information
about
the
release
and
what
we've
done
and
what
here
proud
of
what
we
want
you
to
look
at
so
I
hope.
B
This
is
something
that
you
can
take
the
time
to
read
and
understand,
and
if
you
have
any
questions,
any
comments
or
anything
don't
get
we're
always
here
happy
to
get
your
feedback
going
forward,
we're
thinking
about
we're,
actually
instituting
a
new
project
workgroup
to
define
or
finalize
our
release
strategy
going
forward.
So
that's
something
that
I'm
not
quite
sure
how
we'll
how
it
will
go
on,
but
we're
working
on
that
and
we'll
be
sure
to
communicate
that
as
soon
as
we
have
something
fixed.
A
Thanks
a
lot
Jose
so
now
next
topic
is
the
gke
installation
done
by
Fiat,
but
Before.
We
jump
to
the
topic
small
kind
reminder
as
usual.
Please
add
yourself
to
the
attendees
list
in
the
Google
Doc
I
will
by
stealing
some
in
the
chat
and
even
color.
You
can
continue.
D
Ok,
I'm
sharing,
so
please
confirm
that
you
read
the
release
in
the
browser:
ok,
so
I'm,
starting
when,
where
Hoffa
stopped.
So
we
have
this
release
and
we
have
also
installation
on
google
kubernetes
engine
manual.
Small
version
of
the
manual
is
in
the
race,
so
this
is
the
version.
I
will
use
the
extended
version
we
also
have
in
our
documentation.
So
if
you
go
to
the
documentation,
you
have
installed
Kimen
gke
cluster,
which
contains
all
details
how
to
do
all
so,
for
example,
DNS
zone
management
or
TLS
certificate.
D
So
my
today
demo
will
be
a
mix
of
these
risk
notes
and
and
this
instruction,
because
I
will
go
a
little
bit
deeper
than
than
it
is
stated
here
what
we
have
as
a
prerequisite.
We
of
course
need
to
have
Google
cloud
platform
account
with
access
to
google.
Google
kubernetes
engine
I
have
here
a
couple
of
clusters
in
my
playground.
Project
and
I
have
the
cat
cluster
here
in
case
something
fast,
but
I
will
create
sick
core
cluster
today
and
in
my
Google
project,
I
have
also
a
cloud
DNS
connected
to
my
domain
hamaji.
D
A
this
is
the
domain.
I
will
use
to
host
this
cluster,
so
in
the
end
we
will
have
a
console
sick,
core
kheema
G,
a
URL
that
will
work
right
now.
It
doesn't
work
because
there
is
nothing
there
so
to
start,
I
will
follow
with
this
step,
so
I
will
start
quickly
with
the
creating
cluster
because
it
takes
some
time.
I
will
switch
to
my
notepad
with
with
comments
and
console
that
you
can
see.
I
started
with
some
exporting
some
some
value
so
sick,
cork
emoji
is
our
cluster
and
cost.
D
Our
name
is
sick,
core
and
now
I
will
just
start
creating
that
cluster.
With
the
comment,
the
command
is
copied
from
from
the
manual
from
the
release
notes,
and
you
will
see
that
it
started
to
create.
We
are
good
now,
but
let's
use
the
time
to
get
next
step
from
from
the
tutorial.
So
I
could
really
use
that
step
to
will.
We
will
come
back
later.
Let's
create
the
domain
and
you're
less
certificates
for
that
domain.
I
already
have
this
domain.
D
D
Tries
to
get
new
certificate
from
let's
encrypt,
let's
encrypt
ask
the
domain
owner
to
put
some
entry
in
the
in
the
text
record
in
the
DNS.
This
new
entry
is
automatically
created,
but
by
my
command
I
will
refresh
the
page,
and
here
you
see.
Acne
challenge
for
Secord
is
the
secret
and
that
I
that
the
script
created
for
our
let's
encrypt,
then
let's,
let's
encrypt,
verifies
that
it
is
available
here
and
then
issues
the
certificate.
D
So
let's
come
back
and
check
if
the
script
is
waiting
60
seconds
for
for
doing
that,
so
to
make
sure
that
this
T
text
record
is
applied
on
the
DNS,
so
we
need
to
wait
a
little
bit
more.
In
the
meantime,
cluster
is
already
provisioned,
so
we
will
see
that
the
notes
are
there.
So
I
will
check
get
notes
if
the
cluster
is
really
there
and
I
have
and
in
the
meantime
congratulations.
My
certificate
is
created,
so
yeah
we
have
in
the
folder.
D
Let's
encrypt
I
created,
we
have
life,
we
have
sick,
cork,
imagej
and
we
have
certificate
created
and,
of
course,
private
key
I
will
not
show.
If
you
want
to
copy
it,
you
need
to
have
some
more
try
us,
so,
let's
go
back
and
to
the
flow
I.
Have
these
certificates
created
I
will
export
these
certificates
to
the
environment
variables.
I,
don't
need
this
window
anymore,
it's
let's
do
that
so
I
have
a
certificate
and
now
I
downloaded
following
the
manual
in
the
release.
D
Notes
one
second:
here
you
have
point
number
three:
you
download
the
release
artifact,
which
is
this
kima
config
cluster
I,
have
it
downloaded,
and
this
schema
config
cluster
is
here.
This
is
the
deployment
file
for
kima
installer
and
this
one
second.
This
contains
couple
of
placeholders
like
domain
and
TLS
certainty,
LS
key.
We
need
to
replace
that
values
with
the
values
I
got.
I
have,
of
course,
nice
comment
that
does
it
so
it.
D
And
I
will
create
I
will
install
tiller
on
that
cluster
because
it's
required
as
one
of
the
prerequisites
I,
need
also
to
add
myself
as
an
admin
of
that
cluster.
So
this
command
does
it.
So
my
user
is
bound
to
the
cluster
admin
role
and
now
I
apply
this.
My
Kamiyama
file,
which
install
installer
and
is
its
configuration
I,
will
check
quickly
if
installer
is
running.
D
We
will
see
locks
here,
and
here
we
will
start
the
installation
by
labeling
custom
resource
with
installation,
and
we
still
downloading
keema
is
not
necessary.
Processing
cluster
from
essentials
and
processing
component
Easter,
so
Easter
is
going
to
be
installed
right
now.
In
the
meantime,
I
have
now
some
some
time
have
10
minutes
to
finish
that
installation
I
will
come
back
to
some
steps,
I
intentionally
skipped
before.
So,
let's
go
back
to
the
installation
steps
in
our
case,
I
I
used
this
domain
kimi
GA.
D
I
so
the
first
step
in
the
installation
process
and
I
created
the
dns
manager
zone.
So
you
have
the
instruction
here:
how
to
create
a
dns
zone
in
Google
and
how
to
configure
this
DNS
zone
to
actually
manage
your
own
domain.
I
have
domain
kimi
GA
for
free
I,
took
it
from
from
the
site
for
Reno
com,
I,
not
know
how
they
earn
money
on
that,
but
I
have
also
I
I
need
to
log
in
again,
so
you
can
see.
D
I
have
keema
GA
domain
already
registered
and
you
can
get
it
for
free
from
this
side
and
in
the
management
tools.
All
you
need
to
do
is
go
to
the
name
servers
and
provide
the
information
you
get
from
the
cloud
DNS
from
Google,
so
in
Google
that
information
is
actually
available
here
on
the
Registrar
setup.
You
need
to
copy
these
values
and
enter
these
values
here
in
the
in
the
place
when
you
manage
your
domain.
So
this
is
the
the
way
how
you
delegate
domain
management
to
Google
and
the
other
other
steps.
D
I
I
skipped
was
to
create
this
service
account
DNS
manager
and
added
this
service
account
to
the
DNS
admin
role.
This
step
already
shown
so
I
already
had
this
two
steps
created
and
I
created
this
key
JSON
in
let's
encrypt
folder
during
the
demo.
So
we
let's
check
what
was
created
so
a
cluster.
We
already
should
have
so
sick
core
appeared
here.
You
see
that
the
challenge
and
a
record
should
disappear.
D
Get
faults
me
in
the
names
face.
East
your
system
Oh
still
waiting
for
golly,
but
the
most
important
component
we
are
waiting
for
is
Easter,
ingress
gateway.
It
is
running-
and
this
is
the
entry
point
to
our
system,
because
we
use
e
Co
ingress
gateway,
as
as
a
as
a
load
balancer
for
for
kima
to
get
the
external
IP
of
this
component.
I
will
get
services
from
SEO
system.
D
Second,
ok-
and
we
see
the
external
IP
here
is
of
Easter
ingress
gateways
like
that.
I
will
copy
that
and
that
value
and
this
value
we
need
to
set
in
in
ipv4
address
here
so
asterisk
sakura,
kimi
GA
should
point
here
and
I
added
this
value
and
when
all
the
components
will
be
running
it
will
go
okay,
so
SEO
is
finally
installed.
It
took
more
time
than
expected
because
it's
usually
three
minutes,
but
this
time
it
was.
It
was
almost
five
minutes,
so
we
have
probably
small
delay.
D
What
is
also
may
be
important
from
from
that
instruction
you
have
here.
You
can
see
that
this
is
not
only.
We
are
on
the
steep
step,
six
right
now,
so
this
is
not
only
this
one
record.
We
we
need
also
another
DNS
entry
for
Gateway
and
kima
address,
but
this
gateway
is
not
running
yet
it
is
installed
in
the
in
the
next
step.
So
I
cannot
set
it
right
now.
It
is
required
for
a
remote
for
remote
environment
and
the
application
connector,
so
I
will
not
show
it
today.
D
D
A
E
But
we
have
done,
we
have
tried
to
implement
a
part
of
a
native
eventing
and
this
part
is
related
to
the
net
streaming.
This
was
missed
in
connectivity
now
they
have
all
implementation
for
pops
up
from
Google
and
also
foreign
Kafka.
What
is
interesting
for
native
is
that
they
are
coming
with
a
high
level
concept
of
eventing,
and
these
are
the
low
level
component,
where
you
have
a
principle.
E
A
channel
and
the
source
a
subscription-
and
this
channel
can
be
also
is
a
composite
composable
object,
so
that
you
can
build
very
simple
applies
of
even
processing
where
each
subscription
is
only
a
step
and
is
even
processing,
and
also
they
are.
The
goal
here
is
to
build
something
like
library
of
low
level
components,
so
the
salmon
can
only
build
without
a
writing.
E
E
Is
an
example:
what
means
this,
if
you
write
a
small
service
in
native
I,
have
here
an
HTTP
server
like
very
easy.
It
has
only
one
method,
post
and
now:
I
have
to
define
for
him
a
channel,
and
this
is
the
communication
between
a
name,
no
name
and
bus
implementation
specification.
Our
case
this
is
the
nets
an
application
can
use
in
parallel,
multiple
channels.
So
this.
B
E
These
are
the
classical
as
nothing
to
do
with
event
it
in
now.
What
is
important
is
the
connection
between
a
service
and
the
channel.
This
is
my
subscriber
it's
my
service
which
will
connect
to
the
channel.
This
is
the
channel,
and
that's
all
in
the
name
of
the
subscription
is
something
different
now
I'm
trying
to
show
you
it's
running
a
temperature.
E
E
We
have
contributed
with
till
now
with
these
three
top
components:
net
streaming
is
a
part
of
provided
by
us.
Also
they
have
the
concept
of
dispatcher,
and
each
implementation
of
a
bus
should
provide
this
dispatcher
and
open
a
provisional
as
a
basic
component.
The
provisional
should
be
responsible,
the
future
with
auto-scaling
and
all
the
stuff
for
the
back
end
of
the
event,
implementation,
which
is
which
behavior
is
not
now
known
by
by
that's
by
by
eventing
and
also
I
have
okay.
E
E
E
Okay,
this
is
my
request
and
now
the
from
the
outside
for
the
system,
the
service
is
unknown,
but
opened
often
is
the
channel
so
that
I
can
send
a
request,
each
channel,
which
nobody
knows
who
is
the
subscriber
now
I'm
sending
the
request
and
the
request
is
coming
with
a
separate.
The
payload
was
cadet
is
dead,
and
now
you
can
see
here
is
some
more
low
key
formation,
the
subject
from
that
streaming.
What
this
one-
and
this
is
the
data
channel?
E
Okay
from
that
it
works
from
the
codes
indicate
net
if
they
do
not
have
seen
now
the
concept
of
modules.
This
is
why
we
have
put.
It
is
our
net
implementation
inside
of
the
standard
basis,
and
this
is
why
also
net
streaming
and
his
objects
are
running,
isn't
of
K
native
eventing
in
the
future,
I
suppose
it.
It
should
be.
Another
namespace
like
like
FEMA.
E
What
can
I
say
and
the
integration
is
very
simple
now,
for
example,
because
we
are
developers,
they
have
a
lot
of
constraints.
Writing
such
a
component.
For
example,
you
have
to
use
a
logger.
This
is
all
the
component
should
are
using
the
same
level
and
epilogue,
and
then
you
have
to
define
and
to
think
about
how
many
threads
should
work
here
and
have
always
the
same
pattern
start
stop
and
use
configuration
in
the
logger
is
in
the
thing
is
propagated
from
top
to
bottom,
so
that
they
can
use.
E
I
can
Google
to
change
the
lock
level
very
quickly
and
anna-marie
without
losing
runtime
performance
and
have
one
logging
all
the
components
which
are
working
on
the
same
request
for
us.
If,
in
the
future,
we
want
to
integrate
and
work
deeply
with
with
the
new
part
of
of
a
native,
so
that
we
will
write
controller
which
should
react
of
all
this
input
which
are
coming
from
outside
certain
normal.
You
Panetta's
controller,
and
the
next
time
should
will
be
to
have
a
production
ready
that
streaming.
Implementation
now
is
not
production.
E
D
5
minutes
ago,
processing
kima
components
was
done
and
all
the
ports
are
running
in
the
kima
system.
Namespace,
and
now
we
can
go
back
to
the
browser.
So
we
have
a
cluster.
We
have
entry
in
the
DNS,
pointing
to
see
cork
imagery
to
our
to
the
load.
Balancer
I
created
in
that
cluster
and
ya
da
da
o
console
Sakura
kima
nga
plugin
and
my
fresh
cluster
is
ready.
D
D
A
A
F
it
is
Central
European
Time
current
status
of
the
implementation
can
be
found
on
the
github
in
the
project
keema
project.
There
is
a
repository
test
interest,
so
you
can
follow
changes
in
that
repository.
Also,
you
can
see
what
issues
our
planet
right
now
and
our
goal
is
to
migrate
all
or
Jenkins
plans
till
the
end
of
this
year.
F
So,
as
you
can
hear,
we
have
quite
strict
deadlines
so
and
we
are
looking
for
volunteers
who
can
help
us
in
case
of
any
questions
and
don't
hesitate
to
ask
us
and
in
the
in
the
document
which
I
read,
so
you
can
find
click
link
to
the
slug
we
are
using
dedicated
channel,
namely
WG
pro.
That's
all.
Thank
you.
A
Okay,
Thank
You
Adam,
so
guys
as
you
can
see
on
our
first
meeting,
we
know
that
our
current
CI
is
not
really
encouraging
youth
for
the
contributions
now
we're
working
on
changing
that.
If
you
are
an
expert
in
prowl
and
you're,
gonna,
see
that
we're
doing
something
totally
wrong.
Please
let
us
know
and
have
us
out,
then
the
that's
all
from
the
plant
topics
and
usually
do
you
have
any
feedback.
A
A
We're
a
miss
features,
like
sounds
to
add
them,
so
thanks
a
lot
again
for
joining
us
on
our
third
meeting
another
one
again
in
two
weeks,
we've
sent
you
a
this
time
a
reoccurring
invite,
but
we
know
that
we
had
some
issues
with
the
invite,
if
you're
still
having
some
issues
like
the
invite,
shows
that
the
meeting
takes
24
hours,
then
let
us
know
we're
gonna
fix
that
out
for
you.
Thank
you
very
much
and
thanks
all
to
all
the
presenters
recording
won't
be
soon
available
bye.
Thank
you.