mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-13 00:23:23 +00:00
move aliases to nginx
This commit is contained in:
@@ -6,7 +6,6 @@ aliases:
|
||||
- /rancher/v2.x/en/tasks/global-configuration/
|
||||
- /rancher/v2.x/en/concepts/global-configuration/server-url/
|
||||
- /rancher/v2.x/en/tasks/global-configuration/server-url/
|
||||
- /rancher/v2.x/en/admin-settings/server-url/
|
||||
- /rancher/v2.x/en/admin-settings/log-in/
|
||||
---
|
||||
|
||||
|
||||
@@ -3,7 +3,6 @@ title: Creating Backups for Rancher Installed with Docker
|
||||
weight: 25
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/
|
||||
- /rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/
|
||||
---
|
||||
|
||||
After completing your Docker installation of Rancher, we recommend creating backups of it on a regular basis. Having a recent backup will let you recover quickly from an unexpected disaster.
|
||||
|
||||
@@ -4,8 +4,6 @@ description: The Rancher CLI is a unified tool that you can use to interact with
|
||||
metaTitle: "Using the Rancher Command Line Interface "
|
||||
metaDescription: "The Rancher CLI is a unified tool that you can use to interact with Rancher. With it, you can operate Rancher using a command line interface rather than the GUI"
|
||||
weight: 6000
|
||||
aliases:
|
||||
- /rancher/v2.x/en/concepts/cli-configuration/
|
||||
---
|
||||
|
||||
The Rancher CLI (Command Line Interface) is a unified tool that you can use to interact with Rancher. With this tool, you can operate Rancher using a command line rather than the GUI.
|
||||
|
||||
@@ -2,9 +2,6 @@
|
||||
title: Removing Kubernetes Components from Nodes
|
||||
description: Learn about cluster cleanup when removing nodes from your Rancher-launched Kubernetes cluster. What is removed, how to do it manually
|
||||
weight: 2055
|
||||
aliases:
|
||||
- /rancher/v2.x/en/faq/cleaning-cluster-nodes/
|
||||
- /rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/
|
||||
---
|
||||
|
||||
This section describes how to disconnect a node from a Rancher-launched Kubernetes cluster and remove all of the Kubernetes components from the node. This process allows you to use the node for other purposes.
|
||||
|
||||
@@ -3,7 +3,6 @@ title: Adding Users to Clusters
|
||||
weight: 2020
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/adding-managing-cluster-members/
|
||||
- /rancher/v2.x/en/cluster-provisioning/cluster-members/
|
||||
- /rancher/v2.x/en/k8s-in-rancher/cluster-members/
|
||||
- /rancher/v2.x/en/cluster-admin/cluster-members
|
||||
---
|
||||
|
||||
@@ -3,7 +3,6 @@ title: "Access a Cluster with Kubectl and kubeconfig"
|
||||
description: "Learn how you can access and manage your Kubernetes clusters using kubectl with kubectl Shell or with kubectl CLI and kubeconfig file. A kubeconfig file is used to configure access to Kubernetes. When you create a cluster with Rancher, it automatically creates a kubeconfig for your cluster."
|
||||
weight: 2010
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/
|
||||
- /rancher/v2.x/en/k8s-in-rancher/kubectl/
|
||||
- /rancher/v2.x/en/cluster-admin/kubectl
|
||||
- /rancher/v2.x/en/concepts/clusters/kubeconfig-files/
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Cluster Configuration
|
||||
weight: 2025
|
||||
aliases:
|
||||
- /rancher/v2.x/en/k8s-in-rancher/editing-clusters/
|
||||
---
|
||||
|
||||
After you provision a Kubernetes cluster using Rancher, you can still edit options and settings for the cluster. To edit your cluster, open the **Global** view, make sure the **Clusters** tab is selected, and then select **Ellipsis (...) > Edit** for the cluster that you want to edit.
|
||||
|
||||
@@ -6,7 +6,6 @@ aliases:
|
||||
- /rancher/v2.x/en/concepts/projects/
|
||||
- /rancher/v2.x/en/tasks/projects/
|
||||
- /rancher/v2.x/en/tasks/projects/create-project/
|
||||
- /rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/
|
||||
- /rancher/v2.x/en/tasks/projects/create-project/
|
||||
---
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Tools for Logging, Monitoring, and Visibility
|
||||
weight: 2033
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tools/
|
||||
- /rancher/v2.x/en/tools/notifiers-and-alerts/
|
||||
---
|
||||
|
||||
@@ -47,4 +46,4 @@ Using Rancher, you can monitor the state and processes of your cluster nodes, Ku
|
||||
|
||||
## Istio
|
||||
|
||||
[Istio](https://istio.io/) is an open-source tool that makes it easier for DevOps teams to observe, control, troubleshoot, and secure the traffic within a complex network of microservices. For details on how to enable Istio in Rancher, refer to the [Istio section.]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/istio)
|
||||
[Istio](https://istio.io/) is an open-source tool that makes it easier for DevOps teams to observe, control, troubleshoot, and secure the traffic within a complex network of microservices. For details on how to enable Istio in Rancher, refer to the [Istio section.]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/istio)
|
||||
|
||||
@@ -5,7 +5,6 @@ metaDescription: "Rancher integrates with popular logging services. Learn the re
|
||||
weight: 3
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/logging/
|
||||
- /rancher/v2.x/en/tools/logging/
|
||||
---
|
||||
|
||||
Logging is helpful because it allows you to:
|
||||
|
||||
@@ -3,9 +3,7 @@ title: "Kubernetes Persistent Storage: Volumes and Storage Classes"
|
||||
description: "Learn about the two ways with which you can create persistent storage in Kubernetes: persistent volumes and storage classes"
|
||||
weight: 2031
|
||||
aliases:
|
||||
- /rancher/v2.x/en/concepts/volumes-and-storage/
|
||||
- /rancher/v2.x/en/tasks/clusters/adding-storage/
|
||||
- /rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/
|
||||
- /rancher/v2.x/en/cluster-admin/volumes-and-storage/persistent-volume-claims/
|
||||
---
|
||||
When deploying an application that needs to retain data, you'll need to create persistent storage. Persistent storage allows you to store application data external from the pod running your application. This storage practice allows you to maintain application data, even if the application's pod fails.
|
||||
@@ -57,4 +55,4 @@ In [Rancher Launched Kubernetes clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-
|
||||
|
||||
### Related Links
|
||||
|
||||
- [Kubernetes Documentation: Storage](https://kubernetes.io/docs/concepts/storage/)
|
||||
- [Kubernetes Documentation: Storage](https://kubernetes.io/docs/concepts/storage/)
|
||||
|
||||
@@ -3,7 +3,6 @@ title: NFS Storage
|
||||
weight: 3054
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/nfs/
|
||||
- /rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/examples/nfs/
|
||||
---
|
||||
|
||||
Before you can use the NFS storage volume plug-in with Rancher deployments, you need to provision an NFS server.
|
||||
|
||||
@@ -3,7 +3,6 @@ title: vSphere Storage
|
||||
weight: 3055
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/vsphere/
|
||||
- /rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/examples/vsphere/
|
||||
---
|
||||
|
||||
To provide stateful workloads with vSphere storage, we recommend creating a vSphereVolume [storage class]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/#storage-classes). This practice dynamically provisions vSphere storage when workloads request volumes through a [persistent volume claim]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/persistent-volume-claims/).
|
||||
|
||||
@@ -3,7 +3,6 @@ title: How Persistent Storage Works
|
||||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/workloads/add-persistent-volume-claim
|
||||
- /rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/persistent-volume-claims/
|
||||
---
|
||||
|
||||
A persistent volume (PV) is a piece of storage in the Kubernetes cluster, while a persistent volume claim (PVC) is a request for storage.
|
||||
|
||||
@@ -6,7 +6,6 @@ aliases:
|
||||
- /rancher/v2.x/en/concepts/clusters/
|
||||
- /rancher/v2.x/en/concepts/clusters/cluster-providers/
|
||||
- /rancher/v2.x/en/tasks/clusters/
|
||||
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/
|
||||
---
|
||||
|
||||
Rancher simplifies the creation of clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a cluster. Use the option that best fits your use case.
|
||||
|
||||
@@ -5,7 +5,6 @@ metaDescription: "To create a cluster with custom nodes, you’ll need to access
|
||||
weight: 2225
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-custom/
|
||||
- /rancher/v2.x/en/cluster-provisioning/custom-clusters
|
||||
---
|
||||
|
||||
When you create a custom cluster, Rancher uses RKE (the Rancher Kubernetes Engine) to create a Kubernetes cluster in on-premise bare-metal servers, on-premise virtual machines, or in any node hosted by an infrastructure provider.
|
||||
|
||||
@@ -3,8 +3,6 @@ title: Creating an Amazon EC2 Cluster
|
||||
shortTitle: Amazon EC2
|
||||
description: Learn the prerequisites and steps required in order for you to create an Amazon EC2 cluster using Rancher
|
||||
weight: 2210
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-amazon-ec2/
|
||||
---
|
||||
Use Rancher to create a Kubernetes cluster in Amazon EC2.
|
||||
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: Enabling the API Audit Log to Record System Events
|
||||
weight: 10000
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/api-auditing/
|
||||
- /rancher/v2.x/en/admin-settings/api-auditing/
|
||||
- /rancher/v2.x/en/admin-settings/api-audit-log/
|
||||
---
|
||||
|
||||
You can enable the API audit log to record the sequence of system events initiated by individual users. You can know what happened, when it happened, who initiated it, and what cluster it affected. When you enable this feature, all requests to the Rancher API and all responses from it are written to a log.
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Helm Chart Options for Kubernetes Installations
|
||||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/ha/helm-rancher/chart-options
|
||||
---
|
||||
|
||||
### Common Options
|
||||
|
||||
@@ -3,7 +3,6 @@ title: About Custom CA Root Certificates
|
||||
weight: 1110
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/custom-ca-root-certificate/
|
||||
- /rancher/v2.x/en/admin-settings/custom-ca-root-certificate/
|
||||
---
|
||||
|
||||
If you're using Rancher in an internal production environment where you aren't exposing apps publicly, use a certificate from a private certificate authority (CA).
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Enabling Experimental Features
|
||||
weight: 8000
|
||||
aliases:
|
||||
- /rancher/v2.x/en/admin-settings/feature-flags
|
||||
---
|
||||
|
||||
_Available as of v2.3.0_
|
||||
|
||||
@@ -3,7 +3,6 @@ title: Enable API Auditing
|
||||
weight: 300
|
||||
aliases:
|
||||
- /rke/latest/en/config-options/add-ons/api-auditing/
|
||||
- /rancher/v2.x/en/installation/ha/rke-add-on/api-auditing
|
||||
---
|
||||
|
||||
>**Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Kubernetes Install with External Load Balancer (TCP/Layer 4)
|
||||
weight: 275
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/ha-server-install/
|
||||
- /rancher/v2.x/en/installation/ha/rke-add-on/layer-4-lb
|
||||
---
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Kubernetes Install with External Load Balancer (HTTPS/Layer 7)
|
||||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/ha-server-install-external-lb/
|
||||
- /rancher/v2.x/en/installation/ha/rke-add-on/layer-7-lb
|
||||
---
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Adding TLS Secrets
|
||||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets
|
||||
---
|
||||
|
||||
Kubernetes will create all the objects and services for Rancher, but it will not become available until we populate the `tls-rancher-ingress` secret in the `cattle-system` namespace with the certificate and key.
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: TLS settings
|
||||
weight: 11000
|
||||
aliases:
|
||||
- /rancher/v2.x/en/admin-settings/tls-settings/
|
||||
---
|
||||
|
||||
_Available as of v2.1.7_
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting
|
||||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/ha/helm-rancher/troubleshooting
|
||||
---
|
||||
|
||||
### Where is everything
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: 4. Install Rancher
|
||||
weight: 400
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/air-gap-installation/install-rancher/
|
||||
- /rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-system-charts/
|
||||
- /rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-for-private-reg/
|
||||
- /rancher/v2.x/en/installation/air-gap-high-availability/install-rancher/
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: '2. Collect and Publish Images to your Private Registry'
|
||||
weight: 200
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/
|
||||
- /rancher/v2.x/en/installation/air-gap-high-availability/prepare-private-registry/
|
||||
- /rancher/v2.x/en/installation/air-gap-single-node/prepare-private-registry/
|
||||
- /rancher/v2.x/en/installation/air-gap-single-node/config-rancher-for-private-reg/
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: '1. Prepare your Node(s)'
|
||||
weight: 100
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts
|
||||
- /rancher/v2.x/en/installation/air-gap-single-node/provision-host
|
||||
---
|
||||
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: Docker Install with External Load Balancer
|
||||
weight: 252
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/single-node-install-external-lb/
|
||||
- /rancher/v2.x/en/installation/single-node/single-node-install-external-lb/
|
||||
---
|
||||
|
||||
|
||||
@@ -2,8 +2,6 @@
|
||||
title: Installation Requirements
|
||||
description: Learn the node requirements for each node running Rancher server when you’re configuring Rancher to run either in a Docker or Kubernetes setup
|
||||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.x/en/installation/references
|
||||
---
|
||||
|
||||
This page describes the software, hardware, and networking requirements for the nodes where the Rancher server will be installed. The Rancher server can be installed on a single node or a high-availability Kubernetes cluster.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Project Administration
|
||||
weight: 2500
|
||||
aliases:
|
||||
- /rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/
|
||||
- /rancher/v2.x/en/project-admin/editing-projects/
|
||||
---
|
||||
|
||||
|
||||
@@ -5,9 +5,7 @@ weight: 4000
|
||||
aliases:
|
||||
- /rancher/v2.x/en/concepts/ci-cd-pipelines/
|
||||
- /rancher/v2.x/en/tasks/pipelines/
|
||||
- /rancher/v2.x/en/tools/pipelines/
|
||||
- /rancher/v2.x/en/tools/pipelines/configurations/
|
||||
- /rancher/v2.x/en/project-admin/tools/pipelines
|
||||
---
|
||||
Using Rancher, you can integrate with a GitHub repository to setup a continuous integration (CI) pipeline.
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: v2.0.x Pipeline Documentation
|
||||
weight: 9000
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tools/pipelines/docs-for-v2.0.x
|
||||
- /rancher/v2.x/en/project-admin/tools/pipelines/docs-for-v2.0.x
|
||||
---
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Project Resource Quotas
|
||||
weight: 2515
|
||||
aliases:
|
||||
- /rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/resource-quotas/
|
||||
---
|
||||
|
||||
_Available as of v2.1.0_
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Kubernetes Rollback
|
||||
weight: 1025
|
||||
aliases:
|
||||
- /rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/
|
||||
- /rancher/v2.x/en/upgrades/ha-server-rollbacks
|
||||
---
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Upgrading Rancher Installed on Kubernetes
|
||||
weight: 1020
|
||||
aliases:
|
||||
- /rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm
|
||||
- /rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm-airgap
|
||||
- /rancher/v2.x/en/upgrades/air-gap-upgrade/
|
||||
---
|
||||
|
||||
@@ -3,7 +3,6 @@ title: Upgrading Rancher Installed with Docker
|
||||
weight: 1010
|
||||
aliases:
|
||||
- /rancher/v2.x/en/upgrades/single-node-upgrade/
|
||||
- /rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/
|
||||
- /rancher/v2.x/en/upgrades/upgrades/single-node-air-gap-upgrade
|
||||
---
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Requirements
|
||||
weight: 5
|
||||
aliases:
|
||||
- /rke/latest/en/installation/os
|
||||
---
|
||||
**In this section:**
|
||||
|
||||
|
||||
+72
@@ -45,6 +45,78 @@ map $request_uri $redirect_uri {
|
||||
~^/docs/rancher/rancher-services/health-checks/?$ /docs/rancher/v1.0/en/rancher-services/health-checks/;
|
||||
~^/docs/os/cloud-config/?$ /docs/os/v1.x/en/installation/configuration/;
|
||||
~^/docs/rancher/api/?$ /docs/rancher/v2.x/en/api/;
|
||||
|
||||
~^/docs/rancher/v1.0/en/environments/certificates/?$ /docs/rancher/v1.0/en/rancher-ui/infrastructure/certificates/;
|
||||
~^/docs/rancher/v1.1/en/api/api-keys/?$ /docs/rancher/v1.1/en/api/v1/api-keys/;
|
||||
~^/docs/rancher/v1.1/zh/?$ /docs/rancher/v1.1/en/;
|
||||
~^/docs/rancher/v1.2/en/api/api-keys/?$ /docs/rancher/v1.2/en/api/v2-beta/api-keys/;
|
||||
~^/docs/rancher/v1.2/zh/?$ /docs/rancher/v1.2/en/;
|
||||
~^/docs/rancher/v1.3/en/api/api-keys/?$ /docs/rancher/v1.3/en/api/v2-beta/api-keys/;
|
||||
~^/docs/rancher/v1.4/en/api/api-keys/?$ /docs/rancher/v1.4/en/api/v2-beta/api-keys/;
|
||||
~^/docs/rancher/v1.4/zh/?$ /docs/rancher/v1.4/en/;
|
||||
~^/docs/rancher/v1.5/en/api/api-keys/?$ /docs/rancher/v1.5/en/api/v2-beta/api-keys/;
|
||||
~^/docs/rancher/v1.5/zh/?$ /docs/rancher/v1.5/en/;
|
||||
~^/docs/rancher/v1.6/en/api/api-keys/?$ /docs/rancher/latest/en/api/v2-beta/api-keys/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/agent-options/?$ /docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/api-audit-log/?$ /docs/rancher/v2.x/en/installation/options/api-audit-log/;
|
||||
~^/rancher/v2.x/en/admin-settings/custom-ca-root-certificate/?$ /docs/rancher/v2.x/en/installation/options/custom-ca-root-certificate/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/feature-flags/?$ /docs/rancher/v2.x/en/installation/options/feature-flags/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/?$ /docs/rancher/v2.x/en/removing-rancher/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/?$ /docs/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/server-url/?$ /docs/rancher/v2.x/en/admin-settings/;
|
||||
~^/docs/rancher/v2.x/en/admin-settings/tls-settings/?$ /docs/rancher/v2.x/en/installation/options/tls-settings/;
|
||||
~^/docs/rancher/v2.x/en/cluster-admin/kubectl/?$ /docs/rancher/v2.x/en/cluster-admin/cluster-access/kubectl/;
|
||||
~^/docs/rancher/v2.x/en/cluster-provisioning/cluster-members/?$ /docs/rancher/v2.x/en/cluster-admin/cluster-access/cluster-members/;
|
||||
~^/docs/rancher/v2.x/en/cluster-provisioning/custom-clusters/agent-options/?$ /docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/agent-options/;
|
||||
~^/docs/rancher/v2.x/en/cluster-provisioning/rancher-agents/?$ /docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/rancher-agents/;
|
||||
~^/docs/rancher/v2.x/en/concepts/cli-configuration/?$ /docs/rancher/v2.x/en/cli/;
|
||||
~^/docs/rancher/v2.x/en/concepts/volumes-and-storage/?$ /docs/rancher/v2.x/en/cluster-admin/volumes-and-storage/;
|
||||
~^/docs/rancher/v2.x/en/faq/cleaning-cluster-nodes/?$ /docs/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-high-availability/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/prepare-nodes/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-installation/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-installation/install-rancher/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/populate-private-registry/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-single-node/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/;
|
||||
~^/docs/rancher/v2.x/en/installation/air-gap-single-node/install-rancher/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/;
|
||||
~^/docs/rancher/v2.x/en/installation/api-auditing/?$ /docs/rancher/v2.x/en/installation/options/api-audit-log/;
|
||||
~^/docs/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration/?$ /docs/rancher/v2.x/en/backups/backups/ha-backups/;
|
||||
~^/docs/rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/?$ /docs/rancher/v2.x/en/backups/backups/single-node-backups/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha-server-install-external-lb/?$ /docs/rancher/v2.x/en/installation/options/rke-add-on/layer-7-lb/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha-server-install/?$ /docs/rancher/v2.x/en/installation/options/rke-add-on/layer-4-lb/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha-server-install/nlb/?$ /docs/rancher/v2.x/en/installation/options/rke-add-on/layer-4-lb/nlb/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha/helm-rancher/chart-options/?$ /docs/rancher/v2.x/en/installation/options/chart-options/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/?$ /docs/rancher/v2.x/en/installation/options/tls-secrets/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha/helm-rancher/troubleshooting/?$ /docs/rancher/v2.x/en/installation/options/troubleshooting/;
|
||||
~^/docs/rancher/v2.x/en/installation/ha/rke-add-on/api-auditing/?$ /docs/rancher/v2.x/en/installation/options/rke-add-on/api-auditing/;
|
||||
~^/docs/rancher/v2.x/en/installation/references/?$ /docs/rancher/v2.x/en/installation/requirements/;
|
||||
~^/docs/rancher/v2.x/en/installation/single-node-install-external-lb/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/single-node/single-node-install-external-lb/;
|
||||
~^/docs/rancher/v2.x/en/installation/single-node-install/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/single-node/;
|
||||
~^/docs/rancher/v2.x/en/installation/single-node/?$ /docs/rancher/v2.x/en/installation/other-installation-methods/single-node/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/editing-clusters/?$ /docs/rancher/v2.x/en/cluster-admin/editing-clusters/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/kubeconfig/?$ /docs/rancher/v2.x/en/cluster-admin/cluster-access/kubeconfig/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/kubectl/?$ /docs/rancher/v2.x/en/cluster-admin/cluster-access/kubectl/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/?$ /docs/rancher/v2.x/en/cluster-admin/projects-and-namespaces/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/editing-projects/?$ /docs/rancher/v2.x/en/project-admin/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/project-members/?$ /docs/rancher/v2.x/en/project-admin/project-members/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/resource-quotas/?$ /docs/rancher/v2.x/en/project-admin/resource-quotas/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/?$ /docs/rancher/v2.x/en/cluster-admin/volumes-and-storage/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/examples/nfs/?$ /docs/rancher/v2.x/en/cluster-admin/volumes-and-storage/examples/nfs/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/examples/vsphere/?$ /docs/rancher/v2.x/en/cluster-admin/volumes-and-storage/examples/vsphere/;
|
||||
~^/docs/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/persistent-volume-claims/?$ /docs/rancher/v2.x/en/cluster-admin/volumes-and-storage/how-storage-works/;
|
||||
~^/docs/rancher/v2.x/en/project-admin/tools/pipelines/?$ /docs/rancher/v2.x/en/project-admin/pipelines/;
|
||||
~^/docs/rancher/v2.x/en/tasks/clusters/creating-a-cluster/?$ /docs/rancher/v2.x/en/cluster-provisioning/;
|
||||
~^/docs/rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-amazon-ec2/?$ /docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/;
|
||||
~^/docs/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/?$ /docs/rancher/v2.x/en/cluster-admin/cluster-access/kubectl/;
|
||||
~^/docs/rancher/v2.x/en/tools/?$ /docs/rancher/v2.x/en/cluster-admin/tools/;
|
||||
~^/docs/rancher/v2.x/en/tools/logging/?$ /docs/rancher/v2.x/en/cluster-admin/tools/logging/;
|
||||
~^/docs/rancher/v2.x/en/tools/pipelines/?$ /docs/rancher/v2.x/en/project-admin/pipelines/;
|
||||
~^/docs/rancher/v2.x/en/tools/pipelines/docs-for-v2.0.x/?$ /docs/rancher/v2.x/en/project-admin/pipelines/docs-for-v2.0.x/;
|
||||
~^/docs/rancher/v2.x/en/upgrades/ha-server-rollbacks/?$ /docs/rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/;
|
||||
~^/docs/rancher/v2.x/en/upgrades/single-node-rollbacks/?$ /docs/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/;
|
||||
~^/docs/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm/?$ /docs/rancher/v2.x/en/upgrades/upgrades/ha/;
|
||||
~^/docs/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/?$ /docs/rancher/v2.x/en/upgrades/upgrades/single-node/;
|
||||
~^/docs/rke/latest/en/installation/os/?$ /docs/rke/latest/en/os/;
|
||||
}
|
||||
|
||||
server {
|
||||
|
||||
Reference in New Issue
Block a user