►
From YouTube: Kyma Knative Integration WG meeting 20190124
Description
Meeting Notes : https://docs.google.com/document/d/1BZoJQ5qsSudlix8PXjykQfsJtfwC7EgUy0BP3oORDsA/edit#heading=h.k5vjcpeufmzj
A
B
A
Gaurav
with
brother
and
eventing
is
not
working
properly
because
of
some
problem
with
cognitive
installation.
It's
the
issue.
I
will
show
it
now.
We
identified
the
problem.
There
were
two
two
problems.
First
of
all,
they
were
spending
named
creative
event.
In
name
space
is
not
getting
injected
and
there
are
no
side
cars
which
are
expected
to
be
there,
and
so
we
are
working
right
now
on
not
fixed,
but
it's
a
featuring.
We
were
developing
in
in
current
release,
so
it
will
be
delivered
son
and
the
second
problem
is
that
serving
accept
and
test.
A
We
wrote
somehow
left
test
services
behind
without
deleting
them.
For
now
we
just
disabled
the
test,
but
I've
created
it's
it's
already:
merged
master
and
I've
created
a
follow
up
to
write
those
tests
properly,
so
they
are
not
relying
on
helm
but
create,
are
creating
and
deleting
the
services
themselves
and
there's
a
follow
up.
A
C
Okay,
yeah,
so
I
have
two
updates.
The
first
one
is
basically
I
had
a
discussion
with
the
Kennedy
were
eventing
community,
and
then
we
shared
our
use
cases.
So
what
they're
doing
currently
is
they
are
collecting
the
use
cases
from
different
organizations,
different
products
like
from
pivitol
from
the
rift
and
then
I
think
from
some
other
organizations
also
and
they're,
trying
to
see
that
how
some
of
their
primitives
can
serve
more
or
less
all
of
those
use
cases.
C
So
this
is
going
well
and
I'm.
Waiting
for
update,
maybe
I,
will
need
to
check
on
the
slack
side.
They
will
they're
supposed
to
send
a
new
meeting
in
white
for
some
time.
I,
don't
know
next
week
or
this
week
as
a
separate
meeting
apart
from
their
working
group
meeting,
you
have
a
longer
discussion
around
this,
so
I
will
join
that
and
if
anybody
is
also
interested,
they
I
can
also
publish
the
same
in
the
other
key
native
Channel,
so
that
someone
wants
which
one
they
can
also
join
the
same
one.
C
A
A
C
C
A
meeting
every
Wednesday
on
6,
o
clock
or
6
p.m.
our
time,
ICSD,
and
but
this
meeting
were
to
discuss
the
use
cases
is
supposed
to
be
a
separate
meeting
a
long
one,
okay,
okay,
then
I
will
go
to
the
next
items.
To
the
next
time
is
basically,
we
want
to
upgrade
a
tentative
in
kheema
to
the
0.3
version,
because
it
will
add
some
values
for
the
serving
to
remove
the
increase
gateway
and
also
introduce
for
new
features
and
better
stability.
C
B
C
Is
kind
of
getting
more
realistic
and
then
nearing
the
completion
stage.
So
the
only
thing
that's
pending
there
is
a.
We
need
to
see
how
we
can
modify
our
info
components
to
use
the
new
mini
cube
and
given
it
is
versions.
But
apart
from
that,
we
will
look
good
on
this
and
we
should
be
able
to
complete
it
soon,
at
least
if
you,
when
it
is
upgrade,
and
then
we
can
see
that
maybe
in
the
next
milestone
we
can
pick
up
the
tentative
upgrade
part.
C
C
I
expect
a
review
and
the
next
action
item,
or
the
most
important
action
item
is
that
from
the
different
components
or
different
teams,
we
should
just
get
some
inputs
or
feedbacks
that
they
are
not
impacting.
Whatever
controllers
are
operators
they
have
written.
So
the
tests
are
already
working
and
passing
fine.
C
But
apart
from
that,
if
something
that
it
has
not
been
covered
by
tests
and
something
that
is
that
relies
on
some
kubernetes
under
10
or
features
that
are
deprecated
or
not
available
in
1.11,
maybe
the
team
should
conform
that
the
pull
request
is
in
in
there
and
then
I
have
removed
the
work-in-progress
level,
because
now
it
is
now
there
is
no
more
as
such
a
well
pending.
Apart
from
modifying
the
info
files
to
use
the
new
dependencies.
C
B
We
need
to
have
an
intermediate
version
of
eventing,
which
was
not
published
by
a
kid
native
eventing.
This
intermediate
version
was
prepared
by
kennedy
for
the
cube
call
and
it's
not
labeled
as
a
text,
so
that
we
could
have
a
workaround
tilde
version
0
to
of
content.
If
it's
integrated
in
kima
to
publish
to
publish
the
docker
images,
there
are
three
docker
images
inside
of
our
repository
of
kima
repository
and
then
change
the
installer
to
use
this
instead
of
the
token
coming
with
a
version
0
to
1
from
eventing.
B
B
Will
create
an
issue
for
this
and
we
have
to
decide
if
we
will
solve,
because
I
suppose
the
direct
correction
in
very
is
very
easy
only
to
change
something
in
our
native
installation.
These
3
images,
which
are
producing
only
ones
by
us
and
uploaded
in
the
FEMA
repository,
and
then
we
will
have
to
change
this
with
a
upgrade
for
to
get
a
0
3.