►
From YouTube: Setting up GKE with GDK
Description
Tristan walks through the process for setting Google Kubernetes Engine (GKE) to work with the Gitlab Developer Kit (GDK)
https://docs.gitlab.com/ee/user/project/clusters/#add-existing-kubernetes-cluster
A
Oh
welcome
to
a
recording
of
the
setup
of
kubernetes
for
monitor
development,
so
the
goal
of
this
is
to
is
to
be
able
to,
at
the
end
of
the
dislike,
be
able
to
see
the
cluster,
see
that
page,
the
kubernetes
cluster
house
charts
and
also
the
monitoring
dashboard
in
all
of
the
data
on
there
there's
a
few
prerequisites
so
having
the
GDK
up
and
running.
There's
a
pre
rick,
sir
I'm
not
going
to
cover
that
today.
It's
just
assumed
that
you've
got
that
going
also
having
docker
installed
and
having
cubed
control
install
so
yeah.
A
This
assumes
use
GDK,
set
up
the
docket
install
and
cube
control
or
cube
CTL,
as
it
was
sometimes
pronounced,
I'm
also
going
to
cover
some
stuff
with
the
get
by
Brunner.
So
it
also
assumes
that
the
runner
has
good
labor
anna
has
at
least
been
downloaded
and
installed
yeah.
So,
to
start
with
we're
going
to
create
a
new
project
in
running
GK.
A
A
A
Yeah,
so
the
next
step
is
to
take
a
look
at
the
kubernetes
pane
for
this
project.
Now,
as
you
can
see,
there's
no
cluster
attached
so
yeah.
What
we
want
to
do
is
we're
going
to
add
an
existing
cluster,
but
this
cluster
doesn't
exist
yet.
So
that's
what
I'm
going
to
show
next,
how
to
set
up
a
cluster
on
gke.
A
A
Yes,
so
alright
kubernetes
sitting
up
for
kubernetes
cluster
in
gke,
so
the
monitor
team
has
this.
Has
this
namespace
so
at
least
for
monitor
team
members-
and
this
is
the
one
to
use-
there's
also
get
lab
internal
which
any
get
lab
employees
can
use,
but
it's
it's
limited
by,
like
the
I
can
umber
of
IPs
and
a
few
other
things.
A
A
A
A
A
A
Certificates,
so
that's
here
or
similarly
that
there's
a
command
for
their
service
token.
So
as
these
Doc's
explain,
we
need
to
set
up
a
couple
of
accounts
on
the
cluster
so
that
the
GDK
can
interact
with
it
and
then
because
we'll
be
interacting
using
the
tokens
to
authorize
itself
as
these
accounts,
so
the
instruction
says
create
a
demo
file
with
these
contents.
A
A
For
development
purposes
enough,
and
just
like
just
with
the
default
settings
and
and
whatnot
so
I'll
go
ahead
and
store
helm
till
the
helm.
Teller
is
there
to
install
some
of
these
other
services
and
in
particular,
we
want
to
install
prometheus
because
Prometheus
is
going
to
provide
us
with
metrics
data
about
the
cluster
itself.
A
Yes,
so
they'll
take
a
minute,
or
so
once
that's
done
once
this
is
done,
we'll
be
uninstalled
Prometheus,
it's
done,
I
mean
then
once
prometheus
is
installed,
we'll
be
able
to
see
these
see
the
cluster
health
charts.
So
this
is
kind
of
the
first
objective
that
that
you
want
to
get
to
when
you're
like
sitting
everything
up
as
you
want
to.
A
A
This
is
what
you'll
see
once
the
pasta
has
been
connected
for
a
while,
and
it's
got
some
some
data
I
believe
that
it
is
also
a
way
to
preload
it
would
data,
but
for
basic
development
like
getting
your
environment
set
up
for
the
first
time.
It's
not
required
yeah.
So
you
can
see
these
charts
there
yeah,
they
just
show
kind
of
the
memory
usage
and
the
CPU
usage
of
of
the
class,
the
entire
cluster.
A
A
A
So
for
this,
if
we
look
at
pipelines,
you
can
see
there's
no
pipelines
or
no
environments,
but
if
we
were
to
run
a
pipeline
it
would
not
complete
unless
there
was
a
runner
available
so
run
it
runners
execute
pipelines.
So
if
this
is
your
first
time
sitting
up
the
environment,
you
probably
won't
have
a
runner
available.
A
It
is
possible
to
install
as
we
go
back
to
my
cluster,
to
install
a
runner
on
the
cluster,
and
this
is
this
is
generally
like
the
preferable
approach,
except
for
one
thing,
so
the
runner
needs
to
be
able
to
access
your
computer
or
it
needs
to
be
able
to
access
your
your
GDK.
Basically,
the
get
lab
instance.
A
The
problem
with
that.
If
you're
running
the
GDK
locally
is
it
would
need
to
be
able
to
access
your
local
computer
from
the
kubernetes
cluster.
Since
this
this
install
button,
installs
it
inside
become
an
english
cluster,
so
gke
would
need
to
be
able
to
see
your
computer
so
you're.
Essentially,
your
computer
would
need
to
be
available
to
the
internet.
A
A
So
if
you,
if
you
want
to
test,
if
you
have
a
reason
to
be
testing
the
runner
and
it
needs
to
be
in
kubernetes-
and
you
have
a
local
DBK,
you
can
use
this-
you
can
go
through
this
to
to
get
them
to
talk
to
each
other,
but
for
today
and
for
like
initial
developments,
it
up.
It's
also
something
that
you
don't
necessarily
need.
So
I'm
gonna
show
how
to
get
it
running
with
a
local
runner.
A
A
A
A
A
Don't
know
if
it
explained
it's
the
reason
here,
but
it
it
just
says
you
need.
You
need
to
have
your
IP
address
so,
like
you
can
see,
I'm
accessing
I
was
accessing
my
gbk
from
the
IP.
So
if
that
works,
then
the
IP
is
configured
correctly
and
I've
got
a
couple
of
run-ins
already
but
I'm
going
to
show
how
to
add
another
one.
A
A
A
A
A
A
We
can
see
that
this
is
in
contact
now,
so
that's
good,
so
that
that
is
going
to
run
in
the
meantime,
I'm
going
to
show
what
happens
once
it
has
run
in
my
sample
project,
so
the
environments
page
for
this
right
now
the
project
that
we've
just
created
this
MD
no
deployments
yet
so
this
is
one
that
has
had
a
successful
pipeline
run.
It's
the
same
project,
yeah
just
a
clone,
so
we
can
look
it
once
it's
deployed.
A
We
can
now
look
at
the
monitoring
page
and
this
will
contact
the
kubernetes
cluster
that
we
hooked
up
earlier.
That
has
production
deployed
onto
it
now
and
it
will
gather
some
metrics
so
by
default,
you'll
see
these
system
metrics.
So
this
is
what
you'll
get
with
like
the
default
basics
unit.
There
are
also
some
response,
metrics,
which
are
enabled
by.
A
So
if
you
install
ingress,
you
get
a
few
extra
tarts
by
default.
Oh
yeah,
this
is
so.
This
is
the
matrix
page,
and
this
is
more
or
less
where
you
need
to
get
to
to
be
able
to
start
monitor
development,
some
things
you
can
do
with
this
page.
You
can
create
alerts,
so
you
should
be
able
to
test
that
out
now
and
you
should
be
able
to
add
your
own
metrics
using
pop
QL.
A
B
A
A
Also,
we
should
like
monitor.
Team
members
should,
in
theory,
be
given
access
to
this
cluster
I,
don't
know
exactly
what
permissions
we
are
given,
but
I
know
for
myself.
I
didn't
have
to
request
access
to
this,
so
at
least
for
monitor
team
members.
It
should
be
by
default
that
you
have
access
at
least
for
this
cluster,
but
yeah
thanks
for
me.