mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-29 14:38:50 +00:00
fixing broken links
This commit is contained in:
Denise Schannon
@@ -38,6 +38,6 @@ For more information how to create and use PSPs, see [Pod Security Policies]({{<
|
|||||||
|
|
||||||
## Provisioning Drivers
|
## Provisioning Drivers
|
||||||
|
|
||||||
Drivers in Rancher allow you to manage which providers can be used to provision [hosted Kubernetes clusters]({{< baseurl >}}rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/) or [nodes in an infrastructure provider]({{< baseurl >}}rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/) to allow Rancher to deploy and manage Kubernetes.
|
Drivers in Rancher allow you to manage which providers can be used to provision [hosted Kubernetes clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/) or [nodes in an infrastructure provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/) to allow Rancher to deploy and manage Kubernetes.
|
||||||
|
|
||||||
For more information, see [Provisioning Drivers]({{< baseurl >}}/rancher/v2.x/en/admin-settings/drivers/).
|
For more information, see [Provisioning Drivers]({{< baseurl >}}/rancher/v2.x/en/admin-settings/drivers/).
|
||||||
|
|||||||
+1
-1
@@ -36,7 +36,7 @@ Rancher deploys an agent on each node to communicate with the node. This pages d
|
|||||||
|
|
||||||
### Dynamic IP address options
|
### Dynamic IP address options
|
||||||
|
|
||||||
For automation purposes, you can't have a specific IP address in a command as it has to be generic to be used for every node. For this, we have dynamic IP address options. They are used as a value to the existing [IP address options](#ip-address-options). This is supported for `--address` and `--internal-address`.
|
For automation purposes, you can't have a specific IP address in a command as it has to be generic to be used for every node. For this, we have dynamic IP address options. They are used as a value to the existing IP address options. This is supported for `--address` and `--internal-address`.
|
||||||
|
|
||||||
| Value | Example | Description |
|
| Value | Example | Description |
|
||||||
| ---------- | -------------------- | ----------- |
|
| ---------- | -------------------- | ----------- |
|
||||||
|
|||||||
+1
-1
@@ -1,5 +1,5 @@
|
|||||||
---
|
---
|
||||||
title: Creating an Alibaba ACK Cluster
|
title: Creating an Aliyun ACK Cluster
|
||||||
shortTitle: Alibaba Cloud Container Service for Kubernetes
|
shortTitle: Alibaba Cloud Container Service for Kubernetes
|
||||||
weight: 2120
|
weight: 2120
|
||||||
---
|
---
|
||||||
|
|||||||
+1
-1
@@ -24,7 +24,7 @@ Use Rancher to set up and configure your Kubernetes cluster.
|
|||||||
|
|
||||||
1. {{< step_create-cluster_member-roles >}}
|
1. {{< step_create-cluster_member-roles >}}
|
||||||
|
|
||||||
1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field using the information obtained in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key).
|
1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field using the information obtained in [2. Create Access Key and Secret Key](#prerequisites-in-amazon-web-services).
|
||||||
|
|
||||||
| Setting | Description |
|
| Setting | Description |
|
||||||
| ---------- | -------------------------------------------------------------------------------------------------------------------- |
|
| ---------- | -------------------------------------------------------------------------------------------------------------------- |
|
||||||
|
|||||||
@@ -34,7 +34,7 @@ Use {{< product >}} to create a Kubernetes cluster in Amazon EC2.
|
|||||||
|
|
||||||
1. Complete each of the following forms using information available from the [EC2 Management Console](https://aws.amazon.com/ec2).
|
1. Complete each of the following forms using information available from the [EC2 Management Console](https://aws.amazon.com/ec2).
|
||||||
|
|
||||||
- **Account Access** is where you configure the region of the nodes, and the credentials (Access Key and Secret Key) used to create the machine. See [Prerequisistes](#prerequisistes) how to create the Access Key and Secret Key and the needed permissions.
|
- **Account Access** is where you configure the region of the nodes, and the credentials (Access Key and Secret Key) used to create the machine. See [Prerequisistes](#prerequisites) how to create the Access Key and Secret Key and the needed permissions.
|
||||||
|
|
||||||
{{< step_create-cloud-credential >}}
|
{{< step_create-cloud-credential >}}
|
||||||
|
|
||||||
|
|||||||
@@ -121,7 +121,7 @@ See [Docker Root Directory](#docker-root-directory).
|
|||||||
|
|
||||||
#### enable_cluster_monitoring
|
#### enable_cluster_monitoring
|
||||||
|
|
||||||
Option to enable or disable [Cluster Monitoring]({{< baseurl >}}/rancher/v2.x/en/tools/monitoring/).
|
Option to enable or disable [Cluster Monitoring]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/).
|
||||||
|
|
||||||
#### enable_network_policy
|
#### enable_network_policy
|
||||||
|
|
||||||
|
|||||||
+4
-6
@@ -15,7 +15,7 @@ This guide walks you through create of a custom cluster that includes 3 nodes: a
|
|||||||
|
|
||||||
>**Notes:**
|
>**Notes:**
|
||||||
>
|
>
|
||||||
>- For a summary of Kubernetes features supported in Windows, see [Using Windows Server Containers in Kubernetes](https://kubernetes.io/docs/getting-started-guides/windows/#supported-features).
|
>- For a summary of Kubernetes features supported in Windows, see [Using Windows in Kubernetes](https://kubernetes.io/docs/setup/windows/intro-windows-in-kubernetes/).
|
||||||
>- Windows containers must run on Windows Server 1803 nodes. Windows Server 1709 and earlier versions do not support Kubernetes properly.
|
>- Windows containers must run on Windows Server 1803 nodes. Windows Server 1709 and earlier versions do not support Kubernetes properly.
|
||||||
>- Containers built for Windows Server 1709 or earlier do not run on Windows Server 1803. You must build containers on Windows Server 1803 to run these containers on Windows Server 1803.
|
>- Containers built for Windows Server 1709 or earlier do not run on Windows Server 1803. You must build containers on Windows Server 1803 to run these containers on Windows Server 1803.
|
||||||
|
|
||||||
@@ -28,12 +28,11 @@ When setting up a custom cluster with support for Windows nodes and containers,
|
|||||||
<!-- TOC -->
|
<!-- TOC -->
|
||||||
|
|
||||||
- [1. Provision Hosts](#1-provision-hosts)
|
- [1. Provision Hosts](#1-provision-hosts)
|
||||||
- [2. Cloud-host VM Networking Configuration](#2-cloud-host-vm-networking-configuration)
|
- [2. Cloud-host VM Networking Configuration](#2-cloud-hosted-vm-networking-configuration)
|
||||||
- [3. Create the Custom Cluster](#3-create-the-custom-cluster)
|
- [3. Create the Custom Cluster](#3-create-the-custom-cluster)
|
||||||
- [4. Add Linux Host for Ingress Support](#4-add-linux-host-for-ingress-support)
|
- [4. Add Linux Host for Ingress Support](#4-add-linux-host-for-ingress-support)
|
||||||
- [5. Adding Windows Workers](#5-adding-windows-workers)
|
- [5. Adding Windows Workers](#5-adding-windows-workers)
|
||||||
- [6. Cloud-host VM Routes Configuration](#6-cloud-host-vm-routes-configuration)
|
- [6. Cloud-host VM Routes Configuration](#6-cloud-hosted-vm-routes-configuration)
|
||||||
- [Troubleshooting](#troubleshooting)
|
|
||||||
|
|
||||||
<!-- /TOC -->
|
<!-- /TOC -->
|
||||||
|
|
||||||
@@ -157,7 +156,7 @@ You can add Windows hosts to a custom cluster by editing the cluster and choosin
|
|||||||
|
|
||||||
In Windows clusters, containers communicate with each other using the `host-gw` mode of Flannel. In `host-gw` mode, all containers on the same node belong to a private subnet, and traffic routes from a subnet on one node to a subnet on another node through the host network.
|
In Windows clusters, containers communicate with each other using the `host-gw` mode of Flannel. In `host-gw` mode, all containers on the same node belong to a private subnet, and traffic routes from a subnet on one node to a subnet on another node through the host network.
|
||||||
|
|
||||||
- When worker nodes are provisioned on AWS, virtualization clusters, or bare metal servers, make sure they belong to the same layer 2 subnet. If the nodes don't belong to the same layer 2 subnet, `host-gw` networking will not work. Please contact [Rancher support](https://rancher.com/support/) if your worker nodes on AWS, virtualization clusters, or bare metal servers don't belong to the same layer 2 network.
|
- When worker nodes are provisioned on AWS, virtualization clusters, or bare metal servers, make sure they belong to the same layer 2 subnet. If the nodes don't belong to the same layer 2 subnet, `host-gw` networking will not work.
|
||||||
|
|
||||||
- When worker nodes are provisioned on GCE or Azure, they are not on the same layer 2 subnet. Nodes on GCE and Azure belong to a routable layer 3 network. Follow the instructions below to configure GCE and Azure so that the cloud network knows how to route the host subnets on each node.
|
- When worker nodes are provisioned on GCE or Azure, they are not on the same layer 2 subnet. Nodes on GCE and Azure belong to a routable layer 3 network. Follow the instructions below to configure GCE and Azure so that the cloud network knows how to route the host subnets on each node.
|
||||||
|
|
||||||
@@ -176,4 +175,3 @@ Azure VM | For Azure, create a routing table: [Custom Routes: User-defined](http
|
|||||||
|
|
||||||
|
|
||||||
` `
|
` `
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user