►
From YouTube: GitLab b16.5 Kickoff - Verify:Runner
Description
Kickoff video for GitLab Runner Core & Fleet for GitLab 16.5
https://about.gitlab.com/direction/verify/runner_core/
https://about.gitlab.com/direction/verify/runner_fleet/
A
Hi
everyone
I'm
Gina,
Doyle,
a
senior
product
designer
for
the
runner
fleet,
team
and
I'm.
Here
with
Darren,
we
are
kicking
off
the
16-5
iteration
plan
for
the
runner
group
today,
I'm
going
to
start
off
with
just
giving
an
overview
of
the
runner
fleet
team
and
what
features
we'll
be
taking
on
for
16.5.
So
I'll
start
sharing
my
screen
all
right.
A
So
if
you
want
to
come,
look
at
all
the
issues
they're
in
our
iteration
plan
here,
but
the
first
one
I'll
talk
about
is
something
that
you've
probably
seen
as
a
trend
over
the
past
few
Milestones
is
our
admin
view.
Fleet
dashboard
feature
that
we're
working
on,
and
it
is
combined
of
some
starter
metrics
that
we're
going
to
give
users,
and
this
should
help
those
platform,
Engineers
or
infra
operators
who
are
managing
a
large
Fleet
of
Runners
who
are
self-managed
to
get
a
quick
visibility
or
high
level
overview
of
their
Fleet.
A
This
is
super
exciting
for
us,
because
we
have
finally
made
some
really
great
progress
on
this
wait
time
to
pick
up
a
job
chart
here,
and
this
is
a
crucial,
crucial
feature
for
us
to
ship
as
well.
So
we'll
continue
to
work
on
getting
this
graph
specifically
into
the
front
end
and
then
getting
some
good
documentation
of
how
to
actually
get
this
to
be
set
up
for
an
instance
along
with
that,
like
I
just
said,
we'll
be
working
on
visualizing
those
percentiles.
A
A
B
Okay,
sorry
about
that
everyone,
Hi
I,
was
just
saying
I'm
just
going
to
share
my
screen
so
for
one
I'll
call
just
a
quick
again
just
to
quickly
level
set
our
Direction
Pages
again
the
entry
point,
if
you
want
that
sort
of
like
20
000
foot
view
of
the
major
Strat,
the
major
strategy
to
run
a
call
for
fy24,
and
this
strategy,
of
course,
will
soon
evolve.
As
we
said
from
a
gitlab
product
leadership
perspective
working
on
our
fy25
plan.
But
again
you
consider
I'll
run
a
core
Direction
page.
B
So
if
you're
an
organization
that's
invested
in
kubernetes
and
you're
comfortable
kubernetes,
you
absolutely
are
able
to
use
the
runner
on
kubernetes
and
that's
what
this
is.
A
lot
of
our
customers
are
using
the
runners
on
public
Cloud
instances
and
that's
what
the
next
One
auto
scaling
solution
is
about,
and
so
for
16
5.
B
We
are
working
right
now.
That's
kind
of
the
big
theme
we're
working
on
is
moving
our
new,
auto
scaling,
Solutions,
specifically
what
we
have
called
the
fleeting
plugins
for
Thomas
AWS,
ec2
compute
instances
for
Google
compute
cloud
and
for
Azure,
so
we're
working
very
diligently
from
moving
those
plugins
which
are
currently
in
experimental
to
Beta
and
then
to
GA.
So
for
16.5
we
may
actually
roll
over
the
work,
we're
doing
for
AWS
to
get
that
plug
into
beta
and
then
the
other
goal
as
well.
We
want
to
get
to
it.
B
It
absolutely
encourage
you
to
test
that
out
to
give
us
feedback
to
see
if
we
think
that
we
need
to
work
on
to
transition
those
things
to
Beta
and
then
finally
to
GA,
which
is
our
goal,
is
to
get
at
the
ga.
By
the
time
you
wrap
up
gitlab's
physical
Q4,
which
is
in
January
of
next
year.
So
that's
the
big
sort
of
new
feature
area,
we're
focused
on
for
Runner
core,
the
other
areas
that
we
are
investing
in
continuously
over
the
last.
You
know
two
to
three
quarters
that
I
think
I've
talked
about.
B
This
call
is
a
significant
amount
of
investment
in
the
core
team
is
on
resolving
bugs
in
the
environment
or
in
the
running
quite
environment,
and
so
that's
where
your
CPAs,
under
this
section,
we
have
a
large
number
of
bugs
that
we
try
to
work
through
in
every
iteration.
So
Bob
burn
down
is
a
critical
part
of
our
strategy
to
ensure
that
you
can
effectively
use
the
runner
in
your
environment
for
executing
CI
bills.
B
So
that's
it
for
the
coin
and
65
the
focus
is
continuing
to
move
those
Auto
scaling
plugins
from
experimental
to
Beta
16
5.
The
Google
computer
is
on
Deck.
We
may
roll
over
the
AWS
plugin
and
we
have
some
work
right
now.
That's
still
in
the
flight
in
terms
of
new
testing,
that's
happening
there.
So
if
we
don't
transition
at
AWS
plugin
to
Beta
and
16
4,
it
will
rule
over
the
16.5
as
well
and
let
that
goal
is
again
get
all
of
those
to
Beta
and
then
like
end
of
Q4
to
transition.
A
Thanks
Darren,
so
we
have
a
lot
of
very
exciting
features:
we're
shipping
this
Milestone
and,
as
always,
thank
you
so
much
for
the
feedback.
I
know
we've
met
with
a
lot
of
customers
lately
and
we
really
appreciate
your
feedback
on
current
features
and
future
roadmap
pieces,
and
if
you
have
any
questions
or
concerns,
please
feel
free
to
reach
out
to
Darren
or
I.
Thank.