►
From YouTube: GitLab 13.9 Kickoff - Configure:Configure
A
A
A
A
The
second
goal
we
have
is
to
secure
terraform-related
workloads.
I
will
speak
about
details
later
and
the
third
topic
is
to
start
shipping
some
secrets
management
features.
Let's
see
the
details,
I
already
spoke
about
the
rollouts
on
github.com,
not
going
to
speak
anything
more
about
that.
Clearly,
that's
our
number
one
priority
followingly.
We
have
to
want
to
enable
the
gitlab
side
component
of
the
gitlab
convex
agent.
What
we
call
cas
we
want
to
enable
it
by
default
in
omnibus
and
hand,
chart
based
installations
as
well.
A
We
have
a
transformative
bug
scheduled
to
be
checked
and
if
it
exists
to
be
fixed
in
the
milestone,
and
after
that
we
have
the
what
I
mentioned
the
ci
examiner
setup.
This
is,
is
planned
to
be
delivered
in
multiple
iterations
and
we
want
to
keep
iteration
free
and
we
might
be
able
to
reputation
for,
but
we
just
want
to
get
started
on
iteration
for
actually
all
together
to
ship,
the
ci
tunnel.
We
think
about
five
iterations.
So
there
is
one
more
to
come
later
on.
A
The
next
topic
is
around
secrets:
management.
There's
a
high
requested
feature
by
one
of
the
biggest
gitlab
customers
to
ship
wallet
related
development.
This
is
one
of
the
features
that
we
want
to
use,
to
learn
about
secrets,
management,
code
base
and
features
and
to
be
one
of
our
first
features
in
this
category.
A
After
that
we
have
what
I
mentioned
around
deprecating
gitlab
managed
apps.
We
want
to
provide
an
api
that
will
allow
kubernetes
users
to
register
their
own
ingress
elastic
stack
promises
with
git
lab
to
be
used.
Instead
of
one
click,
gitlab
managed
applications
using
this
api,
we
will
be,
it
will
be
possible
for
us
to
actually
remove
the
existing
integrations
and
our
users
can
use
the
tools
they
prefer
to
to
have
to
use
these
applications.
A
A
This
is
a
highly
requested
feature
on
providing
environment
specific
variables
at
the
group
levels,
not
just
the
project
levels
that
we
have
worked
today,
and
we
have
two
other
ux
depth
issues
that
we
want
to
ship
out
of
this
list,
the
ones
that
have
a
green
check
mark
in
the
first
column.
Actually,
the
third
column
are
the
deliverables
we
have
just
a
few
of
them
because
we
want
to
deliver
these.
A
Here's
one
topic
for
me
that
I
to
present,
which
is
the
research
access
and
authorization
around
infrastructure,
especially
around
kubernetes.
Actually
we
want
to
research
how
users
map
gitlab
projects
and
groups
to
their
cluster
namespaces
or
radius
resources
there.
So
we
can
provide
better
approach
to
the
support
in
the.
B
So
the
next
two
items
are
carryovers
from
13.8.
There
is
a
one
design
issue
for
protected
terraform
state.
I
went
through
it
during
the
last
milestone
kickoff
video,
so
I
will
skip
that,
and
the
next
item
is
a
very
small
design
piece
of
work
to
show
a
spinner
in
the
state
listing
page
if
an
action
result
is
not
eastern.
B
So
from
the
initial
explorations
that
we
did
in
13.8
for
the
design
of
the
agent
details
page
we
identified
if
you
could
jump
to
the
next
tab
victor
we
identified
that
we
will
most
likely
need
four
areas:
four
tabs
in
the
agent
details,
page
one
being
the
first
one
being
the
activity
stream
of
the
agent.
So
what
events,
actions,
errors
etc?
Has
the
agent
well
have
have
appeared,
or
has
the
agent
done?