►
From YouTube: Che Community Meeting October 18th 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Are
you
able
to
see
my
screen
actually,
so
I
wanted
to
start
from
so
that
our
roadmap
just
throw
it
up
an
update
so
on
the
on
the
wiki
of
eclipse
j.
So
we
have
now
this.
This
is
more
like
three
three
six
months,
so
that's
things
that
we're
going
to
work
on
in
the
next
three
months,
but
so
the
the
some
of
those
some
of
those
epics
here
are.
B
Actually
the
estimation
is
to
finish
them
in
six
months
rather
than
three
months,
but
that's
basically
identify
our
direction
currently
and
one
of
those
actually
is
the
production
ready
support
for
the
useful
code
as
a
as
a
generator
and
that's
what
I
wanted
to
talk
about
today.
B
That's
something
that
we
actually
since
we
we
wanted
to
to
support
it
with,
as
we
support
tia
so
supporting
these
extensions
running
in
in
the
in
a
container,
and
we
have
workspaces
they
find
it
specified
from
a
dev
file.
So
actually
we
add
to
think
about
how
to
implement
that,
and
flora
has
done
a
proof
of
concept
of
it
and
it's
based
on
this.
B
The
the
description
that
is
here
and
that
I
wanted
to
present
rapidly
okay,
but
that
represents
so
I
mean
I
think
that
we
should
focus.
I
want
to
make
sure
that
we
understand
the
problem.
The
problem
really
is:
we
want
to
be
able
to
run
visual
code
as
a
chair.
Okay,
so,
and
our
model
today
is
at
least
with
until,
like
the
default,
one
was
the
lever
space
that
before
that
workspace
engine,
it
was
actually
12.
B
B
To
figure
out
that
there
are
extensions
that
are
running
remotely
and
that
also
has
introduced
a
lot
of
bugs
and
problems
in
the
past,
and
we
we
have
been
able
to
put
a
lot
of
work
to
be
able
to
run
that,
so
we
are
able
to
run
a
lot
of
extensions
in
remote
containers,
but
we
spent
a
lot
of
time
to
be
able
to
implement
that
and
to
maintain
that
even
today
we
still
spend
a
lot
of
time
to
implement
that.
B
So,
with
this
your
record,
we
we
could
decide
to
implement
that
as
well.
But
that
would
have
take
time.
B
So
we
thought,
instead
of
like
spending
a
lot
of
time,
to
be
able
to
run
extensions
in
a
remote
container.
Why
are
aren't
we
going
to
to
run
so?
Why
don't
we
try
another
model
that
is
running
extensions
with
a
circle,
and
that
is
actually
what
I've
yeah
put
here
like
having
vsco
code
and
the
extensions
in
the
container
that
is
described
by
the
user
dev
file
so
injecting
via
circle
and
extension
in
index
in
that
container.
B
So
that's,
that's
one.
That's
at
least
that
has
been
how
the
plc
from
psc
has
been
implemented
and
yeah
the
the
tia
for
that
workspace
this
or
to
reduce
the
number
of
workspaces
of
containers
in
the
pod.
Today
it
works
a
little
bit
different
that
it
used
to
work
in
the
sense
that,
by
default,
the
visual
code,
extensions
are
run
in
the
first
container
of
the
of
the
dev
file,
so
here
we're
still
tia
in
one
container.
B
B
It's
it's
pretty
easy,
it's
isolated,
so
it's
either,
but
it's
still
running
t
I'm
on
container
and
we
just
focus
extensions
in
another
remote
container
and
that's
cool
also,
because
if
the
user
has
a
dev
file
with
one
container
where
he,
where
he
has
his
development
tools,
then
the
extension
can
benefit
of
those
tools
and
those
extensions
will
probably
require
like
maven
java
or
go
or
python
or
whatever,
git
etc.
B
Whatever
tool
you
probably
are
using
in
your
development
environment,
if
you
then
need
that
for
your
extension,
so
instead
of
having
tools
in
two
splitted
in
multiple
containers,
you
have
all
the
tools
that
you
need
in
in
one
container.
So
that's
that's.
I
think
it's
it's
the
idle
thing.
We
didn't
want
to
go
there
with
this,
your
code,
because
again
we
didn't
want
to
spend
time
to
implement
running
the
obvious
local
extensions
remotely.
B
So
but
that
said
there
is
a
so
there
has
been
a
few
concerns
that
have
been
that
have
been
raised
by
so,
and
I
think
that's
basically,
our
the
the
controller
team
was
raising
those
concerns,
and
I
think
that
if
I
try
to
sum
up
the
main
thing
that
that's
that
are
problematic
today,
so
I've
put
that
in
a
I
was
looking
at
some
slides
here
and
create
some
slides
to
to
make
it
things
more
clear.
B
B
So
if
we,
if
the
user
has
defined
it,
that
his
component
would
require
one
gigabyte
of
ram
and
then
we
inject
vs4
code
and
some
extension
that
require
two
gigabyte
run,
there
will
be
a
pro
right.
Things
went
wrong,
so
that's
that's
one,
one
thing
that
so
we
should
somehow
find
that
so
create
a
mechanism
to
actually
update
the
resources
required.
So
the
limits
and
the
request
of
cpu
and
ram
for
that
first
component.
B
So
that's
that's
the
first
problem
and
second
problem
is
how
to
start
with
the
so
code.
So
the
usb
code
is
injected
here
in
the
f5
component.
But
this
default
component
will
have
is
entry
point
so
and
we
cannot.
B
We
cannot
override
the
entry
point
of
of
that
component
where
this
is
so
good,
because
that's
something
that
it's
problematic
for
how
the
that
file.
So
we,
since
the
visual
code
is
so
code,
is
defined
in
his
home
that
file.
B
B
Oh
sorry,
the
start
event,
events
off
the
left
file
so
to
today
the
dev
file
version
2
as
events
and
you
can
define
some
comments
that
will
be
executed.
B
Pre-Start
and
those
are
usually
in
it
container
or
postcards.
Usually,
those
are
those
are
comments
that
are
executed
after,
but
we
never
implemented
them.
So
we
should
implement
those
two
things
and
there
are
other
things
around
around
volumes
as
well,
but
those
are
so
like
things
that
we
are
about
to
solve
in
a
way
or
another,
at
least
for
che.
B
That
will
be
so,
but
those
two
points
are
not
solved
yet
at
least
not
aware
of
so
I
think
that
the
the
other
that's
this
one
solution
that
we
can
we
can
propose
is
instead
of
having
a
visa
serial
code
and
the
extensions
injected
in
the
default
component,
we
could
have
until
we
got
these
two
things
called.
B
B
So
that,
as
one
problem,
that
is
a
problem
of
the
tooling
the
tooling,
that
is
so,
we
can
have
like
different.
B
B
So
I
don't
think
that's
easy
ideal.
We
should
we
should
move
forward,
so
we
should
actually
target
this
scenario
here,
but
at
least
at
the
beginning.
I
think
that
was
something
that
was
mentioned
by
sir
g
in
in
his
document
is
that
we
could
have
this
scenario
like
having
video
so-called
and
the
extensions
in
their
container
using
one
container.
B
That
is
like
the
default
container
if
like,
if
no
container
is
specified,
and
so
in
initially
it
will
be
the
default
container
or
visual
code
and
the
extension
will
run
and
when
we
have
implemented
those
like
the
two
problems
that
we
still
have.
C
B
No,
so
the
problem
of
the
volume
I
didn't
want
to
bring
them
here
in
the
equation,
because
those
are
like
are
not
shape
problems.
Those
are
like
deborah
space
problems
in
the
sense
that
when
we
create
the
depth
workspace
of
a
workspace
che
controls
that
so
he
can
inject
in
the
dev
workspace.
B
He
can
inject
the
volume
where
actually
the
that
the
circle
will
be
will
be
copied
right.
So
the
way
to
add
the
so-called
ear
is
with
a
volume
where
we
gonna
copy
the
circle
right.
So
that's
something
that
it's
already
in
the
poc,
that's
already
working.
B
The
thing
that
is
not
working
are
those
two
things,
so
I
don't
I
don't
I
don't.
I
don't
think
we
already.
So
I
think
that
we
can
discuss
about
solution
to
for
those,
but
there
is.
B
What
do
you
mean
with
terminal
volumes.
C
D
B
Okay,
but
anyway,
so
just
to
clarify
so
the
the
solution
here
that
I'm
proposing
here
that
one,
so
let
me
just
make
it
clear-
is
like
an
intermediate
solution
that
doesn't
have
this
problem
right,
because
in
this
case,
that
the
dev
file
that
defines
this
component
here
will
have
a
volume
already
defined.
B
Yes,
it
introduces
other
kinds
of
problems,
but
I
wanted
just
to
discuss
if
that
could
be
like
like
one
first
iteration,
because
I
think
that
we
can
say
we
don't
want
to
solve
those
two
problems,
so
those
are
like
issues
that
don't
doesn't
make
it
ready
for
production
ready.
If
we
don't
solve
those
two
problems
here,
it's
not
production
right.
B
B
B
It's
it's
like
we
can
yeah,
but
we
can
have
just
just
a
visa
so-called
image.
Not
so
just
so.
What
I
mean
is
that
we
can
implement
it
as
we
have
today
in
the
sense
that
we
don't
have
an
image
for
visa,
so
called
we
have
the
universal
image
and
the
universal
image
will
actually
have
a
volume
and
we
still
have
an
init
container
that
that
copies,
the
so-called
in
the
volume
and
with
we,
the
only
the
things
that
change
is
that
we
control
the
entry
point.
So
we
don't
have.
B
We
don't
need
the
past
start.
Okay,
we
control
the
resources,
the
definition
of
the
resources
of
that
image.
B
So
for
our
examples,
I
think
that
we
actually
won't
really
need
that
file
with
a
particular
a
particular
component.
So
it
will
just
be
one
dev
file
with
no
component
with
a
list
of
comments,
because
we'll
need
comments
to
execute,
to
run
the
the
examples
we'll
have
the
extension
json.
That
will
require
the
list
of
exam
extension,
so
I'm
just
trying
to
figure
out
if
there
is
a
way
to
like
having
something
that
doesn't
have
the
volumes
problem
that
we
have
today.
The
problem
with
resources.
B
D
D
C
D
B
Yeah,
but
so
that
that
image
is
not
used
by
only
by
it's
not
for
che
it's
new.
D
But
I
mean
it
can
be
generic,
like
you
have
like
the
psyche,
image
where
you
can
define
an
orient
variable
and
then
it
executes
a
start
command.
B
D
Yeah
but
we
say
that,
for
if
we
don't
have
any
data
file,
the
resolver
should
add
an
the
universal
developer.
D
B
B
What
what
should
a
client
do?
It
doesn't
know
how
to
run
videos
to
a
code
at
all,
so
I
think
it
would
be
better
to
anyway
define
what
they
find
a
container
that
can
run
visual
circle.
I
think
it's
good
that
in
the
dev
file
that
defines
visual
code,
we
actually
say
the
default
container,
so
if
there
is
no
other
container
to
inject
with
the
circle,
so
the
backup
container
to
run
the
so-called
is
the
universal
image
so
that
it's
something
that
is
defined
the
definition
of
a
circle.
B
We
can
call
it
like
backup
component
right,
so
if
we
can
put
an
attribute
saying
this
is
actually
a
component
that
you
can
use
if
there
is
no
other
component
e
id
terminal
component,
that
will
actually,
that
is,
that
exists
in
the
in
the
dev
file.
B
I
don't
know,
but
so
you
so
it
you
could
add.
We
could
add
an
attribute
like
id
terminal
component,
so
we
can
specify
that
actually
the
reason,
so
we
can
say.
Okay,
I
have
a
dev
file
right.
The
user
has
a
def
file
and
the
user
flag
can
flag
the
dev
file,
so
the
like
one
one
component
with
ide
terminal
component,
so
you
can
say:
okay
and
you
can
put
it
in
the
attributes
of-
is
that
file.
B
C
C
I
mean
we
tried
to
keep
their
workspace
as
simple
as
possible
without
knowing
anything
about
editors
ideas,
it's
just
their
file
which
can
be
merged
with
another
file
and
in
there,
and
you
will
get
flattened
file
which
will
be
run
and
this
about
adding
some
ide
specific
stuff
and
it
may
be
okay.
I
just
don't
get
that
margins.
What
is
their
whole
space?
And
what
is
the
chair
in
that?
Well,
but
it's
technical
details
we
can
move
forward.
I
think.
B
Yeah,
I
mean
that's,
that's
that's
something
that
for
me,
it's
just
a
kind
of
clarification.
So
today
the
fact
that
we
are
injecting
vso
code
in
like
the
the
first
arbitrary
component
is
something
that
is
fragile
right.
So
we
need
somehow
to
say,
hey
this
co,
so
we
need
to
an
attribute
or
something
that
say
this
is
so-called
or
the
extensions
need
to
be
in
component
one
or
component
two.
B
That's
something
that,
as
you
say,
it's
an
implementation
today,
that's
something
that
may
be
implemented
on
the
on
the
chase
side,
like
the
the
how
to
react
to
the
fact
that
there
is
this
attribute
so
in
which
in
which
component
visa,
so
code
need
to
be
run.
But
what
I
wanted
to
introduce
is
a
way
to
specify
this
container.
B
That
is,
the
backup
container
for
for
visa
circle
than
the
under
extensions.
D
B
D
B
If,
if
you're
not
injecting
this
so-called
an
exception
in
the
first
component,
you
don't
need
really
to
to
update
the
memory.
So
in
it's
like
the
first,
in
the
first
step,
you
don't
need
to
deal
with
with
the
first
problem.
You
will
need
need
if
you
want
to.
B
B
That's
true,
I
mean
you're
solving
it.
At
least
you
don't
need
to.
You
need
only
to
add
that
to
that
to
the
this
image.
That
is
the
the
editor
image
you
don't
need
to
so
to
the
to
the
component.
That
is
the
editor
component,
but
that's
true.
So
that's
like
something
that
anyway,
it's
a
problem
that
we
have
today.
B
So
we
need
to
solve
that
even
for
tia
space
workspaces,
because
we're
not
doing
that
today,
the
extension
are
injected
and
somehow
that
that
need
to
be
to
be
solved,
but
so
at
least
we
solve
it
for
visas
to
a
quote.
So
it's
just
a
problem
of
container
not
that
we
control
that
we
define.
That
is
actually
the
editor
container.
B
Want
us
to
take
a
decision
on
that
now.
I
want
to
have
a
discussion
so,
but
if
you
can,
please
ever
have
a
look
at
the
proposal
and
just
comment
there.
If,
if
there
is
any
so
for
any
concern
about.
B
C
B
This,
instead
of
implementing
so
the
what
has
been
what
has
been
done
by
floral
in
his
poc,
is
that
he's
in
injecting
visual
code
and
video
circle
extensions
in
the
first
component
after
that
file.
So
there
is
the
there
is
no
container
that
runs
with
a
circle,
not
not
dedicated
container
for
running
the
circle.
B
B
First
step
is:
let's
run
video
so
called
with
this
exchange
extensions
in
their
dedicated
container.
Okay.
So
that's
that's
the
first
step
and
then
the
second
step
would
be
to
implementing
these
two
things
like
updating
the
resources
of
a
dev
file
component
with
the
cpu
and
ram
of
visa
circle,
then
x
and
extensions
implementing
the
post
start
event
in
the
def
file
and
then
being
able
to.
B
Yeah
I
mean
so
we
never
yeah,
I
mean
that's,
that's
been
discussed
in
the
past,
so
we're
we're
going
to
introduce
visual
code,
but
we
are
not
going
to
stop
supporting
tia
at
least
now.
F
C
Think
yeah
that
may
be
another
topic,
but
I
think
it's
this
topic
is
not
open
enough.
The
issue
says
that
it's
just
a
matter
of
iteration
if
we
run
tia
in
the
same
way,
but
actually
we
don't
have
the
full
workflow
for
tia
in
that
workspaces.
C
So
we
we
change
a
lot
in
in
the
dev
file,
user's
dev
file
and
we
don't
have
a
way
to
distinguish
it's
users,
the
file
where
it's
tia
plugins
and
how
then
report
the
changes.
So
maybe
it's
a
sign
that
we
should
take
a
look
on
the
format
we
have
in
that
workspace
and
see
maybe
interior.
It
makes
more
sense
to
run
in
the
same
way
where
we
will
distinguish
users
do
file
and
then
what's
needs
to
be
injected
into
the
works.
The
container
right.
C
Yeah,
because,
currently
that
workspace
don't
support
fully
neither
tia
neither
last
code,
I
would
say
the
the
full
flow
and
in
the
time
this
we
with
that
proposal,
we
continue
moving
forward
two
directions
and
maybe
it's
a
question
of
saving
a
force
and
moving
only
one.
You
just
need
to
decide
which
is
better
and
why.
B
So
yeah,
I
think
that
there
is
something
to
clarify
here,
because
so
you
are
mixing
like
the
dev
workspace
work.
That
is
priority
number
one
and
video.
So
code
is
like
priority
number
two
very
so
we
need
to
release
the
workspace
with
tia.
That's
number
one
priority,
okay,
so
if
then
I
so
the
the
question
from
dimitro
was
about
the
different
kind
of
extensions
that
will
run
with
visa
circles,
so
not
related
really
to
to
that
problem.
B
So
I
I
hear
your
concerns,
but
you're
mixing
like
I
don't
know
why
but
vs
your
codes,
extensions
for
visual
code
with,
like
the
network,
space,
work
and
model.
I
think
that
so
for
the
for
the
extensions.
I
I
think
it's
separate
because.
B
We
can
support
the
circle,
extensions
that
are
that
run
on
tier.
We
can
support
them
with
visa.
So-Called,
so
obvious
record
is
able
to
run
those
rear
circle
extension,
but
we
also
call
the
vso
code
can
run
more
recent,
your
so-called
extensions,
so
maybe
at
some
point
we'll
have
we
will
we
want
to
have
two
two
different
extensions
catalog
with
the
two
list
of
of
those
two
set,
the
the
extensions
that
work
with
t
and
the
extension
that
work
with
with
the
usual
button.
B
B
So
it's
like
intellij
right,
the
that's
something
that
custer
are
looking
for.
F
B
From
at
least
from
a
specification
for
a
view,
I
see
like
the
just
a
matter
of
you-
have
one
death
file
that
defines
pia
and
one
that
file
that
defines
vs
your
code,
those
that
file
are
not
identical
and
we
can
play
with
them
to
actually
decide
to
switch
between
between
these,
like
where
tia
will
run
in
his
container
and
just
record
in
their
container
in
a
separate
container,
and
this
model
is
just
is
not
a
different
logic
in
so
like,
like
a
big
if
and
say.
B
Okay,
we
have
two
diff
different
branches,
one
of
the
code,
one
is
for
visual
code
and
one
is
for
tia.
It's
just
that
we
define
with
the
so-called
saying
in
runs
in
one
container
of
the
user,
and
we
define
tsa
not.
He
runs
in
his
dedicated
container.
B
The
extensions
will
be
the
same
yeah.
They
will
come
from
from
the
plug-in
registry.
C
B
Yeah,
it's
it's
this
one
that
actually
has
a
like
estimated
like
q4,
and
whereas
this
one
is
q1
of
next
year,.
B
And
so
yeah
I
sent
I
sent
out
an
email
on
friday
or
the
team
needs,
so
red
team
leads
mentioning
to
if
they
please
could
prioritize
items
so
for
for
next
pre-planning,
based
on
on
that
so
on
on
on
the
on
that
road
map,
but
putting
like
the
top
number
one
priority
in
the
road
map
is.
B
And
for
planning,
so
the
number
one
priority
anyway,
even
more
priority
than
than
this
one
are
always
bugs.
If
there
are
p1
or
blocker
bugs,
they
should
be
fixed,
so
they
should
be
planned,
at
least
before
anything
else.
C
Okay-
and
this
is
the
topic
up
to
date,
because
it
reference
milestone-
and
I
assume
the
items
in
milestone
and
in
the
epic
itself
in
the
epic
description
are
different.
Like
I
see
multi-cluster
support
using
one
double
space
operator
per
cluster
and
I'm
not
sure
if
there
is
any
any
work
planned
to
that
and
any
need
to
be.
Do
it.
B
So
I
think
that
that's
so
you,
if
you
mean
here,
do
you
mean
in
the
milestone,
or
do
you
mean
in
the
description
in
the
description
like
the
description
of
the
epic
may
not
be
up
to
date,
so
I'm
sure
that
that's
not
up
to
date.
B
So,
but
that's
that's
up
to
date.
That's
that's
what
we've
been
reviewing
right,
so
I'm
confused
here
so
you've
been
working
on
that
for
months
and
it
looks
like
so
it's
a
surprise
for
you
that
actually
we
are
not
so
we're
not
referring
that
as
the
source
of
the
things
where
we're
working
on
right,
that's
and-
and
that's
actually,
the
the
this
description
here
is
the
thing
that
you're
you're
working
you're
looking
at
so
like
that's
kind
of.
C
B
B
If,
then,
you
gonna
look
at
the
things
that
have
changed
in
the
last
six
months
and
we
we
have
been
updating
that
epic
plan
by
line
that's
true,
so
that's
not
and
for
those
people.
I
think
that
it's
true
that
there
is
something
that
we
can
fix.
B
On
the
other
end,
I
think
that's
not
a
question
that
you
should
ask
it's
just
that
you
could
take
and
fix
it.
If
you
think
that
there
there
is
something
that
is
not
so
you're
one
of
the
people
who
have
discussed
these
things
so
milestone
one
muslim,
two
mods
on
three.
You
should
be
even
better
than
me.
You
should
know.
What's
in
those
milestones
and
the
fact
that
you're
asking
me,
because
you
know
that
those
are
not.
B
I
think
that
you,
you
know-
that's
not
updated,
but
you
want
to
ask
that
just
to
to
provoke
right.
That's
why?
I
think
I
think
I'm
saying
it's
provocative
right.
That's
if,
if
you
didn't
know
that,
if,
like
you
were
a
first-time
user
coming
here
and
asking
that
genuinely,
I
would
say,
yeah
you're
right.
B
We
need
to
address
that,
but
you're
somebody
that
has
been
working
on
that
for
months
and
and
you
now
you
it
looks
like
today,
you
figure
out
that
that's
not
updated,
that
has
hasn't
been
updated
for
months,
so
we're
working
on
on
that
right.
So
for
a
team
leads.
I've
been
like
communicating
to
work
on
on
these
butts
on
here,
not
on
the
epic,
because
we're
not
keeping
so
those
things
are
are
changing
every
day.
B
So
I'm
not
going
to
update
it
here
and
if,
if,
if
you
find
that
it's
useful
for
somebody
go
ahead,
please
and
fix
it.
B
Okay!
So,
but
I
think
that's
something
that
has
been
discussed
enough
and
yeah
I
mean
there
is
the
new
and
not
worthy.
If
there
is
anything
else,
any
other
questions,
I
would
be
happy
to
take
it
offline.
A
D
But
when
you
do
that,
you
don't
have
any
way
to
plug
your
editor,
so
by
default
it
will
always
use
the
default
editor
and
in
shape
properties.
The
default
editor
is
a
chat
here,
so
here
it
just.
You
can
provide
an
additional
setting,
which
is
a
che
editor
and
by
providing
that
editor
parameter,
then
you
can
override
the
default
editor.
I
provided
a
demo
link
as
well.
F
D
Nothing
that
will
be
stored
in
the
user
preferences.
It's
a
pair
link
editor.
D
D
E
A
A
E
Yeah,
hello,
everyone,
so
it's
just
an
announcement
that
the
openshift
connector
plugin
was
updated
from
version
0.2.0.
E
Basically,
that's
it
about
openshift,
connector
topic
and
as
for
the
go
update,
so
it's
also
an
announcement
it.
The
co
version
was
updated
in
the
go
sidecar,
so
it
was
updated
from
version
1.16.6
to
1.17.2.