From e6e32529b0807b0d5ccfc768b67b325fca6304d3 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Tue, 6 Oct 2020 14:32:36 +0200 Subject: [PATCH] Add redirects for links that changed with 2.5 updates Signed-off-by: Bastian Hofmann --- .../v2.x/en/backups/restorations/ha-restoration/_index.md | 1 + .../rancher/v2.x/en/helm-charts/legacy-catalogs/_index.md | 1 + .../en/helm-charts/legacy-catalogs/creating-apps/_index.md | 1 + .../v2.x/en/installation/install-rancher-on-k8s/_index.md | 6 +++++- .../air-gap/install-rancher/_index.md | 2 -- content/rancher/v2.x/en/installation/resources/_index.md | 2 ++ .../installation/resources/advanced/api-audit-log/_index.md | 2 ++ .../resources/advanced/arm64-platform/_index.md | 2 ++ .../v2.x/en/installation/resources/advanced/etcd/_index.md | 2 ++ .../v2.x/en/installation/resources/chart-options/_index.md | 2 ++ .../encryption/custom-ca-root-certificate/_index.md | 2 ++ .../installation/resources/encryption/tls-secrets/_index.md | 2 ++ .../resources/encryption/tls-settings/_index.md | 2 ++ .../resources/encryption/upgrading-cert-manager/_index.md | 3 +++ .../v2.x/en/installation/resources/helm-version/_index.md | 5 +++++ .../installation/resources/k8s-tutorials/ha-RKE/_index.md | 4 +++- .../infrastructure-tutorials/ec2-node/_index.md | 4 +++- .../k8s-tutorials/infrastructure-tutorials/nginx/_index.md | 2 ++ .../k8s-tutorials/infrastructure-tutorials/nlb/_index.md | 1 + .../k8s-tutorials/infrastructure-tutorials/rds/_index.md | 4 +++- .../installation/upgrades-rollbacks/upgrades/ha/_index.md | 2 ++ .../upgrades-rollbacks/upgrades/ha/helm2/_index.md | 3 +++ content/rancher/v2.x/en/istio/_index.md | 4 +++- content/rancher/v2.x/en/k8s-resources/_index.md | 4 +++- .../rancher/v2.x/en/k8s-resources/k8s-in-rancher/_index.md | 2 +- .../en/k8s-resources/k8s-in-rancher/certificates/_index.md | 1 + .../en/k8s-resources/k8s-in-rancher/configmaps/_index.md | 1 + .../k8s-in-rancher/horitzontal-pod-autoscaler/_index.md | 2 ++ .../horitzontal-pod-autoscaler/hpa-background/_index.md | 4 +++- .../hpa-for-rancher-before-2_0_7/_index.md | 2 ++ .../manage-hpa-with-kubectl/_index.md | 4 +++- .../manage-hpa-with-rancher-ui/_index.md | 4 +++- .../horitzontal-pod-autoscaler/testing-hpa/_index.md | 5 ++++- .../k8s-in-rancher/load-balancers-and-ingress/_index.md | 2 ++ .../load-balancers-and-ingress/ingress/_index.md | 1 + .../load-balancers-and-ingress/load-balancers/_index.md | 1 + .../en/k8s-resources/k8s-in-rancher/registries/_index.md | 1 + .../v2.x/en/k8s-resources/k8s-in-rancher/secrets/_index.md | 1 + .../k8s-in-rancher/service-discovery/_index.md | 1 + .../en/k8s-resources/k8s-in-rancher/workloads/_index.md | 1 + .../k8s-in-rancher/workloads/add-a-sidecar/_index.md | 1 + .../k8s-in-rancher/workloads/deploy-workloads/_index.md | 1 + .../k8s-in-rancher/workloads/rollback-workloads/_index.md | 1 + .../k8s-in-rancher/workloads/upgrade-workloads/_index.md | 1 + content/rancher/v2.x/en/logging/_index.md | 2 ++ .../v2.x/en/logging/legacy/cluster-logging/splunk/_index.md | 1 + .../v2.x/en/logging/legacy/cluster-logging/syslog/_index.md | 1 + content/rancher/v2.x/en/monitoring-alerting/_index.md | 5 ++++- .../legacy/alerts/cluster-alerts/default-alerts/_index.md | 5 ++--- .../monitoring/cluster-monitoring/cluster-metrics/_index.md | 1 + .../monitoring/cluster-monitoring/custom-metrics/_index.md | 1 + .../monitoring/cluster-monitoring/expression/_index.md | 1 + .../monitoring/cluster-monitoring/prometheus/_index.md | 1 + .../monitoring/cluster-monitoring/viewing-metrics/_index.md | 1 + .../v2.x/en/monitoring-alerting/legacy/notifiers/_index.md | 1 + content/rancher/v2.x/en/pipelines/_index.md | 4 +++- content/rancher/v2.x/en/pipelines/concepts/_index.md | 4 +++- content/rancher/v2.x/en/pipelines/config/_index.md | 4 +++- content/rancher/v2.x/en/pipelines/docs-for-v2.0.x/_index.md | 1 + content/rancher/v2.x/en/pipelines/example-repos/_index.md | 3 ++- content/rancher/v2.x/en/pipelines/example/_index.md | 1 + content/rancher/v2.x/en/pipelines/storage/_index.md | 2 ++ content/rke/latest/en/tutorials/infra-for-ha/_index.md | 2 +- 63 files changed, 119 insertions(+), 22 deletions(-) diff --git a/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md b/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md index c04aab3cf55..cba496f6963 100644 --- a/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md +++ b/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md @@ -4,6 +4,7 @@ shortTitle: Kubernetes Installs weight: 370 aliases: - /rancher/v2.x/en/installation/after-installation/ha-backup-and-restoration/ + - /rancher/v2.x/en/installation/backups/restores --- This procedure describes how to use RKE to restore a snapshot of the Rancher Kubernetes cluster. diff --git a/content/rancher/v2.x/en/helm-charts/legacy-catalogs/_index.md b/content/rancher/v2.x/en/helm-charts/legacy-catalogs/_index.md index fa9eefa88d6..9adf29ad3f8 100644 --- a/content/rancher/v2.x/en/helm-charts/legacy-catalogs/_index.md +++ b/content/rancher/v2.x/en/helm-charts/legacy-catalogs/_index.md @@ -8,6 +8,7 @@ aliases: - /rancher/v2.x/en/concepts/catalogs/ - /rancher/v2.x/en/tasks/global-configuration/catalog/ - /rancher/v2.x/en/catalog + - /rancher/v2.x/en/catalog/apps --- Rancher provides the ability to use a catalog of Helm charts that make it easy to repeatedly deploy applications. diff --git a/content/rancher/v2.x/en/helm-charts/legacy-catalogs/creating-apps/_index.md b/content/rancher/v2.x/en/helm-charts/legacy-catalogs/creating-apps/_index.md index ff72fb6bb19..045f1572461 100644 --- a/content/rancher/v2.x/en/helm-charts/legacy-catalogs/creating-apps/_index.md +++ b/content/rancher/v2.x/en/helm-charts/legacy-catalogs/creating-apps/_index.md @@ -4,6 +4,7 @@ weight: 400 aliases: - /rancher/v2.x/en/tasks/global-configuration/catalog/customizing-charts/ - /rancher/v2.x/en/catalog/custom/creating + - /rancher/v2.x/en/catalog/custom - /rancher/v2.x/en/catalog/creating-apps --- diff --git a/content/rancher/v2.x/en/installation/install-rancher-on-k8s/_index.md b/content/rancher/v2.x/en/installation/install-rancher-on-k8s/_index.md index 0e789a64740..f921126a735 100644 --- a/content/rancher/v2.x/en/installation/install-rancher-on-k8s/_index.md +++ b/content/rancher/v2.x/en/installation/install-rancher-on-k8s/_index.md @@ -2,6 +2,10 @@ title: Install Rancher on a Kubernetes Cluster description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation weight: 3 +aliases: + - /rancher/v2.x/en/installation/k8s-install + - /rancher/v2.x/en/installation/k8s-install/helm-rancher + - /rancher/v2.x/en/installation/install-rancher-on-k8s/install --- > **Prerequisite:** @@ -274,4 +278,4 @@ Doesn't work? Take a look at the [Troubleshooting]({{}}/rancher/v2.x/en ### Optional Next Steps -Enable the Enterprise Cluster Manager. \ No newline at end of file +Enable the Enterprise Cluster Manager. diff --git a/content/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/_index.md b/content/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/_index.md index a7393895f68..a7c5287475f 100644 --- a/content/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/_index.md +++ b/content/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/_index.md @@ -10,8 +10,6 @@ aliases: This section is about how to deploy Rancher for your air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. There are _tabs_ for either a high availability (recommended) or a Docker installation. -> **Note:** These installation instructions assume you are using Helm 3. For migration of installs started with Helm 2, refer to the official [Helm 2 to 3 migration docs.](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) This [section]({{}}/rancher/v2.x/en/installation/options/air-gap-helm2) provides a copy of the older air gap installation instructions for Rancher installed on Kubernetes with Helm 2, and it is intended to be used if upgrading to Helm 3 is not feasible. - ### Privileged Access for Rancher v2.5+ When the Rancher server is deployed in the Docker container, a local Kubernetes cluster is installed within the container for Rancher to use. Because many features of Rancher run as deployments, and privileged mode is required to run containers within containers, you will need to install Rancher with the `--privileged` option. diff --git a/content/rancher/v2.x/en/installation/resources/_index.md b/content/rancher/v2.x/en/installation/resources/_index.md index 90156f1f1e7..2a29b27f342 100644 --- a/content/rancher/v2.x/en/installation/resources/_index.md +++ b/content/rancher/v2.x/en/installation/resources/_index.md @@ -1,6 +1,8 @@ --- title: Resources weight: 4 +aliases: +- /rancher/v2.x/en/installation/options --- ### Docker Installations diff --git a/content/rancher/v2.x/en/installation/resources/advanced/api-audit-log/_index.md b/content/rancher/v2.x/en/installation/resources/advanced/api-audit-log/_index.md index d68051fc7bb..ae8607abbed 100644 --- a/content/rancher/v2.x/en/installation/resources/advanced/api-audit-log/_index.md +++ b/content/rancher/v2.x/en/installation/resources/advanced/api-audit-log/_index.md @@ -1,6 +1,8 @@ --- title: Enabling the API Audit Log to Record System Events weight: 4 +aliases: + - /rancher/v2.x/en/installation/options/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. diff --git a/content/rancher/v2.x/en/installation/resources/advanced/arm64-platform/_index.md b/content/rancher/v2.x/en/installation/resources/advanced/arm64-platform/_index.md index b0a7f913c38..d83cdb8d57e 100644 --- a/content/rancher/v2.x/en/installation/resources/advanced/arm64-platform/_index.md +++ b/content/rancher/v2.x/en/installation/resources/advanced/arm64-platform/_index.md @@ -1,6 +1,8 @@ --- title: Running on ARM64 (Experimental) weight: 3 +aliases: + - /rancher/v2.x/en/installation/options/arm64-platform --- > **Important:** diff --git a/content/rancher/v2.x/en/installation/resources/advanced/etcd/_index.md b/content/rancher/v2.x/en/installation/resources/advanced/etcd/_index.md index a605c7343aa..38fbc6321a3 100644 --- a/content/rancher/v2.x/en/installation/resources/advanced/etcd/_index.md +++ b/content/rancher/v2.x/en/installation/resources/advanced/etcd/_index.md @@ -1,6 +1,8 @@ --- title: Tuning etcd for Large Installations weight: 2 +aliases: + - /rancher/v2.x/en/installation/options/etcd --- When running larger Rancher installations with 15 or more clusters it is recommended to increase the default keyspace for etcd from the default 2GB. The maximum setting is 8GB and the host should have enough RAM to keep the entire dataset in memory. When increasing this value you should also increase the size of the host. The keyspace size can also be adjusted in smaller installations if you anticipate a high rate of change of pods during the garbage collection interval. diff --git a/content/rancher/v2.x/en/installation/resources/chart-options/_index.md b/content/rancher/v2.x/en/installation/resources/chart-options/_index.md index 9a9f4b8ce6c..ff434478ba6 100644 --- a/content/rancher/v2.x/en/installation/resources/chart-options/_index.md +++ b/content/rancher/v2.x/en/installation/resources/chart-options/_index.md @@ -1,6 +1,8 @@ --- title: Helm Chart Options weight: 2 +aliases: + - /rancher/v2.x/en/installation/options/chart-options --- - [Common Options](#common-options) diff --git a/content/rancher/v2.x/en/installation/resources/encryption/custom-ca-root-certificate/_index.md b/content/rancher/v2.x/en/installation/resources/encryption/custom-ca-root-certificate/_index.md index 924bb8a8203..19a275f73d5 100644 --- a/content/rancher/v2.x/en/installation/resources/encryption/custom-ca-root-certificate/_index.md +++ b/content/rancher/v2.x/en/installation/resources/encryption/custom-ca-root-certificate/_index.md @@ -1,6 +1,8 @@ --- title: About Custom CA Root Certificates weight: 1 +aliases: + - /rancher/v2.x/en/installation/options/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). diff --git a/content/rancher/v2.x/en/installation/resources/encryption/tls-secrets/_index.md b/content/rancher/v2.x/en/installation/resources/encryption/tls-secrets/_index.md index ec2da6815aa..a86191c5fe1 100644 --- a/content/rancher/v2.x/en/installation/resources/encryption/tls-secrets/_index.md +++ b/content/rancher/v2.x/en/installation/resources/encryption/tls-secrets/_index.md @@ -1,6 +1,8 @@ --- title: Adding TLS Secrets weight: 2 +aliases: + - /rancher/v2.x/en/installation/options/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. diff --git a/content/rancher/v2.x/en/installation/resources/encryption/tls-settings/_index.md b/content/rancher/v2.x/en/installation/resources/encryption/tls-settings/_index.md index fc57ede4a78..64b515a0921 100644 --- a/content/rancher/v2.x/en/installation/resources/encryption/tls-settings/_index.md +++ b/content/rancher/v2.x/en/installation/resources/encryption/tls-settings/_index.md @@ -1,6 +1,8 @@ --- title: TLS Settings weight: 3 +aliases: + - /rancher/v2.x/en/installation/options/tls-settings --- In Rancher v2.1.7, the default TLS configuration changed to only accept TLS 1.2 and secure TLS cipher suites. TLS 1.3 and TLS 1.3 exclusive cipher suites are not supported. diff --git a/content/rancher/v2.x/en/installation/resources/encryption/upgrading-cert-manager/_index.md b/content/rancher/v2.x/en/installation/resources/encryption/upgrading-cert-manager/_index.md index 19ee7d06ee9..044a06ec4aa 100644 --- a/content/rancher/v2.x/en/installation/resources/encryption/upgrading-cert-manager/_index.md +++ b/content/rancher/v2.x/en/installation/resources/encryption/upgrading-cert-manager/_index.md @@ -1,6 +1,9 @@ --- title: Upgrading Cert-Manager weight: 4 +aliases: + - /rancher/v2.x/en/installation/options/upgrading-cert-manager + - /rancher/v2.x/en/installation/options/upgrading-cert-manager/helm-2-instructions --- Rancher uses cert-manager to automatically generate and renew TLS certificates for HA deployments of Rancher. As of Fall 2019, three important changes to cert-manager are set to occur that you need to take action on if you have an HA deployment of Rancher: diff --git a/content/rancher/v2.x/en/installation/resources/helm-version/_index.md b/content/rancher/v2.x/en/installation/resources/helm-version/_index.md index c4e66f92849..cefc3765216 100644 --- a/content/rancher/v2.x/en/installation/resources/helm-version/_index.md +++ b/content/rancher/v2.x/en/installation/resources/helm-version/_index.md @@ -1,6 +1,11 @@ --- title: Helm Version Requirements weight: 3 +aliases: + - /rancher/v2.x/en/installation/options/helm-version + - /rancher/v2.x/en/installation/options/helm2 + - /rancher/v2.x/en/installation/options/helm2/helm-init + - /rancher/v2.x/en/installation/options/helm2/helm-rancher --- This section contains the requirements for Helm, which is the tool used to install Rancher on a high-availability Kubernetes cluster. diff --git a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/ha-RKE/_index.md b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/ha-RKE/_index.md index 99edaa3e1ce..9f65b04926b 100644 --- a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/ha-RKE/_index.md +++ b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/ha-RKE/_index.md @@ -2,6 +2,8 @@ title: Setting up a High-availability RKE Kubernetes Cluster shortTitle: Set up RKE Kubernetes weight: 3 +aliases: + - /rancher/v2.x/en/installation/k8s-install/kubernetes-rke --- @@ -168,4 +170,4 @@ Save a copy of the following files in a secure location: See the [Troubleshooting]({{}}/rancher/v2.x/en/installation/options/troubleshooting/) page. -### [Next: Install Rancher]({{}}/rancher/v2.x/en/installation/k8s-install/helm-rancher/) \ No newline at end of file +### [Next: Install Rancher]({{}}/rancher/v2.x/en/installation/k8s-install/helm-rancher/) diff --git a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/_index.md b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/_index.md index ecf063ca94e..fafbf80e4e4 100644 --- a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/_index.md +++ b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/ec2-node/_index.md @@ -1,6 +1,8 @@ --- title: Setting up Nodes in Amazon EC2 weight: 3 +aliases: + - /rancher/v2.x/en/installation/options/ec2-node --- In this tutorial, you will learn one way to set up Linux nodes for the Rancher management server. These nodes will fulfill the node requirements for [OS, Docker, hardware, and networking.]({{}}/rancher/v2.x/en/installation/requirements/) @@ -61,4 +63,4 @@ curl https://releases.rancher.com/install-docker/18.09.sh | sh If you are going to install an RKE cluster on the new nodes, take note of the **IPv4 Public IP** and **Private IP** of each node. This information can be found on the **Description** tab for each node after it is created. The public and private IP will be used to populate the `address` and `internal_address` of each node in the RKE cluster configuration file, `rancher-cluster.yml`. -RKE will also need access to the private key to connect to each node. Therefore, you might want to take note of the path to your private keys to connect to the nodes, which can also be included in the `rancher-cluster.yml` under the `ssh_key_path` directive for each node. \ No newline at end of file +RKE will also need access to the private key to connect to each node. Therefore, you might want to take note of the path to your private keys to connect to the nodes, which can also be included in the `rancher-cluster.yml` under the `ssh_key_path` directive for each node. diff --git a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/_index.md b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/_index.md index fde4297dfae..3e2410eab25 100644 --- a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/_index.md +++ b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nginx/_index.md @@ -1,6 +1,8 @@ --- title: Setting up an NGINX Load Balancer weight: 4 +aliases: + - /rancher/v2.x/en/installation/options/nginx --- NGINX will be configured as Layer 4 load balancer (TCP) that forwards connections to one of your Rancher nodes. diff --git a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/_index.md b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/_index.md index 7166089c1c5..39e4ca0fb03 100644 --- a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/_index.md +++ b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/_index.md @@ -4,6 +4,7 @@ weight: 5 aliases: - /rancher/v2.x/en/installation/ha/create-nodes-lb/nlb - /rancher/v2.x/en/installation/k8s-install/create-nodes-lb/nlb + - /rancher/v2.x/en/installation/options/nlb --- This how-to guide describes how to set up a Network Load Balancer (NLB) in Amazon's EC2 service that will direct traffic to multiple instances on EC2. diff --git a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/_index.md b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/_index.md index f40b9f96b59..ad9bd90552f 100644 --- a/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/_index.md +++ b/content/rancher/v2.x/en/installation/resources/k8s-tutorials/infrastructure-tutorials/rds/_index.md @@ -1,6 +1,8 @@ --- title: Setting up a MySQL Database in Amazon RDS weight: 4 +aliases: + - /rancher/v2.x/en/installation/options/rds --- This tutorial describes how to set up a MySQL database in Amazon's RDS. @@ -31,4 +33,4 @@ This information will be used to connect to the database in the following format mysql://username:password@tcp(hostname:3306)/database-name ``` -For more information on configuring the datastore for K3s, refer to the [K3s documentation.]({{}}/k3s/latest/en/installation/datastore/) \ No newline at end of file +For more information on configuring the datastore for K3s, refer to the [K3s documentation.]({{}}/k3s/latest/en/installation/datastore/) diff --git a/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/_index.md b/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/_index.md index 55e2a6e9e9d..35110e1804a 100644 --- a/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/_index.md +++ b/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/_index.md @@ -4,6 +4,8 @@ weight: 1020 aliases: - /rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm-airgap - /rancher/v2.x/en/upgrades/air-gap-upgrade/ + - /rancher/v2.x/en/upgrades/upgrades/ha + - /rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/upgrades/ha --- The following instructions will guide you through using Helm to upgrade a Rancher server that was installed on a Kubernetes cluster. diff --git a/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/helm2/_index.md b/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/helm2/_index.md index 64cf393022d..221c20b2725 100644 --- a/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/helm2/_index.md +++ b/content/rancher/v2.x/en/installation/upgrades-rollbacks/upgrades/ha/helm2/_index.md @@ -1,6 +1,9 @@ --- title: Upgrading Rancher Installed on Kubernetes with Helm 2 weight: 1050 +aliases: + - /rancher/v2.x/en/upgrades/upgrades/ha/helm2 + - /rancher/v2.x/en/upgrades/helm2 --- > Helm 3 has been released. If you are using Helm 2, we recommend [migrating to Helm 3](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) because it is simpler to use and more secure than Helm 2. diff --git a/content/rancher/v2.x/en/istio/_index.md b/content/rancher/v2.x/en/istio/_index.md index 2a7005bc834..a39d487a3ce 100644 --- a/content/rancher/v2.x/en/istio/_index.md +++ b/content/rancher/v2.x/en/istio/_index.md @@ -1,6 +1,8 @@ --- title: Istio weight: 15 +aliases: + - /rancher/v2.x/en/dashboard/istio --- # Istio in Cluster Manager @@ -90,4 +92,4 @@ By default, each Rancher-provisioned cluster has one NGINX ingress controller al ### Egress Support -By default the Egress gateway is disabled, but can be enabled on install or upgrade through the values.yaml or via the [overlay file]({{}}/rancher/v2.x/en/istio/setup/enable-istio-in-cluster/#overlay-file). \ No newline at end of file +By default the Egress gateway is disabled, but can be enabled on install or upgrade through the values.yaml or via the [overlay file]({{}}/rancher/v2.x/en/istio/setup/enable-istio-in-cluster/#overlay-file). diff --git a/content/rancher/v2.x/en/k8s-resources/_index.md b/content/rancher/v2.x/en/k8s-resources/_index.md index 2c460974c1e..22cf85c68bc 100644 --- a/content/rancher/v2.x/en/k8s-resources/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/_index.md @@ -1,6 +1,8 @@ --- title: Kubernetes Resources weight: 10 +aliases: + - /rancher/v2.x/en/k8s-in-rancher --- @@ -8,4 +10,4 @@ weight: 10 _Available as of v2.5_ -The cluster explorer is a new feature in Rancher v2.5 that allows you to view and manipulate all of the custom resources and CRDs in a Kubernetes cluster from the Rancher UI. \ No newline at end of file +The cluster explorer is a new feature in Rancher v2.5 that allows you to view and manipulate all of the custom resources and CRDs in a Kubernetes cluster from the Rancher UI. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/_index.md index 5e50a555387..2d5b45a3724 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/_index.md @@ -4,7 +4,7 @@ weight: 19 aliases: - /rancher/v2.x/en/concepts/ - /rancher/v2.x/en/tasks/ - - /rancher/v2.x/en/concepts/resources/ + - /rancher/v2.x/en/concepts/resources/ --- When your project is set up, [project members]({{}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#project-roles) can start managing their applications and all the components that comprise it. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/certificates/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/certificates/_index.md index 0bf10731b0f..9b83e5d9258 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/certificates/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/certificates/_index.md @@ -4,6 +4,7 @@ description: Learn how to add an SSL (Secure Sockets Layer) certificate or TLS ( weight: 3060 aliases: - /rancher/v2.x/en/tasks/projects/add-ssl-certificates/ + - /rancher/v2.x/en/k8s-in-rancher/certificates --- When you create an ingress within Rancher/Kubernetes, you must provide it with a secret that includes a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate. You can then add the certificate to the ingress deployment. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/configmaps/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/configmaps/_index.md index 20419b97d07..4b0161169bb 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/configmaps/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/configmaps/_index.md @@ -3,6 +3,7 @@ title: ConfigMaps weight: 3061 aliases: - /rancher/v2.x/en/tasks/projects/add-configmaps + - /rancher/v2.x/en/k8s-in-rancher/configmaps --- diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/_index.md index b5f6ea2d0b2..cf5c3c1360b 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/_index.md @@ -2,6 +2,8 @@ title: The Horizontal Pod Autoscaler description: Learn about the horizontal pod autoscaler (HPA). How to manage HPAs and how to test them with a service deployment weight: 3026 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/horizontal-pod-autoscaler --- The [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) (HPA) is a Kubernetes feature that allows you to configure your cluster to automatically scale the services it's running up or down. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/_index.md index d0d487a49ed..073b9bbb634 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-background/_index.md @@ -1,6 +1,8 @@ --- title: Background Information on HPAs weight: 3027 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/horizontal-pod-autoscaler/hpa-background --- The [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) (HPA) is a Kubernetes feature that allows you to configure your cluster to automatically scale the services it's running up or down. This section provides explanation on how HPA works with Kubernetes. @@ -37,4 +39,4 @@ For full documentation on HPA, refer to the [Kubernetes Documentation](https://k HPA is an API resource in the Kubernetes `autoscaling` API group. The current stable version is `autoscaling/v1`, which only includes support for CPU autoscaling. To get additional support for scaling based on memory and custom metrics, use the beta version instead: `autoscaling/v2beta1`. -For more information about the HPA API object, see the [HPA GitHub Readme](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md#horizontalpodautoscaler-object). \ No newline at end of file +For more information about the HPA API object, see the [HPA GitHub Readme](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md#horizontalpodautoscaler-object). diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-for-rancher-before-2_0_7/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-for-rancher-before-2_0_7/_index.md index ab9b55db752..fc54792f5e6 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-for-rancher-before-2_0_7/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-for-rancher-before-2_0_7/_index.md @@ -1,6 +1,8 @@ --- title: Manual HPA Installation for Clusters Created Before Rancher v2.0.7 weight: 3050 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/horizontal-pod-autoscaler/hpa-for-rancher-before-2_0_7 --- This section describes how to manually install HPAs for clusters created with Rancher prior to v2.0.7. This section also describes how to configure your HPA to scale up or down, and how to assign roles to your HPA. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/_index.md index 0d19fa185e2..281226e55f9 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/_index.md @@ -1,6 +1,8 @@ --- title: Managing HPAs with kubectl weight: 3029 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/horizontal-pod-autoscaler/manage-hpa-with-kubectl --- This section describes HPA management with `kubectl`. This document has instructions for how to: @@ -197,4 +199,4 @@ For HPA to use custom metrics from Prometheus, package [k8s-prometheus-adapter]( If the API is accessible, you should receive output that's similar to what follows. {{% accordion id="custom-metrics-api-response-rancher" label="API Response" %}} {"kind":"APIResourceList","apiVersion":"v1","groupVersion":"custom.metrics.k8s.io/v1beta1","resources":[{"name":"pods/fs_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_rss","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_period","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_throttled","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_time","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_read","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_sector_writes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_user","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/last_seen","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/tasks_state","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_quota","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/start_time_seconds","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_write","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_cache","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_periods","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_cfs_throttled_periods","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads_merged","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_working_set_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/network_udp_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_inodes_free","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_inodes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_time_weighted","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_failures","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_swap","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_cpu_shares","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_swap_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_io_current","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_failcnt","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_writes_merged","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/network_tcp_usage","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/memory_max_usage_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/spec_memory_reservation_limit_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_load_average_10s","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/cpu_system","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_reads_bytes","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]},{"name":"pods/fs_sector_reads","singularName":"","namespaced":true,"kind":"MetricValueList","verbs":["get"]}]} - {{% /accordion %}} \ No newline at end of file + {{% /accordion %}} diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/_index.md index b08eb8f8624..f9bd8e81d0a 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-rancher-ui/_index.md @@ -1,6 +1,8 @@ --- title: Managing HPAs with the Rancher UI weight: 3028 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/horizontal-pod-autoscaler/manage-hpa-with-rancher-ui --- _Available as of v2.3.0_ @@ -52,4 +54,4 @@ If you want to create HPAs that scale based on other metrics than CPU and memory 1. Click **Delete** to confirm. -> **Result:** The HPA is deleted from the current cluster. \ No newline at end of file +> **Result:** The HPA is deleted from the current cluster. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/_index.md index 7df9409d618..8ec7bc9ee50 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/_index.md @@ -1,6 +1,9 @@ --- title: Testing HPAs with kubectl weight: 3031 + +aliases: + - /rancher/v2.x/en/k8s-in-rancher/horizontal-pod-autoscaler/testing-hpa --- This document describes how to check the status of your HPAs after scaling them up or down with your load testing tool. For information on how to check the status from the Rancher UI (at least version 2.3.x), refer to [Managing HPAs with the Rancher UI]({{}}/rancher/v2.x/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/). @@ -488,4 +491,4 @@ Use your load testing tool to scale down to one pod when all metrics below targe NAME READY STATUS RESTARTS AGE hello-world-54764dfbf8-q6l82 1/1 Running 0 6h ``` -{{% /accordion %}} \ No newline at end of file +{{% /accordion %}} diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/_index.md index 6c56007e544..559a9be1810 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/_index.md @@ -2,6 +2,8 @@ title: Set Up Load Balancer and Ingress Controller within Rancher description: Learn how you can set up load balancers and ingress controllers to redirect service requests within Rancher, and learn about the limitations of load balancers weight: 3040 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress --- Within Rancher, you can set up load balancers and ingress controllers to redirect service requests. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md index 4392f9fedd8..fc75a74b6cc 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md @@ -4,6 +4,7 @@ description: Ingresses can be added for workloads to provide load balancing, SSL weight: 3042 aliases: - /rancher/v2.x/en/tasks/workloads/add-ingress/ + - /rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/ingress --- Ingress can be added for workloads to provide load balancing, SSL termination and host/path based routing. When using ingresses in a project, you can program the ingress hostname to an external DNS by setting up a [Global DNS entry]({{}}/rancher/v2.x/en/catalog/globaldns/). diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/load-balancers/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/load-balancers/_index.md index 7ae7742018d..c180b2679a1 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/load-balancers/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/load-balancers-and-ingress/load-balancers/_index.md @@ -4,6 +4,7 @@ description: "Kubernetes supports load balancing in two ways: Layer-4 Load Balan weight: 3041 aliases: - /rancher/v2.x/en/concepts/load-balancing/ + - /rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers --- Kubernetes supports load balancing in two ways: Layer-4 Load Balancing and Layer-7 Load Balancing. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/registries/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/registries/_index.md index 8fdff42b006..5c8c35b4a88 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/registries/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/registries/_index.md @@ -4,6 +4,7 @@ description: Learn about the Docker registry and Kubernetes registry, their use weight: 3063 aliases: - /rancher/v2.x/en/tasks/projects/add-registries/ + - /rancher/v2.x/en/k8s-in-rancher/registries --- Registries are Kubernetes secrets containing credentials used to authenticate with [private Docker registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/secrets/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/secrets/_index.md index e251e88271b..e1cfb93e27a 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/secrets/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/secrets/_index.md @@ -3,6 +3,7 @@ title: Secrets weight: 3062 aliases: - /rancher/v2.x/en/tasks/projects/add-a-secret + - /rancher/v2.x/en/k8s-in-rancher/secrets --- [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/service-discovery/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/service-discovery/_index.md index 09334ecc2a0..14a4963bc22 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/service-discovery/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/service-discovery/_index.md @@ -3,6 +3,7 @@ title: Service Discovery weight: 3045 aliases: - /rancher/v2.x/en/tasks/workloads/add-a-dns-record/ + - /rancher/v2.x/en/k8s-in-rancher/service-discovery --- For every workload created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload's pods using the following naming convention: diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/_index.md index 3eed10c697d..0a0279be9fb 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/_index.md @@ -5,6 +5,7 @@ weight: 3025 aliases: - /rancher/v2.x/en/concepts/workloads/ - /rancher/v2.x/en/tasks/workloads/ + - /rancher/v2.x/en/k8s-in-rancher/workloads --- You can build any complex containerized application in Kubernetes using two basic constructs: pods and workloads. Once you build an application, you can expose it for access either within the same cluster or on the Internet using a third construct: services. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/add-a-sidecar/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/add-a-sidecar/_index.md index 36b4355c4f2..1659afde060 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/add-a-sidecar/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/add-a-sidecar/_index.md @@ -3,6 +3,7 @@ title: Adding a Sidecar weight: 3029 aliases: - /rancher/v2.x/en/tasks/workloads/add-a-sidecar/ + - /rancher/v2.x/en/k8s-in-rancher/workloads/add-a-sidecar --- A _sidecar_ is a container that extends or enhances the main container in a pod. The main container and the sidecar share a pod, and therefore share the same network space and storage. You can add sidecars to existing workloads by using the **Add a Sidecar** option. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/deploy-workloads/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/deploy-workloads/_index.md index d6f10728fd6..90da9bf611c 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/deploy-workloads/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/deploy-workloads/_index.md @@ -4,6 +4,7 @@ description: Read this step by step guide for deploying workloads. Deploy a work weight: 3026 aliases: - /rancher/v2.x/en/tasks/workloads/deploy-workloads/ + - /rancher/v2.x/en/k8s-in-rancher/workloads/deploy-workloads --- Deploy a workload to run an application in one or more containers. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/rollback-workloads/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/rollback-workloads/_index.md index d9ad17aab29..7a13ca4ca8c 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/rollback-workloads/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/rollback-workloads/_index.md @@ -3,6 +3,7 @@ title: Rolling Back Workloads weight: 3027 aliases: - /rancher/v2.x/en/tasks/workloads/rollback-workloads/ + - /rancher/v2.x/en/k8s-in-rancher/workloads/rollback-workloads --- Sometimes there is a need to rollback to the previous version of the application, either for debugging purposes or because an upgrade did not go as planned. diff --git a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/upgrade-workloads/_index.md b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/upgrade-workloads/_index.md index bf9a17e4f3d..af82746d90b 100644 --- a/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/upgrade-workloads/_index.md +++ b/content/rancher/v2.x/en/k8s-resources/k8s-in-rancher/workloads/upgrade-workloads/_index.md @@ -3,6 +3,7 @@ title: Upgrading Workloads weight: 3028 aliases: - /rancher/v2.x/en/tasks/workloads/upgrade-workloads/ + - /rancher/v2.x/en/k8s-in-rancher/workloads/upgrade-workloads --- When a new version of an application image is released on Docker Hub, you can upgrade any workloads running a previous version of the application to the new one. diff --git a/content/rancher/v2.x/en/logging/_index.md b/content/rancher/v2.x/en/logging/_index.md index 6c096f25e05..7f70bb593c5 100644 --- a/content/rancher/v2.x/en/logging/_index.md +++ b/content/rancher/v2.x/en/logging/_index.md @@ -4,6 +4,8 @@ shortTitle: Logging description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster. metaDescription: "Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster." weight: 16 +aliases: + - /rancher/v2.x/en/dashboard/logging --- - [Changes in Rancher v2.5](#changes-in-rancher-v2-5) diff --git a/content/rancher/v2.x/en/logging/legacy/cluster-logging/splunk/_index.md b/content/rancher/v2.x/en/logging/legacy/cluster-logging/splunk/_index.md index 0d4edcf49ba..dfb44d3c4b3 100644 --- a/content/rancher/v2.x/en/logging/legacy/cluster-logging/splunk/_index.md +++ b/content/rancher/v2.x/en/logging/legacy/cluster-logging/splunk/_index.md @@ -4,6 +4,7 @@ weight: 300 aliases: - /rancher/v2.x/en/tasks/logging/splunk/ - /rancher/v2.x/en/tools/logging/splunk/ + - /rancher/v2.x/en/cluster-admin/tools/logging/splunk --- If your organization uses [Splunk](https://www.splunk.com/), you can configure Rancher to send it Kubernetes logs. Afterwards, you can log into your Splunk server to view logs. diff --git a/content/rancher/v2.x/en/logging/legacy/cluster-logging/syslog/_index.md b/content/rancher/v2.x/en/logging/legacy/cluster-logging/syslog/_index.md index e5aa8f8482f..a3d17dc5d73 100644 --- a/content/rancher/v2.x/en/logging/legacy/cluster-logging/syslog/_index.md +++ b/content/rancher/v2.x/en/logging/legacy/cluster-logging/syslog/_index.md @@ -3,6 +3,7 @@ title: Syslog weight: 500 aliases: - /rancher/v2.x/en/tools/logging/syslog/ + - /rancher/v2.x/en/cluster-admin/tools/logging/syslog --- If your organization uses [Syslog](https://tools.ietf.org/html/rfc5424), you can configure Rancher to send it Kubernetes logs. Afterwards, you can log into your Syslog server to view logs. diff --git a/content/rancher/v2.x/en/monitoring-alerting/_index.md b/content/rancher/v2.x/en/monitoring-alerting/_index.md index c4889c05aa2..28a2fb9559f 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/_index.md @@ -3,6 +3,9 @@ title: Monitoring and Alerting shortTitle: Monitoring/Alerting description: Prometheus lets you view metrics from your different Rancher and Kubernetes objects. Learn about the scope of monitoring and how to enable cluster monitoring weight: 14 +aliases: + - /rancher/v2.x/en/dashboard/monitoring-alerting + - /rancher/v2.x/en/dashboard/notifiers --- Using Rancher, you can monitor the state and processes of your cluster nodes, Kubernetes components, and software deployments through integration with [Prometheus](https://prometheus.io/), a leading open-source monitoring solution. @@ -95,4 +98,4 @@ You can add this configuration to the ConfigMap using the Rancher UI. ### Configuring Grafana to Use Multiple Data Sources -The data from Prometheus is used as the data source for the Grafana dashboard. Multiple data sources can be configured for Grafana. \ No newline at end of file +The data from Prometheus is used as the data source for the Grafana dashboard. Multiple data sources can be configured for Grafana. diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/alerts/cluster-alerts/default-alerts/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/alerts/cluster-alerts/default-alerts/_index.md index 81feba5aeb0..74053e89580 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/alerts/cluster-alerts/default-alerts/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/alerts/cluster-alerts/default-alerts/_index.md @@ -7,8 +7,7 @@ aliases: When you create a cluster, some alert rules are predefined. These alerts notify you about signs that the cluster could be unhealthy. You can receive these alerts if you configure a [notifier]({{}}/rancher/v2.x/en/cluster-admin/tools/notifiers) for them. -Several of the alerts use Prometheus expressions as the metric that triggers the alert. For more information on how expressions work, you can refer to the Rancher [documentation about Prometheus expressions]({{}} -/rancher/v2.x/en/cluster-admin/tools/monitoring/expression/) or the Prometheus [documentation about querying metrics](https://prometheus.io/docs/prometheus/latest/querying/basics/). +Several of the alerts use Prometheus expressions as the metric that triggers the alert. For more information on how expressions work, you can refer to the Rancher [documentation about Prometheus expressions]({{}}/rancher/v2.x/en/cluster-admin/tools/monitoring/expression/) or the Prometheus [documentation about querying metrics](https://prometheus.io/docs/prometheus/latest/querying/basics/). # Alerts for etcd Etcd is the key-value store that contains the state of the Kubernetes cluster. Rancher provides default alerts if the built-in monitoring detects a potential problem with etcd. You don't have to enable monitoring to receive these alerts. @@ -56,4 +55,4 @@ Alerts can be triggered based on node metrics. Each computing resource in a Kube | Node disk is running full within 24 hours | A critical alert is triggered if the disk space on the node is expected to run out in the next 24 hours based on the disk growth over the last 6 hours. | # Project-level Alerts -When you enable monitoring for the project, some project-level alerts are provided. For details, refer to the [section on project-level alerts.]({{}}/rancher/v2.x/en/project-admin/tools/alerts/#default-project-level-alerts) \ No newline at end of file +When you enable monitoring for the project, some project-level alerts are provided. For details, refer to the [section on project-level alerts.]({{}}/rancher/v2.x/en/project-admin/tools/alerts/#default-project-level-alerts) diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/cluster-metrics/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/cluster-metrics/_index.md index 1f117ec5f65..4ec27fa97d8 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/cluster-metrics/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/cluster-metrics/_index.md @@ -3,6 +3,7 @@ title: Cluster Metrics weight: 3 aliases: - rancher/v2.x/en/project-admin/tools/monitoring/cluster-metrics + - rancher/v2.x/en/cluster-admin/tools/monitoring/cluster-metrics --- _Available as of v2.2.0_ diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/custom-metrics/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/custom-metrics/_index.md index 4ae3893e895..30cdaadac4c 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/custom-metrics/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/custom-metrics/_index.md @@ -3,6 +3,7 @@ title: Prometheus Custom Metrics Adapter weight: 5 aliases: - rancher/v2.x/en/project-admin/tools/monitoring/custom-metrics + - rancher/v2.x/en/cluster-admin/tools/monitoring/cluster-metrics --- After you've enabled [cluster level monitoring]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/#enabling-cluster-monitoring), You can view the metrics data from Rancher. You can also deploy the Prometheus custom metrics adapter then you can use the HPA with metrics stored in cluster monitoring. diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/expression/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/expression/_index.md index ad6981f3a66..c17d1021670 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/expression/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/expression/_index.md @@ -3,6 +3,7 @@ title: Prometheus Expressions weight: 4 aliases: - rancher/v2.x/en/project-admin/tools/monitoring/expression + - rancher/v2.x/en/cluster-admin/tools/monitoring/expression --- The PromQL expressions in this doc can be used to configure [alerts.]({{}}/rancher/v2.x/en/cluster-admin/tools/alerts/) diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/prometheus/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/prometheus/_index.md index 954b6550440..59a374565d4 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/prometheus/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/prometheus/_index.md @@ -3,6 +3,7 @@ title: Prometheus Configuration weight: 1 aliases: - rancher/v2.x/en/project-admin/tools/monitoring/prometheus + - rancher/v2.x/en/cluster-admin/tools/monitoring/prometheus --- _Available as of v2.2.0_ diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/viewing-metrics/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/viewing-metrics/_index.md index af4c34d5fbd..9775343eab7 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/viewing-metrics/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/viewing-metrics/_index.md @@ -3,6 +3,7 @@ title: Viewing Metrics weight: 2 aliases: - rancher/v2.x/en/project-admin/tools/monitoring/viewing-metrics + - rancher/v2.x/en/cluster-admin/tools/monitoring/viewing-metrics --- _Available as of v2.2.0_ diff --git a/content/rancher/v2.x/en/monitoring-alerting/legacy/notifiers/_index.md b/content/rancher/v2.x/en/monitoring-alerting/legacy/notifiers/_index.md index 42c4073f85f..5f777df874e 100644 --- a/content/rancher/v2.x/en/monitoring-alerting/legacy/notifiers/_index.md +++ b/content/rancher/v2.x/en/monitoring-alerting/legacy/notifiers/_index.md @@ -3,6 +3,7 @@ title: Notifiers weight: 1 aliases: - rancher/v2.x/en/project-admin/tools/notifiers + - rancher/v2.x/en/cluster-admin/tools/notifiers --- > In Rancher 2.5, the notifier application was improved. There are now two ways to enable notifiers. The older way is documented in this section, and the new application for notifiers is documented in the [dashboard section.]({{}}/rancher/v2.x/en/dashboard/notifiers) diff --git a/content/rancher/v2.x/en/pipelines/_index.md b/content/rancher/v2.x/en/pipelines/_index.md index 58467078313..dbebec3695b 100644 --- a/content/rancher/v2.x/en/pipelines/_index.md +++ b/content/rancher/v2.x/en/pipelines/_index.md @@ -1,6 +1,8 @@ --- title: Pipelines weight: 11 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/pipelines --- Rancher's pipeline provides a simple CI/CD experience. Use it to automatically checkout code, run builds or scripts, publish Docker images or catalog applications, and deploy the updated software to users. @@ -271,4 +273,4 @@ Available Events: 1. Select which event triggers (**Push**, **Pull Request** or **Tag**) you want for the repository. -1. Click **Save**. \ No newline at end of file +1. Click **Save**. diff --git a/content/rancher/v2.x/en/pipelines/concepts/_index.md b/content/rancher/v2.x/en/pipelines/concepts/_index.md index db8e3a24a58..852d7e50a9b 100644 --- a/content/rancher/v2.x/en/pipelines/concepts/_index.md +++ b/content/rancher/v2.x/en/pipelines/concepts/_index.md @@ -1,6 +1,8 @@ --- title: Concepts weight: 1 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/pipelines/concepts --- The purpose of this page is to explain common concepts and terminology related to pipelines. @@ -33,4 +35,4 @@ Typically, pipeline stages include: - **Deploy:** - After the artifacts are published, you would release your application so users could start using the updated product. \ No newline at end of file + After the artifacts are published, you would release your application so users could start using the updated product. diff --git a/content/rancher/v2.x/en/pipelines/config/_index.md b/content/rancher/v2.x/en/pipelines/config/_index.md index 7443af2daad..3d9d48d69c1 100644 --- a/content/rancher/v2.x/en/pipelines/config/_index.md +++ b/content/rancher/v2.x/en/pipelines/config/_index.md @@ -1,6 +1,8 @@ --- title: Pipeline Configuration Reference weight: 1 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/pipelines/config --- In this section, you'll learn how to configure pipelines. @@ -655,4 +657,4 @@ For details on setting up persistent storage for pipelines, refer to [this page. # Example rancher-pipeline.yml -An example pipeline configuration file is on [this page.]({{}}/rancher/v2.x/en/k8s-in-rancher/pipelines/example) \ No newline at end of file +An example pipeline configuration file is on [this page.]({{}}/rancher/v2.x/en/k8s-in-rancher/pipelines/example) diff --git a/content/rancher/v2.x/en/pipelines/docs-for-v2.0.x/_index.md b/content/rancher/v2.x/en/pipelines/docs-for-v2.0.x/_index.md index 412822f0f96..7f9f61b3950 100644 --- a/content/rancher/v2.x/en/pipelines/docs-for-v2.0.x/_index.md +++ b/content/rancher/v2.x/en/pipelines/docs-for-v2.0.x/_index.md @@ -4,6 +4,7 @@ weight: 9000 aliases: - /rancher/v2.x/en/project-admin/tools/pipelines/docs-for-v2.0.x - /rancher/v2.x/en/project-admin/pipelines/docs-for-v2.0.x + - /rancher/v2.x/en/k8s-in-rancher/pipelines/docs-for-v2.0.x --- >**Note:** This section describes the pipeline feature as implemented in Rancher v2.0.x. If you are using Rancher v2.1 or later, where pipelines have been significantly improved, please refer to the new documentation for [v2.1 or later]({{}}/rancher/v2.x/en/k8s-in-rancher/pipelines/). diff --git a/content/rancher/v2.x/en/pipelines/example-repos/_index.md b/content/rancher/v2.x/en/pipelines/example-repos/_index.md index 4b7fddc4b85..aa8cb80e91b 100644 --- a/content/rancher/v2.x/en/pipelines/example-repos/_index.md +++ b/content/rancher/v2.x/en/pipelines/example-repos/_index.md @@ -3,6 +3,7 @@ title: Example Repositories weight: 500 aliases: - /rancher/v2.x/en/tools/pipelines/quick-start-guide/ + - /rancher/v2.x/en/k8s-in-rancher/pipelines/example-repos --- Rancher ships with several example repositories that you can use to familiarize yourself with pipelines. We recommend configuring and testing the example repository that most resembles your environment before using pipelines with your own repositories in a production environment. Use this example repository as a sandbox for repo configuration, build demonstration, etc. Rancher includes example repositories for: @@ -73,4 +74,4 @@ After enabling an example repository, run the pipeline to see how it works. ### What's Next? -For detailed information about setting up your own pipeline for your repository, [configure a version control provider]({{}}/rancher/v2.x/en/project-admin/pipelines), [enable a repository](#configure-repositories) and finally [configure your pipeline]({{}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#pipeline-configuration). \ No newline at end of file +For detailed information about setting up your own pipeline for your repository, [configure a version control provider]({{}}/rancher/v2.x/en/project-admin/pipelines), [enable a repository](#configure-repositories) and finally [configure your pipeline]({{}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#pipeline-configuration). diff --git a/content/rancher/v2.x/en/pipelines/example/_index.md b/content/rancher/v2.x/en/pipelines/example/_index.md index 512c87af456..3ddc4139bbe 100644 --- a/content/rancher/v2.x/en/pipelines/example/_index.md +++ b/content/rancher/v2.x/en/pipelines/example/_index.md @@ -3,6 +3,7 @@ title: Example YAML File weight: 501 aliases: - /rancher/v2.x/en/tools/pipelines/reference/ + - /rancher/v2.x/en/k8s-in-rancher/pipelines/example --- Pipelines can be configured either through the UI or using a yaml file in the repository, i.e. `.rancher-pipeline.yml` or `.rancher-pipeline.yaml`. diff --git a/content/rancher/v2.x/en/pipelines/storage/_index.md b/content/rancher/v2.x/en/pipelines/storage/_index.md index 6fec0fa6ccb..a4e4d31677a 100644 --- a/content/rancher/v2.x/en/pipelines/storage/_index.md +++ b/content/rancher/v2.x/en/pipelines/storage/_index.md @@ -1,6 +1,8 @@ --- title: Configuring Persistent Data for Pipeline Components weight: 600 +aliases: + - /rancher/v2.x/en/k8s-in-rancher/pipelines/storage --- The internal [Docker registry](#how-pipelines-work) and the [Minio](#how-pipelines-work) workloads use ephemeral volumes by default. This default storage works out-of-the-box and makes testing easy, but you lose the build images and build logs if the node running the Docker Registry or Minio fails. In most cases this is fine. If you want build images and logs to survive node failures, you can configure the Docker Registry and Minio to use persistent volumes. diff --git a/content/rke/latest/en/tutorials/infra-for-ha/_index.md b/content/rke/latest/en/tutorials/infra-for-ha/_index.md index 3ebc52eacdd..b308c931dc2 100644 --- a/content/rke/latest/en/tutorials/infra-for-ha/_index.md +++ b/content/rke/latest/en/tutorials/infra-for-ha/_index.md @@ -59,4 +59,4 @@ You will need to specify this hostname in a later step when you install Rancher, For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer) -### [Next: Set up a Kubernetes Cluster]({{}}/rancher/v2.x/en/installation/resources/k8s-tutorials/ka-rke/) \ No newline at end of file +### [Next: Set up a Kubernetes Cluster]({{}}/rancher/v2.x/en/installation/resources/k8s-tutorials/ha-rke/)