►
From YouTube: GitLab 14.2 Kickoff - Enablement:Distribution
Description
Kickoff for the 14.2 milestone for the GitLab Distribution team.
Planning Issue: https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/857
A
This
is
our
scheduling
issue,
pretty
streamlined
similar
to
our
last
few
milestones
again,
we're
still
cruising
along
on
our
operator.
Ga,
of
course
we
will
work
on
any
rollover,
work
from
14.1
and
then
finally,
we
would
like
to
loop
in
a
little
bit
of
tech
debt,
it's
still
a
motivator
for
us
to
accomplish
a
little
bit
of
tech
debt
every
milestone,
and
that
is
still
true
for
this
milestone
as
well.
A
A
Issue
related
to
the
operator
that
I'd
like
to
mention
this,
this
milestone
is
going
to
be
running
our
functional
qa
tests,
our
functional
and
qa
tests.
Excuse
me
for
the
operator
on
a
kubernetes
cluster,
so
just
making
sure
everything
is
buttoned
up
nicely
to
run
well
in
kubernetes
a
couple
controller,
op
issues
here.
One
is:
we
want
to
be
capable
of
disabling
our
included
redis
and,
allowing
you
know,
users
to
use
an
external
redis.
So
this
is
a,
I
think,
a
big
benefit
to
users,
and
the
same
goes
for
postgres
sql.
A
So
we
want
to
allow
users
to
disable
the
included
database
and
use
one
that
they
they
would
like
to
provide
themselves.
So
I
think,
really
great
additions
coming
along
in
this
milestone
for
the
operator
as
we
get
closer
and
closer
to
ga
again,
the
big
one
was
evaluating
our
operator
installation
options
for
the
last
one
and
now
being
able
to
capitalize
on
that
work,
so
great
job
to
everyone
on
the
team.
A
A
couple
petroni
issues
that
we're
going
to
be
tackling
this
milestone.
One
is
allow
list
support,
so
this
is
added
from
petroni.
So
we
would
like
to
also
include
it
for
support
in
the
omnibus
and
another
one.
That's
related
to
petroni
is
tls
certificates,
so
both
of
these
are
available
for
patrony,
so
we
would
like
to
also
offer
those
options
to
users.
Ultimately,
finally,
we
are
still
working
on
this
issue
which
might
be
familiar
to
some
folks.
This
is
more
of
a
long
tail.
A
You
know
managing
omnibus
configuration
secrets
is
a
large
operation
and
we're
slowly
consuming
a
couple
issues
here
and
there.
I
think
this
will
pick
up
a
little
bit
more
once
the
operator
is
ga,
but
one
of
the
issues
that
we're
going
to
be
working
on
this
milestone
is
encrypting
all
rails
passwords
stored
in
gitlab.rb.