►
From YouTube: GitLab Kickoff 13.7 - Enablement:Distribution
Description
13.7 Kickoff for Distribution
A
I'm
going
through
our
issue
board
that
we'll
be
using
to
coordinate
work
throughout
the
milestone
and
I've
also
gone
ahead
and
grouped
it
with
the
new
feature
to
group
issues
based
on
epics,
which
is
a
great
way
to
more
easily
visualize.
The
work
here
on
the
issue
board.
So,
let's
go
through
and
talk
about
the
big
items
that
we
are
working
on.
The
first
one
is
that
we
want
to
continue
to
really
move
our
operator
ahead
for
deploying
gitlab
on
both
openshift
and
kubernetes.
So
this
really
affords
us
two
main
features
or
two
main
accomplishments.
A
One
is
that
we
want
to.
This
will
allow
us
to
deploy
gitlab
on
openshift,
which
is
been
a
popular
request
for
some
time
and
number
two.
It
also
allows
us
to
build
out
the
an
operator
which
we
see
as
likely
the
future
of
the
cloud
native
installation
of
gitlab
on
kubernetes
and
openshift,
so
really
an
exciting
piece
of
work
here
that
we're
working
on
to
build
out
the
operator.
A
The
first
thing
that
we're
going
to
be
doing
here
is
we
will
be
working
to
render
the
helm
chart
within
the
operator
and
use
that
output
to
then
deploy
the
various
kubernetes
objects.
So
the
idea
here
is
that
we
want
to
utilize
the
known
good
battle
and
helm
chart
and
use
that
templating
to
actually
build
the
objects
that
we
then
run
into
right
into
kubernetes
and
open
shift.
This
way
we
we
know
it
works,
we're
confident
in
it
and
it
can
accelerate
our
openshift
support
and
the
market
readiness
of
our
operator.
A
So
that
is
the
first
thing
here
that
we're
working
on
identifying
the
data
model
to
be
used
as
well
as
also
working
on
the
first
chart
to
prove
this
architecture
out
once
we
have
that
done.
We'll
then
fan
out
and
then
add
support
within
that
model
for
all
the
other
services
and
objects
within
the
helm.
Chart,
as
you
can
see,
we
put
a
few
and
that
list
is
broken
up
here
once
that's
done,
we
should
have
an
operator
that
can
deploy
gitlab
into
openshift
and
kubernetes,
which
is
very
exciting
over
time.
A
You
know
a
couple
couple
releases
after
this:
we'll
work
to
kind
of
consume.
More
of
that
kind
of
a
helm,
chart
work
within
the
operator
itself
and
slowly
over
time,
kind
of
take
apart
the
help
chart,
but
that's
a
much
longer
trajectory.
That's
the
overall
direction
that
we'll
be
heading
in
next
up,
we're
also
working
on
improving
the
structured
logging.
This
is
because,
as
you
sort
of
scale
out
gitlab
on
kubernetes,
it's
important
to
know
what
pods
and
what
containers
the
logs
are
coming
from
and
so
we're
working
to
improve
this.
A
This
is
a
production
request
from
our
gitlab.com
team,
as
they
run
more
of
gitlab.com
on
kubernetes,
and
then
we
also
have
another
really
exciting
feature
here.
We
are
working
to
build.
The
container
for
pages
on
kubernetes
pages
has
been
a
gap
when
the
last
remaining
big
gaps
of
kubernetes
support
for
git
lab,
and
we
are
working
to
address
it
here.
We're
getting
very
close
to
offering
support,
and
so
the
first
step
here
is
that
we're
now
building
the
container
and
the
next
step
is
to
then
build
out
the
helm
chart
support.
A
We're
also
working
to
continue
to
improve
on
our
overall
postgres
12
and
patrony
story.
This
is
important
as
we
look
to
potentially
make
postgres
12
a
required
version
in
14.0,
so
we
can
take
advantage
of
some
of
the
new
features
and
performance
improvements
in
postgres
12.
we're
looking
to
make
it
the
default
in
13.7
for
both
new
installations,
as
well
as
for
upgrades
and
provided
that
we're
able
to
address
some
of
the
flash
remaining
items
mostly
with
petroni,
then
will
be
good
to
go
ahead
and
make
this
on
by
default.
A
Along
with
that,
we'll
also
have
some
work
to
pronounce
application
notices
for
pg-11.
If,
in
fact,
we
do
decide
to
deprecate
and
remove
pg
11
in
14.0
we're
still
looking
into
a
couple
items
there
around,
like
azure
support
around
the
may
time
frame
for
pg12
and
we'll
make
a
decision
here.
This
milestone
we're
also
working
to
continue
to
course
address
a
couple
other
items
for
openshift.
A
We
haven't
had
support
for
this,
but
we've
identified
a
way
to
utilize
config
maps
to
essentially
mount
a
directory
to
all
the
guiley
servers
and
then
run
these
or
and
add
the
support
for
hooks
on
the
kubernetes
implement
of
git
lab,
which
is
quite
exciting
and
last
but
not
least,
here
is
petroni,
as
I
mentioned
before.
We.