►
From YouTube: GitLab 15.11 Kickoff - Verify:Runner
Description
GitLab 15.11 kickoff video for Verify Runner categories, Core, SaaS, Fleet.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29507
A
Some
of
that
includes
providing
some
version,
compatibility
notes
so
that
you
know
exactly
which
Runners
will
be
working
with
the
new
flow
and
which
ones
may
not
be
that
you
would
need
to
update
and
then
another
thing
is
we'll
be
showing
the
new
authentication
token,
which
is
what
you're
going
to
be
using
to
register
Runners,
we'll
only
be
showing
that
in
the
UI
for
a
short
amount
of
time,
because
it
is
secretive.
So
before
you
leave
the
page
before
you
fully
register
your
Runner.
A
If
you
were
to
leave
mid
operation,
we'll
be
adding
a
warning
modal
just
to
tell
you
that
you
might
lose
the
authentication
token
and
you
would
want
to
copy
it
before
you
leave
and
then
some
of
the
stuff
that
we're
working
on
uxy's
will
be
a
new
Runner
Fleet
dashboard.
To
give
you
a
better
visibility
into
your
whole
Fleet
that
you're
dealing
with.
So
we
have
some
ideas
that
have
been
added
here.
A
Already
and
we're
planning
on
getting
some
feedback
into
how
how
much
the
data
is
really
helping
you
as
an
admin
coming
into
this
View
and
then
we'll
be
making
some
edits,
depending
on
the
feedback
that
we
get
and
then
another
fun
one
that
we're
working
on
is
how
to
add
data
for
multiple
Runner
managers,
not
actually
machines
that
we're
calling
right
now.
This
is
also
related
to
the
registration
flow
that
we're
working
on,
because
now,
when
you're
dealing
with
Runner
managers
that
have
the
same
configuration,
they
may
all
have
the
same.
A
They
will
roll
up
into
the
same
auth
token
and
they'll
be
grouped
in
the
UI.
So
we
want
to
just
make
sure
that
we're
showing
you
the
right
data
there-
and
this
is
in
solution-
validation
right
now
so
by
the
by
1511.
We
should
have
this
finalized
design.
Wise
I
think
that
is
all
I
wanted
to
bring
up
I'll,
pass
it
to
Gabriel
or
Darren.
C
Yeah
I'm
gonna
take
it.
Thank
you
Gina.
That
was
amazing.
Thanks
for
sharing
I'm
gonna
share
my
screen
as
well
and
give
you
a
short
outlook
on
what
we're
working
on
in
the
runner
SAS
domain.
So
if
you
follow
the
latest
video,
then
it
isn't
too
surprising
what
I'm
showing
today
we
are
continuing
to
work
on
transitioning
Mac
OS
to
M1
on
AWS.
C
We
are
right
before
testing
and
transitioning
our
current
customers
over
so
I
think
the
next
four
weeks
will
be.
If
you're
part
of
the
the
current
better
customers,
you
will
get
a
notification
and
then
we
will
ask
you
in
some
weeks
to
start
trying
out
the
new
tags
and
see
if
everything
works
out
and
then
hopefully
we
can
make
it
available
this
or
next
Milestone.
The
other
thing
I'm
showing
is
our
GPU,
enabled
Runners,
that's
great
for
envelopes
or
model
Ops
workloads.
C
B
Hey
thanks
people
and
thanks
Gina
super
exciting
welcome
to
another.
Let's
see
if
we
can
share
my
screen
and
Gina.
The
designs
for
the
dashboard
is
just
super
awesome,
so
if
I
run
a
call
and
I'm
so
honestly,
working
with
a
really
great
bunch
of
product
managers
and
designers
on
this
course
super
awesome
so
for
the
quality
details
back
to
run,
Accord
the
binary
that
could
here's
what
we're
doing
or
planning
to
do
again.
B
We
plan
aggressively
I'm
here
in
15
1-1,
so
the
first
area
I
just
want
to
highlight
really
fast
I'm
not
going
to
go
into
much
detail,
but
this
is
the
next
one
I
took
on
architecture.
This
is
the
back
end
stuff
that
Gina
alluded
to
when
she
described
I,
believe
the
registration
flows
and
so
there's
continuing
work
here.
That's
plan
1511
in
the
back
end
areas
to
sort
of
make
all
of
that
happen.
B
It's
moving
into
the
run,
a
core
piece
itself,
specifically
again
like
in
the
past
numerous
milestones.
We
have
a
significant
amount
of
investment
in
terms
of
reducing
the
backlog
of
bugs
that
we
have
especially
our
set
of
two
priority.
Two
bugs
and
so
you'll
see
a
focus
there
as
you
can
see
on
the
screen
in
terms
of
some
of
the
bugs.
We
want
to
get
2
and
15.2
and
15
and
11.
B
in
terms
of
new
features.
I'm
going
to
call
out
just
these
first
three
in
the
list
that
we're
now
labeling
run
a
P1
and
for
this
is
a
new
label
that
we've
just
adopted
and
basically
what
it
means.
It's
a
priority
for
our
team
in
the
iteration.
So
as
we'll
as
a
team
is
coming
in
and
we're
trying
to
figure
out
where
we
might
have
to
spend
out
of
capacity.
B
We're
adopting
we're
looking
to
adopt
the
Ubi
8
for
those
customers
are
using
Red,
Hats
and
Ubi
8
images
on
for
for
Rel
for
the
runner,
we're
going
from
Ubi
8
base
to
Ubi
8
minimal.
So
it's
a
much
more
smaller
footprint.
It
increases
security
and
that
sort
of
thing-
and
so
take
a
look
at
that.
We
don't
expect
a
lot
of
impact
to
customers
who
are
currently
reliant
on
ubia
base,
but
there
are
also
some
changes
in
Ubi
8
minimal.
B
So
if
you
are
building
your
own
custom,
Runner
helper
image
on
top
of
our
base
images
just
be
aware
of
some
changes
in
the
package
management
capabilities
that
are
going
to
be
different
in
Ubi
8,
minimal
versus
Ubi
8
beta.
Now,
that's
a
lot,
but
just
again,
if
you're
building
on
top
of
our
base
package,
just
be
aware
that
we're
switching
to
you,
we
are
eight
minimal
in
1511.
B
in
terms
of
new
features
these
two
here
and
I'm
just
going
to
click
into
it.
This
is
the
the
first
time
we'll
be
releasing
in
Alpha
the
solution
for
our
next
Runner
autoscaler
and
specifically,
what
we're
working
on
I'm,
hoping
to
get
over
the
Finish,
Line,
15
and
11,
is
the
leading
plugin
that
ties
all
of
this
together.
B
So
this
is
going
to
be
an
alpha
officially
in
1511,
and
it
basically
means
that
if
you
were
a
customer
today
that
is
using
the
GitHub
using
gitlab
Runner
and
specifically
Auto
scaling
gitlab
Runner
using
the
docker
machine
based
Auto
scanning
executor.
This
is
your
first
opportunity
to
start
testing
out
our
new
auto
scaling
solution
that
is
using
Auto
scaling
groups
on
AWS,
that
is
using
our
own
internally
development,
intellectual
property
and
it's
using
the
speeding
plugin.
B
So
this
is
your
first
instance
or
first
opportunity
to
really
start
kicking
the
tires
so
to
speak
on
the
new
solution.
So
we're
super
excited
this
is
coming
out
and
once
this
lands
in
1511
it
will
hook
with
an
accelerate
the
next
set
of
feature
set
and
that
you'll
start
seeing
the
plugins
for
Google
compute
Cloud
as
well
as
Azure,
and
that
sort
of
thing
come
out
in
in
subsequent
releases.
B
So
again,
if
you
are
been
asking
and
waiting
for
the
docker
Machine
replacement
solution,
the
first
piece
of
this
is
shipping
in
1511
and
that's
what
I
want
to
call
out
there.
Let
me
just
pop
back
over
to
missions,
nothing
else
yeah.
So
that's
really
good.
Next,
one
Auto
scaling
Alpha,
AWS
and
5011
super
excited
about
that.
That's
it
for
one,
of
course,
back
to
Eugene.