►
From YouTube: Che Community Meeting July 26th 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
A
A
B
B
It
means
that
we
have
to
migrate
to
generate
ingresses
using
networking,
ipi
version
1,
which
is
available
since
kubernetes
1.18,
and
basically
it
means
that
the
minimum
kubernetes
version
which
can
be
used
to
deploy
eclipse
share
will
be
1.19.
C
C
D
And
the
way
I
think
it
it
makes
sense
to
emphasize
that
we
are
picking
119,
not
just
because
it's
of
ingresses
it's
because
it's
a
minimal
official
supported
kubernetes
like
it's
kubernetes,
which
is
support
119
as
a
minimal
version.
D
A
B
I
will
write
email
to
cheddar
conventionalist
will
provide
more
details,
regression
plan
and
yeah.
That's
basically.
A
E
Yeah,
actually
I
did
it,
I
edit
one
more
okay,
so
here
you
can
see
sure
thank
you
so
yeah.
I
just
finished
the
friday
triage
and
I
noticed
that
we
don't
have
a
label
for
double
special
product,
yet
maybe
it
makes
sense
to
introduce
one,
and
maybe
there
are
more
components
that
we
need
to
add
labels
for
and
yeah.
D
E
E
But
yeah
I
don't
have
a
stroke
opinion.
I
would
distinct
the
stuff
on
chao
paratha
side
that
deploys
based
stuff
like
trific,
some
proxies
whatever
and
then
pieces
related
to
their
workspace
routing
instance.
D
A
B
Sorry,
you
mean,
I
agree,
yeah
late
operator
area,
plus
there
were
space
agent,
science.
B
E
E
And
again
there
are,
there
are
issues.
Maybe
issues
like
choprater
is
supposed
to
manage
their
workspace
operator
resources
and
such
issues
would
be
labeled
in
the
same
way.
So
I
still
think
that
the
workspace.
A
F
E
Yeah
sorry
for
that
concern
at
the
last
late
moment.
So
then
we
would
need
to
like
teach
people
that
share
for
out
of
their
workspaces
is
for
the
workspace
routing
not
for
chill
product
that
handles
all
the
workspace
related
stuff,
because
in
the
end,
you
will
have
everything
that
workspace.