Add latest changes from gitlab-org/gitlab@master

11 files changed, 19 insertions, 14 deletions

diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index 55f18987490..737b18fb6c2 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -738,5 +738,5 @@ instance.
 To share the cache between concurrent runners, you can either:
 
 - Use the `[runners.docker]` section of the runners' `config.toml` to configure a single mount point on the host that
-is mapped to `/cache` in each container, preventing the runner from creating unique volume names.
+  is mapped to `/cache` in each container, preventing the runner from creating unique volume names.
 - Use a distributed cache.
diff --git a/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md b/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
index b80bbbc5c98..82f92cdc938 100644
--- a/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
+++ b/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
@@ -276,7 +276,7 @@ include:
 To use DAST on the default branch:
 
 1. Set up a new [service](#create-an-ecs-service). This service will be used to deploy a temporary
-DAST environment.
+   DAST environment.
 1. Use the `CI_AWS_ECS_SERVICE` variable to set the name.
 1. Set the scope to the `dast-default` environment.
 1. Add the following to your `.gitlab-ci.yml` file:
diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md
index beaa2291eea..bc157c7ae08 100644
--- a/doc/ci/docker/using_docker_build.md
+++ b/doc/ci/docker/using_docker_build.md
@@ -853,7 +853,7 @@ This indicates the GitLab Runner does not have permission to start the
 
 1. Check that `privileged = true` is set in the `config.toml`.
 1. Make sure the CI job has the right Runner tags to use these
-privileged runners.
+   privileged runners.
 
 ### Error: `cgroups: cgroup mountpoint does not exist: unknown`
 
diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md
index 03c9a152d98..4a6e0118f3b 100644
--- a/doc/ci/environments/index.md
+++ b/doc/ci/environments/index.md
@@ -108,7 +108,7 @@ To create a static environment, in your `.gitlab-ci.yml` file:
 
 1. Define a job in the `deploy` stage.
 1. In the job, define the environment `name` and `url`. If an
-environment of that name doesn't exist when the pipeline runs, it is created.
+   environment of that name doesn't exist when the pipeline runs, it is created.
 
 NOTE:
 Some characters cannot be used in environment names. For more information about the
diff --git a/doc/ci/index.md b/doc/ci/index.md
index beb7fffeb8a..b74b2e1735b 100644
--- a/doc/ci/index.md
+++ b/doc/ci/index.md
@@ -39,7 +39,7 @@ In the `.gitlab-ci.yml` file, you can define:
 
 - [Create your first `.gitlab-ci.yml` file](quick_start/index.md).
 - [View all the possible keywords that you can use in the `.gitlab-ci.yml` file](yaml/index.md).
-the configuration.
+  the configuration.
 - Use the [pipeline editor](pipeline_editor/index.md) to edit or [visualize](pipeline_editor/index.md#visualize-ci-configuration)
   your CI/CD configuration.
 
diff --git a/doc/ci/review_apps/index.md b/doc/ci/review_apps/index.md
index 3ff25cc8bab..5854704521b 100644
--- a/doc/ci/review_apps/index.md
+++ b/doc/ci/review_apps/index.md
@@ -108,7 +108,7 @@ The following are example projects that demonstrate review app configuration:
 Other examples of review apps:
 
 - <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
-[Cloud Native Development with GitLab](https://www.youtube.com/watch?v=jfIyQEwrocw).
+  [Cloud Native Development with GitLab](https://www.youtube.com/watch?v=jfIyQEwrocw).
 - [Review apps for Android](https://about.gitlab.com/blog/2020/05/06/how-to-create-review-apps-for-android-with-gitlab-fastlane-and-appetize-dot-io/).
 
 ## Route Maps
diff --git a/doc/ci/runners/index.md b/doc/ci/runners/index.md
index 1df93ed8896..bfb30a36be2 100644
--- a/doc/ci/runners/index.md
+++ b/doc/ci/runners/index.md
@@ -33,7 +33,7 @@ When you use SaaS runners:
 - The VM is active only for the duration of the job and immediately deleted. This means that any changes that your job makes to the virtual machine will not be available to a subsequent job.
 - The virtual machine where your job runs has `sudo` access with no password.
 - The storage is shared by the operating system, the image with pre-installed software, and a copy of your cloned repository.
-This means that the available free disk space for your jobs to use is reduced.
+  This means that the available free disk space for your jobs to use is reduced.
 
 NOTE:
 Jobs handled by SaaS runners on GitLab.com **time out after 3 hours**, regardless of the timeout configured in a project.
diff --git a/doc/ci/runners/new_creation_workflow.md b/doc/ci/runners/new_creation_workflow.md
index c870a89a77a..12bffb79e33 100644
--- a/doc/ci/runners/new_creation_workflow.md
+++ b/doc/ci/runners/new_creation_workflow.md
@@ -39,7 +39,7 @@ The new runner registration workflow has the following benefits:
 
 - Preserved ownership records for runners, and minimized impact on users.
 - The addition of a unique system ID ensures that you can reuse the same authentication token across
-multiple runners. For more information, see [Reusing a GitLab Runner configuration](https://docs.gitlab.com/runner/fleet_scaling/#reusing-a-gitlab-runner-configuration).
+  multiple runners. For more information, see [Reusing a GitLab Runner configuration](https://docs.gitlab.com/runner/fleet_scaling/#reusing-a-gitlab-runner-configuration).
 
 ## Estimated time frame for planned changes
 
@@ -61,7 +61,7 @@ To avoid a broken workflow, you must:
 
 1. [Create a shared runner](runners_scope.md#create-a-shared-runner-with-a-runner-authentication-token) and obtain the authentication token.
 1. Replace the registration token in your runner registration workflow with the
-authentication token.
+   authentication token.
 
 ## Using registration tokens after GitLab 17.0
 
@@ -159,7 +159,9 @@ Several runner configuration options cannot be set during runner registration. T
 The following configuration options are no longer supported in [`values.yaml`](https://gitlab.com/gitlab-org/charts/gitlab-runner/-/blob/main/values.yaml):
 
 ```yaml
-## All these fields are DEPRECATED and the runner WILL FAIL TO START if you specify them
+## All these fields are DEPRECATED and the runner WILL FAIL TO START with GitLab Runner 18.0 and later if you specify them.
+## If a runner authentication token is specified in runnerRegistrationToken, the registration will succeed, however the
+## other values will be ignored.
 runnerRegistrationToken: ""
 locked: true
 tags: ""
diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md
index 48f6a22e9b3..d6a556ffd9b 100644
--- a/doc/ci/runners/runners_scope.md
+++ b/doc/ci/runners/runners_scope.md
@@ -576,13 +576,16 @@ A runner can have one of the following statuses.
 
 As an administrator, you can view runner statistics to learn about the performance of your runner fleet.
 
-- The **Median job queued time** value is calculated by sampling the queue duration of the
+The **Median job queued time** value is calculated by sampling the queue duration of the
 most recent 100 jobs that were run by Instance runners. Jobs from only the latest 5000
 runners are considered.
-- The median is a value that falls into the 50th percentile: half of the jobs
+
+The median is a value that falls into the 50th percentile: half of the jobs
 queued for longer than the median value, and half of the jobs queued for less than the
 median value.
 
+To view runner statistics:
+
 1. On the left sidebar, at the bottom, select **Admin Area**.
 1. Select **CI/CD > Runners**.
 1. Select **View metrics**.
diff --git a/doc/ci/variables/index.md b/doc/ci/variables/index.md
index f247d9609fe..86fc813b0cc 100644
--- a/doc/ci/variables/index.md
+++ b/doc/ci/variables/index.md
@@ -967,4 +967,4 @@ As a workaround you can either:
 
 - Use [File-type](#use-file-type-cicd-variables) CI/CD variables for large environment variables where possible.
 - If a single large variable is larger than `ARG_MAX`, try using [Secure Files](../secure_files/index.md), or
-bring the file to the job through some other mechanism.
+  bring the file to the job through some other mechanism.
diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md
index 93c38237993..2575c78461e 100644
--- a/doc/ci/yaml/index.md
+++ b/doc/ci/yaml/index.md
@@ -1634,7 +1634,7 @@ use the new cache, instead of rebuilding the dependencies.
 **Additional details**:
 
 - The cache `key` is a SHA computed from the most recent commits
-that changed each listed file.
+  that changed each listed file.
   If neither file is changed in any commits, the fallback key is `default`.
 
 ##### `cache:key:prefix`