►
From YouTube: GitLab 12 7 Kickoff Enablement Distribution
Description
Highlights for the GitLab 12.7 release
A
Over
the
past
several
months,
we've
been
working
on
building
ubi,
based
images
of
gitlab
and
the
current
phase
that
we're
working
on
for
this
effort
is
to
add
the
ubi
base
images
to
our
release
process.
We
made
really
good
progress
on
this.
In
the
12.6
timeframe,
we
have
two
out
of
three
merge
requests
that
are
being
tested
and
merged,
and
we
just
have
a
little
bit
more
work
to
do
to
get
those
into
the
release
process
and
we
expect
to
wrap
that
up
in
the
12.7
time
frame.
A
A
For
the
charts,
we
have
a
number
of
updates
of
components
that
we've
been
wanting
to
make
we've
been
holding
off
on
those
for
a
major
release
of
the
chart,
and
we
are
scheduling
that
major
release
for
12.7
timeframe.
Here's
an
epic
this
is
in
the
charts
project.
Epic
six
is
tracking
each
of
the
items
that
will
be
going
into
that
release,
so
we
have
updates
coming
for
assert
manager,
Prometheus
and
we're
updating
the
PostgreSQL
chart,
we're
also
switching
to
the
upstream
Redis
chart.
A
A
There
are
a
number
of
api
deprecations
that
were
made
in
cuba,
Nettie's
1.16,
and
we're
making
the
changes
on
our
side
to
remove
dependencies
on
any
of
those
duplicated
API
versions.
And
then,
finally,
we
are
making
some
changes
to
the
sidekick
deployments
so
that
we're
using
a
unique
selector
and
what
this
will
do
is
for
multiple
deployments
of
sidekick
pods.
The
deployments
will
no
now
know
which
pods
belong
to
them.
A
A
And
this
work
is
part
of
a
bigger
effort
that
you
can
track
here
in
this
epoch
to
to
6-0,
which
is
to
move
our
cloud
native,
install
from
the
current
maturity
level
that
we've
given
it,
which
is
viable
to
a
complete
maturity
level,
and
you
can
read
about
what
that
actually
means
in
this
epoch
and
I've
started
writing
down
some
acceptance
criteria
for
what
it
might
look
like
to
move.
The
maturity
level
would
really
appreciate
feedback
from
the
community
on
this
one.
So
please
feel
free
to
jump
into
this
epoch
and
provide
comments.
A
The
first
part
of
this
is
to
be
able
to
automate
that
internally,
so
that
we
can
more
quickly
test
a
che
geo
and
upgrades
on
those
configurations.
A
future
iteration
of
this
will
be
making
it
available
to
the
community
to
automate
your
own
deployments.
We
made
a
little
bit
of
progress
on
this
in
12.6,
but
I
think
expect
to
see
the
majority
of
this
work
happening
in
12.7
and
because
of
the
holiday
break,
probably
more
like
a
12.8
effort.
A
A
We
announced
in
the
last
kick
off
our
plans
to
add
support
for
Postgres,
11
and
12,
so
there's
an
epoch,
that's
linked
to
this
issue
here
that
will
help
you
understand
what
our
plan
is.
There
we
started
researching
what
it
will
take
to
add:
PostgreSQL
11
in
the
12.6
milestone
that
research
work
is
going
to
carry
over
to
12.7,
and
we
expect
to
be
creating
issues
and
actually
starting
to
work
on
those
issues
in
12.7,
so
that
we
can
add
support
for
Postgres
11
in
hopefully
in
the
12.8
timeframe.
A
A
Our
first
step
is
going
to
be
to
add
documentation
on
how
to
check
if
background
migrations
have
completed
and
as
part
of
that
documentation,
we
expect
to
learn
a
lot
about
what
it
would
take
to
actually
implement
guardrails,
and
so
those
the
guardrail
work
is
currently
slated
for
12.8
and
that's
the
highlights.
Thank
you
so
much
for
joining.