public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-30 15:04:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #687 from vickyhella/vk-bilingual

Browse Source 
Update ZH docs and fix broken links
This commit is contained in:
Billy Tat
2023-06-19 11:02:23 -07:00
committed by GitHub
parent ab5a86161b b6149deeac
commit 8cd8ed012b
279 changed files with 1057 additions and 501 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.6/how-to-guides/advanced-user-guides/cis-scan-guides/configure-alerts-for-periodic-scan-on-a-schedule.md
+1 -1
View File
@@ -23,7 +23,7 @@ While configuring the routes for `rancher-cis-benchmark` alerts, you can specify
To configure alerts for a scan that runs on a schedule,
1. Please enable alerts on the `rancher-cis-benchmark` application (#enabling-alerting-for-rancher-cis-benchmark)
1. Please enable alerts on the `rancher-cis-benchmark` application. For more information, see [this page](../../../how-to-guides/advanced-user-guides/cis-scan-guides/enable-alerting-for-rancher-cis-benchmark.md).
1. In the upper left corner, click **☰ > Cluster Management**.
1. On the **Clusters** page, go to the cluster where you want to run a CIS scan and click **Explore**.
1. Click **CIS Benchmark > Scan**.
versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/k3s-for-rancher.md
+1 -1
View File
@@ -35,7 +35,7 @@ When running the command to start the K3s Kubernetes API server, you will pass i
```
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=<VERSION> sh -s - server \
--datastore-endpoint="<DATASTORE_ENDPOINT>"
```
```
Where `<DATASTORE_ENDPOINT>` is the connection URI for your datastore. For example, `mysql://username:password@tcp(hostname:3306)/database-name` if you're using MySQL. Valid datastores include etcd, MySQL, PostgreSQL, or SQLite (default).
versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+3 -3
View File
@@ -119,9 +119,9 @@ resource "rancher2_cluster" "my-eks-to-import" {
The control that Rancher has to manage a registered cluster depends on the type of cluster.
- [Features for All Registered Clusters](#2-5-8-features-for-all-registered-clusters)
- [Additional Features for Registered K3s Clusters](#2-5-8-additional-features-for-registered-k3s-clusters)
- [Additional Features for Registered EKS and GKE Clusters](#additional-features-for-registered-eks-and-gke-clusters)
- [Features for All Registered Clusters](#features-for-all-registered-clusters)
- [Additional Features for Registered K3s Clusters](#additional-features-for-registered-k3s-clusters)
- [Additional Features for Registered EKS, AKS, and GKE Clusters](#additional-features-for-registered-eks-aks-and-gke-clusters)
### Features for All Registered Clusters
versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md
-1
View File
@@ -13,7 +13,6 @@ Because of this change to the controller, the default behavior no longer sets `h
- [Specify a hostname to use](#specify-a-hostname-to-use)
- [Use as the default backend](#use-as-the-default-backend)
- [Certificates](#certificates)
- [Labels and Annotations](#labels-and-annotations)