►
From YouTube: Che Community Meeting June 6, 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
C
C
B
Can
try
thank
you,
india,
this
dude.
B
A
So
yeah
last
week,
I've
I've
shared
the
video
I've
recorded
about
authentication
authorization
and
routing
and
stuff
around
che
gateway
works,
and
this
is
like
in
in
a
scope
of
let's
say,
knowledge
transfer,
because
we
as
a
platform
team,
no
longer
fully
work
on
on
chair.
So
we
would
like
to
transfer
our
knowledge
to
to
other
teams
and
other
developers
so
yeah.
I
I
have
no
no
structure
for
this
meeting,
no
know
like
organization,
so
this
can
be
free
discussion
about
this
topic.
A
If
you
have
any
questions,
if
you
saw
the
video,
if,
if
you
didn't
see
the
video
you
can
still
ask
or
you
can
watch
it
later,
ask
questions
on
mailing
list
being
me
on
slack
matter
most
or
whatever
so
yeah.
That's
that's.
I
think
for
me.
If,
if
any
one
of
you
would
like
to
like
discuss
anything
around
this,
we
can,
I
can
do
it
now.
A
It's
half
an
hour
for
almost
30
minutes.
C
B
B
Okay,
what
if
there
will
be
a
question
after
looking
at
the
video
how
it
would
be
asked.
A
Yeah
yeah,
you
can.
I've
started
writing
in
a
cheddar
mailing
list
with
link
to
this
video.
So
you
can,
you
can
ask
there.
I
think
most
of
you
know
me
and
know.
B
A
C
Yeah,
I
I
have
a
question
after
watching
the
video
and
thanks
michael,
it
was
a
great
video,
very
detailed,
so
I'm
wondering
about
the
performance
actually
and
was.
C
C
C
A
We
have
tested
this
in
like
isolated
environment
when
we
were
like
picking
the
technology
for
the
gateway,
and
we
chose
the
traffic
we
we
have
tested,
I
think
h,
a
proxy
nginx
and
and
envoy.
I
think,
and
we
were
testing
like
we
have.
A
I
don't
know
five
or
six
like
test
cases
which
tested
like
one
test:
one
tested
the
load
of
a
lot
of
open
workspaces.
A
Second,
one
tested
like
a
lot
of
starting
stopping
workspaces
and
stuff
like
that,
and
but
maybe
I
have
some
numbers,
but
these
numbers
might
be
like
two
years
old,
so
I'm
not
sure
if,
if
it's
really
like,
if
it
has
any
any
real
value
and
we
haven't
tested
it
on
a
real
environment
like
on
real
installation
and
yeah,
that's
that's
true
that
if
there
is.
A
A
I
think
that
I
think
that's
that
might
be
some
either
back
in
in
traffic
itself
or
we
are
doing
something
wrong,
but
I
don't
know
what
exactly.
C
Okay,
yeah,
just
if,
if
you
still
have
this
data
about
like
number
of
concurrently
starting
stopping
and
working
concurrently,
running
workspaces
and
can
share
it
in
this
mailing
right,
it
would
be
very
useful.
A
The
single
host
gateway,
poc
performance
test
results
recommend
is
like
the
report
from
that
from
that
testing.
So
it's
summarized
results
and
most
important
pieces
that
we
figure
out.
A
C
Okay,
cool
okay,
but
there
are
no
figures
at
this
point
you
can
provide,
because
I
I'm
scheming
the
dog,
but
I
don't
see
like,
for
example,
it's
like
500.
A
B
B
C
Discussed
it
with
michael
asynchronously,
it's
about
the
fact
that
currently,
all
the
api
requests
are
stateful
and
the
authorization
cookie
is
required,
so
it
can
be
fixed
on
the
proxy
config
in
geocarator.
C
But
my
understanding
is
that
in
in
the
latest
version
of
chat,
basically
the
server
api
can
be
reached
only
from
browser.
So
it
means
that
only
dashboard
and
mainly
from
swagger-
you
can
execute
it,
but
no
one
else
can
technically
execute
any
request
to
your
server.
Why.
C
This
one,
because
we
have
an
issue
for
database
decommissioning
and
actually
maybe
we
can
just
leave
it
as
this
so
may
mean
that
chess
server
api
currently
cannot
be
executed,
for
example,
from
command
line
right,
because
you
will
not
be
able
to
provide
the
cookie
yes
and
it's
a
good
indicator
is
that
chess
server
api
is
not
used.
That's
at
least
my
understanding
right.
C
I
think
it
used
to
used
to
call,
for
example,
ssh
key
creation
with
chess
server
api,
but
I
don't
think
it
use
it
anymore.
I
think
that
it
was
removed
at
some
point.
This
logic
was
so
we
there
was
a
plan
not
to
use
your
server
api
from
mainly
chatty
yeah.
I
think
that
was
the
plan
for
their
workspaces.
A
A
But
I'm
really
not
sure
if,
if
if
it
is
using
for
anything-
and
I
would
bet
that
it-
it
does
not
use
it,
because
we
were
like
moving
some
some
of
this
data
that
was
previously
called
from
just
server
to-
I
don't
know,
secrets
or
conflict
maps
or
or
at
least
that
that
was
the
plan.
As
far
as
I
remember.
C
C
So
this
kind
of
another
sanity
check
that
this
api
currently
cannot
be
just
use
from.
You
know
command
line,
for
example,
and
it
will
be
easier
to
to
remove
the
database,
knowing
that,
like
services
cannot
be
called
without
this
cookie
and
yeah.
There
are
no
consumers
of
these
endpoints
other
than
let's
say
dashboard.
C
A
A
B
A
Yeah
I
see
it
is,
it
is
not
tested
on
chair,
it
is
isolated
environment.
So
it's
just
some
because
we
were
testing
the
the
technology
to
use
to
to
do
the
routing.
B
A
B
A
That
was,
it
was
really
just
to
to
to
test
the
technology.
We
should
use
to
make
the
decision,
but
don't
don't
trust
the
numbers.
Basically
I
mean
like
if
we,
if
we
simulated,
I
don't
know
500
running
workspaces
with
some
traffic,
don't
don't
like
transfer
that
to
real
environment
that
that
won't
work.
I
think.
B
A
A
A
So
that
should
not
happen
and
I
haven't
seen
that
and
hopefully
it
will.
It
won't
happen.
But
again
it's
it's
like
two
years
since
we
did
did
the
testing,
so
the
traffic
itself
evolved
a
bit
so.
A
A
A
Traffic
like
the
traffic
project
or
oh
project
yeah,.