►
From YouTube: GitLab 14.2 Kickoff - Configure Configure
A
Let's
see
what
do
we
have
to
offer,
we
have
basically
four
goals
for
this
milestone.
First
of
all,
we
would
like
to
fix
our
error
budget
by
looking
into
the
root
cause
we
identified
it's
likely
likely
related
to
the
traffic
state
api
as
we
encrypt
and
decrypt
the
state
files
and
the
state
files
grow.
Naturally,
we
can't
fit
the
one
second
limit
there.
We
want
to
investigate
whether
this
is
really
the
root
cause
and
whether
we
have
other.
A
Actually
we
don't
consider
this
to
be
a
bug
in
the
system
that
we
can't
fit
in
one.
Second,
we
think
that
three
seconds
should
be
totally
fine
for
this
use
case
at
the
same
time
want
to
be
sure
that
this
is
the
reason
why
we
fail
the
expectations
here
and
whether
the
metrics
should
be
adjusted
or
whether
we
have
something
to
fix.
A
The
second
item
is
around
the
gitlab
commence
agent
ci
tunnel.
We
released
the
ci
tunnel
during
14.1
and
it
will
be
released
on
for
on
for
south
managed
in
14.1
and
at
the
same
time
we
are
going
to
move
to
core
the
this
version
of
the
ci
tunnel
and
for
14.2.
Our
plan
is
to
prepare
the
movement
to
core
and
perhaps
to
start
as
well
related
to
the
ci
tunnel.
We
continue
development
of
the
tunnel.
A
A
Our
final
goal
is
to
improve
the
management
interfaces
around
the
kubernetes
agent
in
14.1.
We
are
shipping,
a
new
registration
ui,
and
we
have
further
plans
to
add
various
data
to
the
agent
details
page
like
the
version
that's
installed
in
the
cluster
and
what's
available
besides
gitlab,
so
we
can
show
compatibility
information
and,
in
general,
our
primary
objective
is
to
support
troubleshooting
use
cases
with
this
ui.