Fix broken links

2026-09-28 05:59:03 +00:00 · 2019-12-06 16:07:52 -08:00
parent 65e52ec86b
commit ed2a18451e
8 changed files with 15 additions and 15 deletions
@@ -48,11 +48,11 @@ _Available as of v2.3.0_
 With this feature, you can upgrade to the latest version of Kubernetes as soon as it is released, without upgrading Rancher. This feature allows you to easily upgrade Kubernetes patch versions (i.e. `v1.15.X`), but not intended to upgrade Kubernetes minor versions (i.e. `v1.X.0`) as Kubernetes tends to deprecate or add APIs between minor versions. 
-The information that Rancher uses to provision [RKE clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/) is now located in the [Rancher Kubernetes Metadata]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rke-metadata/). For details on metadata configuration and how to change the Kubernetes version used for provisioning RKE clusters, see [Rancher Kubernetes Metadata]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rke-metadata/).
+The information that Rancher uses to provision [RKE clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/) is now located in the Rancher Kubernetes Metadata. For details on metadata configuration and how to change the Kubernetes version used for provisioning RKE clusters, see [Rancher Kubernetes Metadata]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rke-metadata/).
 Rancher Kubernetes Metadata contains Kubernetes version information which Rancher uses to provision [RKE clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/).
-For more information on how metadata works and how to configure metadata config, see [Rancher Kubernetes Metadata]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rke-metadata/).
+For more information on how metadata works and how to configure metadata config, see Rancher Kubernetes Metadata.
 ## Enabling Experimental Features
@@ -35,7 +35,7 @@ Before you can set up Google OAuth in Rancher, you need to log in to your G Suit
 **Result:** Rancher has been added as an authorized domain for the Admin SDK API.
 ### 2. Creating OAuth2 Credentials for the Rancher Server
-1. Go to the Google API console, select your project, and go to the [credentials page.]((https://console.developers.google.com/apis/credentials) )
+1. Go to the Google API console, select your project, and go to the [credentials page.](https://console.developers.google.com/apis/credentials)
 ![Credentials]({{<baseurl>}}/img/rancher/Google-Credentials-tab.png)  
 1. On the **Create Credentials** dropdown, select **OAuth client ID.** 
 1. Click **Web application.**
@@ -151,7 +151,7 @@ _Available as v2.2.0_
 When creating applications that span multiple Kubernetes clusters, a Global DNS entry can be created to route traffic to the endpoints in all of the different clusters. An external DNS server will need be programmed to assign a fully qualified domain name (a.k.a FQDN) to your application. Rancher will use the FQDN you provide and the IP addresses where your application is running to program the DNS. Rancher will gather endpoints from all the Kubernetes clusters running your application and program the DNS.
-For more information on how to use this feature, see [Global DNS]({{< baseurl >}}/rancher/v2.x/en/admin-settings/globaldns/).
+For more information on how to use this feature, see [Global DNS]({{< baseurl >}}/rancher/v2.x/en/catalog/globaldns/).
 ## Chart Compatibility with Rancher
@@ -9,7 +9,7 @@ A Rancher [administrator]({{<baseurl>}}/rancher/v2.x/en/admin-settings/rbac/glob
 1. From the **Global** view, navigate to the cluster where you want to enable Istio.
 1. Click **Tools > Istio.**
-1. Optional: Configure member access and [resource limits]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/istio/config/) for the Istio components. Ensure you have enough resources on your worker nodes to enable Istio.
+1. Optional: Configure member access and resource limits for the Istio components. Ensure you have enough resources on your worker nodes to enable Istio.
 1. Click **Enable**.
 1. Click **Save**.
@@ -88,7 +88,7 @@ The following table depicts the port requirements for [Rancher Launched Kubernet
 ### Port Requirements for Clusters Hosted by an Infrastructure Provider
-If you are launching a Kubernetes cluster on nodes that are in an infastructure provider such as Amazon EC2, Google Container Engine, DigitalOcean, Azure, or vSphere, [these port requirements]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/node-requirements/port-reqs-for-infrastructure-provider) apply.
+If you are launching a Kubernetes cluster on nodes that are in an infastructure provider such as Amazon EC2, Google Container Engine, DigitalOcean, Azure, or vSphere, these port requirements apply.
 These required ports are automatically opened by Rancher during creation of clusters using cloud providers.
@@ -32,7 +32,7 @@ For a full list of all the best practices that we recommend, refer to the [best
 For more information on what each role is used for, refer to the [section on roles for nodes in Kubernetes.]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/production/nodes-and-roles)
-For more information about the recommended number of nodes for each Kubernetes role, refer to the [section on recommended architecture.]({{<baseurl>}}/rancher/v2.x/en/cluster/provisioning/recommended-architecture)
+For more information about the recommended number of nodes for each Kubernetes role, refer to the [section on recommended architecture.]({{<baseurl>}}/rancher/v2.x/encluster-provisioning/recommended-architecture)
 ### Logging and Monitoring
@@ -146,7 +146,7 @@ The following tables break down the port requirements for inbound and outbound t
 | TCP | 2376 | Any node IP from a node created using Node driver | Docker daemon TLS port used by Docker Machine |
 | TCP | 6443 | Hosted/Imported Kubernetes API | Kubernetes API server |
-**Note** Rancher nodes may also require additional outbound access for any external [authentication provider]({{< baseurl >}}rancher/v2.x/en/admin-settings/authentication/) which is configured (LDAP for example).
+**Note** Rancher nodes may also require additional outbound access for any external [authentication provider]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication/) which is configured (LDAP for example).
 ### Additional Port Requirements for Nodes in High-Availability Rancher Installations
@@ -36,7 +36,7 @@ This Quick Start Guide is divided into different tasks for easier consumption.
  >**Note:**
  > When using a cloud-hosted virtual machine you need to allow inbound TCP communication to ports 80 and 443.  Please see your cloud-host's documentation for information regarding port configuration.
  >
-  > For a full list of port requirements, refer to [Single Node Installation]({{<baseurl>}}/rancher/v2.x/en/installation/node-requirements/).
+  > For a full list of port requirements, refer to [Single Node Installation]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/node-requirements/).
  Provision the host according to our [Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/requirements/).