►
From YouTube: Kubernetes visualizations in GitLab
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
Hello,
my
name
is
Victor
Naj
I
am
the
product
manager
of
the
environments
group
here
at
gitlab,
and
in
this
demo
video
I
would
like
to
show
you
how
you
can
visualize
a
cluster
state
within
gitlab
as
a
preparation.
I
already
have
a
cluster
running
here
that
has
slacks
installed
and
the
gitlab
agent
installed
and
in
gitlab
you
can
see
this
agent
to
be
connected
to
gitlab
and
it
doesn't
have
a
configuration
right
now
for
this
feature
to
work.
I
will
need
a
configuration
title.
A
A
This
snippet
here
this
is
how
you
can
configure
use
user
access
from
the
gitnab
UI
to
a
specific
list
of
project
and
or
groups
which
means
I
could
have
here
as
well
groups,
and
then
I
would
need
to
change
here
to
remove
the
last
project.
Part
at
first
I'm,
going
to
show
you
how
user
access
input
using
the
agent
service
account
works.
This
is
available
for
gitlab
free
users
as
well,
but
for
premium
and
ultimate
users
you
can
actually
restrict
user
access
to
the
specific
gitlab
user.
I
will
show
you
that
as
well.
A
So
let's
merge.
Let's
commit
this
file
to
gitlab,
enable
UI
access.
A
A
This
will
only
show
up
if
you
have
authorized
it
in
your
agent
configuration
now
I'm
going
to
save
the
environment
and
there
are
no
any
deployments
coming
from
the
pipeline,
so
this
page
is
empty,
but
the
environment
list
page
actually
shows
something
called
commanded
overview
and
if
I
expand
that
Chevron,
it
shows
me
that
there
are
10
running
pods.
Two
succeeded
shows
me:
the
number
of
deployments
demon,
cells,
applicants
and
service
details
as
well.
Let's
see.
A
What
do
we
see
under
the
pods
list
and
that's
correct?
We
actually
have
10
running
boards
and
two
that
succeeded
here
in
the
install.
This
is
great
now
let
me
show
you
what
you
can
do
if
you
are
actually
a
premium
or
ultimate
customer.
Let's
go
back
to
the
IDE
and
change
agent
to
user
now
enable
UI
access
as
the
big
lab
user,
as
my
cluster
doesn't
have
the
air
box
set
up
yet
for
my
user,
this
page
actually
cannot
load.
A
It's
sad
that
the
gitlab
user
knowledge
widget
lab
can
at
least
the
resources
required
here
so
to
allow
that
we
will
create
a
file,
let's
call
it
gitlab
user
airbag.tml
and
the
content
could
be,
for
example,
this
one.
A
Here
you
can
see
that
I'm
providing
a
cluster
role
binding
with
view
right
for
the
whole
cluster
and
for
the
user
modular
user.
As
you
have
seen
before,
there
are
a
few
more
groups
that
we
impersonate
together
with
the
user.
You
can
Target
those
as
well
I
briefly
touch
on
them
once
I
show
you
this
feature
so
hello,
access
to
a
hip
lab.
A
So,
as
I
mentioned,
you
can
actually
have
different
subjects
specified
here
as
well
as
we
documented
in
the
documentation.
We
provide
several
groups
and
a
few
extras
to
have
more
information
and,
for
example,
you
could
Target
the
specific
role
within
your
project
or
a
specific
role
within
your
group
here
as
well
to
restrict
airbag
as
you
prefer.
A
We
have
a
few
limitations.
This
is
the
first
release.
Is
you
might
know
that
the
main
limitation
is
around
namespace
handling
at
this
stage?
That's
why
I
was
using
a
cluster
role
by
link
here
and
not
a
role
binding.
We
do
not
support
namespaces
yet,
but
that
will
come
soon
in
a
few
Milestones
slightly.
Thank
you
very
much
for
your
attention.
If
you
have
any
questions,
please
reach
out
to
our
customer
success
managers
and
you
can
reach
us
through
gitlab
issues
as
well.