►
From YouTube: Kyma Core SIG community meeting 20191023
Description
Meeting notes: https://docs.google.com/document/d/1vWleTon7sJIk0teee4SoVezS4mR3K8TlkvXkgLJwRD8/edit#heading=h.c6h3wzeefpg4
A
Okay,
welcome
everybody
to
call
him
a
Korsak
meeting.
It
looks
like
it's
gonna,
be
a
short
meeting
today,
so
yeah
the
first.
The
first
item
on
our
agenda
is
about
very
waited
for
and
belated
kima
won
six
release.
We
finally
arrived
to
munich
after
a
lot
of
disturbance,
and
we
had
some
interesting
findings
during
this
release
about
improving
our
pipeline,
also
about
detecting
a
very
nasty
regression
that
showed
up
at
the
very
last
minute,
which
was
more
or
less
spamming
our
api
server,
and
that
was
very
difficult
to
figure
out.
A
But
at
the
end
we
end
up
with
a
very
nice
blog
post,
where
you
can
read
more
about
the
new
features
and
kim
yunsik's
was
already
introduced
before
briefly,
but
the
detailed
blog
is
out
there.
We
have
a
brand
new
API
gateway.
We
have
a
very
simplified
UI
for
the
logging
and
we
have
also
micro
front
ends
with
optimization
for
pre
loading.
We
are
introducing
compass,
which
is
more
or
less
kimura
management
components
that
you
probably
have
seen
a
brief
glimpse
about
in
previous
course.
A
A
We
have
a
troubleshooting
guide
for
the
backup,
documentation,
improvement
for
the
documentation,
installation
and
updated
event,
a
native
eventing
versions
and
can
do
even
thing
to
0-8.
We
are
still
sticking
to
staying
one
release
behind
kinetics,
so
right
now,
they're
on
zero,
nine,
we
are
in
zero.
Eight
next
step
will
upgrade
to
zero
nine
unless
there
is
a
very
strong
reason
to
either
stay
or
jump
to
the
latest.
We
be
transparent
about
these
decisions,
but
the
general
approaches
one
release
behind.
A
Also
there
was
an
introduction
for
head
reform
for
kubernetes
provisioning
and
Kino
provisioning,
some
support
for
better
logging
like
support
for
fluent
bits.
We
have
also
some
enhance
that
you
feature
in
functional
controller,
which
is
an
experimental
controller
that
you
can
try
for
building
very
right
now.
Standalone
functions
running
out
of
a
CRT
object,
and
this
is
gonna
be
the
way
to
move
forward
with
replacing
or
kiba's
based
on
the
functions
with
kindof
serving
based
once
on
the
cluster,
also
on
the
service
management
side.
A
So
we
have
service
kind
of
log
that
switch
it
to
the
CRD
implementation
and
also
we
don't
no
longer
use
the
GCP
service
broker.
That
is,
that
was
introduced
as
a
preview
mode.
However,
we
use
it
fully
now.
I
believe
for
service
mesh
is
tu
was
updated
to
one
to
seven
and
I
believe
there
is
another
version
that
might
land
soon
and
female
one
eight.
If
I'm
not
mistaken,
stay
tuned
for
it
yeah.
You
can
read
more
all
the
details
on
keema
project,
bio,
slash
blog
on
our
website.
A
Next
topic
is
a
couple
of
demos
that
will
be
introduced
by
omission,
hoodie,
who
also
has
been
taking
it
on
his
shoulder
to
produce
some
improvement
in
the
overall
developer
experience
for
kima,
and
he
will
start
with
the
very
interesting
updates
about
how
to
have
kima
installed
in
kind
kind
as
a
project
that
stands
for
kubernetes
in
poker,
and
it's
a
very
interesting
project
that
you
might
check
out
if
you're
using
kubernetes
bocalee
will
mimic
you.
For
example,
missions
I
will
stop
the
sharing
and
you
can
take
it
from
here.
B
B
So,
as
you
can
see,
you
have
our
dashboard
when
we
just
show
that
job
that
is
start
crema
on
kind
with
organization
drops.
The
first
thing
that
you
might
notice,
if
you
are
familiar
with
our
pro
setup,
is
that
we
are
generating
the
JV
report,
where
you
can
see
all
steps
that
the
job
is
doing
with
proper
times.
B
The
second
thing
that
we
have
to
thanks
to
the
JV
report
will
already
integrate
our
brow
cluster
with
a
test
grid.
So
you
can
tracked
all
tests
across
at
the
build
and,
as
you
can
see,
if
here
you
have
some
problems
with
our
infrastructure,
but
for
example,
here
the
integration
test
side.
What
is
important?
This
is
just
the
first
attempt
for
our
configuration,
j-unit
and
come
on
kind.
So,
of
course
we
can
improve
that
report,
but
that
I
now
just
wanted
to
check
if
it
works,
doing
work
on
that
task.
B
We
also,
as
you
see
we
make
improve
camera
that
is
able
to
run
on
kind.
Not
only
on
the
cube
and
kind
is
the
kubernetes
in
docker
solution,
and
thanks
to
that
you
have,
we
can
have
a
multiple
nodes,
not
only
one
as
in
card,
but
you
can
have
multiple
control,
plane,
nodes
or
worker
nodes
that
matter,
and
thanks
to
that
it
is
a
pure
kubernetes
cluster.
We
found
I
found
a
few
bugs
in
our
commercial,
but
we
also
fixed,
so
it
is
beneficial
for
us
and
also
thanks
to
that.
B
We
are
have
simpler
testing
infrastructure
than
previously,
because
I
don't
know
if
you
know,
but
previously
we
use
for
the
camera
light.
We
used
mini
coop
and
it
was
proven
on
virtual
machine
right
now.
Everything
is
done
inside
our
CI,
proud
cluster.
The
whole
configuration
related
to
command
kind
currently
is
testing
for
a
repository
in
kind
directory,
and
here
you
can
find
the
script
that
is,
that
also
works
on
your
local
environment,
but
it
installed
a
full
crema
with
monitoring,
logging
and
other
things.
B
So
we
need
to
have
a
powerful
machine,
let's
say,
but
we
are
working
on
improvements
related
to
that,
together
with
some
improvement
related
to
our
whole
testing
infrastructure.
So,
probably
later
we
have
a
support
in
commercial
I
for
kind
and
it
will
be
much
more
useful
than
mini
cube,
I
think
any
questions
so
far
or
every
far
everyone
understand
it.
C
B
Right
now,
I
don't
have
proper
jobs
here,
but
I
made
some
comparison
and
our
pipeline,
that
is
the
FEMA
light
on
me,
cube
talks,
something
like
around
40
minutes
and
the
pipeline
that
installed
full
crema
on
kind
with
motoric
parameters
with
everything
and
execute
I've
done
more
tests
than
any
cube.
It
was
almost
ten
minutes
faster
than.
B
B
Every
time
when
you
have
some
open,
API
or
named
swagger
a
specification,
we
just
gave
you
a
file
that
you
need
to
put
the
swagger
editor
on
any
other
page
when
you
can
have
visualization
of
that
file
right
now.
We
provide
some
improvements,
but
it
is
all
only
available
on
the
master
branch.
So
later
it
will
be
on
release
1.7,
but
if
you,
for
example,
it
goes
to
the
application.
Connector
specifications
usually
see
the
new
section
API
consoles,
and
if
you
click
it,
it
will
open
the
new
model
with
the
render
of
the
specification.