►
From YouTube: GitLab 14.3 Kickoff - Enablement:Geo
Description
Geo 14.3 Planning Issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5016
A
Our
first
order
of
business
in
14
3
is
to
wrap
up
a
couple
of
items
that
we
made
a
lot
of
progress
in
in
14
2.
We
highlighted
these
in
the
kickoff
video.
Those
are
the
single
command
to
promote
any
secondary
node
to
a
primary
node.
That's
going
to
be
get
lab,
ctl
promote
as
well
as
work
to
proxy
any
operations
that
can't
be
done
on
a
secondary,
for
example,
anything
that
might
write
to
the
database
to
the
primary
site.
So
we
got
those
the
main
code,
mrs
merged,
for
those
in
14.2
and
in
143.
A
Some
work
that
we're
going
to
do
to
help
make
getaway
cluster
and
geo
work
better
together,
and
this
is
to
avoid
repo
renames
on
geosecondaries
as
more
large
customers
move
to
environments
using
both
getaway
cluster
and
geo.
Further
high
availability
needs.
We
want
to
reduce
obstacles
to
set
up
and
maintain
these
complex
architectures
because
of
how
repositories
are
tracked
by
getaway
cluster
jio's.
Current
method
of
renaming
repositories
during
a
sync
can
cause
problems
and
lead
to
potential
data
loss.
So
in
14.3
we're
going
to
implement
a
solution
that
will
allow
secondaries
to
avoid
this
renaming.
A
And
next
thing
I'm
excited
about
in
14
3
is
to
support
geo-replication
of
get
lab
pages.
With
gitlab
pages,
you
can
publish
static
websites
directly
from
a
repository
in
gitlab
in
a
disaster
recovery
scenario,
it's
already
possible
to
regenerate
pages.
After
failing
over
to
the
new
primary
site.
However,
now
geo
will
replicate
those
pages
deployments
which
will
provide
an
extra
some
extra
protection
against
data
loss
and
also
reduce
the
recovery
time
by
removing
the
need
to
regenerate
these
pages
after
a
failover.
A
So
those
are
our
highlights
for
14.3.
You
can
see
all
the
other
stuff
we
have
on.
We
have
plan
for
14
3
in
our
planning
issue.
As
always,
we
work,
intervally
and
continuously
so
just
feel
free
to
follow
along
in
our
various
issues
in
epics,
for
the
latest
updates.
Thanks
so
much
and
see
you
next
time.