GitLab

Update [runners.machine] section in Autoscaling GitLab Runner on AWS EC2 documentation

See merge request gitlab-org/gitlab-runner!2480

Update vale rules

See merge request gitlab-org/gitlab-runner!2502

Bring over updated vale rules from main
project

Docs: Updated top-level page

See merge request gitlab-org/gitlab-runner!2496

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/225448

Fix definition of security related jobs

Closes #27122

See merge request gitlab-org/gitlab-runner!2499

The jobs added with https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/1897
and https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/2347
are causing a duplicate pipeline started for each branch push. It also
causes unwanted jobs to be started in context of the MR pipeline.

This commit will disable unwanted jobs and will add missing rules
definition to the fuzz testing one.

Change mention of custom cache containers to volumes

See merge request gitlab-org/gitlab-runner!2491

Use latest docs linting image

See merge request gitlab-org/gitlab-runner!2497

Update link to runner helper image in documentation

See merge request gitlab-org/gitlab-runner!2494

Add kubernetes runners allowPrivilegeEscalation security context configuration

Closes #26998

See merge request gitlab-org/gitlab-runner!2430

Run all containers with the `allowPrivilegeEscalation` flag enabled. When empty, it does not define the `allowPrivilegeEscalation` flag in the container `SecurityContext` and allows Kubernetes to use the default [privilege escalation](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#privilege-escalation) behavior.

Improve build logging testing

See merge request gitlab-org/gitlab-runner!2465

Clarify how service_account in toml is used

See merge request gitlab-org/gitlab-runner!2476

Provide a full list of metrics available for GitLab runners in the documentation

See merge request gitlab-org/gitlab-runner!2479

Fix TestBuildCancel from timing out

Closes #27077

See merge request gitlab-org/gitlab-runner!2468

In https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27077 we are
seeing timeouts of the `TestBuildCancel` test because when the job in
canceled we send `SIGTERM` to process that is running. After a certain
amount of time we send `SIGKILL` if that process hasn't terminated yet,
the default is [10
minutes](https://gitlab.com/gitlab-org/gitlab-runner/-/blob/56fbbb1150681915e4de33551a01cb3d4defa91c/helpers/process/killer.go#L17).
Since the default timeout of go tests is 10 minutes our test ends up
timeing out because `SIGKILL` hasn't been sent yet.

Have the GracefulKillTimeout and ForceKillTimeout configurable and set
it at a low amount for tests so we don't waste time waiting for a
process to terminate since the processes don't usually have any cleanup
to do.

closes https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27077

Introduce usage of Runner Manager terminology

See merge request gitlab-org/gitlab-runner!2474

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/250481

Teach artifact/cache commands about the archive interface

See merge request gitlab-org/gitlab-runner!2467

Update Kubernetes' documentation to include ephemeral storage requests/limits

Closes #27059

See merge request gitlab-org/gitlab-runner!2457

Implement archiver/extractor interface

See merge request gitlab-org/gitlab-runner!2195

This job is causing a few problems:
1. Preventing forks from running https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27021
1. Blocking releases because pipelines on tags fail https://gitlab.com/gitlab-org/gitlab/-/issues/263711