►
From YouTube: GitLab 16.0 Kickoff - Verify:Runner
Description
Kickoff video for Runner Fleet, SaaS, Core 16.0.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29260
https://about.gitlab.com/direction/verify/runner_fleet/
https://about.gitlab.com/direction/verify/runner_saas/
https://about.gitlab.com/direction/verify/runner_core/
A
This
Milestone
will
be
continuing
to
work
on
the
new
creation
workflow
for
runners,
so
you're
going
to
see
this
in
the
projects
section
as
well.
We've
already
done
this
for
the
admin
and
groups,
but
it's
behind
a
feature
flag
at
the
moment
and
so
we'll
be
working
to
bring
this
to
the
product
view
too.
A
So
we'll
give
you
a
little
bit
of
a
warning
when
you
disable
them
just
so
that
you
know
that
you
won't
be
able
to
re-enable
them
as
easy
as
it
was
to
disable
them
and
then
further
ux
we'll
be
working
on
solution.
Validation
for
the
runner,
Fleet
dashboard,
which
is
something
I
shared
in
our
last
video
and
we're
still
working
on
meeting
with
users
about
this
to
validate
it
and
then,
on
the
back
end
side
of
things.
A
We're
going
to
work
on
trying
to
tighten
up
the
architect
the
blueprint
architecture
for
how
we're
gonna
be
able
to
create
this
feature.
So
how
we'll
support
all
the
metrics
that
we're
going
to
be
showing
so
that
we
can
then
be
ready
to
start
implementing,
hopefully
very
soon.
B
Amazing,
thank
you
so
much
Gina
very
exciting
iteration
for
Fleet.
Let
me
jump
into
Runner
sauce
and
share
my
screen
yeah.
If
you
follow
the
last
videos,
then
you
might
be
familiar
with
the
theme,
because
most
of
our
topics
are
kind
of
carryovers.
Unfortunately,
for
priority
one
here,
we
have
getting
Mac
OS
Runners
into
production
and
dog
fooding
their
usage,
so
we're
confident
in
our
migration
to
M1.
That
is
a
big
theme.
B
Already,
since
the
last
or
past
past
weeks,
we
have
a
clear
cut
on
it
when
we
have
to
finish
the
migration
which
is
end
of
March,
and
that
is
the
reason
end
of
May.
B
Sorry
March
has
already
been
that's
the
reason
why
this
is
currently
Priority
One,
the
other
topic
we
are
focusing
on
which
we
kind
of
have
everything
set
up
already,
and
it's
a
bummer
that
we
couldn't
release
it
already
with
this
iteration
is
to
get
our
first
GPU
enabled
Runner
out
the
door
which
really
will
unlock
all
our
model,
Ops
customers
to
start
building
and
training
their
own
models
and
using
gitlab
CI
for
it.
B
Unfortunately,
we're
currently
still
waiting
for
some
quota
increase
and
are
kind
of
blocked.
Probably,
as
you
all
know,
gpus
are
kind
of
thought
song
after
on
the
market
right
now,
so
it's
not
too
easy
to
get
them,
but
we
are
really
doing
our
best
here
to
get
this
out
in
the
next
one
to
two
weeks
and
then
release
it
officially
with
the
upcoming
release.
B
Next
one
we
have
our
okr
and
our
our
goal
to
become
and
still
be,
our
best
in
class
and
CI
build
speed.
And
as
one
of
these
efforts
we
are
upsizing
our
current
Linux
offering
so
the
we
have
three
computes
currently
offered
for
Linux
three
three
sizes
which
being
small
medium
and
large,
and
we
will
double
the
vcpus
for
them.
So
that
will
be
good
news.
B
It
comes
with
no
extra
cost
for
our
users,
so
yeah
that
should
be
super
exciting
yeah,
that's
about
it
on
the
runner,
SAS
topic
and
then
handing
over
to
edern.
C
Hey
thanks
a
bunch
super
excited
to
see
what's
happening
in
both
since
we.
Let
me
share
my
screen
and
talk
a
bit
about
run
and
call
so
for
Runner
core
I'm,
going
to
kind
of
switch
up
the
web
and
talking
about
it,
because
sometimes
we
go
way
into
into
the
weeds
as
we
as
we
all
know.
I'm
assuming
everyone
knows
the
runner
core
application
comes
out.
C
A
lot
of
surface
area
right,
gitlab
Runner
supports
many
many
clouds,
many
types
of
compute
platforms
and
so
many
different
things
that
we
do
in
one,
of
course,
to
enable
GitHub,
CI,
CBI
scale,
and
so
sometimes
on
these
Kpop
videos.
We
tend
to
go
way
into
the
V8
in
terms
of
like
really
intricate
features,
and
so
sometimes
we
get
lots
of
the
flowers
from
the
trees
or
the
trees
from
the
forest.
C
But
what
I
want
to
start
doing
for
the
next
two
or
three
particular
videos
is
kind
of
focus
on
some
big
themes
or
some
thematic
areas
for
run-up
call,
as
we
get
into
Q2
and
there's
a
Q3
of
this
year
and
that
specifically
going
to
kind
of
focus
on
gitlab
Runner
or
what
we're
currently
following
next
run
on
auto
scaling.
So,
even
though,
on
these
calls
in
the
future,
videos
I
might
highlight
incremental
features.
C
Like
say,
we
are
doing
work
on
our
cumulative
executor
and,
if
there's
something
interesting
to
highlight
there,
I
will
talk
about.
Like
last
time,
we
talked
about
the
Pod
spec
World,
which
is
kind
of
one
of
those
like
in
the
weeds
features,
talk
about
powerful
for
our
AI
customers
and
our
data
science,
customers
that
are
using
Google
clouds.
For
example.
C
What
I'm
going
to
focus
on
a
lot
is
next
on
auto
scaling
over
the
next
three
Kpop
videos
and
so
kind
of
just
to
kind
of
preface
what's
happening.
There
get
lab
Runner
over
scaling,
which
we
have
been
employing
the
next
one
or
the
skill
until
now,
I'm
kind
of
switching
the
language
up
a
bit
just
a
little
bit
clearer.
C
It's
our
replacement
for
dark
machine
on
the
screen,
but
what's
super
interesting
about
this
technology
is
that
it's
getting
a
develop
IP
and,
more
importantly,
it
allows
you,
the
users
that
are
self-managing
your
devops
platform.
So
customers
don't
get
websites.
C
It's
another
piece
of
the
pie
and
we'll
be
adding
AI
capabilities
into
this
in
the
future,
and
it's
an
important
piece
of
the
pie
in
that
it
allows
you
to
scale
efficiently
this
estate,
that's
required
to
read
all
of
this
stuff
work
on
any
Cloud
platform,
super
cloud
agnostic,
any
Cloud
platform
and
over
time
in
the
most
cost,
efficient
way
possible.
So
the
GitHub
Auto
scaling
technology
is
new
technology
that
we
develop
here
at
gitlab.
That
enables
you
to
say:
okay,
I'm,
attacking
the
GitHub
devops
platform
and
I
use
Google
Cloud.
C
For
my,
you
know,
for
my
infrastructure
and
I
run
this
platform
and
scale
absolutely
fair,
and
so
this
is
what
it
looks
like
at
a
high
level.
A
very
simple
architecture
that,
under
the
covers,
makes
a
lot
of
interesting
things
happen
and
so
what's
happening
in
16.0
and
then
actually
backup
for
a
bit.
C
We've
actually
started
releasing
pieces
of
this
and
we
are
as
we
as
I
was
speaking
right
now:
we're
refining
the
documentation
so
that,
as
you
come
into
our
docs,
starting,
hopefully
in
15
at
one
and
definitely
been
16
and
adult
there
will
be
a
landing
page
called
get
lab.
Runner,
Auto
scaling,
and
so
you
can
kind
of
hit
that
non-new
page
and
understand
how
to
get
from
point
A
to
point
Z.
What
we
have
right
now
is
we
have
the
initial
Auto
scalar
technology
for
Docker.
C
We
have
the
autoscaler
technology
for
instances,
I'm
not
going
to
go
into
that
on
this
call,
but
basically
what
it
allows.
That's
the
foundational
pieces
and
what
we're
doing
in
what's
coming
out
in
15.11
is
the
alpha
plug-in
that
makes
all
of
this
work
for
customers
of
AWS
just
to
pop
back
over
to
the
slides-
and
this
makes
everyone
understand
this-
we
need
in
order
to
make
this
all
work.
There's
this
kind
of
this
plug-in
model.
C
So
the
AWS
plugin
is
what
allows
you
if
you
are
using
AWS
to
reuse
the
git
background
Auto
scaling
on
AWS,
the
gcp
plugin
is
what's
going
to
enables
you
to
run
this
on
gcp.
The
Azure
plugin
is
what
allows
you
to
run
this
on
Azure
in
the
future.
If
you
potentially
conceive
of
it,
maybe
you
do
a
VMware
in-house.
C
We
potentially
can
have
a
VL
web
plugin
that
allows
you
to
scale
very
easily
on
VMware
and
so
15.11
we're
releasing
the
AWS
plugin
in
Alpha
and
n16.0
and
now
finally,
back
to
the
600
iteration
plan,
the
main
feature
set.
We
want
to
get
out
the
door.
Forerunner
call
is
the
cleaning
plugin
for
Google
compute
Cloud.
So
today
you
can
start
testing
out
our
order,
scaling
solution
and
15.11.
You
can
stack
it
in
the
tiles
of
AWS,
but
in
69.
C
Oh,
we
want
you
to
be
able
to
grab
the
plugin
for
Google
cloud
and
start
testing
this
out
on
Google
Cloud
platform
and
so
just
to
wrap
up
and
we'll
have
more
videos
in
the
future,
specifically
on
the
value
proposition
of
the
auto
scaling
theme,
because
this
is
not
our
only
Auto
scaling
solution.
We
also,
obviously,
can
we
keep
talking
about
in
every
K-pop
video
kubernetes.
C
So
this
is
for
customers
that
don't
want
to
sub
kubernetes
and
securely
efficiently
and
cause
the
fresh
effectively
scale
up
the
devil
platform
building
environment
at
scale.
So
we're
super
excited
on
that
Focus.
So
in
16,
at
all,
16
number
and
1602
I'm
going
to
keep
hitting
on
this
theme
around
all
the
scaling
and,
of
course,
we'll
just
to
wrap
up
again
another
Focus
area
person
or
is
continued
addressing
any
of
our
Legacy
priority.
C
Two
bugs
that
you
know
when
we
have
brothers
in
different
areas
of
the
code
that
we
want
to
definitely
get
addressed
in
in
this
in
the
in
the
code
base.
But
in
terms
of
new
feature
sets.
This
is
going
to
be
our
Focus
here,
open
the
next
three
releases.
That's
it
for
you
want
to
call.
A
Awesome
that
was
great
Darren
thanks
for
sharing
that
presentation
too.
Just
a
quick
shout
out
that
we've
been
working
a
lot
in
like
since
this
group
started
been
working
a
lot
with
the
customer
success,
managers
and
they've
been
super
helpful
for
us.
So
if
you're
watching
thank
you
and
thanks
to
to
all
the
users
who
have
been
giving
us
feedback
as
well
reach
out
as
usual,
if
you
have
anything
that
you
want
to
give
us
feedback
on,
thank
you.