►
From YouTube: GitLab 15.7 Kickoff - Configure:Configure
A
A
This
we
expected
to
provide
a
big
increase
in
usage
because
up
to
date,
personal
namespaces
could
use
the
agent,
but
it
was
not
possible
to
share
a
single
agent
across
several
of
the
product
projects.
This
will
make
it
a
possibility.
Finally,
and
thankfully
it's
a
really
minor
change,
thanks
to
other
developments,
we
did
around
the
cicd
access
share.
A
The
second
item
is
to
provide
front-end
access
to
the
kubernetes
API
through
cars,
a
little
bit
more
simply
to
allow
the
gitlab
UI
based
Integrations
of
the
underlying
kubernetes
cluster
into
GUI.
This
will
enable
all
kinds
of
amazing
things
like
providing
a
summary
view
on
the
environments
page
within
gitlab.
We
are
already
working
on
designs
for
this
feature
and
we
are
working
together
with
the
release
stage
to
build
the
underlying
architecture.
For
this.
A
It
will
allows
as
well
to
build
a
whole
scale,
full-scale
versus
dashboard,
with
all
kinds
of
views
that
are
possible
today,
mostly
on
third-party
tools,
not
even
GitHub
stores
actually,
and
it
has
rely
likely
a
huge
amount
of
other
possibilities
like
managing
secrets
from
gitlab
through
some
logic
in
the
cluster
or
whatever
we
can
imagine
later
on.
This
is
really
amazing
enabler
for
many
other
features.
A
Our
third
item
might
be
an
improvement
around
our
hand
supports
with
the
agent,
but
it's
still
being
refined,
and
for
that
reason
I
think
it's
less
likely
to
go
in
that
direction.
The
fourth
item
in
our
private
is,
which
is
actually
deliverable,
still
is
to
evaluate
the
possibility
of
switching
the
our
GitHub
solution
to
flux
CD
flag
CD
is
together
with
Argo.
A
Cd
is
one
of
the
leading
Solutions
on
the
gitos
markets
today,
and
we
already
discussed
to
switch
to
Argo
CD,
but
it
wouldn't
bring
much
value
why
it
would
bring
a
huge
amount
of
dependencies
and
complexities
and
maintenance,
and
you
still
need
to
build
out
everything
that
we
plan
to
build.
Even
today,
flux
is
a
more
lightweight
tool
and
we're
evaluating
whether
it
was
worth
switching
away
from
our
current
solution
and
focusing
primarily
on
doing
github's
bit
flux.
A
By
this,
the
we
would
lift
one
of
the
big
limitations
of
our
current
CI
access
sharing,
namely
today,
when
an
agent
is
set
up
to
be
shared,
to
have
a
shared
connection
with
a
given
project
or
group.
That
means
that
all
the
CI
jobs
in
that
project
are
all
the
projects
on
in
a
group
receive
access
to
the
cluster.
A
If
we
would
restrict
access
to
specific
environments,
this
would
be
limited
to
the
CI
jobs
targeting
that
given
environment
and
as
a
result,
it's
much
more.
It
secures
down
the
risk,
the
attack
surface
around
the
cluster
and
finally,
we
might
start
working
on
providing
support
for
several
manifest
projects
around
a
single
agent
configuration
project
today
manifests
need
to
be
stored
together
with
the
agent
configuration.