►
From YouTube: GitLab 13.12 Kickoff - Configure:Configure
A
A
First,
we
are
getting
more
and
more
focused
on
smaller
sized
epics,
usually,
and
this
allows
us
to
to
target
more
more
teams,
more
epics
in
a
given
direction
and
as
well.
We
are
actually
closing
down
to
directions
given
the
reorganization
that
just
happened
and
what
about
team
members
leaving
and
we
are
starting
in
new
directions
right
without
the
devops,
so
the
goals
we
have
is
to
get
ready
for
14.00
in
terms
of
deprecations
and
removals.
A
A
The
second
goal
we
have
is
to
get
ready
for
the
design
sprint
in
autodevops
without
the
devops.
We
we
received
this
category
to
bleed
a
few
months
ago
and
we're
a
bit
slow
here,
but
finally,
we
finish
and
we
actually
want
to
even
add
design
spring
to
the
very
end
of
the
milestone
or
by
the
beginning
of
the
next
one.
A
The
third
goal
is
to
ship
the
term
from
registry.
We
have
very,
very
different
scope
there.
It
seems
to
be
feasible,
so
it's
one
of
our
deliverables
and
once
we
ship
it,
we
will
actually
turn
our
attention
away
from
each
code
and
transform
development
to
focusing
on
auto
devops
and
juventus
management.
A
A
As
a
result,
our
focus
will
be
out
to
devops
and
quebec's
management.
The
other
issues
are
in
kubernetes
integration.
We
have
a
ci
tunnel.
The
first
situation
is
to
to
be
able
to
deploy
from
a
runner
job
into
your
cluster,
using
the
eat
lab
commands
agent
using
the
agent's
identity
and
its
access
rights.
A
This
means
that
the
user
doesn't
have
to
set
up
all
kinds
of
kubernetes
configurations
and
anything
that
is
necessary
today
even
to
deploy
something
from
the
runner,
because
the
agent
will
have
its
own
cube
context.
Pre-Configured
and
deployments
can
happen
with
the
agent's
context
in
later
iterations.
We
want
to
add
user
impersonation
here
so
that
whatever
the
user
is
allowed
to
do
in
the
cluster,
we
can
do
that
with
the
agent
and
your
impersonation
as
well
and
a
few
other
things
I'm
going
to
speak
about
that.
A
A
A
You
have
to
write
graphq
operates
by
hand
even
two
of
them,
and
we
want
to
streamline
this
process
and
provide
you
a
nice
ui
and
finally,
something
that
we
remain
even
once
the
institute's
code
development
will
kind
of
get
too
hard.
Is
the
telephone
provider
work
that
we
have
beyond
the
gitlab
traffic
provider?
A
It's
mostly
driven
by
the
community?
We
have
a
few
issues
as
well
that
that
are
kind
of
internal
and
that
we
want
to
develop
there,
and
these
are
our
goals
for
the
next
milestone.
But
let's
see
the
let's
give
you
a
bit
better
idea.
What
we're
working
on
what
you
can
see
here
is
that
we
have
been
working
on
jobs
to
be
done
for
interesting
infrastructures
code.
Mostly,
it
will
probably
ongoing
work,
but
nevertheless
it
was
planned
for
the
current
milestone.
A
A
We
want
to
fix
that
in
the
next
milestone,
together
with
marcia
our
technical
writer,
the
telephone
registry
that
was
already
mentioned,
it
is
to
be
ready
by
the
end
of
the
next
meister.
So
this
is
one
of
our
deliverables
actually,
and
we
are
working
on
the
outer
devops.
As
you
can
see,
it
won't
end
at
the
end
of
the
mystery
a
little
bit
later.
That's
our
guess
and
then
there's
removal.
That's
should
end
by
the
end
of
14.0
and
I'm
going
to
expand
these
two
epics.
A
To
give
you
a
better
idea
what
we
plan
to
do
so
we
are
going
to
work
now
on
the
new
agent
ui
registration
with
that
is
related
to
the
management
interface
of
the
agent
and
we're
going
to
have
work
even
after
that
with
basic
details
around
the
agent
status,
and
you
want
to
provide
the
status
check
page
on
this
details,
page
that
helps
with
troubleshooting
and
kind
of
says.
Other
features
as
well
that
the
user
might
did
not
configure
horizontal
there
on
the
kubernetes
ci
tunnel
side.
A
We
are
working
now
on
providing
this
agent
identity
based
ci
tunneling,
and
after
that
we
want
to
provide
user
impersonation,
and
these
might
still
change,
but
we
have
plans
on
adding
it
at
the
group
level
as
well,
so
that
single
agent
for
the
whole
group
and
set
up
it
only
at
once,
and
we
might
want
to
add
cig
impersonation
as
well,
but
this
is
totally
unplanned
and
will
happen
sometime
in
the
far
future.
So
this
is
our
road
map
in
terms
of
deliverables.