Merge branch 'docs-anchors2' into 'master'

Docs: Fix all Kubernetes and Runner related anchors

See merge request gitlab-org/gitlab-ce!25063

doc/install/kubernetes/gitlab_chart.md

@@ -5,7 +5,7 @@ This is the official way to install GitLab on a cloud native environment.
 NOTE: **Kubernetes experience required:**
 Our Helm charts are recommended for those who are familiar with Kubernetes.
 If you're not sure if Kubernetes is for you, our
-[Omnibus GitLab packages](../README.md#install-gitlab-using-the-omnibus-gitlab-package-recommended)
+[Omnibus GitLab packages](../README.md#installing-gitlab-using-the-omnibus-gitlab-package-recommended)
 are mature, scalable, support [high availability](../../administration/high_availability/README.md)
 and are used today on GitLab.com.
 It is not necessary to have GitLab installed on Kubernetes in order to use [GitLab Kubernetes integration](https://docs.gitlab.com/ee/user/project/clusters/index.html). 

doc/install/kubernetes/gitlab_omnibus.md

@@ -4,7 +4,7 @@ CAUTION: **Caution:**
 This chart is **deprecated**. We recommend using the [`gitlab` chart](gitlab_chart.md)
 instead. A comparison of the two charts is available in [this video](https://youtu.be/Z6jWR8Z8dv8).
 
-For more information on available GitLab Helm Charts, see the [charts overview](index.md#chart-overview).
+For more information on available GitLab Helm Charts, see [Installing GitLab on Kubernetes](index.md).
 
 - This GitLab-Omnibus chart has been tested on Google Kubernetes Engine and Azure Container Service.
 - This work is based partially on: <https://github.com/lwolf/kubernetes-gitlab/>. GitLab would like to thank Sergey Nuzhdin for his work.
@@ -39,7 +39,7 @@ The deployment includes:
 - _At least_ 4 GB of RAM available on your cluster. 41GB of storage and 2 CPU are also required.
 - Kubernetes 1.4+ with Beta APIs enabled
 - [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) provisioner support in the underlying infrastructure
-- A [wildcard DNS entry](#networking-prerequisites), which resolves to the external IP address
+- A [wildcard DNS entry](#networking-requirements), which resolves to the external IP address
 - The `kubectl` CLI installed locally and authenticated for the cluster
 - The [Helm client](https://github.com/kubernetes/helm/blob/master/docs/quickstart.md) installed locally on your machine
 
@@ -52,7 +52,7 @@ and [Mattermost](https://docs.gitlab.com/omnibus/gitlab-mattermost/).
 
 To support the GitLab services and dynamic environments, a wildcard DNS entry
 is required which resolves to the [load balancer](#load-balancer-ip) or
-[external IP](#external-ip). Configuration of the DNS entry will depend upon
+[external IP](#external-ip-recommended). Configuration of the DNS entry will depend upon
 the DNS service being used.
 
 #### External IP (recommended)
@@ -84,13 +84,13 @@ to configure the Wildcard DNS entry. For more information on creating a wildcard
 DNS entry, consult the documentation for the DNS server you are using.
 
 For production deployments of GitLab, we strongly recommend using a
-[external IP](#external-ip).
+[external IP](#external-ip-recommended).
 
 ## Configuring and Installing GitLab
 
 For most installations, two parameters are required:
 
-- `baseDomain`: the [base domain](#networking-prerequisites) of the wildcard host entry. For example, `mycompany.io` if the wild card entry is `*.mycompany.io`.
+- `baseDomain`: the [base domain](#networking-requirements) of the wildcard host entry. For example, `mycompany.io` if the wild card entry is `*.mycompany.io`.
 - `legoEmail`: Email address to use when requesting new SSL certificates from Let's Encrypt.
 
 Other common configuration options:
@@ -105,7 +105,7 @@ For additional configuration options, consult the
 
 ### Choosing a different GitLab release version
 
-The version of GitLab installed is based on the `gitlab` setting (see [section](#choosing-gitlab-edition) above), and
+The version of GitLab installed is based on the `gitlab` setting (see [section](#configuring-and-installing-gitLab) above), and
 the value of the corresponding helm setting: `gitlabCEImage` or `gitabEEImage`.
 
 ```yaml

doc/install/kubernetes/gitlab_runner_chart.md

@@ -11,7 +11,7 @@ This chart configures the Runner to:
 - For each new job it receives from [GitLab CI](https://about.gitlab.com/features/gitlab-ci-cd/), it will provision a
   new pod within the specified namespace to run it.
 
-For more information on available GitLab Helm Charts, please see our [overview](index.md#chart-overview).
+For more information on available GitLab Helm Charts, please see our [overview](index.md).
 
 ## Prerequisites
 
@@ -33,7 +33,7 @@ In order for GitLab Runner to function, your config file **must** specify the fo
 
  - `gitlabUrl`  - the GitLab Server URL (with protocol) to register the runner against
  - `runnerRegistrationToken` - The Registration Token for adding new Runners to the GitLab Server. This must be
-    retrieved from your GitLab Instance. See the [GitLab Runner Documentation](../../ci/runners/README.md#creating-and-registering-a-runner) for more information.
+    retrieved from your GitLab Instance. See the [GitLab Runner Documentation](../../ci/runners/README.md) for more information.
 
 Unless you need to specify additional configuration, you are [ready to install](#installing-gitlab-runner-using-the-helm-chart).
 
@@ -51,7 +51,7 @@ gitlabUrl: http://gitlab.your-domain.com/
 
 ## The Registration Token for adding new Runners to the GitLab Server. This must
 ## be retrieved from your GitLab Instance.
-## ref: https://docs.gitlab.com/ce/ci/runners/README.html#creating-and-registering-a-runner
+## ref: https://docs.gitlab.com/ee/ci/runners/README.html
 ##
 runnerRegistrationToken: ""
 
@@ -227,7 +227,7 @@ helm repo add gitlab https://charts.gitlab.io
 helm init
 ```
 
-Once you [have configured](#configuration) GitLab Runner in your `values.yml` file,
+Once you [have configured](#configuring-gitlab-runner-using-the-helm-chart) GitLab Runner in your `values.yml` file,
 run the following:
 
 ```bash
@@ -236,7 +236,7 @@ helm install --namespace <NAMESPACE> --name gitlab-runner -f <CONFIG_VALUES_FILE
 
 - `<NAMESPACE>` is the Kubernetes namespace where you want to install the GitLab Runner.
 - `<CONFIG_VALUES_FILE>` is the path to values file containing your custom configuration. See the
-  [Configuration](#configuration) section to create it.
+  [Configuring GitLab Runner using the Helm Chart](#configuring-gitlab-runner-using-the-helm-chart) section to create it.
 
 ## Updating GitLab Runner using the Helm Chart
 
@@ -247,11 +247,12 @@ helm upgrade --namespace <NAMESPACE> -f <CONFIG_VALUES_FILE> <RELEASE-NAME> gitl
 ```
 
 Where:
+
 - `<NAMESPACE>` is the Kubernetes namespace where GitLab Runner is installed
 - `<CONFIG_VALUES_FILE>` is the path to values file containing your custom configuration. See the
-  [Configuration](#configuration) section to create it.
+  [Configuring GitLab Runner using the Helm Chart](#configuring-gitlab-runner-using-the-helm-chart) section to create it.
 - `<RELEASE-NAME>` is the name you gave the chart when installing it.
-  In the [Install section](#installing) we called it `gitlab-runner`.
+  In the [Installing GitLab Runner using the Helm Chart](#installing-gitlab-runner-using-the-helm-chart) section, we called it `gitlab-runner`.
 
 ## Uninstalling GitLab Runner using the Helm Chart
 
@@ -265,4 +266,4 @@ where:
 
 - `<NAMESPACE>` is the Kubernetes namespace where GitLab Runner is installed
 - `<RELEASE-NAME>` is the name you gave the chart when installing it.
-  In the [Install section](#installing) we called it `gitlab-runner`.
+  In the [Installing GitLab Runner using the Helm Chart](#installing-gitlab-runner-using-the-helm-chart) section, we called it `gitlab-runner`.

doc/install/kubernetes/index.md

@@ -7,7 +7,7 @@ description: 'Read through the different methods to deploy GitLab on Kubernetes.
 NOTE: **Kubernetes experience required:**
 Our Helm charts are recommended for those who are familiar with Kubernetes.
 If you're not sure if Kubernetes is for you, our
-[Omnibus GitLab packages](../README.md#install-gitlab-using-the-omnibus-gitlab-package-recommended)
+[Omnibus GitLab packages](../README.md#installing-gitlab-using-the-omnibus-gitlab-package-recommended)
 are mature, scalable, support [high availability](../../administration/high_availability/README.md)
 and are used today on GitLab.com.
 It is not necessary to have GitLab installed on Kubernetes in order to use [GitLab Kubernetes integration](https://docs.gitlab.com/ee/user/project/clusters/index.html). 

doc/install/kubernetes/preparation/eks.md

@@ -26,7 +26,7 @@ With EKS, there are a few important details to keep in mind:
 
 The easiest way to solve this and still utilize dynamic provisioning is to utilize, or create, a Storage Class that is locked to a specific zone.
 
-> **Note**: Restricting volumes to specific zone will cause GitLab and any other application using this Storage Class to only reside in that zone. For multiple zone support, utilize [manually provisioned volumes](#manual-provisioning-of-volumes).
+> **Note**: Restricting volumes to specific zone will cause GitLab and any other application using this Storage Class to only reside in that zone. For multiple zone support, utilize [manually provisioned volumes](#manual-provisioning-of-volumes-recommended).
 
 To create the storage class, download and edit Amazon EKS's [sample Storage Class](https://docs.aws.amazon.com/eks/latest/userguide/storage-classes.html) and add the following parameter:
 

doc/install/kubernetes/preparation/networking.md

@@ -12,7 +12,7 @@ To support the GitLab services and dynamic environments, a wildcard DNS entry is
 
 To provision an external IP on GCP and Azure, simply request a new address from the Networking section. Ensure that the region matches the region your container cluster is created in. Note, it is important that the IP is not assigned at this point in time. It will be automatically assigned once the Helm chart is installed, to the Load Balancer.
 
-Set `global.hosts.externalIP` to this IP address when [deploying GitLab](../gitlab_chart.md#configuring-and-installing-gitlab).
+Set `global.hosts.externalIP` to this IP address when [deploying GitLab](../gitlab_chart.md#installing-gitlab-using-the-helm-chart).
 
 Then, create a [wildcard DNS record](#wildcard-dns-entry) which resolves to this IP address.
 
@@ -35,4 +35,4 @@ Please consult the documentation for your DNS service for more information on cr
 - [Google Domains](https://support.google.com/domains/answer/3290350?hl=en)
 - [GoDaddy](https://www.godaddy.com/help/add-an-a-record-19238)
 
-Set `global.hosts.domain` to this DNS name when [deploying GitLab](../gitlab_chart.md#configuring-and-installing-gitlab).
+Set `global.hosts.domain` to this DNS name when [deploying GitLab](../gitlab_chart.md#installing-gitlab-using-the-helm-chart).

doc/install/kubernetes/preparation/tools_installation.md

@@ -16,4 +16,4 @@ You can get Helm from the project's [releases page](https://github.com/kubernete
 
 # Next steps
 
-Once installed, proceed to the next [installation step](../gitlab_chart.md#prerequisites).
+Once installed, proceed to the next [installation step](../gitlab_chart.md#installing-gitlab-using-the-helm-chart).