►
From YouTube: GitLab 13.4 Kickoff - Enablement:Distribution
Description
Highlights for 13.4 include PostgreSQL 12, OpenShift, cloud native maturity, encrypted passwords, Orchestrator, and gitlab.com Kubernetes migration
A
A
A
After
that,
we'll
be
taking
a
break
from
postgres
work
for
a
couple
of
milestones
until
13.6,
which
is
the
release
in
which
we
will
default
to
postgres
12.
A
and
just
as
a
reminder,
postgres
11
will
continue
to
be
supported
until
get
lab
14.0
after
that,
12
will
become
the
minimum
required
version.
A
A
The
the
most
recent
things
they've
been
working
on.
There
are
adding
support
for
backing
up
gitlab
and
upgrading
git
lab
with
the
operator
on
our
side.
We've
been
doing
some
investigation
into
whether
we
can
have
the
operator
use
the
home
chart
and
things
are
looking
really
positive
there.
A
We
did
some
great
investigation
into
that
and
found
that
it's.
It
looks
like
something
that
we'll
be
able
to
do,
and
so
in
13.4
the
focus
will
be
a
bit
more
evaluation
of
replacing
hard-coded
objects
in
the
home
chart
with
dynamic
ones,
which
will
will
help
support
being
able
to
use
helm
chart
and
the
the
benefit
of
that
is
that,
instead
of
having
a
third
project
being
the
operator
where
we
need
to
add
support
for
new
get
lab
features.
A
A
A
A
We
think
that
we'll
still
be
able
to
complete
the
majority
of
this
work
by
october
and
just
have
the
pages
component,
the
last
remaining
item,
and
once
we
do
get
all
of
the
things
checked
off,
except
for
pages,
we'll
start
work
on
moving
the
cloud
native
install
to
the
lovable
maturity.
So
we're
not
going
to
sit
around
and
wait
for
pages.
We
will
continue
to
make
progress
on
the
maturity,
so
there
are
two
things
related
to
the
maturity,
epic,
that
we've
got
scheduled
for
13.4.
A
One
is
adding
support
for
smart
cards,
and
once
we
get
that
support
in
that
will
be
one
of
the
few
remaining
known
limitations
of
the
helm
installed
taken
care
of
the
other
one
is
we're
going
to
be
working
on
some
better
documentation.
A
A
A
All
right
here
we
go
so
the
mvp
was
targeted
at
our
geo
team
and
enabling
them
to
quickly
spin
up
a
scaled
instance
of
get
lab
with
a
geo
secondary
side,
so
that
included
three
console
nodes.
Three
database
nodes,
one
application,
node
and
support
for
a
secondary
site.
A
We
have
quite
a
few
issues
scheduled
for
this
13.4
milestone
that
are
part
of
the
alpha
epic
and
they
are
mostly
the
themed
around
efficiency
improvements
for
how
the
orchestrator
runs
so,
for
example,
ensuring
that
that
the
orchestrator
is
item
potent.
So,
for
example,
if
you
run
the
orchestrator
a
second
time
and
you've
already
before
running
it,
you
already
had
a
license
assigned
to
the
instance.
A
A
And
finally,
we
are
migrating
gitlab.com
over
to
kubernetes.
This
has
been
an
incremental
project.
Traditionally
we
managed
gitlab.com
with
the
omnibus
installer
and
we
are
migrating
one
component
at
a
time
across
two
kubernetes.