►
From YouTube: Che Community Meeting April 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).
A
All
right
so
yeah
thanks
for
the
patience
and
welcome
to
the
this
new
jaco
musical.
So
there
was
just
one
topic,
though,
that
I've
added.
So
if
you
want
to
talk
about
something
else,
we
will
have
the
time
I
guess,
but
I
would
like
to
keep
this
call
today,
just
a
30
minute
call
as
I
have
our
stop.
I
need
to
join
another
call
in
in
now
25
minutes,
but
so,
let's
start
with
the
with
today
topic
we
add
so
I
will
just
share
a
link
to
the
google
doc.
A
A
I
wanted
to
talk
about
git
configuration,
something
that
we
discussed
this
morning
with
igor
and
valerie
and
that
I've
discussed
with
others
in
the
past,
but
I
wanted
just
to
make
sure
that
we
are
aligned
on
that
and
basically
the
situation
today
is
that
when
I
start
my
workspace,
so
I
will
have
a
example
workspace
here
and
yeah
when
I,
when
I
started
by
default
today,
I'm
in
a
situation,
so
the
users
are
in
a
situation
where
they
do
not
have
git
configured
yet
so
they
need.
A
So
they
if
they
start
with
tia,
for
example,
they
should
get.
A
A
You
cannot
do
a
commit
from
the
command
line
until
you
have
set
your
username
and
email
in
the
past,
so
that
was
working
out
of
the
box
because
you
we,
we
were
populating
the
git
username
and
an
email
with
the
one
from
keyclock.
So
we
could
save
that
in
key
clock
and
we
could
set
it
so
this
is,
we
don't
have
keyclock
anymore,
so
there
is
kind
of
a
void
that
is
that
is
here.
A
So
the
way
to
be
able
to
do
that
today,
so
the
the
recommended
way
is
to
actually
create
a
config
map
so
that
I
will
it's
a
little
bit
bigger.
So
I
will
show
it
from
here
yeah.
This
is
like
the
conflict
map.
A
A
The
developer
should
have
a
config
map
in
his
namespace,
with
some
annotation
to
mount
the
content
of
the
kit
ma
the
configmap
in
etc,
git
config
and
then
the
data
of
the
configmap
should
be
just
the
the
key
config.
So
once
the
if
the
user
has
that
so
I've
just
applied
that.
So
I
created
the
config
map.
So
now
I
can
just
restart
my
workspace
with
that.
Setting.
A
While
it
starts,
I
will
go
to
my
config
maps
here
on
on
openshift,
so
I
should
see
that
the
git
config
is
here
with
the
configuration
so
once
we
create
that
that
will
be
mounted
in
every
container
of
every
workspace.
A
So
there
is
nothing
more
to
do
on
tier
side
close
this
one.
A
So
you
see
that
here
and
for
this
circle
it
should
be
the
same.
It
figures
out
that
you
are
actually
already
set
up.
You
have
already
set
up
the
git
config
because
it's
you
it's
set
globally.
So
it's
it's
possible.
So
you
you
don't
have
to
set
up
anything.
So
if
I
do
a
git
config
here
I
see
I
should
see
that
my
email
and
name
are
set
okay,
so
that
that's
something
that
it's
easy
today.
A
So
it's
like
the
current
situation
and
we
would
like
to
somehow
fill
the
gap
with
what
we
had
in
the
past.
So
we
have
there
is
another.
So
there
is
an
issue
that
we
had
created.
A
Zero
config
one
so
and
on
this
epic
we
are
trying
to
to
address
or
to
make
those
settings
more
automated.
So
the
first
thing
that
we
we
would
like
to
do
to
do
when
igor
is
working
on.
It
is
like
if
someone,
instead
of
creating
a
conflict
map,
configmap,
doesn't
exist,
but
someone
set
the
username
and
email
from
tia.
A
We
we
want
that
to
be
persisted
and
we
want
that
to
work
out
of
the
box.
So
this
is
one
thing.
Second
thing
is
at
the
startup
of
the
workspace.
A
We
would
like
to
always
authorize
the
users
with
is
keep
token,
even
if
it's
not
just
it's,
not
the
private
private
git
repository.
A
So
if
you're
trying
to
get
clone
a
github
github
repository-
and
you
have
set
up
the
github
service
for
your
instance
of
j
and
at
that
point
the
the
user
should
should
be
asked
to
authorize
che
to
access
his
data,
and
at
that
point
we
will
will
be
able
to
inject
the
secret
that
will
help
the
user
to
to
actually
push
this
code
same
thing
for
name
and
email
from
the
personal
access
token.
A
So
this
is
where
we
we
want
to
go.
So
we
want
that
to
be
as
automated
as
possible
the
user
when
he
first
created
his
first
is
his
first
workspace
and
if
the
administrator
I
set
up
the
git
integration
so
with
github,
then
we
will
automatically
set
everything
up
for
the
user.
So
that
means
the
config
map
that
I
just
show,
but
also
the
second
thing
that
so
because
on
my
ear
I
don't
I'm
won't
be
able.
A
So,
although
I've
set
up
my
git
config,
I
won't
be
able
to
push
from
here
so
because
I
don't
have
any
credentials
set
up
so
for
the
credential.
It's
not
the
conflict
level.
It's
another
object,
he's
a
secret
that
need
to
be
created
today
is
still
manual,
but
we
want
to
automate
that
as
well.
So
I
just
wanted
to
make
sure
that
we
we
were
on
the
same
page
with
with
these
and
yeah.
A
I
wanted
to
share
to
share
that
and
that's
something
that
plugins
team
is
is
leading
today,
so
they
are
working
on
on
that.
So
I
hope
that
will
in
the
next
version
we'll
have
that
automation
done.
B
I
have
a
question
and
who
is
going
to
be
in
charge
which
component?
Which
operand
will
be
going
to
be
in
charge
of
this
automation.
A
A
A
We
don't
plan
to
change
any
no,
I
mean
it's,
I
think
it's
the
simplest
approach
today,
then
there
is
also
the
the
the
more
we
we
move
forward,
the
bet
so
the
more
we
should
get
rid
of
the
chase
server,
but
I
don't
think
that
that's
that
makes
it's
not
such
a
big
change.
That
makes
sense
to
move
the
git.
B
Yeah,
that's
true,
but
at
the
same
time
I
think
we
really
need
to
prioritize
removal
of
the
database
and
removal
of
the
user
service,
because
you
know
it's
just
becomes
pretty
hard,
for
example,
for
to
support
from
the
developer
sandbox
perspective,
I'm
with
the
new
move
to
the
new
new
product.
B
I
expect,
for
example,
due
to
this
just
server
related
things
that
manages
users
at
some
point.
We
might
have
again
hard
times
with
with
our
sas
to
to
set
up
their
provisioning
flow.
Correct,
yeah,
just
just
saying
that
I'm
not
very
into
the
details,
but
since
valerie
is
going
to
work
on
that
valerie's
team,
just
yeah
don't
fall
back
on
database
at
any
rate
because
yeah
we
we
still,
we
need
to
expose.
A
Yeah,
but
it's
I
think,
it's
a
good
point
to
mention
so
don't
yeah.
Never
so
because
there
may
be
a
temptation
to
just
add
something
to
the
database
but
yeah.
We
should
yeah
keep
in
mind
that
the
database
is
something
that
we
want
to
deprecate
and
remove
completely.
So
we
should
not
store
any
user
related
stuff
in
in
the
database,
but
use
config
map
and
secrets
as
much
as
possible.
A
A
C
C
When
we
implement
this
flow
to
authorize
user,
when
we
use
public
repository
user
will
be
interrupted
each
time
to
to
login
to
authorize
so
each
time
an
user
will
create
the
workspace
for
the
first
time,
it
will
be
interrupted
just
to
inform
them
about
that.
A
And
if
you
haven't,
if
the
administrator
hasn't
set
up
the
git,
the
github
application,
we
should
not
intro.
So
there
is
no
oauth
flow
because
we,
the
administrator,
hasn't
set
it
up.
A
C
Yeah
one
one
more
topic
I
haven't
edited,
but
it
probably
makes
sense
to
discuss
for
the
next
month.
We
need
to
change
the
moderator
for
this
call
and,
as
I
see
from
the
table,
it
should
be
from
platform
team,
but
I'm
not
sure
if
he'll
be
able
to
do
that.
A
Yeah,
so
I
will,
I
will
ping
sergey
to
see
if
he
wants
to
do
that
anyway
or
but
otherwise
we'll
all
so,
I
will
ask
nick
to
do
that.
A
Okay,
thank
you!
Okay,
so
yeah!
Thank
you.
Everyone
and
sorry
for
the
delay
at
the
beginning.
Have
a
nice
rest
of
the
day,
bye.