Automatic merge of gitlab-org/gitlab-ce master

doc/administration/gitaly/index.md

@@ -36,13 +36,18 @@ installations will be better served with the default configuration
 used by Omnibus and the GitLab source installation guide.
 
 Starting with GitLab 11.4, Gitaly is able to serve all Git requests without
-needed a shared NFS mount for Git repository data.
+requiring a shared NFS mount for Git repository data.
 Between 11.4 and 11.8 the exception was the
 [Elasticsearch indexer](https://gitlab.com/gitlab-org/gitlab-elasticsearch-indexer).
 But since 11.8 the indexer uses Gitaly for data access as well. NFS can still
 be leveraged for redudancy on block level of the Git data. But only has to
 be mounted on the Gitaly server.
 
+Starting with GitLab 11.8, it is possible to use ElasticSearch in conjunction with
+a Gitaly setup that isn't utilising NFS. In order to use ElasticSearch in this
+scenario, the [new repository indexer](../../integration/elasticsearch.md#elasticsearch-repository-indexer-beta)
+needs to be enabled in your GitLab configuration.
+
 NOTE: **Note:** While Gitaly can be used as a replacement for NFS, it's not recommended
 to use EFS as it may impact GitLab's performance. Review the [relevant documentation](../high_availability/nfs.md#avoid-using-awss-elastic-file-system-efs)
 for more details.

doc/administration/troubleshooting/elasticsearch.md

@@ -5,7 +5,7 @@ Troubleshooting ElasticSearch requires:
 - Knowledge of common terms.
 - Establishing within which category the problem fits.
 
-## Common Terminology
+## Common terminology
 
 - **Lucene**: A full-text search library written in Java.
 - **Near Realtime (NRT)**: Refers to the slight latency from the time to index a
@@ -138,7 +138,7 @@ graph TD;
   F7(Escalate to<br>GitLab support.)
 ```
 
-## Troubleshooting Walkthrough
+## Troubleshooting walkthrough
 
 Most ElasticSearch troubleshooting can be broken down into 4 categories:
 
@@ -317,7 +317,7 @@ dig further into these.
 Feel free to reach out to GitLab support, but this is likely to be something a skilled
 ElasticSearch admin has more experience with.
 
-## Common Issues
+## Common issues
 
 All common issues [should be documented](../../integration/elasticsearch.md#troubleshooting). If not,
 feel free to update that page with issues you encounter and solutions.

doc/user/clusters/applications.md

 # GitLab Managed Apps
 
 GitLab provides **GitLab Managed Apps**, a one-click install for various applications which can
-be added directly to your configured cluster. These applications are
-needed for [Review Apps](../../ci/review_apps/index.md) and
-[deployments](../../ci/environments.md) when using [Auto DevOps](../../topics/autodevops/index.md).
+be added directly to your configured cluster.
+
+These applications are needed for [Review Apps](../../ci/review_apps/index.md)
+and [deployments](../../ci/environments.md) when using [Auto DevOps](../../topics/autodevops/index.md).
+
 You can install them after you
-[create a cluster](../project/clusters/index.md#add-new-gke-cluster).
+[create a cluster](../project/clusters/index.md#adding-and-removing-clusters).
 
 ## Installing applications
 
@@ -20,8 +22,10 @@ This namespace:
 To see a list of available applications to install:
 
 1. For a:
-   - Project-level cluster, navigate to your project's **Operations > Kubernetes**.
-   - Group-level cluster, navigate to your group's **Kubernetes** page.
+   - [Project-level cluster](../project/clusters/index.md),
+     navigate to your project's **Operations > Kubernetes**.
+   - [Group-level cluster](../group/clusters/index.md),
+     navigate to your group's **Kubernetes** page.
 
 Install Helm first as it's used to install other applications.
 
@@ -160,9 +164,9 @@ file.
 When installing JupyterHub onto your Kubernetes cluster, [JupyterLab's Git extension](https://github.com/jupyterlab/jupyterlab-git)
 is automatically provisioned and configured using the authenticated user's:
 
-- Name
-- Email
-- Newly created access token
+- Name.
+- Email.
+- Newly created access token.
 
 JupyterLab's Git extension enables full version control of your notebooks as well as issuance of Git commands within Jupyter.
 Git commands can be issued via the **Git** tab on the left panel or via Jupyter's command line prompt.
@@ -233,8 +237,10 @@ The applications below can be upgraded.
 To upgrade an application:
 
 1. For a:
-   - Project-level cluster, navigate to your project's **Operations > Kubernetes**.
-   - Group-level cluster, navigate to your group's **Kubernetes** page.
+   - [Project-level cluster](../project/clusters/index.md),
+     navigate to your project's **Operations > Kubernetes**.
+   - [Group-level cluster](../group/clusters/index.md),
+     navigate to your group's **Kubernetes** page.
 1. Select your cluster.
 1. If an upgrade is available, the **Upgrade** button is displayed. Click the button to upgrade.
 
@@ -263,8 +269,10 @@ The applications below can be uninstalled.
 To uninstall an application:
 
 1. For a:
-   - Project-level cluster, navigate to your project's **Operations > Kubernetes**.
-   - Group-level cluster, navigate to your group's **Kubernetes** page.
+   - [Project-level cluster](../project/clusters/index.md),
+     navigate to your project's **Operations > Kubernetes**.
+   - [Group-level cluster](../group/clusters/index.md),
+     navigate to your group's **Kubernetes** page.
 1. Select your cluster.
 1. Click the **Uninstall** button for the application.