►
From YouTube: GitLab 14.8 Kickoff - Verify:Runner Group
Description
Kickoff video for the 14.8. iteration plan .
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28647
https://about.gitlab.com/direction/verify/runner/
https://about.gitlab.com/direction/verify/runner_fleet/
https://about.gitlab.com/direction/verify/runner_saas/
A
Hey
everyone
welcome.
This
is
the
first
gitlab
runner
group
kickoff
video
for
the
new
calendar
year
and
also
actually
for
a
new
fiscal
year,
so
gina
doyle's
with
me,
product
designer
lead
producer
for
github
runner
group.
So
today
I'm
going
to
share
my
screen
out
and
we're
going
to
do
a
kickoff
video
for
fortnite,
but
we're
also
going
to
give
you
a
little
bit
of
quick
context
in
terms
of
the
strategic
direction
for
our
three
major
categories
in
the
roanoke
groups.
A
Let
me
just
share
my
screen
really
fast,
which
I
should
have
done
before
and
just
to
set
the
stage
for
those
folks
have
been
following
along
prior
to
september
or
october
of
last
year.
We
only
had
one
category
direction,
page
for
the
runner
group.
A
So
again,
we
have
three
direction
pages
for
the
runner.
The
one
I'm
on
right
now
is
for
one
of
core.
We
have
one
for
runner
sas,
and
then
we
have
one
for
runner
fleet.
Just
as
we're
heading
into
calendar
year.
You
know
2022
and
get
that
fiscal
year
fy23.
A
So,
for
this
is
some
of
the
big
things
for
us:
the
security,
compliance
and
secure
software
supply
chain,
so
we're
working
on
a
flips,
compliant
gitlab
runner,
for
example,
and
that
would
actually
ship
pretty
soon,
which
is
coming
on
the
fourth
note,
seven
and
we're
also
looking
at
significant
security
enhancements
in
terms
of
the
actual
core
runner
architecture,
and
this
is
critical
to
our
long-term
strategy
of
enabling
of
of
delivering
the
best
kit
lab
ci,
cd,
the
best
ci
cd
platform
and
so
we'll
be
looking
at
enhanced
security
improvements
for
github
runner,
similarly,
and
also
related
to
the
security
theme
and,
more
specifically,
the
secure
software
supply
chain.
A
A
really
interesting
piece
of
work
for
us
this
year
as
well,
is
thinking
about
how
we
integrate
get
lab
runner
with
the
metadata
data
store.
It's
a
lot
of
buzz
in
the
industry.
There's
a
lot
of
of
need
around
this
whole
concept
of
securing
yourself
a
supply
chain
of
of
doing
things
like
s-bombs
and
the
runner
has
an
integral
piece
of
that,
and
so
we'll
we'll
be
working
on
and
looking
at
metadata
data
store
integration
with
gitlab
runner
here
in
this
calendar
year.
A
Finally,
in
terms
of
the
security
and
compliance
themes,
continuing
those
as
well
as
again
major
theme
for
us
this
year,
security
plans,
two
big
things
for
us,
so
we'll
be
looking
at
this
concept
of
namespace
or
protecting
get
vibrant
tags
and
kind
of
thinking
about
how
that
fits
within
the
overall
ci
cd
architecture.
A
And
then
we
also,
as
we
get
into
the
back
end
of
the
calendar
year,
the
backend
of
the
fiscal
year.
I
forget
that
kind
of
thinking
about
and
studying
some
incremental
world
around
updating
your
own
architecture
and
making
and
evolving
the
architecture
again
with
a
goal
of
ensuring
that
we
provide
the
most
secure
and
reliable
ci
cd
building
environment.
For
for
your
for
your
ci
cd
jobs
and
gitlab
onrun
assass-
and
this
is
the
page
for
remossas.
A
A
We'll
be
looking
to
take
our
mac,
os
runners
that
are
currently
in
beta
test
currently
in
beta,
and
thank
you
so
much
for
the
community
as
the
indian
and
the
customers
are
seeing
them
with
a
lot
of
customers
on
our
beta
platform.
Right
now
is
giving
us
a
bunch
of
great
feedback.
Our
goal
would
be
by
qt
one
of
this
fiscal
year
to
move
that
into
ga,
to
look
for
more
announcements
and
and
and
information
on
that,
and
then
we're
also
having
this
theme
around
scalability.
A
So
we're
looking-
and
this
relates
to
run
accord
for
a
bit
implementing
a
new
order,
skating
solution
for
our
docker
runozone.com,
the
ones
that
actually
are
currently
hosted
on
linux,
vms-
and
this
is
part
of
our
long-term
architectural
evolution
again
to
ensure
that
for
our
customers
are
using
vietnam
sas
that
you
are
able
to
to
depend
on
and
rely
on,
the
most
scalable
and
performance
ict
birth
platform
in
the
industry,
and
so
we'll
be
doing
a
lot
of
work
this
year
in
terms
of
implementing
and
improving
other
skating
architecture.
A
And
then,
last
but
not
least,
we've
had
all
windows,
runners,
undone
on
github.com,
it's
been
in
beta
for
over
a
year
now,
we've
got
a
few
customers
that
are
really
interested
in
us.
Moving
that
particular
offer
to
ga.
A
So
we'll
also
be
looking
to
move
that
offer
to
ga
in
this
fiscal
year
as
well
so
run
a
feature
starts
this
wrap
up,
scalability
improvements,
new
order,
skating
solutions,
as
well
as
on
the
brain
for
for
this
fiscal
year,
getting
all
macro
astronomers
to
ga
and
then
when
this
runs
to
ga
as
well,
so
I'll
stop
shooting
at
gina.
Do
a
quick
overview
of
kind
of
what's
happening
over
normal
fleet
and
then
we'll
touch
on
and
then
we'll
go
into.
The
fourth
and
eighth
iteration
plan.
B
Thank
you
all
right,
I'll
share
my
screen,
so
just
a
summary
of
what
runner
fleet
is,
which
we've
been
talking
about
for
the
past
few
milestones
now,
but
our
vision
is
really
to
provide
one
place
for
configuration
management
capabilities
that
relate
to
runners
and
in
the
future,
allow
for
predictive
analytics
to
administer
that
fleet
of
runners.
B
Right
now
we
have
some
visionary
mocks
that
were
we're
moving
towards
to
be
able
to
improve
the
search
and
association
with
runners,
so
that
you
know
exactly
what
you're
looking
for
and
you
can
find
that
runner
really
easily,
and
that
includes
a
whole
bunch
of
improvements,
but
we've
kind
of
scoped
those
improvements
into
themes
down
here
in
our
strategic
priorities,
so
we're
first
focusing
on
the
foundational
work
so
that
we
can
build
a
strong
foundation
to
then
add
new
features,
and
with
that
we're
also
looking
at
usability
improvements
that
a
lot
of
them
were
identified
from
a
ux
scorecard
that
we
carried
out
in
2021,
and
that
gave
us
a
lot
of
recommendations
of
how
to
improve
the
experience
and
then
also
happening
in
q1
of
this
year.
B
Sorry
we
have
improvements
of
search
and
association
and
being
able
to
export
your
data
for
an
admin
and
for
group
views
and
we're
also
going
to
turn
our
attention
to
usability
improvements
in
the
group
view,
which
is
something
that
we
haven't
really
exactly
looked
at
right
now,
since
we've
been
so
concentrated
on
getting
the
admin
view
up
to
speed
and
then
in
fy,
23
q2
we'll
be
looking
at
runner
admin
view
in
adding
new
features
in
there,
as
well
as
adding
new
features
in
the
group
view,
and
the
timings
here
potentially
could
change.
B
A
Yeah,
thank
you
so
on
the
14
8
iteration
plan,
I'm
going
to
share
my
screen
again
just
kind
of
dive
into
that
more
tactically.
So
again,
we
just
wanted
to
frame
up
the
fees
for
the
year.
There's
a
lot
of
broad
themes,
and
now,
when
we
talk
about
our
iteration
plans,
it's
you
know,
obviously
a
bit
more
tactical.
A
It's
kind
of
what
we
have
on
the
docket,
what
we
actually
coding
to
to
deliver
and
our
ship
in
this
next
milestone
so
I'll
cover
briefly
what's
happening
in
renault
core
from
a
features
perspective
and
I'll
touch
briefly
in
terms
of
what's
happening
around
the
science
works,
three
stream
and
fourteen
and
eight
so
in
one
core
for
fourth
and
eighth,
we've
got
as
you
can
see
on
my
screen.
Here
we
have
a
number
of
critical
bugs
that
we
need
to
get
wrapped
up
so
it'll
be
a
primary
for
a
key
focus.
A
I
should
say
a
primary
focus.
First
unfortunate
eight
is
resolving
the
bugs
that
are
listed
here
on
the
screen.
We've
got
one
with
cleaning
up
volumes,
there's
also
one
related
to
the
kubernetes
executor
and
also
an
issue
with
the
resource
quarter.
There
are
also
some
additional
issues
that
are
listed
here
below
that
we
need
to
tackle
related
to
get
fed
strategy
some
stuff
with
a
pipeline's
namespace
and
something
to
do
with
csv
to
cash.
So
we've
got
a
lot
of
broke
on
the
docket
in
run
accord.
A
That's
focus
on
bugs
as
a
result
of
that.
As
you
look
under
our
features
section,
our
feature
sections
have
some
new
capabilities
for
runner
core.
We
talked
about
this
in
our
last
release.
We
are
working
on
releasing
a
gitlab
runner
operator
for
kubernetes.
Just
to
recap,
we
currently
have
a
gitlab
runner
operator
for
red
hat
openshift.
It's
been
very
successful
and
very
and
provides
a
lot
of
great
value
for
our
customers
and
our
user
base
that
uses
red
hat
openshift.
A
A
Unfortunately,
we
didn't
wrap
it
up,
so
that's
why
you're
seeing
it
now
end
fortnite
the
other
thing
we
want
to
also
get
over
the
finish
line
in
terms
of
new
features
and
run
a
coin
fortnite,
and
this
is
again.
This
relates
to
our
platform,
enablement
theme
that
we
started
in
last
fiscal
year
and
that
we
have
transferred
over
this
fiscal
year
and,
apart
from
enabling
team
that
same
run
operator,
then
release
for
red
hat
open
shift
last
fiscal
year.
We
want
to
enable
it
on
a
ppc64,
led
architecture.
A
So
we've
been
doing
a
bunch
of
work
on
getting
that
done.
There
are
a
bit
of
hiccups
with
some
support
of
some
support,
some
some
hiccups
in
terms
of
some
blockers
from
a
technical
standpoint.
We
hope
to
resolve
those
and
get
us
shipped
out
to
you
here
in
in
14a.
A
In
addition
to
platform
support,
we
also
want
to
go
ahead
and
start
releasing.
Finally,
a
github
runner
version,
that's
built
for
the
apple
m1
chipsets.
Currently,
I
will
get
that
runner
version
that
we
release
is
built
for
x8,
x86
and
64
chipsets,
and
so
this
is
to
go
ahead
and
build
that
build
a
version
of
the
runner
for
the
apple
m1
chipset,
a
stretch
goal
for
us
in
terms
of
new
features
and
capabilities
for
running
core.
A
Unfortunately,
which
is
back
to
the
theme,
if
you
recall
from
the
direction
page
where
we're
talking
about
the
security
and
compliance
team,
is
that
we
hope
to
get
to
start
working
on
a
proof
of
concept
where
we're
integrating
our
own
internal
gitlab
run
run
a
build
process
with
an
artifact
metadata
data
store,
whether
that's
a
graphics
that
was
released
by
google,
open
source
or
some
other
solution.
But
our
first
goal
is
to
get
a
poc.
A
Do
some
internal
dog
fooding
on
that
one
get
that
running
perspective
so
that
we
can
make
some
decisions
technically
in
terms
of
what
the
right
next?
What
the
right
next
iteration
is
in
terms
of
a
developing
a
solution.
That's
fully
integrated
with
github
runner
and
it
provides
you
the
end
user
and
customer
a
seamless
solution
as
part
of
the
broader
software
supply
chain
and
security
strategy.
A
Finally,
on
run
assassins,
we
don't
have
anything
planned
to
shift
in
terms
of
our
new
features
or
capabilities
in
terms
of
the
runners
that
are
on
gitlab.com.
Nor
are
we
planning
to
enforcing
that
aid
release
anything
as
ga.
What
we
are
focused
on
is
some
additional
in
some
internal
work.
That's
very
important
in
terms
of
the
health
of
all
of
our
own
assassins
platform,
on.com
and
so
we'll
be
focused
on
that
on
important
aid
for
run,
assassin
run
the
fleet,
I'm
going
to
pause
and
gina
I'll.
A
B
Great,
thank
you
I'll
start
sharing
again
all
right,
so
I'm
gonna
walk
through
a
couple
of
these,
but
there
is
quite
a
lot
that
we're
taking
on
for
both
back
end
front
end
and
then
also
for
ux
this
milestone.
B
So
to
start,
we
have
this
one
issue
about
creating
audit
events
in
relation
to
runners
and
this
one
specifically
that
we're
going
to
be
starting
with
is
adding
the
registration
token
audit
event.
B
This
is
specifically
on
the
front
end
that
we
have
a
lot
of
work
going
on
here,
but
we
also
have
back
end
work
to
support
this,
and
one
of
those
is
to
be
able
to
add
a
group
field
to
the
runner
so
that
you
could
then
identify
the
group
that
that
runner
is
associated
with.
So
you
know
when
you're
looking
at
a
runner,
you
can
easily
find
the
group
rather
than
having
to
go
through
multiple
areas,
which
is
kind
of
the
experience
that
that's
there
today,
there's
also
some
other
similar
work.
B
Finally,
we
have
some
additional
work
that
we're
doing
around
statuses
for
runners.
So
there's
some
inconsistencies
with
the
statuses
today
and
we're
trying
to
get
that
solved
so
that
we
can
show
a
better
breakdown
of
those
statuses
and
that
will
hopefully
help
at
one
glance
just
being
able
to
see
overall
how
many
runners
are
active
versus
how
many
are
offline
and
then
stale
as
well
and
so
and
so
so
on,
and
then
on
the
ux
side.
B
The
issue
that
I'm
going
to
be
working
on
in
14
8
is
adding
maintenance
notes
for
runners,
and
this
is
kind
of
the
way
that
we
could
allow
for
admins.
To
add
a
specific
note.
If
that
runner
was
to
come
into
a
problem,
and
you
needed
a
point
of
contact
for
it.
For
example,
you
could
add
just
in
like
a
normal
text
field,
some
notes
about
where
to
go,
to
do
that,
so
that
there's
a
direct
line
of
communication
there.
A
Hey
thank
you
that
stuff
looks
super
interesting
and
again
much
kudos
to
you
and
the
rest
of
the
team.
That's
working
on
the
fleet
for
all
of
the
great
work
you've
done
and
just
to
wrap
up
this
fortnite
giggle
video.
With
this
quick
look,
looking
back
and
a
quick
shout
out,
there's
a
you
know
massive
thanks
thanks.
A
I
should
say
to
the
runner
group
for
the
past
all
the
great
work
for
the
past
year,
there's
been
so
much
fabulous,
work
done
and
we
didn't
really
get
a
chance
to
just
pause
and
reflect
back
on
all
of
the
great
value
that
you've
added
to
our
users
community
for
the
past
year
and
to
just
super
psyche
in
terms
of
the
energy
as
we
get
into
this
fiscal
year.
For
this
group
there's
so
many
cool
things
planned.
A
The
team
has
just
got
back
from
the
holidays
and
it's
meeting
with
customers
and
and
trying
to
like,
develop
and
solve
really
interesting
problems
so
that,
at
the
end
of
the
day
we
develop
and
we
deliver
the
best
platform.
Gitlab
city
plan
from
there
is,
and
so
just
want
to
say.
Thank
you
to
the
runner
group,
if
you're
looking
at
this
video
and
I'm
looking
forward
to
an
awesome
fy23,
so
this
is
for
our
fortnite
video.
Thank
you.
Gina
for
doing
this
with
us
see
you
same
time
same
place.
Next
time
cheers.