►
From YouTube: GitLab Kubernetes Agent Setup Walkthrough - Round 2
Description
Issue - https://gitlab.com/gitlab-com/Product/-/issues/3068
Example Project - https://gitlab.com/gitlab-examples/ops/kubernetes-agent-setup-with-ui
Round 1 Video - https://www.youtube.com/watch?v=ant-aLGuqBU
A
A
Okay,
so
the
walkthrough
is
about
the
kubernetes
agent
setup.
I'm
calling
it
round
two,
because
I
previously
done
a
walkthrough
of
kubernetes
agents
set
up
maybe
three
months
ago,
and
I
wanted
to
do
a
refresh
because
we
recently
added
a
ui
for
creating
agent
records
and
installing
the
agent
kind
of
like
a
walkthrough
for
installing
the
agent.
A
A
Just
gonna
add
a
new
file
here,
so
when
I
actually
let
me
not
do
that
when
I
go
to
kubernetes
clusters,
I
know
this
is
infrastructure
thing
over
here.
I
want
to
show
that
I
have
a
cluster
attached.
It
just
happens
to
be
that
the
group
I'm
using
gitlab
examples
has
a
cluster
attached
with
the
certificate
method.
I'm
going
to
add
one
with
agent.
It
says
hey
if
you
want
to
do
this.
You've
got
to
create
an
agent
configuration
in
this
repository.
A
Okay,
here's
the
agent
tells
me
about
the
get
ops
workflow
that
I
can
utilize
get
started,
set
up
the
kubernetes
agent
server.
I
don't
need
to
do
that,
define
a
configuration
repository,
okay,
I've
got
a
configuration
repository
and
I
need
to
create
a
file
that
looks
like
that.
Okay,
so
I'm
going
to
add
a
file
that
is
dot
gitlab,
slash.
A
A
A
This
project
and
I'll
see-
I
have
one
file
on
here.
It's
this
it's
this
config
yaml
file.
So
I
did
that
and
then
let's
go
back
to
here,
where
it
told
me
to
go,
look
at
the
thing.
I
could
get
that
agents.
Okay.
So
now
it
doesn't
say:
hey
you
need
a
configuration
file.
It
says
I
can
integrate
with
agent.
A
I
select
one.
I
select
the
primary
agent,
which
is
picking
up
that
config
that
I
have
in
the
repo
say
next
and
says:
oh
okay,
here's
the
things
you
need
to
do
basically
run
this
command
in
your
cluster,
which
will
pull
down
the
docker
container
and
solve
the
appropriate
agent
services
in
your
kubernetes
cluster
to
get
started.
So
I'm
gonna
do
that
connected.
A
B
A
A
A
A
So
the
gitops
workflow
should
say:
okay.
Well,
I'm
going
to
recognize
that
there
are
changes
in
this
repository
in
that
manifest
file
and
ensure
that
the
agent
is
going
to
ensure
that
the
kubernetes
clusters
configuration
matches
what's
in
the
agent
or
what's
defined
in
the
manifest
okay
does
not
have
minimum
availability
all
right,
so
that's
cool.
All
I
did
was
add
that
manifest
file
and
then
given
each
cluster,
automatically
updated,
let's
just
showcase
that
this
works.
Also
after
the
fact,
I'm
gonna
change
replicas
from
two
just
two
pods
to
five.
B
A
A
One
thing
that
I
am
going
to
take
some
notes
on
is:
it
would
have
been
great
when
I
clicked
on
go
to
repository
if
it
provided
a
default
path,
an
agent
name.
So
when
I
clicked
on
it,
it
kind
of
took
me
to
the
general
repository.
It
would
be
great
if
it
took
me
to
a
specific,
create
a
file
called
in
your
dot.
Gitlab,
slash
agent,
just
called
primaryagent
or
firstagent
as
a
default
for
users.
Slash
config.yml.
A
A
Is
that
going
to
get
updated,
doesn't
look
like
it
and
I
feel
like
I,
I
just
used
it
to
didn't.
I
use
it
to
create
that
so
it'd
be
great.
If
there
was
some
kind
of
immediate
feedback
for
users
that
the
agent
was
installed
and
connected
correctly
to
the
right
to
the
project,
so
right
now,
it
just
feels
like
it's
just
telling
me
about
the
agent
record.