►
From YouTube: Che Community Meeting - September 7th, 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
Yes,
can
you
hear
me
roman,
yes,
yeah?
Thank
you
very
much,
so
I
just
wanted
to
take
the
opportunity
now
that
is
so
where
most
of
the
people
are
coming
back
from
vacations
and
we
restart
to
to
provide
a
short
high
level
overview
of
chair
road
map
or
the
near
term.
B
Okay,
so
yeah.
Those
are
like
a
few
items
that
I
wanted
to
talk
about,
but
before
that
maybe
not
everyone
is
familiar
with
the
labels
that
we
are
adding
to
to
the
issues
and
mainly
to
epics.
So
there
are
a
few
roadmap
labels
that
we
are
adding
and
there
there
is
a
label
for
six
months
or
one
year.
B
I
guess
that
we
so
on.
We
have
also
the
three
months
label,
so
we
are
so
what
we
would
like
to
do.
It's
something
that
we
we're
still
working
progress,
because
that's
there
is.
We
need
probably
need
to
do
some
cleanup
on
the
issues
that
are
here.
B
There
are
some
that
are
missing,
but
what
we
like
to
do
is
that
for
every
epic
that
we
create
to
assign
it
a
roadmap
label
to
indicate
if
it's
like
three
months,
six
months
or
or
one
year,
and
we
so
that
that
anybody
would
be
able
to
see
the
roadmap,
doing
a
query
on
github
so
like
what's
coming
in
the
next
three
months,
what's
coming
in
the
next
six
months,
so
we
are
doing
that.
We're
not
ready
yet.
So
it's
not.
B
As
I
said,
it's
not
so
there
are
like
probably
issues
that
are
small
or
not
should
not
be
epic
that
are
here,
but
yeah.
You
can
have
an
overview
right
now
for
for
that,
it's
at
least
something,
and
there
are
still
things
that
need
to
be
added
here.
So
that's
why
I've
I've
actually
created
an
eye
level,
chair
roadmap,
slides
and
the
other
thing
is
that
once
this
has
been
cleaned
up
and
is
good
enough.
B
We'll
update
the
road
map
that
we
have
in
the
wiki
to
actually
reflect
that,
so
that
people
can
look
at
those
issues,
those
labels
and
those
queries
to
look
at
the
three
month,
six
months
and
one
year
issues.
B
So
let's
say:
let's
go
through:
let's
see
what
are
actually
eye
level,
so
something
that
I
wanted
to
stress
is
that
we
are
trying
to
concentrate
and
refocus
on
the
optimal
installation
of
che,
because
there
are
a
lot
of
configuration
options
in
the
last
years
that
we
have
added.
B
You
could
start
single
user
or
multi-user
che.
You
could
actually
have
install
all
the
workspaces
in
one
namespace,
kubernetes
namespace,
or
you
could
actually
have
one
per
user
or
multiple,
multiple
namespace
one
for
every
workspace.
So
there
are
those
are
like
a
lot
of
things
that
we
want
to
get
rid
of.
B
We
want
just
to
support
what
we
think
is
the
best
for
users,
and
this
is
first
of
all
multi-tenant,
so
an
installation
that
is
that
has
security
and
authentication
setup
by
default,
one
namespace
per
user,
so
that
all
the
workspaces
of
a
user,
all
the
kubernetes
objects
related
to
a
user
workspaces
will
be
will
be
created
in
one
namespace.
B
We
want.
We
don't
want
to
support
one
namespace
per
all
the
users
configuration
and
we
don't
want
to
support
the
multiple
namespaces
for
one
user
configuration
either.
B
So
that's
what
we
think
is
the
best
approach
as
a
oneness
space
per
user.
So
and
from
the
networking
point
of
view
also,
we
want
to
support
single
lost
only
so
we
don't
want
to
have
a
different
url
for
every
workspace.
We
want
to
have
just
one
work,
one
url
that
is
so
one
one
url
one
one
domain,
one
us
name
for
everything
j
so
for
accessing
the
user
dashboard
for
accessing
workspaces.
B
So
let's
solves
a
lot
of
problems
for
certificates,
so
because
that
means
that
we
only
need
a
tls
certificate
and
yeah.
That's
that's
kind
of
kind
of
things
that
have
been
feedback
that
we've
been
hearing
during
those
last
years,
so
we're
we
want
to
have
to
support.
Only
only
that
then
the
other
thing
from
a
user's
point
of
view.
B
So
we
we
currently
have
users
and
kubernetes
users,
so
the
the
j
users
can
be
different
than
the
users
of
the
underlying
kubernetes
cluster
that
doesn't
allow
to
to
do
some
stuff,
so
some
operation
on
on
the
kubernetes
cluster.
B
If
not
we
so
if
so,
the
only
way
to
do
that
so
to
do
some
operation
is
to
provide
the
user
with
some
default
service
account
so
that
he
can
do
some
operational
kubernetes
like
deploying
an
application,
but
I
think,
but
we
think
that
it's
much
better
if
the
user,
the
che
user,
is
actually
a
kubernetes
user.
So
user
of
the
cluster,
so
we
are
going
to
support
that
scenario
only,
and
we
are
also
for
that
we're
going
to
remove
the
dependency
from
key
clock.
B
So
you
you
don't
need
key
clock.
We
are
able
to
use.
We
should
be
able
we'll
be
able
to
use
any
oidc
provider
for
authentication
whatever
is
being
used
by
is
used
in
kubernetes
for
authenticating
users.
B
The
other
thing
is
that
yeah
we
we
want
to
use
oauth
for
git
providers
more
and
more
so
want
to
use
that
instead
of
using
ssh
key
pairs
or
git
credentials.
B
So
we
would
like
to
actually
use
the
oauth
flow
to
authenticate
users
through
git
providers,
so
that
everything
is
automated
for
the
user
that
doesn't
have
to
copy
their
password
some
somewhere
or
or
copy
paste
their
ssh
ssh
key.
Then.
The
other
thing
is
that
we
want
to
have
sort
of
this
oauth
flow,
and
since
the
user
is
a
kubernetes
user,
we
would
like
to
have
the
user
from
the
start
from
the
first
time
that
they
start
the
workspace
to
be
able
to
do.
B
Git,
push
and
cube
ctl
apply
from
within
a
workspace
without
any
manual
configuration
by
the
user,
so
we
want
to
go
to
the
zero
config
for
pushing
to
get
and
to
using
kubernetes
the
kubernetes
api,
so
that
j
will
always
be
integrated
with
with
kubernetes
with
the
underlying
kubernetes
cluster
and
with
the
the
source
control
manager,
so
the
sorry,
the
git
provider.
B
So
that's
that's
about
the
optimal
installation,
the
configuration
I
want
to
really
focus
on
and
yeah.
We
want
to
be
more
opinionated
and
removing
some
options
that
we
thought
that
were
not
evil
and
introduced
more
problems
and
benefits.
So
then
we
have
the
dev
file
version,
2
base
workspaces
and
the
network
space
operator.
We
are
in
the
right
in
the
middle
of
the
transition
really
important
transition
for
us.
B
We
are
going
to
move
from
the
chase
server
that
the
j
server
api-
that
was
a
a
web
application
written
in
java
that
could
be
it
was
exposing
an
api
to
start
workspaces.
B
We
are
going
to
replace
that
with
a
kubernetes
api,
an
extension
of
the
kubernetes
api-
that
is,
the
that
workspace
operator.
This
actually
will
create
just
an
extension
to
is
creating
an
extension
to
the
kirenas
api
so
that
any
kubernetes
client
will
be
able
to
create
a
new
dev
workspace
resource
that
actually
will
implement
the
che
workspaces.
B
So
the
dev
file
version
two
are
will
be
used
to
create
that
workspace's
resources
in
inches.
So
that's
already
possible
what
we
are,
what
we
still
need
to
do.
The
work
that
need
to
be
done
is
to
make
that
enterprise
ready
production
ready
because
it's
there
are
some
features
like
idling
or
like
air
gap,
support
that
are
not
there
yet.
So
we're
working
for
that
and
are
also
the
all
our
samples
are
not
being
redefined
with
the
file
version.
B
Two
then,
for
the
key
clock,
dependency
removal.
We
already
talked
about
that.
Another
important
thing
is
that
we
want
to
support
visual
code
as
as
an
editor,
so
there
will.
There
will
be
soon
a
proof
of
concept
of
using
vsco
code
as
an
alternative
to
tia
that
we
that
that
is
the
is
the
fourth
error
editor,
and
so
we
already
it's
already
possible
to
use
intellij
and
orders
jetbrains
ideas.
So
we
want
to
provide
the
possibility
to
use
jesus
circle
as
well.
B
B
We
think
that
there
are
many
places
where
we
can
actually
start
using
some
cache
systems
so
that
we
don't
need
to
reprocess
the
definition
of
the
workspace
so
that
the
workspace
will
will
be
able
to
to
start
it
faster
and
but
before
that,
the
thing
that
we
want
to
do
is
that
we
want
to
start
testing
and
measuring
the
num
that
the
time
it
takes
to
start
a
a
workspace
and
making
sure
that
at
every
release
we
will
consider
a
blocker
if
we
are
introducing
so
as
the
startup
time
is,
is
is
is
lower,
so
it
takes.
B
The
sort
of
timing
is
longer
than
the
previous
release,
so
we
want
to
improve
that
at
at
every
release
and
then
the
other.
The
last
thing
is
that
we
would
like
to
use
the
oauth
flow
for
authenticated
for
git
provider
more,
so
we
currently
support
that
for
factories,
but
would
like
to
support
them.
B
Even
not
in
the
factory
link
startup
so
when,
when
starting
a
workspace
from
like
from
a
just
a
a
dev
file
or
yeah
a
custom
workspace,
we
would
like
to
to
start
using
the
overflow
for
for
all
those
for
every
every
scenario,
so
that
so
the
the
git,
the
the
user,
will
be
authenticated
with
with
git
since
his
start
and
he
opened
his
workspace.
B
So
that's
that's
basically
it
for
the
this
high
level.
Chair
roadmap,
we
we
are
probably
going
to
go
through
more
in-depth
in
deep
details
on
some
of
those,
I'm
thinking,
for
example,
about
the
vso
code
as
an
editor.
I
think
in
the
next
week
we'll
be
we'll-
may
have
some
presentation
and
demos
about
that.
But
for
for
today
that's
that's
just
I
wanted
just
to
provide
an
eye
level
yeah
view
of
of
the
work
that
we're
doing
so,
yeah,
roman!
B
That's
that's
it
for
for
that
topic,
so
I
will
stop
sharing
and
if
there
is
any
question
just
feel
free
to
to
ask
them.
Thank.
C
Questions
comments
here,
so
I
have
a
few
first
about
this
code.
Editor.
Does
we
do
do
we
plan
to
just
support
it
as
an
editor
or
we
plan
to
make
it
default.
B
So
we
we
want
to
support
so
the
as
as
as
of
today,
this
today's
stage.
What
we
know
is
that
we
want
to
support
it
as
we
support
other
editors.
B
So
as
it
will
be
one
of
one
of
three
editors,
then
the
thing
that
we
need
to
think
about
is
how
good
is
it
so
compared
to
tia
so
in
in
terms
of
multiple
things
and
then
we'll
we'll
decide
if
that
will
become
the
default
or
not,
but
today
we're
not
ready
to
say
that
that
it
may
become
the
the
default,
but
if,
for
some
reason
so
we
have
invested
in
tia
we're
investing
in
tia
still
so
yeah.
B
If,
for
some
reason,
vstrocode
doesn't
perform,
or
we
see
that
it's
harder
to
maintain
as
an
editor
will
keep
tia
as
a
default.
But
today
t
has
the
fault
and
we
would
just
want
to
do
a
poc
to
start
testing
and
playing
with
it
so
to
and
to
get
feedback
from
from
users.
So
that's
the
main
goal.
C
B
We
will
we'll
call,
I
think,
we'll
need
to
to
change
the
the
major
version
as
soon
as
we'll
stop
supporting
the
version
one
of
the
dev
file.
B
So
it's
not
it's
not
about
adding
features
is
more
like
when
we
stop
supporting
that
file
version
one.
So
the
idea
is
get
to
the
feature
complete
with
the
file
version.
Two
so,
and
I
hope
that
by
december
we
should
be
close
to
that
and
then,
when
we,
when
we
get
to
that
start
so
getting
feedback,
etc,
and
when
we
feel
ready,
we
communicate
on
the
deprecation
of
the
default
version.
B
One
we
give
some
iteration
some
time
to
users
for
that
and
then
to
yeah,
to
update
their
their
clients
and
their
installations
and
and
then
we'll
deprecate
and
so
we'll
remove
the
support
for
it
and
we'll
release
to
eight.
B
It
could
be
as
a
as
an
outcome.
So
I
don't
know,
then
I'm
not
sure
exactly
what
what
why
we
need
an
outcome
for.
So
it's
not
a
disguise.
It
hasn't
been
a
discussion
right
where
we
actually
had
a
question
and
we
had
to
decide
on
something
here.
So
I
don't
think
that
this
topic
really
needs
an
outcome,
but
not
sure
why
we,
we
have
an
outcome
for
every
topic.
B
E
Hello
folks,
so
I
just
want
to
quickly
announce
that
today
we
we
have
published
web
id
github
action
under
the
red
hat
publisher,
so
I
can
quickly
show
you
what
we
are
trying
to
achieve
and
what
we
are
trying
to
promote
with
the
demo.
So
roman.
If
this
is
okay,
I
can
start
sharing
the
screen
right.
E
Okay,
so
all
right
folks,
so
on
the
github
marketplace
under
the
ide
category,
you
now
should
be
able
to
find
try
in
web
ide
github
action
which
allows
you
to
add
a
comment
and
status
check
and
to
open
a
project
on
online
web
id
instance.
So
by
default
it's
going
to
be
workspaces,
openshift.com
eclipse
hosted
by
red
hat,
but
you
should
be
able
to
also
customize
it
and
point
it
to
your
own,
hosted
instance
with
the
web
id
instance
input
and
how
it
works.
E
So
I
already
enabled
this
github
action
on.
One
of
our
repositories
that
is
currently
is
under
the
incubation
is
kubernetes
image
cooler.
So
when
you
add
the
action,
it
actually
adds
two
things
by
default,
so
it
creates
a
comment
with
the
link
to
the
trying
the
pull
request
on
the
eclipse
share,
hosted
by
red
hat,
as
well
as
edit
the
status
check.
That,
basically
does
the
same.
So
it
points
to
the
factory
link
for
opening
the
pull
request
on
the
eclipse
hosted
by
red
hat.
So
let's
try
to
do
that.
E
I
click
on
these.
Obviously,
you'll
need
to
have
a
developer
sandbox
account
since
workspaces
openshift.com
offering
comes
from
from
the
developers
redhat.com.
E
E
Okay,
we
got,
we
got
a
problem
with
the
nightly
attack,
which
I
suppose
was
removed.
Sorry,
so
it's
just
demo
effect.
So
yeah.
E
To
fix
it
really
quickly,
let's,
let's
see
how
it
works
in
reality,
so
the
problem
is
that
dev
file
has
been
removed.
E
E
Because
it
still
uses
some
obsolete.
C
E
Okay,
folks,
so
sorry,
I
just
I
just
think
that
this
action
got
broken,
so
not
the
action,
but
the
dev
file
actually
got
broken,
because
because
our
dev
file
was
pointed
the
just
the
wrong
branch.
So
if
I
just
quickly
merge
it,
I
think
it
should
work
now.
E
If
I
now
do
some
very,
very
basic
update,
let's
just
make
sure
that
our
dev
file
is
is
fine
and
is
using
the
right
clay
image
for
golan.
E
So,
what's
going
to
happen
is
that
web
id
github
action
kicks
in
and
it
should
actually
provide
the
status
check
and
comment
in
the
pull
request,
just
how
it
works
now.
So,
let's
give
it
another
go
now
from
the
status
and
we're
already
using
a
different
branch
and
fingers
crossed.
It
should
start
the
workspace
correctly.
E
We
can
run
the
build
and
literally
check
all
the
things
in
action
just
like
from
the
normal
id
so
yeah.
I'm
stop
sharing
yeah,
sorry
for
pretty
long
of
pretty
long
description.
So
what
is
coming
in
that
we
we
are
going
to
update
the
documentation
website
as
well
as
in
next
week.
E
We
are
going
to
publish
a
blog
post
on
the
developersredhat.com,
with
more
details
about
the
github
action,
as
you
might
know
that
the
github
action
actually
fall
back
on
the
dev
file
for
the
id
creation,
so
we
will
cross
link
in
in
the
in
the
documentation
blog
post.
E
That's
about
it!
Any
questions.
B
Yeah
one,
I
was
wondering
if
it's
possible
with
the
github
api
to
know
who
is
using,
who
has
been
using
this
github
action,
which
repos.
E
Yeah,
it's
a
good
question.
I
I
don't
know
so
what
we,
what
we,
what
we
do
know
is
just
basically
the
regular
statistics,
but
I
can
I
can
look
into
that.
It's
yeah
that
would
be
interesting
to
know
so
we
just
published
it
today.
Actually,
so
it's
like
collaborative
effort
with
the
red
hat
github
action
team.
So
we
have
other
other
actions
in
place.
So
I
will,
I
will
stay
in
touch
yeah.
We
will
probably
need
more
details
on
on
the
on
the
usage
once
it
will
be
more
promoted.
E
F
E
Yeah
well,
the
github
action
is
actually
very
simple,
so
it
only
just
adds
the
relevant
pull,
request,
comment
and
status,
so
it
basically
generates
the
appropriate
links
right.
So
there
will
be
no
problems
with
that.
However,
as
as
I
mentioned
that
the
github
action
actually
usage
usually
depends
on
the
dev
file
that
is
located
in
the
repository
right.
E
So
if
the
workspace
for
this
particular
project
is
very
resource
consuming,
there
are
chances
that
you
will
not
be
able
to
open
it
on
workspaces,
openshift.com
right,
because
we
do
have
the
resource
limitations
there.
Like
eight
gigabytes,
I
think
seven
gigabytes
of
ram
and
in
order
to
use
it
like
you,
you
will
need
to
host
your
own.
Your
own
instance
and
update
the
web.
Ide
instance
input
to
point
it
to
your
particular
eclipse
chair
that
will
satisfy
the
requirements
for
your
repository
right.
F
E
Yeah,
I
think
we
will
so.
As
I
said,
we
are
planning
to
update
the
documentation,
so
this
action
will
probably
be
under
the
eclipse
hosted
by
red
hat
docs.
Plus
we
want
to
craft
a
blog
post
on
developersredhat.com,
so
we
will
need
to
put
the
limitations
in
place
and
and
yeah
provide
the
details
about
the
dev
file
usage.
So
currently
it's
for
workspaces,
openshift.com,
it's
defiled
version
one
in
future.
I
believe
we
will
switch
to
their
file
version
too.
So
yeah,
that's
important.
E
Okay,
thank
you,
so
stay
tuned,
more
dogs
update
are
coming.
B
Any
questions
and
I
thought
from
a
user
point
of
view-
is
there
any
any
change
or
impact.
B
Okay
and
and
that's
in
term
of
open
shift
that
is
not
changed
yeah,
but
what
version
of
openshift
had
the
abandoned?
The
old
version.
D
G
Yeah
sorry
like
if
you
write
letters
right
now,
if
you
start,
for
example,
for
mini
q,
like
the
rate
this
by
default
is
0.70,
it's
not
to
be
fine.
I
don't
remember
anything
so
nothing
changing
the
point
of
user
and
in
the
openshift
side
I
think
from
4.3
is
using
0.17.