►
From YouTube: A quick demo of the GitLab Kubernetes Agent
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
Hi
in
this
quick
video,
I
want
to
show
you:
how
does
the
gitlab
quantity
agent
work
with
a
repository
on
gitlab.com?
We
have
our
amazing
documentation
under
the
usual
docs.gitlab.com
page,
and
I've
already
made
the
initial
setup
of
this
agent.
The
github
site
component
is
managed
by
the
gitlab
series,
so
we
don't
have
to
deal
with
that.
What
that
is,
I
created
a
configuration
repository.
You
can
see
it
here.
A
I
will
speak
about
this
in
a
moment
and
I
created
the
agent
record
using
gitlab's,
graphql,
editor
and
retrieved
the
token
I
did
not
install
the
agent
to
the
cluster
yet
so
this
is
what
I'm
going
to
do.
First,
yeah,
let's,
let's
start
with
that,
I
have
a
k
n
s.
Actually
what
what
we
are
going
to
use
is
a
local
kubernetes
cluster.
It's
a
k3s
cluster
running
in
multipass,
so
it's
totally
local
to
my
computer
and
we
will
synchronize
it
with
pool
based
deployments
from
github.com.
A
Okay,
let's
see
create
the
namespace
as
it
was
added
in
documentation.
Now
we
can
see
that
we
have
the
namespace
created
and
the
next
command
would
be
to
install
the
cluster
set
component,
but,
as
I
already
have
everything
set
up,
it
will
immediately
grab
this
configuration.
So
I
will
speak
a
bit
about
this,
so
when
I
set
up
this
project,
I
did
a
few
things.
First,
I
added
the
pod
info.
A
Manifests
to
this
repository,
it
comes
from
the
official
github
repository
for
pod
info
actually
and,
as
you
can
see
here,
it
has
to
be
installed
in
three
steps.
If
you
use
pure
commands
manifest
first,
the
common
files,
then
the
back
end,
then
the
front
end.
For
this
reason,
I
only
have
the
common
files
uncommented,
the
others
are
still
commanded.
A
How
does
this
file
look
like?
You
can
see
that
this
is
the
github
section
with
manifest
project.
The
id
reflect
is
the
same
project
where
these
files
are
available.
I
can
specify
a
default
namespace
or
not
in
this
case.
Actually,
the
ml
files
contain
the
namespace,
but
it
will
create
the
web
up
namespace
itself
as
well.
So
that's
why?
Actually,
we
have
a
few
later
steps.
A
Okay,
let's
get
started
so
here
we
go
and
I'm
going
to
install
the
agent
and
we'll
see
as
it
starts
and
once
it's
available
here,
I
will
jump
into
the
logs.
Of
course
it
takes
some
time
to
start
up.
So
let's
wait
for
that
until
I
will
upload
a
few
things
for
this
recording,
and
here
you
can
already
see
that
it
creates
develop.
Namespace
create
the
service
account
and
everything
around
that.
So
I
think
we
are
good
to
go,
but
let's
have
a
look
at
the
namespaces.
Yes,
the
web
app
namespace
is
available
here
perfect.
A
Done:
okay,
oops!
I
think
I
might
be
late
now,
but
let's
see
if
we
can
still
catch
things
happening
yep
we
are
just
applying
the
resources
everything
is
being
applied
here.
So
as
we
move
to
develop,
the
back
end
is
already
there
perfect.
Now,
let's
go
to
enabling
the
front
end,
install
the
front
end.
A
You
might
ask:
how
does
this
part
work?
Actually,
the
the
gitlab
site
component
watches
our
git
repository,
and
then
there
is
a
new
version
available.
It
brings
the
agent
in
the
cluster
to
install
the
front-end.
Okay,
a
quick
port
forward
with
will
help
us
to
test
if
everything
works.
Well,
so,
let's
see.