►
From YouTube: GitLab 15.5 Kickoff - Enablement:Distribution
Description
Planning Issue - https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/1074
A
A
We
certainly
won't
finish
our
the
first
goal
here,
but
it's
something
we
want
to
continue
working
towards,
which
is
improving
our
distribution
team
pipelines
for
developer
productivity.
So
this
is
a
long
issue
or
excuse
me
a
long
epic
and
a
very
long-standing
project,
but
we
want
to
keep
continue
making
progress
for
that.
So
this
is
one
of
the
main
themes
that
we'll
focus
on.
A
However,
we
are
still
working
on
a
lot
of
compliance
work,
so
this
will
be
more
something
that
we're
we
fit
in
if
we
have
a
chance,
along
with
some
other
issues
that
I'll
mention
here.
But
the
main
focus,
I
would
say,
is
our
compliance
work
and
if
we
can
outside
that
compliance
work,
our
personal
goal
and
distribution
will
be
improving
our
team
pipelines.
A
The
next
portion
of
the
issues
I'm
going
to
mention
here
are
a
lot
of
issues
that
our
customer
requests,
and
so
these
issues
that
I
have
listed
here
are
going
to
be
issues
that
I
mentioned
in
the
kickoff
video.
So
you
can
find
them
here
in
the
scheduling
description.
A
The
first
issue-
I
don't
mention
here
that
is
very
exciting-
is
adding
packages
for
amazon
linux
2022..
This
is
set
to
be
released
soon
and
we
want
to
prep.
So
something
that
we're
going
to
work
towards
in
this
milestone
is
adding
these
packages
for
amazon
links
2022,
so
that
we're
ready
when
the
release
is
available.
A
So
the
next
two
issues
I
have
here
support
multiple
architecture
builds
for
cng
images
and
viability
of
cng.
Support
for
multiple
multi-arch
images
are
all
a
part
of
a
grander
epic,
adding
multi-architecture
support
for
cloud-native
gitlab.
A
So
currently,
there's
no
cloud
native
gitlab
docker
image
available
for
these
arm.
64
cpus
and
I
know,
there's
growing
interest
for
these
new
architectures,
and
so
we
would
like
to
add
our
containers
into
the
mix
moving
to
the
next
issue
here
right
now,
we
do
not
have
a
service
for
rotating
the
logs,
similar
to
our
built-in
service
that
we
have
in
the
omnibus.
A
So
in
omnibus
we
have
a
built-in
log
rotate
service,
and
we
would
like
to
reflect
the
same
here
in
our
chart
because
right
now,
as
the
logs
are
created,
they
do
not
rotate
and
that
creates
a
large
storage
consumption
problem,
and
we
want
to
mitigate
that.
So
this
issue
is
probably
more
of
a
research
issue.
Hopefully
we'll
discover
a
lot
and
move
towards
a
solution.
A
A
Moving
on
to
our
next
issue
here,
which
is
we
have
a-
we
have
a
a
problem
right
now
with
repo
mirroring
not
working
for
package
cloud
repos,
so
we
actually
have
a
fix
in
place
and
because
of
that
it,
it
caused
this
problem
of
not
working
for
images
related
to
or
excuse
me,
repos
related
to
red
hat
satellite.
A
A
But
in
the
meantime
we
want
to
investigate
and
document
a
workaround
for
mirroring
our
gitlab
rpm
repos
via
red
hat
satellite,
as
the
title
here
suggests.
So
this
is
an
exciting
one
and
we
want
to
make
sure
that
we
offer
at
least
a
workaround
in
the
meantime
that
is
suitable,
so
we're
going
to
do
our
own
investigation
here.
A
The
final
one
that
I
want
to
mention
here
is
adding
our
gitlab
agent
for
kubernetes
to
our
to
the
iron
bank.
So
right
now,
customers
are
interested
in
using
gitlab
adrian
for
humanities,
but
we
don't
offer
that,
and
so
we
want
to
add
the
agent
for
kubernetes
container
to
these
dsop
scripts,
which
is
essentially
the
iron
bank,
so
for
our
iron
bank
customers.
This
is
something
that
we're
going
to
work
towards
in
15.5.