►
From YouTube: Kyma Knative Integration WG meeting 20190103
A
B
Okay-
and
the
only
point
for
today
we
have
no
one
else
have
haven't
put
in
something
here
here
is
the
planning,
for
it
is
0.7,
which
happens
next
week
from
my
side
is
one
thing:
I
would
like
to
discuss
and
I
see
myself
as
feasible
for
for
next
release.
Maybe
there
are
other
topics
you
want
to
mention,
but
they're
not
here.
So
let
me
start
first
thing
I'd
like
to
have
in
0.7
release
is
I'm
grading,
creative
to
newest
version,
hopefully
0.3.
Why
is
that?
B
Because
version
0.20
version
0.3
will
get
rid
of
creative
English
great
way,
which
will
help
a
lot
with
our
installation
process
and
will
enable
us
to
do
some
creative,
much
stuff
with
installation,
for
example,
having
dynamic,
IP
allocations
and
etc,
etc,
etc,
which
have
been
creative
English
greatly
prevents
us
I
have
an
issue
for
that.
Let
me
shove
it.
B
It's
here.
I
will
link
it
and.
C
B
C
C
B
C
So
in
our
case,
when
we
look
at
kima,
we
have
a
lot
of
events,
and
if
we
follow
this
abstraction,
we
might
end
up
having
a
lot
of
low-level
pods
and
resources.
That
might
not
be
right
approach
to
do
so.
So
this
is
one
item
that
at
some
point
we
would
like
to
align
with
the
cannot
even
see
their
to
how
they
can
use
some
kind
of
multiplexing
around
them.
Most.
C
B
C
B
C
C
Another
thing
that
is
going
on
at
the
kinetic
level
they
are
discussing
about
the
kinetic
use
cases
like
oh,
how
they
envision
various
aspects
of
eventing
as
a
use
case
from
a
business
aspect
and
I
think
at
some
point
we
will
also
provide
some
inputs
to
that,
for
that
I
have
a
document,
but
that's
currently
not
public,
so
at
some
point
I
will
make.
It
probably
can
then
share
it.
B
C
Was
actually
a
targeted
40.6
because
we
wanted
to
initially
have
a
very
rudimentary
version
of
a
kima
running
on
top
of
kima
eventing
running
on
top
of
kennedy
venting,
and
then
this
proposal
was
a
part
of
that.
So
this
is
still
we
want
to
target
it.
4.6
and
I.
Think
10th
of
January
is
that
I'd
line
for
this
review.
If
I
remember
it
correctly,.