►
From YouTube: Che Community Meeting May 23, 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
A
B
A
So
let's
wait
a
couple
of
minutes
so
that
we
have
more
people
joining
and
then
we'll
get
started.
C
A
All
right
so
welcome
everyone
to
the
this
new
community
call.
A
So
I
think
that
yeah,
you
should
see
my
screen,
the
google
doc
with
the
topics,
so
we
have
released
the
j7
j748
last
week
and
the
next
one
next
release
will
be
749
in
a
couple
of
weeks
and
basically
I
think
that
that's
it
for
the
releases
and
there
is
no
upcoming
or
past
event,
and
so
let's
get
started
right
away
with
the
first
topic.
So
anatoly
you
had
the
the
first
topic.
D
Hello,
everyone.
Do
you
hear
me?
Yes,
we
hear
you
well,
okay,
fine,
so
yeah
we
have.
We
have
the
issue
with
customer
service
creation,
so
basically
everything
was
fine
when
eclipse
is
deployed
from
gstl,
but
it
when
it
comes
to
openshift
ui.
It
goes
in
a
slightly
different
way,
so
the
workflow
is
the
following.
D
We
install
eclipse
here
using
openshift
ui,
it's
installing
openshift
operators
in
a
space
and
when
it
comes
to
custom
resource
creation,
openshift
ui
suggests
to
create
the
custom
resource
in
the
very
same
name
space.
It's
actually
open
shift
operators,
and
it's
not
it's
not
what
we
would
like,
because
in
general,
all
operands
should
go
in
a
different
time.
Space
right
and
there
is
a
problem.
How
we
can.
D
How
can
we
achieve
that
right?
Because
customer
source
is
created
by
a
user?
D
A
Is
it
correct?
Yeah,
yes,
correct,
yes
correct,
so
the
idea
would
be
that
the
operator
when
it
started
it.
It
looks
for
one
customer
source
of
type
check
cluster.
If
there
is
no
no
check
cluster
customer
source,
it
creates
the
eclipse
jnamespace
and
add
their
default
check,
cluster
and
yeah.
Basically,
that's
that's.
Basically,
it.
D
But
what
if
a
user
want
to
configure
samsung
in
a
cluster.
A
He
will
he
will
be
able
to
do
that
later,
so
it
will
have
the
default
configuration
and
if
you
want
to
change
something,
you
will
have
the
opportunity
to
do
that
later.
It
doesn't
really
change
much
it's
just
and
most
of
the
time
it
should
be
fine
with
the
so,
at
least
for
the
first
time
that
he
installed,
he
should
be
fine
and
then
he
can
iteratively
try
to
change
things
on
check
cluster
customer
source.
But
I
think
that
this
is
really
bad.
Much
better.
A
Then,
even
like
the
first
time
you
deploy
che,
you
need
to
go
through
two
steps
like
one
you
install
the
operator
and
then
you
need
to
go.
Do
a
second
step,
creating
a
check
cluster
and
you
don't
know
why
you
need
to
do
those
two,
because
actually
you
just
want
to
have
che,
and
you
don't
know
exactly
what
you
need
to
change
in
the
configuration.
So
most
of
the
of
the
time
is
like
that.
You
just
want
the
default
one.
A
So
it's
it's
just
really
a
matter
of
trying
to
make
the
thing
simple
for
the
most
used
use
case,
the
most
common
use
case.
The
most
common
use
case
is,
I
just
want
the
default.
A
Then
there
is
a
particular
use
case
when
you
want
some
particular
configuration
and
then
here
you,
you
don't
really
make
it
more
difficult,
because
it's
still
two
steps,
two
steps
operation.
So
you
need
to
deploy
the
operator
to
subscribe
to
operator
and
then
second
step
is
configuring
the
check
cluster?
So
it
doesn't
really
change
much.
It's
it's
from
my
point
of
view.
It's
really
just
a
benefit
for
administrators.
D
I
think
if
we
go
in
this
way,
we
have
to
update
all
documentation.
Key
has
to
adopt
the
workflows
and
yeah.
A
lot
of
changes
will
come
to
gctl
as
well
and
to
separator.
A
Yeah
I
mean
for
for
documentation,
at
least
that
that's
where
everything
started
is
because
today
it's
so
complicated
so
to
describe
the
installation,
because
you
need
to
explain
that
and
it
makes
things
super
simple.
A
So
it's
just
just
subscribe
to
the
operator
and
that's
it
and
then
you
you
have
in
eclipse
j
namespace.
You
have
the
disease
that
is
installed,
so
it's
really
simplify
that
for
qe.
Yes,
let's
discuss
that,
but
we
discuss
so
I
discussed
with
with
dimitro
earlier
today
and
they
they
agree
that
that's
like
makes
things
work
better.
So.
D
A
Yeah
absolutely
and
to
be
clear:
it's
something
that
we
we
didn't
wanted
for
a
death
spaces
street
at
all.
So
so
at
least
what
I
said
is
that
we're
not
able
to
have
that
for
death
spaces
3-0.
So
that's
something
that
will
come
later,
but
for
three.
So
we'll
we'll
document
that
as
a
known
issue
for
now
for
the
next
for
the
3-0
and
probably
for
3.1.
So
that's
something
that
we
can
target
for
3.2.
D
D
Yeah,
but
I
see
some
issues
here,
for
instance,
so
brother
is
deployed.
It
creates
such
a
cluster
customer
source
by
itself
and
then
user
tries
to
create
another
one
custom
resource
from
shift
ui,
because
yeah
api
is
there
so
and
if
it
leads
to
problem
for
which
operator
it
will
find
two
custom
resources.
D
E
A
But
that
that's
a
problem,
so
if
you,
if
you
test
with
openshift
key
tops,
I
think
that
when
they,
when
their
the
operator
is
installed,
they
are
not
directed
to
the
page
where
you
can
create
customer
sources
so
and
that's
a
problem
that
we
have
already
today.
So
today
a
user
can
create
two
two
customer
sources
and
that's
problematic.
A
A
A
Okay,
so
let's
move
to
the
to
the
second
topic,
those
are
actually
two,
I
think
two
presentation
from
sergi
and
max.
So
I
I
will
stop
sharing
if
you're,
okay,
sergey
and
max.
E
Oh
yeah,
so
that's
two
topics,
as
you
mentioned,
about
the
namespace
creation
and
provisioning
and
the
second
topic
about
authentication
authorization
which
was
prepared
by
mihawk
so
most
work
made
by
him,
but
unfortunately
he
was
not
able
to
join.
I
think
maybe
maxim
we
can
start
with
you
here.
E
F
F
What
do
we
have?
We
have
three
main
main
operations.
First,
one
is
getting
the
list
of
the
available
namespaces
to
provision
chain
to
them.
It
has
nothing
to
do
with
provision
itself,
but
it
can
be
useful,
for
example,
for
dashboard
to
show
user
the
options
where
we
can,
where
he
can
install
chair
or
something
like
second
stage,
is
provision
which
is
done
on
chess
server
side
and
third
stage
is
provision
of
which
is
done
of
chopper.
F
Here
is
also
a
couple
of
couple
of
options,
so
the
first
option
is
try
to
find
namespaces
which
are
maybe
prepared
by-
I
don't
know,
cluster
admin
or
chairman
or
whatever,
to
to
use
the
as
a
as
a
user
workspaces
there
so
to
prepare
them.
Admin
should
put
correct
labels
and
correct
annotations
on
that
namespaces,
and
we
will
find
they
will
find
them,
and
then
provision
chairs
there.
F
So
if
you're
talking
about
the
getting
list,
it
just
will
be
returned
as
a
options
list.
Second
step.
If,
if
there
wasn't,
there
is
no
prepared,
namespaces
riaz
and
look
into
user
preferences,
we
try
to
find
namespace
names
there,
because
user
may
be
using
some
somehow
earlier
and
he
may
want
to
reuse
his
namespace
in
the
in
the
new
in
the
new
architecture
psg
operator.
C
C
E
F
That's
probably
that's
probably
for
first
step
when
we
did
the
migration
from
database
database
based
into
operator
based
change.
So
when
it
was
database
based
chair,
we
have
user
preferences
stored
somewhere
right
now.
If
I
remember
correctly
there
stored
versus,
did
you
remember
exactly.
E
So
the
pre-preferences
used
to
store
the
configuration.
Then
what
was
that
the
moment
of
the
namespace
creation
and
that's
needed
to
in
case
if
admin
changed
the
preference
on
the
on
the
go
like?
Let's
say
there
was
a
username
chair,
already
have
10
name
space
created,
and
then
he
decided
to
change
it
to
username
crw.
Something
like
that.
So
to
make
sure
users
will
not
lost
existed,
namespaces
with
via
workspace,
the
namespace
preferences
is
used.
E
So
that's
that's
a
place
to
save
the
name
of
the
already
created
namespace,
because
that
that
was
the
main
purpose
of
the
using
preferences
in
namespace
level
like
in
in
in
the
process
of
detecting
the
name
of
the
user's
namespace.
E
C
E
E
And-
and
I
think
at
that
time-
I'm
not
sure
did
we
store
the
annotation,
the
username
and
annotation.
So
maybe
there
was
no
step
step
one
as
it
is
right
now,
like
search
by
label.
Annotation.
A
Just
as
a
as
a
note,
the
now
we
are
renaming
quadri
workspaces
to
dev
spaces.
So
when
a
user
migrate
an
existing
instance
of
quadratic
workspaces,
then
we
change
the
default
namespace
name,
and
that
means
that
that
property,
so
that
preference
will
be
used.
In
that
case,
I
guess
for
for
the
immigration
part.
C
C
I
just
don't
get
it,
but
okay,
you
mean
that
if
there
is
a
pattern
set
like
username
dash
chair,
so
in
the
new
version
of
the
products,
it
will
be
like
not
share,
but
something
different
or
not
crw
whatever,
and
then
the
check
on
the
prep
on
the
database
kicks
in
and
continue
using
this
like
old
pattern
for
all
namespaces.
C
C
A
No,
that's
that's
a
lot,
much
more
reliable,
but
what
you're
saying
is
that
the
code
today
relies
on
the
on
the
namespace
preference
in
this
use.
So
if,
if
I'm
an
administrator-
and
I
change
the
namespace
default,
the
the
in
check
cluster-
the
server
property
namespace
default,
then
what
you
are
saying
is
that,
instead
of
looking
at
the
labels,
you
are
going
to
look
at
the
preferences
in
this
case
to
make
to
to
avoid
to
create
a
new
namespace
for
user.
That
already
had
one
with
the
old
name.
E
Not
exactly
like
a
we
are
looking
at
the
a
slide
which
is
telling
that
that's
a
chain,
so
first
step
is
label
and
annotation
and
if
they
already
exist,
no
matter
what
the
pattern
and
no
matter
what
they
preference,
I
think
that
would
be
used.
A
Okay,
yeah
and
what
is
the
in?
What?
In
what
circumstances?
The
labels
would
not
be
there
so
because,
because
che
adds
labels
and
if,
if
they
are
created
automatically
so
the
namespace
is
created
automatically.
And
if
the
namespace
is
created
manually
pre-created
by
the
administrator,
he
has
to
add
labels.
E
Like,
ideally,
yes,
but
I
would
say,
there
are
multiple
circumstances
for,
for
instance,
I
think
like
a
deaf
clusters.
They
don't
have
those
annotations
and
labels
and
they
use
pattern.
Am
I
right.
E
C
C
You
know
with
the
conversion
of
the
product,
but
there
is
explicit
preferences
that
we
have
added
recently,
because
previously
we
haven't
got
that
one
checking
for
kubernetes,
namespace,
labeled,
true
and
before
we
haven't
got
that
one.
So
it
was,
you
know,
set
to
false.
I
think,
and
we
haven't
got
the
labels
in
place,
but
we
enabled
it
some
time
ago.
C
I
think
roughly
like
a
month
ago.
So
now
we
also
label
the
namespaces,
and
I
think
mario's
question
was
why
why?
Why
do
we
need
this?
You
know
boolean
flag
chain
for
kubernetes
namespace
label,
true
or
false,
because
it
looks
like
the
labels
should
be
always
in
place,
because
it's
like
reliable,
reliable
way
of
doing
that,
but
we
currently
have
this
flag
that
need
to
be
set
explicitly
so
that
the
labels
would
be
set
on
the
namespace
level.
E
I'm
not
sure
like
400,
but
as
far
as
I
remember
not
all
clusters
allow
labeling
namespaces.
I
may
be
wrong,
but
I
think
that's
that's
the
case.
C
E
Yeah,
I
I
remember
like
at
the
like
a
long
time
ago,
there
was
like
some
difficulties
with
labeling,
an
annotation
which
requires
some
extra
privilege
for
chess
servers
account
or
or
we
use
we
used
to
create
the
namespaces
on
behalf
of
user
users,
service
account
and
it
was
not
allowed
for
them.
But
at
some
point
of
time
we
switched
to
use
chess
server
service
account
to
create
new
spaces.
Maybe
that
was
the
case
white
white,
where
we
add
this
property.
F
Yeah,
so
to
summarize,
that's
the
third,
the
first
time
user,
creating
a
namespace,
for
example,
he's
using
default
template,
something
like
username,
chair
or
username
dave
and
yeah.
When
creating.
We
will
see
that
later
when
it's
created,
it's
already
made
properly
labeled
so
next
time
it's
just.
It
just
goes
to
the
step,
one
and
fins,
one
which
is
properly
labeled
and
annotated
and
use
it
for
four.
F
It
checks
the
kubernetes,
namespace
creational
load
flag
and
if
we
don't
have
namespace
and
that
creation
aloft
is
not
is
not
set
sell
to
false,
we
will
throw
exception,
of
course,
because
we
can't
we
don't
have
any
namespace
and
we
can
create
it.
Otherwise
such
namespace
is
created
and
properly
labeled
with,
as
I
just
mentioned
before
so
third
step
of
of
that
process
is
the
running
namespace
configurators.
F
So
there
is
an
interface
called
namespace
configurator
and
there
is
like
maybe
10
of
implementations.
Some
of
them
are
infrastructure-specific
made
specifically
for
openshift
or
for
copyrighted,
and
some
of
them
are
common,
which
configure
security
service
accounts,
different
kind
of
permissions
preferences,
ssh
case
and
stuff
like
that,
so
they
all
executed
one
by
one
and
that's
it
for
the
chat
server
itself.
C
F
Yeah,
those
both
properties,
namespace
label
and
namespace
annotate,
it's
which,
which
labels
and
annotations
should
be
set
to
the
newly
newly
created
namespace.
So
if
you
just
create
it
from
scratch,
you
should
set
some
annotate,
probably
that's
in
interior.
It
should
just
should
be
the
same
as
as
we
said,
as
we
look
for
right
to
them
to
be
found
next
time.
C
Because
there
is
labels
like
liberal
and
and
singular
so
the
the
singular
one
is
just
a
boolean
right.
The
plurals,
probably
you
specified
the
labels
so
that
we
will
be
able
to
identify
that
this
particular
label
is
used
for
workspace.
F
Yeah,
maybe
you
write
a
probably
service
zenbach
in
my
presentation,
because
I
see
there
should
be
a
list
of
annotations,
but
probably
yes.
This
is
also
all
only
boolean
wallets
which,
if
true,
then,
that
you
set
multiple
wallets
from
from
previous
one
right
to
annotation,
to
avoid
to
avoid
like
mistakes
and
different
different
annotations
right.
But
I.
E
Yeah,
it's
exactly
the
same
like
a
label
whatever
it
should
be
annotated
or
not.
I
guess
at
least
I
see
it
in
my
chair
cookies.
E
Little
same
like
a
labels,
whatever
you
need
to
annotate
name
spaces
in
singular,
it's
a
boolean,
it's
selling,
whatever
you're
doing
labeling
or
annotating
and
in
plural,
that's
exactly
the
labels
or
notation
that
has
to
be
at
a
value.
E
E
So
annotation
is
used
because
in
theory,
username
can
contain
some
characters
that
does
not
allow
it
to
be
a
label.
E
So
that
is
why
we
search
first
by
label
and
then
iterating
by
overall
all
items
and
checking
annotation
one
by
one
because,
like
a
username
can
in
theory
contains
something
which
we
can
put
in
label.
E
F
A
Before
releasing
the
presentation
for
more
understanding,
so
I
mean,
since
we've
annotation,
you
are
free
to
have
also
characters
that
are
not
allowed
in
labels,
so
you're,
putting
like
the
the
name
in
the
notation
right.
That's
what
that's
by.
E
Understanding?
Yes,
yes,
yes,
yes,
so
labels
are
static.
Thingy
right
now,
by
default,
an
annotation,
it's
something.
So
something
which
is
changing
depends
on
the
user.
A
The
the
characters
are
are
not
valid
ones,
so
we
could
have
instead
used
annotation
right
away.
So.
A
It's
just
my
understanding
because
it
looks
like
then
the
the
algorithm
for
the
algorithm
for
looking
for
the
namespace
of
a
user
would
be
of
being
simpler.
So
you
filter
by
labels.
You
see,
okay,
these
are
chain
names
faces,
and
then
you
you
look
at
the
rotation
for
the,
maybe
maybe
it's
it's
not
good
for
performances.
So
just.
A
And
so
it's
because
we
don't,
we
don't
just
use
annotation,
because
it's
it's
better
because
for
for
performance
as
one
of
you
it's
better
to
filter
on
labels.
E
No,
let's
once
again,
so
we
use
both
labels
and
annotations.
We
use
annotation
to
store
the
username,
because
in
theory
we
assume
that
username
may
contain
something
which
we
can't
put
in
a
label.
E
So
right
now
what
we
are
doing
when
we
searching
the
namespace,
we
filter
all
namespaces
by
the
label
and
then
iterating
over
those
name
spaces.
What
we
found
and
compare
the
the
annotation.
E
That
might
be
not
the
best
performance,
but
that's
a
safer
in
terms
of
some
very
surprising
characters
and
usernames.
E
A
problem-
I
guess
the
user
open
shift
username,
so
all
valid
namespace,
but
that's
my
assumption.
I.
F
Let's
switch
to
operator
provision,
so
what
operator
does
is
provisioning
of
all
kind
of
certificates,
certificates
like
self-signed
trusted
or
something
like
that
provision
of
proxy
settings?
If
there
is
any
gtls
certificates
and
not
selector
and
tolerations.
F
Probably
for
self
sign
and
trust,
it's
just
the
process
of
copying
copying
the
secrets
from
check
cluster
namespace,
where
the
chains
installed
into
username
spaces
and
just
just
adding
correct
names
and
some
annotations
as
well,
and
that's
it
about
proxy
settings.
They
are
read
from
check
cluster
sierra
license.
F
Confirm
up,
I
believe,
but
it's
just
kind
of
strange
I
was
expecting
say
story
as
a
secret,
but
it's
a
config
mug.
In
fact,
and
also
it's
like
a
secrets:
it's
just
copied
into
username
space
and
just
change
change,
name
a
little
bit
and
get
the
proper
annotations
and
note
selector
and
tolerations
also
copied
from
check
cluster.
C
Yeah,
I
have
a
design
question,
mainly
white
who's
decided
to
spread
it
across
two
components
like
chair
for
87,
because
my
understanding
that,
on
chess
server
side,
we
have
like
a
couple
of
configurators,
it
could
be
a
lot
of
configurators.
I'm.
E
C
Yeah
I
mean
I
understand
the
part
with
the
share
operator
not
being
able
to
catch
the
action
when
the,
for
example,
user
user
needs
a
new
namespace
right,
but
at
the
same
time
I'm
not
very
clear
with
the
database
part,
because
so
the
the
we
have
an
issue
about
the
database
decommissioning
already
right.
This
is
something
that
we
want
to
proceed
with,
and
my.
C
I
understand
that
there
is
an
edge
case
for
migration,
where
we
could
potentially
find
something
in
preferences
that
would
allow
us
to
identify
the
namespace
that
was
you
know
previously
used
for
workspaces,
but
other
than
that.
Do
we
have
anything
else
there.
E
Maximum
may
ask
you
to
go
back
to
the
slide.
Then
the
name
space
provisionary
by
chester,
namespace
configurators-
is
there
a
list
of
them
on
some
slides.
E
Like
sort
of
b,
I
wouldn't
say
that
because,
like
ssh
keys
preferences
stuff
like
that,
so
it's
more
like
coping
the
data.
What
was
in
chess
seven
it
used
to
in
the
format
which
is
needed
for
their
workspaces
and,
as
you
said,
the
the
share
database
should
be
decommissioning
and
only
the
theme
like
native
kubernetes
thing
has
to
be
used.
So
I
I
would
say
those
configurators
are
absolute,
which,
which
is
in
the
chess
error.
C
E
F
Yeah,
probably
they
should
be
reviewed
because
I
believe
not
not.
All
of
them
works
with
database
directly
or
reach
something
from
there
for,
for
instance,
this
one
which
configures
service
account
and
stuff
like
that
they
are
kind
of
kind
of
independent,
but
those
ones
which
yeah,
which
like
read
sshk,
for
example,
from
from
your
from
your
profile.
C
So
my
understanding
that
so
the
in
in
general,
even
if
there
are
some
bits
that
use
database
for
namespace
provisioning,
they
should
be
removed
right
because
they,
you
know
they
either
ambiguous
at
some
point,
because
you
know
that
you
know
we
shouldn't
probably
get
any
info
about
the
what
namespace
to
use
for
workspace
creation
from
the
database
right
from
whatever
preferences.
C
We
should
fall
back
on
labels
and
annotations
or
on
the
pattern
and
yeah
they.
If
there
are
some
edge
cases,
we
can
rework
it,
but
if
there
are
some
configurators
that
use
database,
they
should
be
removed
and
in
general
the
reason
is
that
namespace,
provisioning
from
just
server
side
should
not
hold
back
on
database.
In
any
sense.
F
A
I
think,
like
yeah
in
the
in
the
chase,
server
git
repository,
somehow
you
should
probably
have.
A
So
like
looking
at
the
the
time,
we
don't
have
a
lot
of
time,
so
that
remains
so
maybe
sergi.
The
the
the
second
topic
is
something
that
you
you
may
want
to
bring
next
week
would
be
that
okay,
for
you.
E
Yeah,
that's
okay.
I
may
share
this
video
in
the
melody,
so
everybody
can
take
a
look
and
prepare
some
questions.
They
have
okay,
cool.
A
Right
all
right
is
there
any
any
other
topic
that
somebody
want
to
talk
about,
or
questions
for,
for,
mac's
presentation
and
by
the
way
max.
Thank
you.
Thank
you
very
much.
This
is
this
is
alfo.
I
think
that
that
brought
a
lot
of
discussion,
questions
and
better
understanding
of
the
the
work
of
the.
So
what
was
going
on
with
the
chase
server.
A
Yeah
there
is
a
question
from
tyrell
sadiq,
so
hello
to
ralph.
So
the
the
question
is:
if
we,
if
we
have
access
to
those
powerpoint,
I
think
that
the
the
the
that
max
will
make
it
available
from
for
everyone,
and
it
will
put
the
link
on
the.
A
I
think
that
the
best
way
would
be
if
you,
if
you
also
send
so
if
you,
if
you
put
it
in
the
contributing
markdown
file
in
chess
server,
it's
good,
but
also,
if
you
send
it
to
the
mailing
list.
Also
it
would
be,
would
be
really
good.
I
think.
A
Yeah
for
last
week,
yeah
max,
that's,
I
think,
a
game
for
you.
A
Cool
okay!
Thank
you.
Thank
you
very
much
and
talk,
so
I
think
we
can
close
the
call
here
and
talk
to
you
next
week,
bye-bye
everyone
bye.
Thank
you
folks,
bye-bye.