►
From YouTube: Installing Gitlab using Helm (GKE)
Description
We provision a K8s cluster in GKE and then set up a static IP and a DNS entry to eventually install Gitlab on said cluster, with Helm
A
Okay,
I've
started
the
recording
okay,
so
what
we're
gonna
do
today
is
we're
gonna
provision,
a
gke
cluster
kubernetes
cluster
and
we're
going
to
install
going
to
install
gitlab
on
on
that
cluster,
and,
let's
see
how
I
will
share
my
screen.
B
A
A
A
B
A
Let
us
test
let's
test,
I
guess
that's
one,
that's
one!
That's
fine!
Okay,
and
let's
do
something
in
europe
or
better.
Okay,
let's
see
that
yeah,
let's
go
with
release
channel.
I
think
that.
B
A
Available
and
yeah
that
should
be
fine.
I
usually
also
name
my
resources
pool
okay,
number
of
nodes.
B
B
Because
of
the
provision
and
sometimes
you'll
find
that
some
pods
fail
so
yeah
yeah.
B
Yeah,
so
that.
A
Works
good,
I
think
that's
mostly
it
yeah.
A
Okay,
I'm
not
exactly
sure
where
this
goes.
I
know
there
was
like
metadata
to
add,
for
example,
frugal
time
for
goalscape.
B
A
A
Something
one
I
think
that's
about
it,
let's
put
on
europe
as
well,
your
request,
that's
fine
reserved,
okay,
and
with
this
this
ip,
let
me
see
if
it's
actually
been
provisioned.
A
C
A
And
let's
see
yeah,
this
is
still
ongoing,
so
let's
wait
for
it
to
to
complete.
In
the
meantime,
this
is
the
page
I
think
most
of
us
should
use
to.
Is
it.
A
B
A
Yeah,
so
it's
chart
installation
deployments,
blah
blah
blah
and
it's
install
or
something
it's
all
the
way
at
the
end,
yeah
yeah,
this
one,
oh
yeah,
I
didn't
mention
the
the
prereqs
that
one
would
need
for
for
this
install,
so
you
need
to
have
cube
ctl
installed,
helm
as
well
as
whether
as
g
util,
which
is
the
google
cloud
command
line
utility.
A
It's
not
really
necessary,
but
I'm
gonna
use
it
because
I'm
lazy
and
I
don't
wanna,
add
my
configuration
to
cube
ctl
like
the
configuration
of
the
new
kubernetes
cluster
to
qctl
manually,
or
it's
just
going
to
give
me
a
command.
A
Let's
see
in
the
meantime,
if
it's
done
yep,
it's
not
going
there.
So
I
need
to
go
manually
and
I'm
going
to
show
you
what
I
mean
by
that
if
you
go
here
to
connect,
so
this
is
the
cluster
that
we've
created
in
kubernetes
and
if
you
go
to
connect,
there's
this
this
line
here
that
you
can.
A
A
Whatever
so,
this
actually
runs
on
the
the
new
cluster
new
kubernetes
cluster,
okay,
so
let's
install
gitlab
now
and
yeah,
as
I've
said,
I've
already
installed
helm
and
I've
also
added
the
repo.
So
an
additional
step
for
those
who
are
just
starting
up
and
just
installed
helm.
They
would
also
need
to
add
the
the
repo
chart
repo
and
then
maybe
do
a
helm
repo
update.
Actually
I
can
do
this
as
well.
C
A
Okay,
let's
see
do
I
have
anything
underneath
no
okay
boom,
it's
it's
it's
clean!
So
let's
grab
this
command
like
that
and
yeah.
A
It's
gonna
put
it
here
without
the
update
stuff,
so
timeout,
it's
explained
also
in
the
docs,
but
this
means
that
every
component
will
need
to
install
in
under
600
seconds.
If,
if
that
one
single
component
goes
over,
the
the
command
will
fail.
So
it's
not
the
entire
flow,
not
the
entire
gitlab,
but
the
the
various
resources
that
are
spun
up
need
to
be
under
600
seconds
and
then
here
we're
gonna
have
to
put
in
the
the
stuff
that
we've
created
so
the
domain
and
all
that
other
stuff.
So,
let's
see.
C
A
A
Okay,
did
I
grab
the
right
one?
Maybe
not.
Let's
try
that
again.
What
is
it
here?
So,
let's
replace
example.com
with
this
okay.
A
B
A
A
B
A
The
bare
minimum
but
yeah,
let's
just
get
git
lab
to
work
and
then
we
can.
We
can
do
other
stuff
afterwards,
so
version
mappings.
A
So
here
is
the
where
you
get
the
actual
version
that
you
would
need
to
pass
to
this
command
to
get
the
actual
version
of
gitlab.
So
let's
say
you
want
1311
to
or
let's
do
1310.2,
for
example,
which
is
quite
popular.
We
would
just
need
to
do
this.
I'm
just
gonna
do
it
here,
so
I
don't
do
any
extra
spacing
or
whatever
version
like
that,
maybe
equal
actually
and
then
maybe
a
good
idea
would
be
to
create
a
namespace.
A
You
could
install
it
to
default,
but
it's
I
think
it's
a
good
practice
to
to
do
it
under
under
a
namespace,
especially
considering
when
you're
trying
to
I
mean
if,
if
your
install
fails
or
you
fail
to
uninstall
it,
you
can
just
delete
the
namespace
and
most
of
the
stuff
will
be
deleted.
So
that's
kind
of
what
I
why
I
do
a
namespace.
So,
let's.
B
A
B
A
B
A
A
Then,
okay-
and
I
mean
this-
could
be
just
as
well
helm
install
it
doesn't
have
to
be
upgrade
minus
install.
I
don't
know
why
it's
put
that
way
in
the
docks,
but
I
guess
this.
This
will
also
work
when
you
change
the
version,
for
example,.
A
Yeah
exactly
you
can
that's
why
I'm
putting
an
older
version,
so
we
can,
I
mean
we
can
hopefully
do
earlier
version,
but
still
so
let
me
double
check.
Does
everything
look
right,
yeah,
we'll
see.
A
B
That
are
going
on
no
yeah,
okay,
it's
not
a
fair
review
on
1.22,
so
yeah.
A
B
A
B
One
down
there
down
there
there's
a
problem
with
privilege:
yeah
there's
a
one
in
there,
it's
like
a
notice
or
something
yeah,
but
it
still
works
anyway.
So.
A
Yeah
exactly,
I
think,
that's
also
in
the
documentation.
B
A
Anyway,
okay,
so
now,
if
I
do
qct
I'll
get.
C
B
B
A
A
A
A
Radius,
you.
B
Yeah
because
there
are
some
jobs
that
in
in
in
it,
which.
A
B
Yeah
there's
a
possibility.
We
did
the
two
cpus
and
you
described
that
we
just
see.
Probably
it's
an
issue
of
resource.
A
Yeah,
I
I
think
that
the
one
that
I
picked
out
initially
e,
that
that
didn't
show
me
any
any
problems.
But
let's
see.
A
A
Fails
momentarily
but
those
are
all
getting
retried.
So,
okay,
so
this
looks
good.
Let's
see
again
the
ingress
stuff.
A
A
A
That
just
secrets
-10.
A
C
C
C
A
C
A
Good
cool
so
yeah.
This
means
that
we
have
a
running
kubernetes
cluster
on.
Actually,
let's
see
that
lmls,
minus
and
git
lab
yeah
status
deployed
chart
version,
410,
0
and
app
version
1310
too,
and
actually
we
can
do
the
same
thing,
but
we
can
change
the
version.
A
A
That's
something
that's
that
didn't
occur
to
me,
but
it's
relatively
easy
with
helm.
Let's
say
we
do
497,
that's
that
should
work.
A
497
was
what
version
1397
your
corresponds.
C
A
Yep
we
can
see
that
there's
things
and
if
we
do
helm
unless.
A
Yeah
we
can
see
that
we
were
first
on
thirteen
ten
two
and
now
thirteen
nine
seven.
I
think
we
can
also
do
a
roll
back
hell.
B
A
B
A
Yeah
you
don't
have
to
I
mean
I
have
one
latest,
you
don't
have
to
mention
it.
It's
actually
one
the
revision
that
we're
going
to
minus,
and
here
let's
see.
B
A
You
can
what
sylvester
is
saying
is
that
here
you
can
actually
do
well.
Actually,
let's
do
history.
First,
you
will
get
one
two
three.
Maybe
I
don't
know
it
can
continue
for
for
a
while
and
if
you,
if
you
want
to
pick
a
specific
version
that
you
want
to
roll
back
to
it's
this
command,
but
then
you
just
add
the
revision,
one
or
three
or
two
or
whatever.
A
If
you
just
do
it
like
like
this,
it's
to
the
latest,
so
it
would
be,
it
would
be
just
the
one
before
the
current
one
and
you
can
actually
see
the
status
as
well.
So
this
is
deployed
and
the
other
ones
are
superseded.
A
Okay,
yeah,
I
think
that's
that's
kind
of
what
I
wanted
to
show
on
the
recording.
Is
there
anything
else
that
might
be
interesting.
B
A
B
A
A
It
yeah
and
yeah
also,
if
you
just
want
to
install
the
latest
version,
you
just
need
to
exclude
it
just
do
this,
and
this
will
install
the
newest
gitlab
version,
provided
you've
updated
the
the
repos
initially
so
this
command
right
here.
Where
is
it
this
one.
B
A
Right
right
and
actually
I've
tried
this
a
few
times.
I
I
just
pressed
enter
on
the
newest
version,
one
minute
but
yeah,
that's
simple,
that's
helen
delete
and
then
the
name
we'll
see
that
in
a
second.
B
No,
no,
I
I
meant
the
cluster
the
you
see.
If
you
look,
we
we
took
the
1.19.
B
B
Of
kubernetes,
yes,
yes,
if
you
have
like
17
or
16,
you
may
not
see
some
of
this
one
yeah
yeah,
I'm
just
mentioning,
because
you
may
have
a
cluster
that
so
it's
just
good
to
be
aware
that.
A
A
Now
they're
still
doing
work
yeah,
I
just
want
to
leave
them
come
up,
so
we
don't
delete
it
while
it's
still
bringing
stuff
up.
Although.
A
Delete,
that's
it
yeah,
no
other
things
necessary.
Oh
minus
n,.
B
B
Yeah,
maybe
a
quick
note
on
this
delete.
It
will
not
actually
remove
everything
so.
A
True
so,
let's
see
bugs
gitlab.
That
would
be
there's,
obviously
a
bunch
of
stuff
in
terminating,
but
it's
it's
not
gonna
delete
all
the
resources
like,
for
example,
let's
see
secrets.
A
So
those
were
not
getting
terminated
for
users.
I
think
there's
there's
quite
a
few
resources
that
will
not
get
removed,
I'm
not
sure
about
pvcs
yeah.
B
Even
volumes
yeah
because,
like
now
you
view
an
ins
you've
deleted
install
another
instance.
You
should
be
able
to
get
your
data
there.
So.
A
Yeah-
it's
not
in
this
page
but
yeah,
and
I'm
I'm
suspecting
that
I
have
a
ticket
with
someone
who's
trying
to
install
runner,
but
it's
getting
into
some
weird
errors
that
might
be
related
to
any
proper
cleanup
that
happened
beforehand.
So
yeah
yep.
Okay,
I
guess
that's
that's
about
it!
For
for
now,
I'm
gonna
stop
the
recording
feel
free
to
reach
out
to
us.
If
you
have
questions
about
what
you've
seen
here,
bye.