►
From YouTube: Kyma Core SIG community meeting 20190116
A
Okay,
hello,
guys
welcome
to
our
course
egg
meeting
today
the
agenda
is
full
of
releases.
I
will
be
moderating
that,
and
the
meeting
today
and
Lukesh
chronically
will
take
the
notes-
and
please
don't
forget,
to
add
your
name
to
the
attendees.
The
first
topic
we
will
start
with
now
is
announcing
our
zero
sex
release.
We.
Finally,
we
successfully
last
week
released
kima
0.6
cairo,
and
you
can
guys
go
to
keema
project
that
I
out
or
blog
posts
and
read
more
of
about
the
topic
of
the
release
right
now.
A
The
main
good
announcements
that
achievements
that
we
did
in
this
release
is
that
we
used
and
released
teen
100%
by
plow.
That
was
very
successfully
implemented
by
our
public,
proud
working
group,
which
will
have
a
brief
about
in
a
little
bit.
Also
one
of
the
main
released
themes
that
we
achieved
is
more
in
2k
native
integrations.
We
have
an
installation
of
FEMA
with
Kenneth
that
you
can
enable
it
based
on
a
feature
flag,
and
we
also
have
renaming
for
the
remote
environment
and
the
environment
controller
into
applications
and
namespaces
namespace
controller.
A
B
I,
do
not
have
a
blog
post
yet,
but
I
promise
to
have
it
soon.
So
right
now,
I
will
just
talk
about
that
briefly.
What
is
your
plan
for
the
next
release?
What
I
can
share
today
is
that
the
release
date
is
11th
of
February,
so
we
start
with
this
release.
Four-Week
cadence,
so
each
four
weeks
we
plan
to
have
new
release,
so
new
features
and
memories
will
be
every
four
weeks
and
in
the
next
one
open
Stefan,
the
codename
will
be
doubling,
and
so
the
previous
one
was
Cairo
now
Dublin.
B
We
will
have
such
improvements
there.
So,
starting
with
proud
mentioned
before
we
have
prowess
a
main
CIS
city
for
for
Chima,
and
we
will
add
a
new
pipeline
to
check
if
kima
is
upgradable,
so
starting
with
relax
release,
we
want
to
have
really
upgrade
ability
as
a
capability
of
kima,
so
you
will
be
able
to
to
upgrade
the
existing
version
to
the
new
version,
because
we
will
have
new
version
every
four
weeks.
B
B
You
know
in
infrastructure,
probably
also
our
guest
to
to
build
nightly
and
weekly
build,
so
we
will
check
every
night
and
I've
how
integration
tests
are
going
and
we
will
also
have
some
longer-lasting
clusters,
so
this
go
for
weekly
pipelines
is
to
have
tests
how
in
a
longer
period
we
will
our
components
and
all
the
integrated
components
will
behave
and
have
more
stability
in
our
product.
So
this
is
more
referring
referring
to
the
infrastructure,
then
a
couple
of
features.
B
We
started
in
0.6
working
on
the
authorization,
authentication
concept
for
our
UI
API
layer,
so
graph
QL,
and
now
it
will
be
applied
and
undocumented
in
this
release
for
our
components,
so
we
will
have
authorization
implemented
there,
big
improvement.
We
continue
also
working
on
environments,
replacing
them
with
with
namespaces.
So
in
the
UI,
you
do
not
see
environments
anymore.
These
are
fine
namespaces.
We
will
continue
in
this
series
that,
under
the
hood
also
namespace
is
first
crisis
and
we
get
rid
of
these
environments.
B
Then
we
also
revert
a
little
bit
in
the
way
how
we
operate
with
service
patch,
which,
if
your
so
we
in
current
version,
we
have
default
sidecar
injection
disables.
We
will
change
that,
so
every
new
namespace
you
create
will
have
this
automatic
sidecar
injection.
So
you
will
not
be
required
to
modify
or
deployments
and
use
all
service
mesh
capabilities
out-of-the-box,
and
we
do
some
improvements
in
auto
scaling
of
components
like
app
server
proxy.
B
B
So
you
can
pick
either
broker
and
for
us
in
from
the
surface,
cut
along
and
install
it
with
your
subscription
details
and
end
you
sitting
in
running
kima,
cluster
independent,
yes,
so
a
couple
of
small
improvements
in
hand
broker
like
one
professional
only
once
because
yeah
deploying
multiple
brokers
doesn't
make
sense,
so
that's
that
small
province
also
will
be
there
in
a
point,
seven
from
creative
integration
point
of
view.
We
want
to
have
even
publishing
and
having
a
subscription
in
a
native
in
the
next
release.
B
B
Yeah,
it
will
be
there
some
improvements
in
Lambda
UI,
and
so
we
will
have
possibility
to
run
to
test
lambdas
directly
from
from
UI.
So
you
do
not
need
to
expose
this
laptop
before
you
can
just
test
it
from
from
from
the
console,
and
we
will
have
couple
of
improvements
in
monitoring.
We
will
add
more
controller
services
and
UI
components
to
our
graph
on
Azure.
We
will
see
more
and
more
detail
seen
in
monitoring
what
I
have
more.
B
B
We
want
to
have
pick
a
refactoring
current,
somehow
new
component
assets
store
that
will
handle
that
things.
So
this
is
our
foundation
of
headless
CMS
that
we
will
deliver
as
a
MVP
in
the
first
in
the
next
release.
Yeah
also
some
improvements
in
test
areas,
so
first
end-to-end
tests
will
be
implemented
that
have
that's
actually
checks
entire
story
with
application
connector.
B
We
will
have
this
application
connector
mock
in
used
there,
so
we
will
do
all
the
design
to
end-to-end
testing
and
we
also
improve
couple
UI
tests,
especially
in
service
catalog
area,
so
this
binding
will
be
tested
automatically.
I
think
this
is
most
of
the
scope
we
plan
for,
for
the
next
release.
I
will
try
to
put
it
in
nice,
blog
post,
so.
A
A
Yeah
guys
keep
checking
with
our
website
and
watch
out
for
the
post
and
make
sure
make
sure
that
you
give
us
any
feedback
about
any
of
these
plan
features
whenever
you
want
speaking
about
feedback
also,
we
also
like
to
regularly
announce
on
our
core
meeting
our
proposals
that
are
public
on
our
github.
So
we
have
a
couple
of
photos
that
we
would
like
to
talk
about,
and
Mukesh
will
talk
to
you
about
them.
D
So
there
are
four
different
proposals
that
came
in
I'm
gonna
leave
this
at
the
end,
because
it's
longer
talk
so,
first
of
all,
it's
about
application,
connector
improvements,
which
is
part
of
our
application
connectivity
in
in
keema.
That
allows
you
to
connect
external
applications
into
keema.
So
please
take
a
look
on
this
proposal.
The
other
two
is
the
first
one.
Is
the
release
process
improvement
so
raising
on
our
working
and
also
the
release
strategy
that
we
want
to
publish
soon?
D
We
already
started
thinking
about
how
we
can
improve
the
current
process
to
address
the
strategy
that
we're
aiming
for
so
basically
be
able
to
release
every
day.
So
that
is
super
important
proposal
to
get
feedback
on,
because
it
just
addresses
current
issues
with
some
solution
that,
at
the
end
can
be
on
the
disease
can
be
solved
in
different
ways
as
well.
So
if
you
could
get
feedback
or
even
create
a
contra
puzzle-
and
it
would
be
awesome,
then
this
common
code
validator,
that's
something
for
contributors,
internal
and
external.
Soon.
D
D
This
different
components
simply
have
their
own
approach,
different
solutions
and
one
of
our
guys
had
time
to
prepare
a
nice
proposal
that
will
be
consolidates
the
approach
and
make
it
really
nice
to
maintain.
So
we
will
not
repeat
the
configurations
in
each
component
that
much
so
really
awesome.
If
you
could
give
feedback
here
and
the
assets
tour,
something
that
already
PV
mentioned,
that
the
MVP
is
planned
for
0-7.
D
Continuing
of
the
proposal
that
we
published
two
months
ago
to
the
public
so
for
a
headless
CMS
that
also
people
mentioned,
so
we
work
on
it
for
some
time.
We
would
like
to
close
the
discussion
on
Friday,
but
we
already
started
some
operation
for
the
implantation,
so
yeah
keep
in
mind
that
you
can
still
influence
where
we
go
and
yeah.
That's
it.
If
it
comes
to
the
proposals.
A
Thank
You
Lucas
yeah
feel
free
to
contact
us
regarding
any
of
these
proposals,
whether
on
slack
or
directly,
on
the
Google
group
or
on
the
public
repo,
and
if
you
also
have
proposal,
feel
free
to
send
it
to
our
mailing
list.
The
next
is
about
our
community
related
topics,
and
one
of
the
our
working
groups
have
successfully
is
successfully
closing
business
after
becoming
rich
and
closing
down,
and
we
have
Philemon,
who
is
one
of
the
leads
of
the
working
group?
C
C
How
is
up
and
running,
and
it's
integrated
with
all
of
them.
So
when
you
create
a
PR
for
one
of
those
ripples,
you
will
notice
that
proud
will
trigger
the
jobs
automatically,
and
on
top
of
that,
we,
as
it
says,
he
also
release
the
latest
version
of
kima
using
purely
on
prowl
and
last
but
not
least,
although
the
proud
working
group
has
come
to
an
end,
we
will
still
continue
improving
prowl
because
it
is,
it
is
a
very
active
community
and
it
is
changing
every
day.