►
From YouTube: Che Community Meeting July 25, 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).
B
C
Okay,
hello,
everyone
welcome
to
the
checkout
meeting
today
is
the
25th
of
july,
and
I
send
the
link
into
chat
to
the
document
with
the
agenda.
C
So
last
week,
chair
7.51.0
was
released
and
for
more
information
you
can
go
into
matter
most
eclipse
journalists
channel
also
about
upcoming
events.
This
week
on
wednesday,
we
will
have
another
session
of
cloud
2
time,
which
is
hosted
by
eclipse
foundation
where
ilya
will
talk
about
eclipsia
and
develop
space
engine,
so
please
feel
free
to
join
and
yeah
about
today's
agenda.
We
have
only
one
topic:
it's
from
anatolia,
about
chia
cluster
api
version,
one.
D
You
know
that
we
have
two
cluster
api
versions
that
we
support.
It's
version
one
and
version
two.
We
have
one
release
since
we
introduced
a
second
version
and
I
think
it's
time
to
duplicate
version
1
and
to
remove
it
in
a
future
release.
D
Basically,
the
reason
behind
this
is
the
following
that,
since
we
have
to
support
both
versions,
when
we
extend
check
cluster
version
2
with
the
new
fields
and
new
structure,
we
have
to
add
the
similar
fields,
to
version
1
and
to
implement
conversion
that
sometimes
it's
not
a
big
problem.
But
when
we
introduce
a
quite
big
changes
to
version
2,
it's
it
brings
real
difficult
to
to
support
in
the
same
way
version
one.
D
So
that's
why
I
created
this
issue
and
I've.
I
already
created
a
pull
request
that
duplicate
version
one
and
I
think
it's
time
for
all
clients
that
uses
version
one
to
switch
to
version
two.
Basically,
in
echo
eclipse
ecosystem.
I
think
it's
mainly
dashboard
that
we
have
to
check
if
it
use
version
one
and
I
think
it
might
be
qe
scripts
that
still
uses
version
one
somewhere,
but
I'm
not
sure
I
think
they
already
switched
to
version
two.
D
But
anyway,
everything
have
to
be
checked
before
I
remove
version
2
completely,
and
I
have
a
one
question
here:
inversion
in
eclipse,
sam
7.51
version,
one
will
be
duplicated
and
I
think
I
will
remove
it
in
the
next
version.
7.52,
if
it's
okay
or
we
have
to
extend
support
in
version
one.
B
So
the
the
question
is
more
like
what
that,
from
a
customer
point
of
view,
that
should
be
transparent
right
because
it
they
it
will
if
they
upgrade
from
one
version
to
the
other,
it
will
be
already
so
they
already,
even
if
they
started
from
a
v1
as
soon
as
they
upgrade
to
a
new
version.
It's
it's.
B
A
E
One
more
question
this
yeah
sure,
so
am
I
right
that
we
are
now
supporting
two
versions
of
two
versions
of
cluster
version,
one
and
version
two.
D
So
yeah
I
mean
sorry
when
you
you
can
you
are
able
to
create
ship
cluster
version,
one
right.
D
To
create
and
will
be
automatically
converted
to
version
two
and
then
if
you
push
a
check
cluster.
A
E
A
D
Think
that's
not
important.
I
recommend
you
to
check
if
you
use
version
one
in
some
scripts
and
switch
to
using
a
newer
version.
That's
my
recommendation.
E
A
A
Yeah,
so
absolutely
I
will
create
an
issue
for
that,
so
that
the
dashboard
will
do
a
switch
to
check
last
api
version.
E
Anatolia,
maybe
one
more
question.
So
could
you
please
clarify
so
once
you
will
remove
version
one?
It
will
not
be
required
to
use
this
header
when
past
your
g
cluster
is
this
version.
D
I
think
it
will
be
required
because
its
requirements
comes
from
gctl
when
it
applies
patch.
It
checks.
If
version
is
specified,
and
I
think
I
will
keep
it
to
be
sure
that
users
apply
the
right
version
of
the
cluster
api
patch.
E
A
D
Okay,
anything
else.