►
From YouTube: GitLab 13.8 Kickoff - Configure:Configure
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Oops
yep
like
this
so
I'll,
be
start
first
and
then
I
will
hand
over
to
maria,
so
our
goals
are.
We
have
three
goals
for,
for
this
relatively
short
milestone,
one
is
around
observability.
A
There
are
many
areas
in
our
product
categories
that
are
not
well
instrumented,
and
we
want
to
improve
upon
that.
Then.
The
second
goal
is
to
measure
the
agent
primarily
this
means
to
make
it
finally
available
on
gitlab.com
and
make
it
enabled
by
default
for
all
the
installation
types
we
have
and
the
third
goal
we
have
is
around
gitlab,
minister
from
states.
We
are
continuing
our
development
journey
here
by
extending
the
the
management
interfaces
around
little
administration
states,
so
to
get
into
more
details
around
our
delivery
plan.
A
The
third
item
here
is
is
a
bug
that
seems
to
exist,
but
we
are
not
sure
about
it.
Yet.
So,
let's
move
on
to
observable
issues,
given
the
quite
widespread
option
of
of
the
gitlab
star
from
state,
which
means
that
there
are
more
than
3
000
state
files
today
managed
by
git
lab
it's
time
to
move
to
a
user-based
metric
as
well,
and
we
are
developing
that
moreover,
another
very,
very,
very
interesting
topic
is
the
instrumenting
ci
templates
usage.
A
We
would
love
to
instrument
all
the
templates,
but
we
are
a
bit
afraid
of
the
performance
impact,
so
we
are
actually
instrumenting.
10
templates,
the
security
ones,
the
core
auto
devops
and
traffic
templates
and
the
auto
really
auto,
deploy
templates
to
see
how
many
ec2,
ecs
and
kubernetes
users
there
might
be.
A
The
following
items
are
more
back-end
type.
I
would
say,
like
end-to-end,
test
supporting
encryption
of
that
from
reports
at
rest.
So,
let's
move
rather
to
the
providing
actions
like
it
may
start
from
states.
This
is
an
item
I
mentioned
in
the
gauze
to
have
a
better
support
for
gitlab
manager
from
state.
We
are
adding
actions
like
dating
the
state
files,
downloading
them,
etc.
A
A
That
basically
means
that
the
agent
will
be
able
to
deploy
from
ci
pipelines
and,
as
the
agent
is
more
secure
in
the
current
setup,
this
provides
offer
requested
security
feature
for
our
users
in
the
first
iteration.
We
just
want
to
make
it
possible
to
connect
git
lab
and
the
the
cluster
through
the
agent
and
be
able
to
provide
a
status
feedback
from
the
agent
towards
gitlab,
like
a
red
green
status,
that
the
agent
is
online
and
connected
or
we
have
lost
it.
B
So,
from
the
design
side,
we
are
continuing
on
the
agent
details
page
that
we're
starting
to
design
the
initial
explorations
this
milestone,
so
we're
continuing
with
the
high
fidelity
design
of
the
agent
details
page,
which
also
includes
the
manifest
sync
status
which
is
not
in
this
list.
But
it's
in
this
milestone
in
13.7,
following
that
we
have
the
design
for
protected
terraform
states,
so
we're
continuing
the
work
for
terraform.