►
Description
Cluster integration & Cluster management apps (aka. GMA v2) walkthrough:
- https://www.youtube.com/watch?v=mKm-jkranEk
Cilium and Ingress (through GMA v2) installation walkthrough:
- https://www.youtube.com/watch?v=pgUEdhdhoUI
Cilium&Ingress in your local dev environment:
- https://www.youtube.com/watch?v=R2O2Y8_MrQ8
Gitlab k8s agent docs:
- https://docs.gitlab.com/ee/user/clusters/agent/
A
Hello,
everyone.
So
this
time
we
are
going
to
go
through
from
having
a
ceiling
installed
in
a
cluster,
and
in
this
case
we
are
going
to
use
gke
and
also
assuming
that
the
cluster
integration
has
been
done
already.
For
that.
I'm
gonna
include
three
videos
in
the
description.
One
video
is
how
to
have
the
cluster
integration
with
celium
on
your
local
dev
environment.
A
The
other
features
how
to
do
a
cluster
integration
if
you
are
using
gitlab.com
and
the
other
videos
how
to
specifically
have
c
installed
in
your
cluster
by
using
gma
v2.
So
just
a
quick
recap,
let
me
show
my
terminal
so
here
we
have
a
g
key.
A
I'm
gonna
show
you
that
it
just
had
just
have
one
node,
that's
enough
for
for
having
this
test
and
then
on
the
left
side
of
the
screen.
Here
we
can
see
that,
apart
from
the
regular
gke
pods,
we
have
celium
pod
and
if
you
install
celium
with
gma
v2
you're
going
to
get
also
the
hubble
relay
pod.
A
In
addition
to
that,
we
need
nginx,
that's
also
you
can
install
using
cluster
applications.
That's
again,
that's
going!
There
is
going
to
be
a
link
on
the
description
with
information,
how
you
can
install
cd
and
nginx
using
cluster
management
project,
which
is
also
known
as
a
gma
feature.
So,
let's
get
started,
I
haven't
prepared
much.
Basically,
I
have
an
existing
a
project
here
in
my
environment
and
it
has
a
it
has
already
a
deployment.
A
That's
running
here,
open
this.
It's
for
the
sake
of
clarity,
yeah,
that's
a
demo
application
that
we
have.
I
can
put
a
link
in
the
description
as
well.
I
use
that
for
testing.
So
basically,
we
have
a
project
repository
that
was
integrated
with
jmav2
and
it
has
seen
nginx
deployed
and
also
the
this
repository
has
been
deployed
as
production,
so
that
that's
what
you
can
see
here
under
environment
so
from
here
what
we're
going
to
have
from
here.
A
Let
me
just
close
this
extra
ui
so
that
we
are
confusing
okay,
so
the
the
documentation
so
far
for
kubernetes
agent,
it's
around
git
ops.
In
this
video,
we
are
not
going
to
talk
about
githubs.
There
are
other
videos
talking
about
githubs
this.
This
video
is
just
going
to
talk
about
saving
alerts.
A
Still
we
are
going
to
go
to
step
by
step
here
in
order
to
to
kind
of
see
how
we
can
integrate
this.
A
This
video
is
mostly
for
for
users
that
are
having
gitlab.com
for
other
users,
for
if
you
have
a
self
management
instance,
you
need
to
go
through
a
little
bit
other
steps
here
for
a
couple
of
other
steps
here
that
we
are
not
considering
for
this
video,
for
example,
you
have
to
enable
cass
in
this
case
here
we
are
using
one
of
the
gitlab
environments
that
already
have
accounts
cast
installed.
A
A
So,
okay,
so
then
I
actually
missed
that
so
that
that's
exactly
right,
we
have
a
define.
The
final
configuration
repository.
That's
going
to
be
the
configuration
for
the
agent,
so
basically
the
format
is
to
have
folders
nested
folders
in
a
way
that
it's
dot,
gitlab,
slash
agent,
slash
the
agent
name,
slash
config.ml.
A
A
A
A
Copy
paste
here
so
then
I
I
don't
make
it.
I
don't
have
a
taco,
that's
the
hyperlay
address
and
hubberley
address
is
going
to
depend.
It's
going
to
depend
on
how
you
install
hubble
on
your
on
your
kubernetes.
You
can
also
have
a
depends
on
how
you
follow
celium
configuration,
you
might
have
a
different
setup.
So
in
this
case
here
let's
just
go
and
grab
the
hubble
that
we
have.
A
A
A
A
So
now,
if
we
go
down
here,
we
need
the
next
step
would
be
the
first
one.
We
define
the
project
for
the
agent
next
one.
We
need
to
create
the
agent
record
in
gitlab.
There
is
an
option
to
do
through
rails
console.
If
you
are
having
like
a
gitlab
self
management
instance,
you
might
be
able
to
do
that
or
if
you're
using
gdk.
You
also
can
do
that.
But
in
this
case
here
we
are
going
through.
A
We
are
going
to
use
graphql,
so
I'm
going
to
copy
this.
I
haven't
done
that
before
I'm
gonna
copy
this
query.
First,
I
have
the
graphql
for
this
endpoint
and
then
let's
just
follow
the
steps.
So
first
we
need
the
path
to
the
configuration
project.
Let's
go
there
and
grab
the
path
to
the
configuration
project.
A
To
here,
just
following
the
documentation
and
next
step,
we
need
the
agent
name
that
we
had
before
we
defined
that
it's
agent
test
and
then
we
can.
We
can
just
run
it
okay.
So
now
we
have
a
new
agent
and
we
also
have
the
id.
So
let
me
just
grab
this
id
here
and
save
so
then
we
don't
forget
it.
I
think
we
need
that
for
the
next
step.
A
A
A
A
A
We
see
it
here
and
on
this
other
window
here
you
can
see
that
the
the
new
department
has
finished.
So
we
should
have
the
the
new
version
of
the
code
there.
Okay,
so
we
have
namespace,
let's
go
there,
and
so
next
step
here
is
to
create
the
the
token
inside
the
cluster
and
then.
A
A
Cuba,
we
have
the
token
created.
Let's
go
back
to
the
documentation.
A
And
so
now
it's
talking
about,
we
need
to
install
the
agent
in
the
cluster
right
now,
it's
a
manual
step,
there's
a
couple
of
things
going
on
that
that's
going
to
make
this
step
a
little
bit
more
streamlined
so
right
now
there
is
this
resource
ml
here,
and
there
is
a
couple
of
structures
here
on
updating,
namespace
and
a
couple
of
other
things,
I'm
going
to
open
here
just
for
making
clear.
A
So
it's
a
it's
a
resource
ml
with
a
couple
of
things.
The
service
account
related
to
the
to
the
agent,
and
we
have
the
deployment
itself
that
here
you
can
see
that's
pointing
to
the
agent
itself
image
and
there
are.
There
are
three
things
here
that
we
need
to
be
careful,
so
we
don't
forget.
First,
one
is
that
we
need
to
make
sure
that
the
namespace
here-
and
here
it's
exactly
the
name
space
that
we
just
created.
So
probably
we
are
going
to
have
to
update
this
here.
A
A
A
Let
me
just
show
you
here:
we
can
see
the
version
of
cass
here,
so
that's
the
one
that
was
latest
and
that's
the
one
that
we're
going
to
tie
in
our
resource
file.
Let's
go
back
again
to
the
resource
file.
The
third
thing
is
that
that's
the
host
and
you
can
use
different
setups
in
this
case.
Here
we
are
not
deploying
on
gitlab.com.
We
are
deploying
a
different
environment.
A
So
then
we
we
just
have
to
update
this
one,
and
I
have
one
I
have
one
file
locally
already,
so
I'm
just
going
to
open
this
file
here,
so
we
can
see
together
what
I
have
so
far,
and
we
might
need
to
update
something
that
I
didn't
update
before
what
recording
this
video.
A
So
we
see
here
that
online
23
we
already
have
the
version
instead
of
latest
we
have
13.9.1.
A
This
is
to
make
sure
that
we
have
an
agent
version
that
match
casts
cast
is
going
to
run
besides
git
lab
and
agent
k
is
running
inside
the
cluster
and
then
on
line
27.
Here
we
are
pointing
to
the
environment
that
we
want
to
use
if
you're
using
gitlab.com
you're
going
to
use
the
one,
that's
specifying
the
documentation
or
if
you
have
your
self-managed
instance
you
might
you
might
using
a
different
configuration
here
as
well,
and
the
third
thing
is
the
namespace
that
I
mentioned
before
so
here
we
have.
A
Oh,
it's
it's
already
the
finances
we
have
namespace
here
agent
test,
that's
the
namespace
we're
using
and
here
is
also
asian
test.
So
I
can
just
close
this
file.
So
just
close
this
file
and-
and
we
can
go
back
here
and
see-
I
think
we
just
need
to
deploy
it
yeah.
So
basically,
that's
the
structure
that
we
need
to
deploy.
A
A
So
then
we
can
see
on
the
on
the
right
side.
We
can
hear
that
that
we
have
search
account.
We
can
have
we
net,
we
have
the
cluster
role,
that's
going
to
define
the
permissions,
and
then
we
have
closer
two
cluster
roles,
one
for
region
and
one
for
writing,
and
we
have
the
two
cluster
row
bindings.
That's
the
same.
It's
going
to
be
associating
the
service
account
with
each
cluster
row
and
also
we
have
the
the
deployment.
A
So
if
we
look
inside,
if
we're
looking
to
the
log
of
this
pod,
let's
take
a
look
and
I
can
keep
it
as
a
follower.
A
A
So
let's
go
back
to
the
project
itself
and
let's,
let's
go
to
try
the
monitoring
and
let's
create
a
policy
for
this
environment.
That's
going
to
trigger
alert,
so
I'm
just
going
to
say
here
trigger
alerts
and
I'm
gonna
enable
the
policy.
I'm
just
gonna.
Add
one
rule:
I'm
gonna
say
that
this
this
pod
can
just
receive.
I
can
just
having
grass
from
another
pod
that
has
the
label
at
none
in
this
case
in
this
cluster.
A
There's
nothing
like
this,
so
I
just
want
to
force
the
drop
and
then
I
can
come
here
and
add
alert
because
I
want
to
see
the
alerts
and
then
create
policy
reach
network
policy.
A
We
should
see
the
policy
here
now
and
if
we
spin
up
the
environment
for
this
project,
the
only
one
that
we
have
deployed,
we
should
get
a
timeout,
because
no
pod
is
allowed
to
communicate
with
that
part
that
we,
the
deployment
that
we
had
and
after
some
time.
Oh,
if
we
take
a
look
in
the
cluster,
we
should
see
the
messages
here.
A
A
I
think
that's
that's
good.
For
this
video
we
are
going
to
have
a
couple
of
more
features
coming
up
and
watch
out,
keep
an
eye
on
this
channel
for
more
videos
on
that.
Thanks
for.