►
From YouTube: Che Community Meeting May 9, 2022
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
There
we
go
all
right,
so
yeah,
welcome
to
the
shay
community
meeting
for
the
9th
of
may
just
a
quick
note
about
logistics,
we're
hoping
to
switch
over
to
the
eclipse
foundation
zoom
as
of
next
week,
we're
using
blue
jeans
today
there
should
be
a
7
48
release
next
week
around
the
18
and
then,
as
usual,
going
forward
every
three
weeks.
Another
release
after
that
yeah
first
topic:
we
have
is
shay
cluster
api
version,
two
from
anatoly.
B
B
B
So
basically
in
used
version
api.
We
have
four
four
main
sections
points
for
space
sections
is
everything
related
to
workspaces
there.
Then
we
have
server
component
sections
where
we
have
all
server
components,
including
dashboard
server
postgres.
B
Progress
registries,
image,
cooler
and
everything
else
related
to
server.
Other
section
is
ingress,
it's
related
to
identification,
configuration
gateway
and
configuration
address,
including
secrets,
host
name
domain
and
everything
related
to
your
route
or
ingress,
and
the
last
section
is
container
registry
basically
to
write
the
contain
registry
container
to
pull
images.
B
We
had
a
pull
request
created.
It's
a
lot
of
changes.
Besides
vision
to
a
new
version,
I
had
a
lot
of
refactoring
there,
so
it's
probably
hard
to
review
as
the
only
things
that
make
sense
to
review
it's
a
new
cluster
api
to
get
no
the
structure,
the
sections,
the
fields,
everything
else.
I
don't
think
it
may
seem
to
just
sense
to
review.
B
So
this
pull
request
is
basically
ready
to
mesh.
We
have
some
conflicts
which
is
very
simple
to
solve
and
if
nobody
minds
I'm
going
to
merge
it
this
week,
but
having
this
progress
merged
of,
I
think
for
downstream
project,
it's
very
highly
recommended
for
basic
product
spaces.
It
will
be
very
highly
recommended
to
retest,
basically
all
scenarios,
because
a
lot
of
changes
have
been
introduced
there.
B
C
So
I
I'm
just
not
sure
it's
the
best
choice.
Frankly,
I
would
rather
prefer
something
more
generic.
D
It
was
not
about
the
chase
server,
but
it
was
like
server
components,
and
I
just
if
it's
not
clear
enough,
we
can
discuss
about
something
more
generic,
but
I
wanted
just
to
make
a
distinction
between
changes
to
the
server
components
of
j
and
changes
to
the
so
configuration
of
workspace
components.
So
everything
that
is
on
the
in
the
namespace
that
is
running
for.
C
Very
different,
difficult
part,
but
yeah
because
dashboard
a
I'm,
not
sure
if
the
server
components
in
general
sorry
yeah,
I'm
not
sure
about.
For
example,
the
dashboard
should
be
part
of
the
server
component.
C
D
Not
global
are
just
that
they
are
in
the
main
server
namespace,
like
the
dashboard
postgres,
such
as
server
registries.
Those
are
like
all
things
that,
if
you
change
configuration
for
one
you
change
it
for
so
for
forever.
D
So
for
a
thing
that
is
running
in
that
in
that
namespace,
so
these
are
like
central,
so
I
I
call
it
the
server
components
because
they
are
running
in
the
server
namespace
and
then
there
are
other
components
are
workspace,
components
that
are
running
in
the
namespaces
of
the
users
and
you
have
multiple
instances
of
those
yeah.
So
it's.
A
D
D
D
Maybe
you're
right-
and
I
don't
know
it's
just
that
yeah
I
want
to
make
it
easy
for
someone
that
says.
Okay,
I
want
to
change.
D
I
don't
know
settings
for
the
workspaces
of
the
users
like
I
want
to
make
the
default
id
something
or
I
want
to
be
the
default
name
of
the
namespaces,
something
yeah
I
want
to
make
it
easy
that
is,
is
in
the
workspaces
that
you
need
to
look,
whereas
if
you
want
to
change
a
configuration
of
the
registries,
this
is
like
not
something
that
it
running
for
a
user
is
something
that
you
need
to
look
at.
D
D
Okay,
yeah,
if
you
so
we
can,
if,
if
others
and
you
or
others,
have
other
proposal,
let's
discuss
that.
C
D
B
Will
come
maybe
it's
better
to
comment
in
the
mailing
front
right?
Yes,
okay,.
A
C
Yeah
grouping
is
fine,
I'm
just
you
know
that
there
are
some
discussions
about
the
server
decommissioning,
not
clear
if
we
are
actually
going
to
do
this
this
at
some
point
but
yeah
with
with
the
server
report,
there's
a
key
section
for
the
api.
I
think
we
can
provide.
D
Yeah,
but
that
that's
that's
like
we
are
not
decommissioning
server
components,
we're
decommissioning,
a
java
application
that
is
providing
some
api
to
create,
so
that
used
to
provide
some
an
api
to
create
workspaces,
but
the
functionalities
are
still
there.
So
I.
D
D
A
B
And
I
think
you
jim
you
have
to
take
a
look
and
maybe
adopt
something
in
their
tasks,
but
in
general
everything
should
keep
working
if
they
use
clustered
by
version
one.
It
should
keep
working
with
the
new
changes.
Oscillation
is
converted
from
one
version
to
another.
A
All
right
any
other
questions
or
thoughts
around
this
topic.