Change tab indentations to space indentations

2026-05-23 05:15:16 +00:00 · 2022-09-13 17:23:20 +08:00
parent 76b33211be
commit efb87b2abd
65 changed files with 422 additions and 415 deletions
@@ -11,15 +11,15 @@ Configuring an Amazon NLB is a multistage process. We've broken it down into mul

 1. [Create Target Groups](#create-target-groups)

-	Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.
+    Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.

 2. [Register Targets](#register-targets)

-	Add your Linux nodes to the target groups.
+    Add your Linux nodes to the target groups.

 3. [Create Your NLB](#create-your-nlb)

-	Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
+    Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.

 > **Note:** Rancher only supports using the Amazon NLB when terminating traffic in `tcp` mode for port 443 rather than `tls` mode. This is due to the fact that the NLB does not inject the correct headers into requests when terminated at the NLB. This means that if you want to use certificates managed by the Amazon Certificate Manager (ACM), you should use an ELB or ALB.

@@ -134,28 +134,28 @@ Use Amazon's Wizard to create an Network Load Balancer. As part of this process,
 4. Choose **Network Load Balancer** and click **Create**.

 5. Complete the **Step 1: Configure Load Balancer** form.
-	- **Basic Configuration**
+    - **Basic Configuration**

-	   - Name: `rancher`
-	   - Scheme: `internal` or `internet-facing`
+       - Name: `rancher`
+       - Scheme: `internal` or `internet-facing`

-	     The Scheme that you choose for your NLB is dependent on the configuration of your instances/VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`.
-	- **Listeners**
+         The Scheme that you choose for your NLB is dependent on the configuration of your instances/VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`.
+    - **Listeners**

-		Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
-		- `TCP`: `443`
+        Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
+        - `TCP`: `443`

-	- **Availability Zones**
+    - **Availability Zones**

-	   - Select Your **VPC** and **Availability Zones**.
+       - Select Your **VPC** and **Availability Zones**.

 6. Complete the **Step 2: Configure Routing** form.

-	- From the **Target Group** drop-down, choose **Existing target group**.
+    - From the **Target Group** drop-down, choose **Existing target group**.

-	- From the **Name** drop-down, choose `rancher-tcp-443`.
+    - From the **Name** drop-down, choose `rancher-tcp-443`.

-	- Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.
+    - Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.

 7. Complete **Step 3: Register Targets**. Since you registered your targets earlier, all you have to do is click **Next: Review**.

@@ -19,15 +19,15 @@ Configuring an Amazon NLB is a multistage process. We've broken it down into mul

 1. [Create Target Groups](#create-target-groups)

-	Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.
+    Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.

 2. [Register Targets](#register-targets)

-	Add your Linux nodes to the target groups.
+    Add your Linux nodes to the target groups.

 3. [Create Your NLB](#create-your-nlb)

-	Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
+    Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.


 ## Create Target Groups
@@ -141,26 +141,26 @@ Use Amazon's Wizard to create an Network Load Balancer. As part of this process,
 4. Choose **Network Load Balancer** and click **Create**.

 5. Complete the **Step 1: Configure Load Balancer** form.
-	- **Basic Configuration**
+    - **Basic Configuration**

-	   - Name: `rancher`
-	   - Scheme: `internet-facing`
-	- **Listeners**
+       - Name: `rancher`
+       - Scheme: `internet-facing`
+    - **Listeners**

-		Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
-		- `TCP`: `443`
+        Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
+        - `TCP`: `443`

-	- **Availability Zones**
+    - **Availability Zones**

-	   - Select Your **VPC** and **Availability Zones**.
+       - Select Your **VPC** and **Availability Zones**.

 6. Complete the **Step 2: Configure Routing** form.

-	- From the **Target Group** drop-down, choose **Existing target group**.
+    - From the **Target Group** drop-down, choose **Existing target group**.

-	- From the **Name** drop-down, choose `rancher-tcp-443`.
+    - From the **Name** drop-down, choose `rancher-tcp-443`.

-	- Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.
+    - Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.

 7. Complete **Step 3: Register Targets**. Since you registered your targets earlier, all you have to do is click **Next: Review**.

@@ -19,15 +19,15 @@ Configuring an Amazon ALB is a multistage process. We've broken it down into mul

 1. [Create Target Group](#create-target-group)

-	Begin by creating one target group for the http protocol. You'll add your Linux nodes to this group.
+    Begin by creating one target group for the http protocol. You'll add your Linux nodes to this group.

 2. [Register Targets](#register-targets)

-	Add your Linux nodes to the target group.
+    Add your Linux nodes to the target group.

 3. [Create Your ALB](#create-your-alb)

-	Use Amazon's Wizard to create an Application Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
+    Use Amazon's Wizard to create an Application Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.


 ## Create Target Group
@@ -71,32 +71,32 @@ Use Amazon's Wizard to create an Application Load Balancer. As part of this proc
 4. Choose **Application Load Balancer**.

 5. Complete the **Step 1: Configure Load Balancer** form.
-	- **Basic Configuration**
+    - **Basic Configuration**

-	   - Name: `rancher-http`
-	   - Scheme: `internet-facing`
-	   - IP address type: `ipv4`
-	- **Listeners**
+       - Name: `rancher-http`
+       - Scheme: `internet-facing`
+       - IP address type: `ipv4`
+    - **Listeners**

-		Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
-		- `HTTP`: `80`
-		- `HTTPS`: `443`
+        Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
+        - `HTTP`: `80`
+        - `HTTPS`: `443`

-	- **Availability Zones**
+    - **Availability Zones**

-	   - Select Your **VPC** and **Availability Zones**.
+       - Select Your **VPC** and **Availability Zones**.

 6. Complete the **Step 2: Configure Security Settings** form.

-	Configure the certificate you want to use for SSL termination.
+    Configure the certificate you want to use for SSL termination.

 7. Complete the **Step 3: Configure Security Groups** form.

 8. Complete the **Step 4: Configure Routing** form.

-	- From the **Target Group** drop-down, choose **Existing target group**.
+    - From the **Target Group** drop-down, choose **Existing target group**.

-	- Add target group `rancher-http-80`.
+    - Add target group `rancher-http-80`.

 9. Complete **Step 5: Register Targets**. Since you registered your targets earlier, all you have to do it click **Next: Review**.

@@ -152,8 +152,8 @@ RKE uses a `.yml` config file to install and configure your Kubernetes cluster.

 1. Download one of following templates, depending on the SSL certificate you're using.

-	- [Template for self-signed certificate<br/>](../cluster-yml-templates/node-certificate.md)
-	- [Template for certificate signed by recognized CA<br/> ](../cluster-yml-templates/node-certificate-recognizedca.md)
+    - [Template for self-signed certificate<br/>](../cluster-yml-templates/node-certificate.md)
+    - [Template for certificate signed by recognized CA<br/> ](../cluster-yml-templates/node-certificate-recognizedca.md)



@@ -99,8 +99,8 @@ RKE uses a YAML config file to install and configure your Kubernetes cluster. Th

 1. Download one of following templates, depending on the SSL certificate you're using.

-	- [Template for self-signed certificate<br/> `3-node-externalssl-certificate.yml`](../cluster-yml-templates/node-externalssl-certificate.md)installation/options/cluster-yml-templates/3-node-externalssl-certificate)
-	- [Template for certificate signed by recognized CA<br/> `3-node-externalssl-recognizedca.yml`](../cluster-yml-templates/node-externalssl-recognizedca.md)
+    - [Template for self-signed certificate<br/> `3-node-externalssl-certificate.yml`](../cluster-yml-templates/node-externalssl-certificate.md)installation/options/cluster-yml-templates/3-node-externalssl-certificate)
+    - [Template for certificate signed by recognized CA<br/> `3-node-externalssl-recognizedca.yml`](../cluster-yml-templates/node-externalssl-recognizedca.md)



@@ -30,8 +30,8 @@ The Rancher API server is built on top of an embedded Kubernetes API server and

 ### Authorization and Role-Based Access Control

-  **User management:** The Rancher API server [manages user identities](../../pages-for-subheaders/about-authentication.md) that correspond to external authentication providers like Active Directory or GitHub, in addition to local users.
-	**Authorization:** The Rancher API server manages [access control](../../pages-for-subheaders/manage-role-based-access-control-rbac.md) and [security](../../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md) policies.
+- **User management:** The Rancher API server [manages user identities](../../pages-for-subheaders/about-authentication.md) that correspond to external authentication providers like Active Directory or GitHub, in addition to local users.
+- **Authorization:** The Rancher API server manages [access control](../../pages-for-subheaders/manage-role-based-access-control-rbac.md) and [security](../../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md) policies.

 ### Working with Kubernetes

@@ -23,7 +23,7 @@ For this workload, you'll be deploying the application Rancher Hello-World.

 5.  Click **Deploy**.

-	**Step Result:** The **Deploy Workload** page opens.
+    **Step Result:** The **Deploy Workload** page opens.

 6.  Enter a **Name** for your workload.

@@ -33,15 +33,15 @@ For this workload, you'll be deploying the application Rancher Hello-World.

 9.  From the **As a** drop-down, make sure that **NodePort (On every node)** is selected.

-	![As a dropdown, NodePort (On every node selected)](/img/nodeport-dropdown.png)
+    ![As a dropdown, NodePort (On every node selected)](/img/nodeport-dropdown.png)

 10.  From the **On Listening Port** field, leave the **Random** value in place.

-	![On Listening Port, Random selected](/img/listening-port-field.png)
+    ![On Listening Port, Random selected](/img/listening-port-field.png)

 11. From the **Publish the container port** field, enter port `80`.

-	![Publish the container port, 80 entered](/img/container-port-field.png)
+    ![Publish the container port, 80 entered](/img/container-port-field.png)

 12. Leave the remaining options on their default setting. We'll tell you about them later.

@@ -23,7 +23,7 @@ For this workload, you'll be deploying the application Rancher Hello-World.

 5.  Click **Deploy**.

-	**Step Result:** The **Deploy Workload** page opens.
+    **Step Result:** The **Deploy Workload** page opens.

 6.  Enter a **Name** for your workload.