►
From YouTube: GitLab 13.10 Kickoff - Configure:Configure
A
A
A
Besides,
measuring
the
agent
set
of
goals,
we
are
working
on
shipping,
the
first
iteration
of
traffic
registry.
This
iteration
will
not
have
a
user
interface
yet,
but
we
hope
that
we'll
be
able
to
shift
something
that
works
in
the
ci
at
least,
and
the
third
goal
we
have
is
to
ship
some
high
value
issues
in
secrets,
management
space
that
jackie
didn't
had
time
to
before.
A
B
Thank
you.
So
we
have
mainly
ux
work,
visual
work
to
do
this
milestone
and
mainly
around
the
agent.
So
we
are
continuing
to
work
on
the
agent
details
page
and
this
this
time
we're
gonna.
The
first
item
is
complete,
so
the
agent
top
level
and
access
tokens
information
is
almost
complete
and
it
will
go
to
development.
A
B
And
I'll
go
to
them
actually,
the
fourth,
so
the
activity,
information
for
the
kubernetes
agent.
This
will
be
the
activity
tab
for
the
agent,
so
it
will
have
information
like
what
the
agent
deployed.
When
was
the
agent
updated?
If
the
configuration
of
the
agent
was
changed,
so
any
information
the
user
would
like
to
see
for
troubleshooting
purposes
or
for
information
purposes
for
the
agent
and
the
agent
activity.
B
B
So
new
clusters
creation
is
not
a
great
experience
anymore
and
the
agent
creation
is
not
possible
from
the
ui.
So
we
want
to
tidy
up
all
the
screen
and
navigation,
which
brings
me
to
the
last
item
in
the
list.
Sorry
for
jumping
around,
so
we
want
to
add
some
agent
installation
instructions
in
the
ui
to
help
the
user
install
the
agent
without
necessarily
having
to
jump
to
the
documentation,
at
least,
if
they're
somewhat
familiar
with
the
agent.
B
Protected
terraform
states,
so
this
has
been
carry
over
for
two
milestones
now
and
hopefully
I'll
complete
it.
This
milestone,
it's
a
premium
feature
for
terraform
the
ability
to
add
the
protected
state
to
a
terraform
state,
so
quite
simple,
and
then
working
with
jeremy
from
the
foundations
team,
on
a
new
icon
for
the
agent
and
an
avatar
for
github
agent
project
and
the
item
below
is
a
collaboration
with
the
secure
team
on
the
auto
devops
features.
A
So,
let's
see
the
build
track,
we
have
a
pretty
huge
list
of
deliverables
compared
to
previous
months.
This
is
mostly
due
to
the
fact,
as
we
changed
from
a
hand,
curated
planning
issue
to
a
much
more
automatic
board,
as
you
can
see
today,
and
as
a
result,
it
automatically
it's
much
easier
to
add
issues
here
and
that's
why
we
have
more
issues.
A
A
First,
we
start
with
feature
flag
and
only
specific
projects
can
will
have
access
to
the
kubernetes
agent
server,
but
once
we
get
to
general
availability,
this
feature
flag
has
to
be
removed
and
to
get
to
general
velocity
availability.
We
have
to
finish
a
few
more
tasks
that
were
asked
by
our
infrastructure
team.
A
The
first
one
is
so
we
want
to
provide
name
around
the
agent
and
we
want
to
show
the
kubernetes
agent
address
associated
with
the
gitlab
instance
on
the
ui,
so
we
can
make
a
nicer
experience
for
users
to
set
up
a
new
agent,
and
the
remaining
two
items
are
about
the
terraform
registry.
I
already
spoke
about,
and
finally,
one
item
around
the
ci
tunnel
for
the
secrets
management
features.
We
I
decided
not
to
take
in
any
deliverables,
because
the
code
base
is
still
relatively
new.
A
We
we
shipped
the
first
feature
related
to
what
in
13.9,
but
the
next
feature
is
actually
more
is
not
related
to
towards,
but
what
we
think
is
the
highest
value.
One
is
the
environment,
specific
variables
and
the
group
level,
that
is,
that
users
are
able
to
specify
for
a
given
environment
rather
that
in
which
environment
it
should
be
available.
This
is
this
feature
that
exists
in
project
level.
A
For
some
time
you
want
to
add
it
on
the
group
level
as
well,
and
the
other
one
would
be
warning
when
the
value
of
environment
character
contains
a
dollar
sign,
because
because
of
a,
I
would
say,
it's
design
bug
that
today
we
replace
variables
and
variables
by
default
and
in
case
of
passwords.
This
is
not
very
useful
for
our
users,
so
these
are
the
two.
They
are
not
at
the
highest
level,
because
there
are
other
categories
that
we're
working
on
as
well,
but
in
the
service
management
space,
these
are
the
most
important
ones.