public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-17 10:25:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change tab indentations to space indentations

Browse Source
This commit is contained in:
vickyhella
2022-09-13 17:23:20 +08:00
parent 76b33211be
commit efb87b2abd
65 changed files with 422 additions and 415 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/getting-started/introduction/overview.md
+2 -2
View File
@@ -32,8 +32,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
versioned_docs/version-2.5/getting-started/quick-start-guides/deploy-workloads/nodeports.md
+13 -13
View File
@@ -15,35 +15,35 @@ You're ready to create your first Kubernetes [workload](https://kubernetes.io/do
For this workload, you'll be deploying the application Rancher Hello-World.
1. From the **Clusters** page, open the cluster that you just created.
1. From the **Clusters** page, open the cluster that you just created.
2. From the main menu of the **Dashboard**, select **Projects/Namespaces**.
2. From the main menu of the **Dashboard**, select **Projects/Namespaces**.
3. Open the **Project: Default** project.
3. Open the **Project: Default** project.
4. Click **Resources > Workloads.**
4. Click **Resources > Workloads.**
5. Click **Deploy**.
5. Click **Deploy**.
**Step Result:** The **Deploy Workload** page opens.
**Step Result:** The **Deploy Workload** page opens.
6. Enter a **Name** for your workload.
6. Enter a **Name** for your workload.
7. From the **Docker Image** field, enter `rancher/hello-world`. This field is case-sensitive.
7. From the **Docker Image** field, enter `rancher/hello-world`. This field is case-sensitive.
8. From **Port Mapping**, click **Add Port**.
8. From **Port Mapping**, click **Add Port**.
9. From the **As a** drop-down, make sure that **NodePort (On every node)** is selected.
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.
versioned_docs/version-2.5/getting-started/quick-start-guides/deploy-workloads/workload-ingress.md
+1 -1
View File
@@ -25,7 +25,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.