►
From YouTube: GitLab 14.3 Kickoff - Verify:Runner
Description
Kickoff video for GitLab 14.3
GitLab Runner category direction: https://about.gitlab.com/direction/verify/runner/
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28044
A
A
This
is
where
we
talk
about
the
overall
vision,
forget
flat
runner,
and
we
also
talk
about
what's
next
for
the
major
pro
development
categories,
as
well
as
some
of
the
vision,
islands
for
the
major
product
development
categories
for
gitlab
runner
and,
to
recap
the
three
main
product
development
categories
for
gitlab
runner,
and
then
we
talk
about
or
run
a
call
run
a
cloud
and
run
an
enterprise
management
and
on
a
call,
is
of
course,
the
features
and
capabilities
related
to
the
github
runner
executable
ie,
the
the
build
agent
that
we
use
for
executing
your
ci
jobs.
A
All
the
capabilities
that
goes
into
that
very
important
piece
of
software
is
what
we
refer
to
as
runner
core
run.
A
cloud
is
our
support
for
hosted
runners
from
gitlab
science
and
that's
basically
supporting
our
get
that
build
cloud
offerings
for
linux
windows
and
mac
os,
which
is
coming
soon
and
then
running
enterprise
management.
A
That's
where
we
talk
about
features
and
capabilities
for
installing
configuring,
managing
and
monitoring
of
a
gitlab
runner,
fleet
or
gitlab
runner,
csd
built
infrastructure,
and
so
it's
related
to
all
of
those
management
capabilities,
as
well
as
the
ux,
the
ux
and
ui
experience
of
managing
runners
within
the
vietnam
ui.
So
that's
our
three
main
product
development
categories.
A
When
you
come
to
this
direction
page,
that's
how
we
have
sort
of
broken
out
the
the
product
development,
though
so
you
can
kind
of
understand
how
all
the
different
pieces
work
together
and
so
you'll
see
a
section
here
that
talks
about
the
top
vision
items
and
then
we
go
into
the
what's
next
and
why
categories
and
so
the
what's
next,
and
why
categories
is
generally
where
we
are
narrowing
the
aperture
and
looking
a
bit
more
closely
in
terms
of
what's
coming
up
in
the
near-term
releases
for
the
various
product
development
categories.
A
So,
finally,
for
today,
we'll
focus
very
narrowly
on
what
we're
working
on
for
the
upcoming
release,
miles
stone,
which
in
this
case
is
14.3
so
important
to
three,
and
actually
we
in
an
enhancing
our
investment
in
this
particular
theme
that
we've
started
over
the
past
few
release,
milestones,
which
is
around
scalability
reliability.
A
And
so,
if
you,
if
you've
noticed
and
you've
been
following
along
in
1403,
we've
moved
up
the
tech
debt
section
to
the
top
of
the
iteration
plan,
and
this
is
just
to
basically
signal
that
our
investment
and
focus
in
40.3
is
really
around
improving
reliability
and
scalability.
So
we're
devoting
a
lot
of
time
and
resources
to
key
features
and
capabilities.
A
In
support
of
that.
So
you
see
some
of
these.
These
issues
here
and
then
below
under
the
runa
cloud
category
you'll
also
notice
that
we
are
continuing
our
engineering
allocation,
our
30
engineering
allocation,
which
means
that
we
have
these
engineers
and
these
develop.
These
developers
focus
on
critical
issues,
supporting
improving
stability,
reliability
and
improving
our
optics,
slo
scores
for
crms
and
gitlab.com,
so
significant
investment
in
4.3,
a
wrong
scalability
and
around
reliability,
and
so
that
means
that
we
have
less
features
planned
for
the
core
category
in
terms
of
future
span
to
ship
and
fortnet3.
A
However,
we
do
have
some
important
features
and
capabilities
that
we're
working
on
getting
over
the
finish
line,
the
first
one
I
want
to
call
your
attention
to
for
runner
core
is
around
the
the
kubernetes
theme,
and
this
is
actually
a
very
important
feature.
It's
the
one
around
the
cubans
executive
today
doesn't
ignores.
Actually,
I
should
say,
ignores
docker
entry
point.
It's
actually
a
feature,
that's
been
well,
it's
been
asked
for
quite
a
bit
for
the
number
of
users
in
the
community,
and
so
in
fortnite
3.
A
A
Another
theme,
another
feature
story
around
kubernetes
that
we're
working
on
in
1493
is
finalizing
the
fix
for
this
situation,
where
all
running
fans
are
hanging
around
and
eventually
blocking
new
parts
from
standing
up.
You
may
recall
that
I
chatted
a
bit
about
this
in
1402
and
the
reason
being
that,
unfortunately
ii,
we
started
the
initial
work
on
getting
a
solution
in
this.
The
first
iteration,
if
you
will
for
getting
a
solution
in
place
to
finally
solving
this
problem.
A
So
in
fourth
and
the
three
we
hope
to
finish
up
the
second
piece
of
work
and
finally
close
off
this
issue,
so
that
to
resolve
this
issue
of
pods
not
being
properly
removed
and
therefore
causing
an
issue
with
condition
with
new
parts
being
starting
up
now.
One
issue
that
we
may
have
is
that
some
of
the
work
that's
ongoing
right
now
for
the
first
iteration
is
still
in
flight
as
of
today.
So,
depending
on,
where
things
line.
A
When
we
freeze
our
code
base
later
on
this
week,
we
may
have
to
continue
some
of
this
initial
iteration
work
as
we
get
in
the
first
part
of
fortnite
3.
So
we'll
see
how
things
go,
but
again,
our
goal
is
to
wrap
up
this
particular
feature
set
and
solve
this
particular
issue
of
the
running
parts
hanging
around
and
fourth
and
then
3.
so
for
running
coin,
fortnite,
3,
really
the
main
features
and
capabilities
we're
working
to
deliver
are
around
the
kubernetes
executive.
A
There's
one
other
feature
that
I
want
to
call
the
attention
to
which
is
around
creating
a
section
for
scriptline,
and
this
is
building
on
some
capabilities
that
we
added
last
year
and
it's
going
to
simplify
or
improve
the
way
that
the
actual
logging
files
are
displayed
in
the
get
time
ui.
So
this
is
one
additional
piece
of
capability:
I've
been
working
on
shipping
and
1403
in
the
core
and
the
core
on
the
codebase
and
finally
for
run
enterprise
management
and
ui.
We
don't
have
anything
apprenticeship
and
14.3.
A
So
that's
it
for
github
run
4.3
net
innovation
plan,
as
always,
if
there
are
critical
issues,
feature
sets
or
what
have
you
that
you
need
attention
that
you
have
a
question
on
or
you
would
like
an
additional
eyes
on
audience.
People
or
you
want
to
boost
that
signal,
feel
free,
always
to
add
me
on
on
the
issue
at
darren.
Eastman
I'll
definitely
take
a
look
until
next
time
for
fortinet
4.
This
is
darren.
Signing
off
talk
to
you
soon.