►
From YouTube: Geo helm chart demo (part 1)
Description
Recently the helm charts to deploy GitLab Geo in kubernetes were merged. In this demo Toon Claes (Geo Senior Backend Engineer) is following the documentation set this up.We ran in a couple of errors, so this part 1 only goes up to the end where the license is added to the primary node.
Documentation: http://docs.gitlab.com/charts/advanced/geo
Issue: https://gitlab.com/gitlab-org/gitlab/issues/36965
A
B
B
C
B
B
So
it's
not
in
the
shorts
support
application
stuff
like
that
I
guess
it
just
omnibuses,
so
it
should
be,
should
be
supporting
test
setup
omnibus
instances.
That's
what
I've
done
already
I'm,
not
sure.
If,
for
this
I
need
some
extra
firewall
rules,
maybe
we'll
need
to
check
that
out
later
on
other
than
that,
so
I've
use
a
operating
system
and
I
have
installed
two
omnibus
package
on
there.
Without
an
external
URL
I've
set
up
two
clusters,
which
I've
done
just
yet
both
English
using
HTTP
I'm,
not
sure
what
this
step
additionally
is.
A
B
Access
to
persistent
storage
mean
you're
not
required
if
using
external.
Yet
these
I
wasn't
sure
what
I'd
be
sure
it
should
be
doing
with
I
did
not
set
some
set
up
any
Gately
or
mini
or
Redis
I'm,
not
sure.
Maybe
we
can
offload
it
also
to
the
Omnibus
installations
or
the
charges
doing
it,
I'm,
not
sure
where
they
are
supposed
to
resign.
Sure.
D
B
B
A
B
B
B
F
B
B
B
B
B
G
B
A
A
H
A
A
B
B
A
B
B
B
B
B
G
A
G
B
G
C
G
G
B
G
H
G
G
G
C
G
B
G
B
G
A
G
G
A
B
H
Okay,
well,
the.
C
A
B
C
G
H
C
G
B
G
B
G
G
B
C
G
All
right
now
and
then
the
lot
the
pod
name.
So
if
you
do
a
or
if
you
do
L
app
equals
migrations,
sorry
app
app,
a
PV
equals
migrations.
G
B
B
G
G
E
G
B
G
We
add
there
exactly.
G
So
I
should
try
again
and
see
that
secret
exists.
So
if
you
do
the
describe
pod
again
command
again,
we're
probably
hitting
a
back
off
threshold
right
now,
so
it
might
take
a
little
bit
to
make
it
move
forward.
You
can
always
delete
the
pod
and
then
the
deployment
will
recreate
it
or
the
job
should
recreate
it.
I
think
mm-hmm.
F
F
G
A
G
F
B
A
A
B
G
B
A
A
A
A
B
A
It
actually
works
perfectly
fine
on
omnibus
the
problem
is
in
the
containerized
ecosystem
and
the
way
boots
nap
actually
checks.
What
version
of
ABI
is
running
against
and
we're
working
to
catch
that
to
be
correct
so
that
we
can
actually
rebuild
the
cache
and
distribute
it
so
that
it's
not
locked
to
a
very
specific
kernel
version
and
compile
time.
F
G
C
A
B
B
F
A
A
G
A
B
C
G
G
F
G
I
G
G
G
B
A
G
B
B
B
E
G
G
G
B
H
B
G
B
G
F
E
E
B
A
B
B
B
G
B
G
B
G
G
G
B
B
B
G
Maybe
we
did
just
add
so
the
now
the
we're
not
sure
has
actually
merged
yet,
but
it
hasn't
been
released
for
sure
that
running
the
geo
migrations
on
the
secondary
once
that's
deployed
so
in
here
it
should
be
a
manual
step
on
the
server
and
that's
no
longer
required
uh-huh,
but
other
than
that
everything
should
be
the
same.
You
shouldn't
need
to
run
the
migrations
on
the
secondary
I
can.