►
From YouTube: GitLab 13.10 - Enablement:Distribution
Description
Learn more about what the Distribution is working on in our 13.10 release.
A
A
We
want
to
make
sure
that
anything
that
our
gitlab.com
needs
to
accomplish
their
goal
of
operating
gitlab.com
is
met
their
kind
of
need
to
haves,
for
example,
and
then
here
we're
also
continuing
to
really
focus
on
finishing
up
the
last
remaining
items
to
support
deploying
git
lab
on
openshift
in
a
beta
fashion.
So
whatever
it
takes
to
get
that
kind
of
proven
to
closure,
we're
trying
to
make
sure
we
have
room
for
in
this
release,
and
then
we
actually
think
we're
all
done
with
the
pg
upgrade
items
which
is
great.
A
That
was
the
pg-12
upgrade,
which
is
essentially
ready
to
be
required
in
may,
and
then.
Finally,
of
course,
I
need
nice
to
haves
in
production.
Of
course
you
want
to
try
and
see
if
we
can
fit
in
as
well.
So
that's
the
high
level
kind
of
main
priorities
and
let's
talk
a
bit
more
about
these
in
detail
here
again.
This
is
a
continuing
theme.
We
want
to
be
able
to
support
customers
and
folks
who
want
to
deploy
gitlab
on
openshift
gitlab,
the
server
it's
worth
mentioning.
A
The
reason
this
is
important
is
because
there
are
folks
who
enterprise
standard
is
is
open
shift,
and
today
you
have
to
have
a
lot
of
compromises
that
most
folks
aren't
willing
to
to
do
to
run
git
lab
there,
and
so
we
want
to
be
able
to
better
support
these
folks
and
deploy
gitlab
there
so
that
they
can
run
out
the
way
they
want
to
be
ran,
and
this
requires
an
operator
in
order
to
accomplish,
and
so
the
great
benefit
here
is
that
not
only
are
we
addressing
the
need
of
potential
customers
on
openshift,
but
we're
also
building
the
base
core
operator
that
we
want
to
use
for
really
going
forward
for
all
of
our
cloud
native
distribution
get
left.
A
A
So
that's
kind
of
the
real
future.
There
we
see
the
operator
eventually
replacing
the
helm
chart
going
forward
over
time
for
these
reasons
of
kind
of
making
a
better
experience
so
very
excited
about
this.
It's
critical
to
our
long-term
strategy
of
deploying
git
lab
on
open
on
cloud
native
and
making
sure
it's
really
a
great
experience
and
better
than
we
had
before,
with
virtual
machines
from
there
we're
also
looking
at
doing
a
spike
of
what
it
would
take
to
support.
A
Officially
amazon
linux
2..
We
weren't
quite
aware
of
how
much
usage
there
was
of
this,
since
we
don't
currently
collect
the
linux
distribution
as
part
of
our
overall
telemetry
package,
and
so
it
was
a
bit
surprising
when
we
deprecated
centos
6
and
all
of
a
sudden.
We
had
a
lot
of
customers
complaining
that
we
broke
the
rams
on
linux
installation
and
then
they
could
no
longer
upgrade.
A
The
reason
is:
is
that
inadvertently,
our
installation
script
detected
amazon
x2
as
centos
6,
and
so
it
just
happened
to
work
and
when
we
duplicated
centos
6,
because
it
was
in
the
life
upstream,
this
ended
up
removing
a
upgrade
pathway
for
these
customers
on
amazon
x2.
A
So,
in
the
current
release,
13
at
nine,
we
did
a
spike
and
determined
that
actually,
the
centos
7
package
seems
to
work
just
fine
and
we're
making
a
change
in
the
script
so
that
it
is
detected
by
centos
seven
and
gets
installed
in
a
session.
So
we
have
an
upgrade
pathway
for
these
folks
and
through
to
net
10.
Here.
What
we
would
like
to
do
is
we
would
like
to
do
a
spike
to
see
what
it
would
take
to
officially
support
amazon
linux
2.
A
So
that
would
be
we
don't
have
these
accidents
or
these
unintended
breakages.
That
might
happen
in
the
future.
So
that's
what
this
is
about
here
in
13.10,
since
it
clearly,
we
have
a
lot
of
folks
who
are
interested
in
running
it.
This
way
from
there
we're
also
continuing
to
address
some
of
the
known
issues
with
running
and
installing
gitlab
on
a
fips-enabled
system.
A
You
can
see
here
we're
actually
addressing
a
an
issue
in
13.9
and
we're
carrying
forward
direction
issue
on
centos,
eight
with
tips
as
well,
and
this
can
help
us
better.
Smart
customers
should
deploy
gitlab
there,
but
also
it
helps
us
to
really
kind
of
unblock
some
of
our
estimation
and
other
exploratory
work
that
we're
in
taking
for
the
broader
fifth
compliance
effort,
no
timelines
there
or
any
kind
of
guarantees
we're
evaluating
it,
but
we
want
to
at
least
make
sure
we
don't
have
these
kind
of
known
package,
installation
problems
so
from
there.
A
That
is
it
for
our
kind
of
big
highlighted
themes
for
13.10.
We
are
really
excited
about
this
release
and
we
can't
wait
to
have
the
beta
release
of
openshift
and
our
operator
out
there.
That
is
super
exciting
and
just
the
amount
of
goodness
that
it
will
unlock
for
our
customers
in
the
future.
Is
you
know
we're
very
excited
about,
so
we
hope
you're
excited
too
and
stay
tuned
next
month
for
our
13.11
kickoff
and
learn
about
all
the
great
things
we're
doing
there
thanks
and
see.
You
then.