[deploy and manage] Fix external links (#682)

In the migration tool, external URLs that contained `.html` were
incorrectly modified to use `.md`.

To (attempt) to fix these links:

1. I ran a script to find URLs that started with `http` (i.e. is not an
internal or cross-repo link) and included `.md` somewhere in the URL.
2. Then I ran all the resulting URLs through an external link-checker.
i. If I got a [`200` status
code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/200)
back, I didn't do anything to the link.
ii. If I got a [`404` status
code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404)
back, I swapped out the `.md` with `.html`.
3. I reran the link-checker to make sure all the updated links were now
returning `200`.

Author: colleenmcginnis

deploy-manage/deploy/cloud-enterprise/ece-software-prereq.md

@@ -25,7 +25,7 @@ We recommend using kernel 4.15.x or later on Ubuntu.
 To check your kernel version, run `uname -r`.
 
 ::::{note} 
-Elastic Cloud Enterprise is not supported on Linux distributions that use [cgroups](https://man7.org/linux/man-pages/man7/cgroups.7.md) version 2.
+Elastic Cloud Enterprise is not supported on Linux distributions that use [cgroups](https://man7.org/linux/man-pages/man7/cgroups.7.html) version 2.
 ::::
 
 

deploy-manage/deploy/cloud-on-k8s/advanced-elasticsearch-node-scheduling.md

@@ -22,7 +22,7 @@ You can combine these features to deploy a production-grade Elasticsearch cluste
 You can configure Elasticsearch nodes with [one or multiple roles](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/node-settings.md).
 
 ::::{tip}
-You can use [YAML anchors](https://yaml.org/spec/1.2/spec.md#id2765878) to declare the configuration change once and reuse it across all the node sets.
+You can use [YAML anchors](https://yaml.org/spec/1.2/spec.html#id2765878) to declare the configuration change once and reuse it across all the node sets.
 ::::
 
 

deploy-manage/deploy/cloud-on-k8s/create-custom-images.md

@@ -44,7 +44,7 @@ Providing the correct version is always required as ECK reasons about APIs and c
 ::::
 
 
-The steps are similar for [Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/tutorial-kubernetes-prepare-acr) and [AWS Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-basics.md#use-ecr).
+The steps are similar for [Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/tutorial-kubernetes-prepare-acr) and [AWS Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-basics.html#use-ecr).
 
 If your custom images follow the naming convention adopted by the official images, and you only want to use your custom images, you can also simply [override the container registry](air-gapped-install.md#k8s-container-registry-override).
 
@@ -53,6 +53,6 @@ For more information, check the following references:
 * [Elasticsearch documentation on Using custom Docker images](/deploy-manage/deploy/self-managed/install-elasticsearch-with-docker.md#_c_customized_image)
 * [Google Container Registry](https://cloud.google.com/container-registry/docs/how-to)
 * [Azure Container Registry](https://docs.microsoft.com/en-us/azure/container-registry/)
-* [Amazon Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.md)
-* [OpenShift Container Platform registry](https://docs.openshift.com/container-platform/4.12/registry/index.md)
+* [Amazon Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.html)
+* [OpenShift Container Platform registry](https://docs.openshift.com/container-platform/4.12/registry/index.html)
 

deploy-manage/deploy/cloud-on-k8s/deploy-eck-on-openshift.md

@@ -23,7 +23,7 @@ This section shows how to run ECK on OpenShift.
 1. To run the instructions on this page, you must be a `system:admin` user or a user with the privileges to create Projects, CRDs, and RBAC resources at the cluster level.
 2. Set virtual memory settings on the Kubernetes nodes.
 
-    Before deploying an Elasticsearch cluster with ECK, make sure that the Kubernetes nodes in your cluster have the correct `vm.max_map_count` sysctl setting applied. By default, Pods created by ECK are likely to run with the `restricted` [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.md) (SCC) which restricts privileged access required to change this setting in the underlying Kubernetes nodes.
+    Before deploying an Elasticsearch cluster with ECK, make sure that the Kubernetes nodes in your cluster have the correct `vm.max_map_count` sysctl setting applied. By default, Pods created by ECK are likely to run with the `restricted` [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.html) (SCC) which restricts privileged access required to change this setting in the underlying Kubernetes nodes.
 
     Alternatively, you can opt for setting `node.store.allow_mmap: false` at the [Elasticsearch node configuration](node-configuration.md) level. This has performance implications and is not recommended for production workloads.
 

deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-elasticsearch.md

@@ -11,7 +11,7 @@ mapped_pages:
 Use the following code to create an Elasticsearch cluster `elasticsearch-sample` and a "passthrough" route to access it:
 
 ::::{note} 
-A namespace other than the default namespaces (default, kube-system, kube-**, openshift-**, etc) is required such that default [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.md) (SCC) permissions are applied automatically. Elastic resources will not work properly in any of the default namespaces.
+A namespace other than the default namespaces (default, kube-system, kube-**, openshift-**, etc) is required such that default [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.html) (SCC) permissions are applied automatically. Elastic resources will not work properly in any of the default namespaces.
 ::::
 
 

deploy-manage/deploy/cloud-on-k8s/k8s-openshift-deploy-operator.md

@@ -25,7 +25,7 @@ This page shows the installation steps to deploy ECK in Openshift:
 
 3. Create a namespace to hold the Elastic resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash):
    ::::{note}
-   A namespace other than the default namespaces (default, kube-\*, openshift-\*, etc) is required such that default [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.md) (SCC) permissions are applied automatically. Elastic resources will not work properly in any of the default namespaces.
+   A namespace other than the default namespaces (default, kube-\*, openshift-\*, etc) is required such that default [Security Context Constraint](https://docs.openshift.com/container-platform/4.12/authentication/managing-security-context-constraints.html) (SCC) permissions are applied automatically. Elastic resources will not work properly in any of the default namespaces.
    ::::
 
    ```sh

deploy-manage/deploy/cloud-on-k8s/nodes-orchestration.md

@@ -21,7 +21,7 @@ This section covers the following topics:
 NodeSets are used to specify the topology of the Elasticsearch cluster. Each NodeSet represents a group of Elasticsearch nodes that share the same Elasticsearch configuration and Kubernetes Pod configuration.
 
 ::::{tip}
-You can use [YAML anchors](https://yaml.org/spec/1.2/spec.md#id2765878) to declare the configuration change once and reuse it across all the node sets.
+You can use [YAML anchors](https://yaml.org/spec/1.2/spec.html#id2765878) to declare the configuration change once and reuse it across all the node sets.
 ::::
 
 

deploy-manage/deploy/self-managed.md

@@ -5,4 +5,4 @@ mapped_pages:
 
 # Self-managed cluster [dependencies-versions]
 
-See [Elastic Stack Third-party Dependencices](https://artifacts.elastic.co/reports/dependencies/dependencies-current.md) for the complete list of dependencies for {{es}}.
+See [Elastic Stack Third-party Dependencices](https://artifacts.elastic.co/reports/dependencies/dependencies-current.html) for the complete list of dependencies for {{es}}.

deploy-manage/deploy/self-managed/executable-jna-tmpdir.md

@@ -33,7 +33,7 @@ To resolve these problems, either remove the `noexec` option from your `/tmp` fi
 If you need finer control over the location of these temporary files, you can also configure the path that JNA uses with the [JVM flag](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/jvm-settings.md#set-jvm-options) `-Djna.tmpdir=<path>` and you can configure the path that `libffi` uses for its temporary files by setting the `LIBFFI_TMPDIR` environment variable. Future versions of {{es}} may need additional configuration, so you should prefer to set `ES_TMPDIR` wherever possible.
 
 ::::{note} 
-{{es}} does not remove its temporary directory. You should remove leftover temporary directories while {{es}} is not running. It is best to do this automatically, for instance on each reboot. If you are running on Linux, you can achieve this by using the [tmpfs](https://www.kernel.org/doc/html/latest/filesystems/tmpfs.md) file system.
+{{es}} does not remove its temporary directory. You should remove leftover temporary directories while {{es}} is not running. It is best to do this automatically, for instance on each reboot. If you are running on Linux, you can achieve this by using the [tmpfs](https://www.kernel.org/doc/html/latest/filesystems/tmpfs.html) file system.
 ::::
 
 

deploy-manage/deploy/self-managed/important-settings-configuration.md

@@ -184,7 +184,7 @@ By default, {{es}} enables garbage collection (GC) logs. These are configured in
 
 You can reconfigure JVM logging using the command line options described in [JEP 158: Unified JVM Logging](https://openjdk.java.net/jeps/158). Unless you change the default `jvm.options` file directly, the {{es}} default configuration is applied in addition to your own settings. To disable the default configuration, first disable logging by supplying the `-Xlog:disable` option, then supply your own command line options. This disables *all* JVM logging, so be sure to review the available options and enable everything that you require.
 
-To see further options not contained in the original JEP, see [Enable Logging with the JVM Unified Logging Framework](https://docs.oracle.com/en/java/javase/13/docs/specs/man/java.md#enable-logging-with-the-jvm-unified-logging-framework).
+To see further options not contained in the original JEP, see [Enable Logging with the JVM Unified Logging Framework](https://docs.oracle.com/en/java/javase/13/docs/specs/man/java.html#enable-logging-with-the-jvm-unified-logging-framework).
 
 
 ### Examples [_examples]