From e12eb296b262c374b61a242d468a6e751ee7816a Mon Sep 17 00:00:00 2001 From: Olly P Date: Wed, 31 Jul 2019 18:36:20 +0100 Subject: [PATCH] Fix deadlinks (#9181) --- .../configure/use-your-own-tls-certificates.md | 18 +++++++++++++++--- ee/supported-platforms.md | 5 +++-- ee/ucp/admin/install/index.md | 2 +- ee/ucp/user-access/kubectl.md | 2 +- 4 files changed, 20 insertions(+), 7 deletions(-) diff --git a/ee/dtr/admin/configure/use-your-own-tls-certificates.md b/ee/dtr/admin/configure/use-your-own-tls-certificates.md index e6478d5021..4bff6b11a7 100644 --- a/ee/dtr/admin/configure/use-your-own-tls-certificates.md +++ b/ee/dtr/admin/configure/use-your-own-tls-certificates.md @@ -4,10 +4,22 @@ description: Learn how to configure Docker Trusted Registry with your own TLS ce keywords: dtr, tls, certificates, security --- -Docker Trusted Registry (DTR) services are exposed using HTTPS by default. This ensures encrypted communications between clients and your trusted registry. If you do not pass a PEM-encoded TLS certificate during installation, DTR will generate a [self-signed certificate](https://en.wikipedia.org/wiki/Self-signed_certificate). This leads to an insecure site warning when accessing DTR through a browser. Additionally, DTR includes an [HSTS (HTTP Strict-Transport-Security) header](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security) in all API responses which can further lead to your browser refusing to load DTR's web interface. +Docker Trusted Registry (DTR) services are exposed using HTTPS by default. This +ensures encrypted communications between clients and your trusted registry. If +you do not pass a PEM-encoded TLS certificate during installation, DTR will +generate a [self-signed +certificate](https://en.wikipedia.org/wiki/Self-signed_certificate). This leads +to an insecure site warning when accessing DTR through a browser. Additionally, +DTR includes an [HSTS (HTTP Strict-Transport-Security) +header](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security) in all +API responses which can further lead to your browser refusing to load DTR's web +interface. -You can configure DTR to use your own TLS certificates, so that it is automatically -trusted by your users' browser and client tools. As of v2.7, you can also [enable user authentication via client certificates](/ee/enable-authentication-via-client-certs/) provided by your organization's public key infrastructure (PKI). +You can configure DTR to use your own TLS certificates, so that it is +automatically trusted by your users' browser and client tools. As of v2.7, you +can also [enable user authentication via client +certificates](/ee/enable-client-certificate-authentication/) provided by your +organization's public key infrastructure (PKI). ## Replace the server certificates diff --git a/ee/supported-platforms.md b/ee/supported-platforms.md index 426064f085..20368c18da 100644 --- a/ee/supported-platforms.md +++ b/ee/supported-platforms.md @@ -104,5 +104,6 @@ details on EOL of minor and major versions of Docker Enterprise. ## Where to go next -- [Install Docker](/engine/installation/index.md) -- [Get Started with Docker](/get-started/index.md) +- [Install Docker Engine - Enterprise for RHEL](/install/linux/docker-ee/rhel/) +- [Install Docker Engine - Enterprise for Ubuntu](/install/linux/docker-ee/ubuntu/) +- [Install Docker Engine - Enterprise for Windows Server](/install/windows/docker-ee/) diff --git a/ee/ucp/admin/install/index.md b/ee/ucp/admin/install/index.md index a215c86ee8..76a0d94540 100644 --- a/ee/ucp/admin/install/index.md +++ b/ee/ucp/admin/install/index.md @@ -81,7 +81,7 @@ To install UCP: This runs the install command in interactive mode, so that you're prompted for any necessary configuration values. To find what other options are available in the install command, check the - [reference documentation](/reference/ucp/3.1/cli/install.md). + [reference documentation](/reference/ucp/3.2/cli/install.md). > Custom Container Networking Interface (CNI) plugins > diff --git a/ee/ucp/user-access/kubectl.md b/ee/ucp/user-access/kubectl.md index c2ff249d3d..a94173b91d 100644 --- a/ee/ucp/user-access/kubectl.md +++ b/ee/ucp/user-access/kubectl.md @@ -29,7 +29,7 @@ To use kubectl, install the binary on a workstation which has access to your UCP {: .important} First, find which version of Kubernetes is running in your cluster. This can be found -within the Universal Control Plane dashboard or at the UCP API endpoint [version](/reference/ucp/3.1/api/). +within the Universal Control Plane dashboard or at the UCP API endpoint [version](/reference/ucp/3.2/api/). From the UCP dashboard, click on **About Docker EE** within the **Admin** menu in the top left corner of the dashboard. Then navigate to **Kubernetes**.