►
From YouTube: GitLab 14.2 Kickoff - Enablement:Geo
Description
See what GitLab's Geo team is up to in the 14.2 release milestone.
More details: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5013
A
A
A
A
This
can
be
pretty
time
consuming
for
large
environments
and
it's
possible
to
script
the
existing
process,
but
can
still
be
pretty
complex.
So,
with
this
single
command,
it
will
recognize
what
type
of
node
it's
being
run
on,
update
the
appropriate
configuration
and
do
the
required
steps
to
promote
that
node
from
a
secondary
to
a
primary.
A
In
the
past,
we've
run
end-to-end
tests
using
a
docker
and
docker
approach,
which
simulates
a
pretty
basic
single
node
geo
setup.
But
the
reality
is
that
many
geo
customers
run
complex
multi-node
environments
and
we
need
to
ensure
that
we're
testing
geo
not
just
the
replication
functionality,
but
also
setup
and
processes
such
as
failovers
on
environments,
that
more
closely
resemble
what
our
customers
are
using
in
production
with
the
gillab
environment
toolkit
now
supporting
deployment
of
reference
architectures
with
geo.
A
We
can
use
this
to
automate
deployment
and
testing
of
these
more
complex
environments
in
our
qa
pipelines
in
14
2.
We're
going
to
iterate
on
this
by
starting
with
adding
the
ability
to
manually
trigger
a
job
that
builds
a
geo
environment
with
the
get
the
gitlab
environment
toolkit
alongside
our
existing
manual
package
and
qa
job
and
then,
after
that,
we'll
we'll
go
from
there
and
follow
up
with
adding
stages
to
get
lab.
Qa
mirror
to
spin
up
and
destroy
a
1k
geo
install
and
then
we'll
update
the
ee
geo
job
to
run
against
this
instance.