►
From YouTube: Upgrade Geo HA installation from 12.4.8 to 12.5.7
Description
The Geo team performs a Geo HA upgrade as described inhttps://docs.gitlab.com/omnibus/update/README.html#multi-node--ha-deployment-with-geo
A
B
A
A
So
here
the
instructions
are
going
to
follow
multi-node
hydrophobic
appointment
with
Geo,
and
it
says
so.
We
need
to
nominate
one
instance
as
a
primary
deploy
node
and
one
instance
for
the
secondary
deploy
node
in
both
cases,
I'm
going
to
use
the
app
one.
So
there's
two
application
notes,
also
Italy
Redis
Postgres
and
then
the
secondary
has
the
tracking
database
as
well.
A
A
A
A
So
I
just
pulled
up,
get
lab
dot
RB
file
to
check
if
it
actually
is
set
to
false
for
all
excluding
the
primary
node
deploy
node
it
is
set
to
false,
except
for
what
the
deploy
knows
which
we
want,
but
it
was
also
set
to
true
on
the
second
deploy.
Note.
However,
valor
tells
me
if
I
change
this
and
rerun
your
configure,
it
should
be
okay.
So,
let's
go
with
that
update
this.
A
A
A
A
A
A
A
Okay,
I'll
make
it
make
this.
This
is
something
I've
seen
before
it's
not
necessarily
be
related
to
this
upgrade
that
don't
take
a
note
of
that
and
we'll
see
how
the
other
tests
do
just
just
a
log
in
and
create
project.
So
it's
just
continuously
doing
that
they're
in
the
upgrade
I'm
just
going
to
be
done
over
there,
so
keep
an
eye
on
it.
A
A
A
A
A
A
B
A
B
C
A
A
A
A
A
A
A
A
A
A
A
B
A
A
B
A
B
Think
is:
is
there
some
information
about
this
above,
as
you
already
read
it,
so
maybe
let's
check
okay
I,
don't
see
actually
I.
A
B
B
So
maybe
we
already
fixed
it
because
instruction
says
it:
the
three
categories
should
ran
migrations
for
fgw,
but
before
that
we
used
to
run
special
comment
like
like
this
and
I,
see
that
it's
not
updated
steel.
So
probably
we
still
need
to
run
this
command
explicitly.
It
seems
so
I
propose
to
shaker.
Add
me
in
one
more
time:
okay,.