►
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
We
want
to
simplify
this
setup
in
a
later
release
by
extending
the
gitlab
gitlab
CLI
to
make
it
a
more
thin
line
process.
Today
you
have
to
run
free
comments.
I
already
run
these
first.
You
have
to
Define
where
your
gitlab
server,
actually
kubernetes
access
server
attached
to
your
gitlab
instance,
can
be
found.
A
Then
you
have
to
provide
the
credentials.
The
credentials
are
combination
of
the
numerical
ID
of
the
agent.
You
can
see
it
in
the
agent
list
View
and
a
personal
access
token,
with
the
kubernetes
proxy
scope.
This
scope
was
introduced
in
the
current
liab
release
and
finally,
you
have
to
combine
the
two
into
context
and
use
that
context.
A
A
A
Now
this
request
required
some
time
because
I'm
in
Europe
gitlab.com
is
in
the
US,
while
my
cluster
is
again
in
Europe,
so
there
was
quite
a
lot
of
traffic
going
on
across
the
world,
but
the
whole
idea
is
that
I
could
access
that
with
my
user
identity,
as
this
is
a
regular
kubernetes
access
I
could
use
any
tool
that
I
prefer
to
use
like,
in
this
case,
kinin
s
on
my
local
laptop
to
access.
My
cluster
and
troubleshoot
issues,
or
just
see
how
things
are
going.
A
To
use
this
setup,
you
can
use
command
as
regular,
kubernetes
airbag
to
Define
the
authorizations
a
user
has
in
the
cluster.
If
you
are
a
premium
or
ultimate
user,
then
we
impersonate
the
gitlab
user
behind
the
person
access
token
in
the
cluster,
and
you
can
simply
Target
your
airbag
rides
for
that
user.
If
you
are
a
free
user,
then
you
are
restricted
to
use
the
service
account.
The
agent
k
pod
is
running
with
and
you
have
to
set
up
the
airbag
with
that
service
account.