mirror of https://github.com/rancher/docs.git
Delete 2.x docs and add redirects for all deleted pages
This commit is contained in:
Catherine Luse
parent
53d9ecec1f
commit
d08ebaa95c
|
|
@ -7,6 +7,8 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/backups
|
||||
- /rancher/v2.0-v2.4/en/backups/legacy/backup
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/backup/
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/backup/
|
||||
---
|
||||
This section contains information about how to create backups of your Rancher data and how to restore them in a disaster scenario.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/legacy/backup/single-node-backups/
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/backup/docker-backups
|
||||
- /rancher/v2.0-v2.4/en/installation/backups-and-restoration/single-node-backup-and-restoration/
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/backup/docker-backups/
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/legacy/backups/k3s-backups
|
||||
- /rancher/v2.0-v2.4/en/backups/legacy/backup/k3s-backups
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/backup/k3s-backups
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/backup/k3s-backups/
|
||||
---
|
||||
|
||||
When Rancher is installed on a high-availability Kubernetes cluster, we recommend using an external database to store the cluster data.
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/legacy/backups/ha-backups
|
||||
- /rancher/v2.0-v2.4/en/backups/legacy/backup/ha-backups
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/backup/rke-backups
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/backup/rke-backups/
|
||||
---
|
||||
This section describes how to create backups of your high-availability Rancher install.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/restorations
|
||||
- /rancher/v2.0-v2.4/en/backups/legacy/restore
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/restore
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/restore/
|
||||
---
|
||||
If you lose the data on your Rancher Server, you can restore it if you have backups stored in a safe location.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/installation/after-installation/single-node-backup-and-restoration/
|
||||
- /rancher/v2.0-v2.4/en/backups/restorations/single-node-restoration
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/restore/docker-restores
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/restore/docker-restores/
|
||||
---
|
||||
|
||||
If you encounter a disaster scenario, you can restore your Rancher Server to your most recent backup.
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/legacy/restore/k8s-restore/k3s-restore/
|
||||
- /rancher/v2.0-v2.4/en/backups/legacy/restore/k3s-restore
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/restore/k3s-restore
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/restore/k3s-restore/
|
||||
---
|
||||
|
||||
When Rancher is installed on a high-availability Kubernetes cluster, we recommend using an external database to store the cluster data.
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/backups/legacy/restore/k8s-restore/rke-restore/
|
||||
- /rancher/v2.0-v2.4/en/backups/legacy/restore/rke-restore
|
||||
- /rancher/v2.0-v2.4/en/backups/v2.0.x-v2.4.x/restore/rke-restore
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/restore/rke-restore/
|
||||
---
|
||||
|
||||
This procedure describes how to use RKE to restore a snapshot of the Rancher Kubernetes cluster.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: "Rolling back to v2.0.0-v2.1.5"
|
||||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.x/en/backups/v2.0.x-v2.4.x/restore/rke-restore/v2.0-v2.1/
|
||||
---
|
||||
|
||||
> Rolling back to Rancher v2.0-v2.1 is no longer supported. The instructions for rolling back to these versions are preserved here and are intended to be used only in cases where upgrading to Rancher v2.2+ is not feasible.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: Best Practices Guide
|
||||
weight: 4
|
||||
aliases:
|
||||
- /rancher/v2.x/en/best-practices/v2.0-v2.4/
|
||||
---
|
||||
|
||||
The purpose of this section is to consolidate best practices for Rancher implementations. This also includes recommendations for related technologies, such as Kubernetes, Docker, containers, and more. The objective is to improve the outcome of a Rancher implementation using the operational experience of Rancher and its customers.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 100
|
|||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/best-practices/containers
|
||||
- /rancher/v2.0-v2.4/en/best-practices/v2.0-v2.4/containers
|
||||
- /rancher/v2.x/en/best-practices/v2.0-v2.4/containers/
|
||||
---
|
||||
|
||||
Running well-built containers can greatly impact the overall performance and security of your environment.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 100
|
|||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/best-practices/deployment-strategies
|
||||
- /rancher/v2.0-v2.4/en/best-practices/v2.0-v2.4/deployment-strategies
|
||||
- /rancher/v2.x/en/best-practices/v2.0-v2.4/deployment-strategies/
|
||||
---
|
||||
|
||||
There are two recommended deployment strategies. Each one has its own pros and cons. Read more about which one would fit best for your use case:
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 100
|
|||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/best-practices/deployment-types
|
||||
- /rancher/v2.0-v2.4/en/best-practices/v2.0-v2.4/deployment-types
|
||||
- /rancher/v2.x/en/best-practices/v2.0-v2.4/deployment-types/
|
||||
---
|
||||
|
||||
A high-availability Kubernetes installation, defined as an installation of Rancher on a Kubernetes cluster with at least three nodes, should be used in any production installation of Rancher, as well as any installation deemed "important." Multiple Rancher instances running on multiple nodes ensure high availability that cannot be accomplished with a single node environment.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 101
|
|||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/best-practices/management
|
||||
- /rancher/v2.0-v2.4/en/best-practices/v2.0-v2.4/management
|
||||
- /rancher/v2.x/en/best-practices/v2.0-v2.4/management/
|
||||
---
|
||||
|
||||
Rancher allows you to set up numerous combinations of configurations. Some configurations are more appropriate for development and testing, while there are other best practices for production environments for maximum availability and fault tolerance. The following best practices should be followed for production.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ metaDescription: "The Rancher CLI is a unified tool that you can use to interact
|
|||
weight: 21
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/cluster-admin/cluster-access/cli
|
||||
- /rancher/v2.x/en/cli/
|
||||
---
|
||||
|
||||
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,8 +2,9 @@
|
|||
title: CIS Scans
|
||||
weight: 18
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/cis-scans/legacy
|
||||
- /rancher/v2.0-v2.4/en/cis-scans
|
||||
- /rancher/v2.0-v2.4/en/cis-scans/legacy
|
||||
- /rancher/v2.0-v2.4/en/cis-scans
|
||||
- /rancher/v2.x/en/cis-scans/v2.4/
|
||||
---
|
||||
|
||||
_Available as of v2.4.0_
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cis-scans/legacy/skipped-tests
|
||||
- /rancher/v2.0-v2.4/en/cis-scans/v2.4/skipped-tests
|
||||
- /rancher/v2.0-v2.4/en/cis-scans/skipped-tests
|
||||
- /rancher/v2.x/en/cis-scans/v2.4/skipped-tests/
|
||||
---
|
||||
|
||||
This section lists the tests that are skipped in the permissive test profile for RKE.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/alerts
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/alerts/cluster-alerts
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-alerts
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-alerts/
|
||||
---
|
||||
|
||||
To keep your clusters and applications healthy and driving your organizational productivity forward, you need to stay informed of events occurring in your clusters and projects, both planned and unplanned. When an event occurs, your alert is triggered, and you are sent a notification. You can then, if necessary, follow up with corrective actions.
|
||||
|
|
|
|||
|
|
@ -9,6 +9,8 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/cluster-logging/
|
||||
---
|
||||
|
||||
Logging is helpful because it allows you to:
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging/elasticsearch
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging/elasticsearch
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/elasticsearch
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/cluster-logging/elasticsearch/
|
||||
---
|
||||
|
||||
If your organization uses [Elasticsearch](https://www.elastic.co/), either on premise or in the cloud, you can configure Rancher to send it Kubernetes logs. Afterwards, you can log into your Elasticsearch deployment to view logs.
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Fluentd
|
||||
weight: 600
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging/fluentd
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging/fluentd
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/fluentd
|
||||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging/fluentd
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging/fluentd
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/fluentd
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/cluster-logging/fluentd/
|
||||
---
|
||||
|
||||
If your organization uses [Fluentd](https://www.fluentd.org/), you can configure Rancher to send it Kubernetes logs. Afterwards, you can log into your Fluentd server to view logs.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging/kafka
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging/kafka
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/kafka
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/cluster-logging/kafka/
|
||||
---
|
||||
|
||||
If your organization uses [Kafka](https://kafka.apache.org/), you can configure Rancher to send it Kubernetes logs. Afterwards, you can log into your Kafka server to view logs.
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging/splunk
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging/splunk
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/splunk
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/cluster-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.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/logging/syslog
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/cluster-logging/syslog
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/cluster-logging/syslog
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/cluster-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.
|
||||
|
|
|
|||
|
|
@ -8,6 +8,8 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/cluster-monitoring
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/monitoring/cluster-monitoring
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/
|
||||
---
|
||||
|
||||
_Available as of v2.2.0_
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/monitoring/cluster-metrics
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/cluster-metrics
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/cluster-metrics
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/cluster-metrics/
|
||||
---
|
||||
|
||||
_Available as of v2.2.0_
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/custom-metrics
|
||||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/monitoring/custom-metrics/
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/custom-metrics
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/custom-metrics/
|
||||
---
|
||||
|
||||
After you've enabled [cluster level monitoring]({{< baseurl >}}/rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/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.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/monitoring/expression
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/expression
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/expression
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/expression/
|
||||
---
|
||||
|
||||
The PromQL expressions in this doc can be used to configure [alerts.]({{<baseurl>}}/rancher/v2.0-v2.4/en/cluster-admin/tools/alerts/)
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/monitoring/prometheus/
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/prometheus
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/prometheus
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/prometheus/
|
||||
---
|
||||
|
||||
_Available as of v2.2.0_
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/monitoring/viewing-metrics
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/viewing-metrics
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/viewing-metrics
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/viewing-metrics/
|
||||
---
|
||||
|
||||
_Available as of v2.2.0_
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/
|
||||
- /rancher/v2.0-v2.4/en/project-admin/istio
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/cluster-istio
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/
|
||||
---
|
||||
_Available as of v2.3.0_
|
||||
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/disabling-istio
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/disabling-istio
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/disabling-istio
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/disabling-istio/
|
||||
---
|
||||
|
||||
This section describes how to disable Istio in a cluster, namespace, or workload.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/rbac
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/rbac
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/rbac
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/rbac/
|
||||
---
|
||||
|
||||
This section describes the permissions required to access Istio features and how to configure access to the Kiali and Jaeger visualizations.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/release-notes
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/release-notes
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/release-notes
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/release-notes/
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/resources
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/resources
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/resources
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/resources/
|
||||
---
|
||||
_Available as of v2.3.0_
|
||||
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/
|
||||
---
|
||||
|
||||
This section describes how to enable Istio and start using it in your projects.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/deploy-workloads
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/deploy-workloads
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/deploy-workloads
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/deploy-workloads/
|
||||
---
|
||||
|
||||
> **Prerequisite:** To enable Istio for a workload, the cluster and namespace must have Istio enabled.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/enable-istio-in-cluster
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/enable-istio-in-cluster
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/enable-istio-in-cluster
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/enable-istio-in-cluster/
|
||||
---
|
||||
|
||||
This cluster uses the default Nginx controller to allow traffic into the cluster.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/enable-istio-in-cluster/enable-istio-with-psp
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/enable-istio-in-cluster/enable-istio-with-psp
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/enable-istio-in-cluster/enable-istio-with-psp
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/enable-istio-in-cluster/enable-istio-with-psp/
|
||||
---
|
||||
|
||||
>**Note:** The following guide is only for RKE provisioned clusters.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/enable-istio-in-namespace
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/enable-istio-in-namespace
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/enable-istio-in-namespace
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/enable-istio-in-namespace/
|
||||
---
|
||||
|
||||
You will need to manually enable Istio in each namespace that you want to be tracked or controlled by Istio. When Istio is enabled in a namespace, the Envoy sidecar proxy will be automatically injected into all new workloads that are deployed in the namespace.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/gateway
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/gateway
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/gateway
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/gateway/
|
||||
---
|
||||
|
||||
The gateway to each cluster can have its own port or load balancer, which is unrelated to a service mesh. By default, each Rancher-provisioned cluster has one NGINX ingress controller allowing traffic into the cluster.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/node-selectors
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/node-selectors
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/node-selectors
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/node-selectors/
|
||||
---
|
||||
|
||||
> **Prerequisite:** Your cluster needs a worker node that can designated for Istio. The worker node should meet the [resource requirements.]({{<baseurl>}}/rancher/v2.0-v2.4/en/cluster-admin/tools/istio/resources)
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/set-up-traffic-management
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/set-up-traffic-management
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/set-up-traffic-management
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/set-up-traffic-management/
|
||||
---
|
||||
|
||||
A central advantage of traffic management in Istio is that it allows dynamic request routing. Some common applications for dynamic request routing include canary deployments and blue/green deployments. The two key resources in Istio traffic management are *virtual services* and *destination rules*.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/istio/setup/view-traffic
|
||||
- /rancher/v2.0-v2.4/en/istio/legacy/setup/view-traffic
|
||||
- /rancher/v2.0-v2.4/en/istio/v2.3.x-v2.4.x/setup/view-traffic
|
||||
- /rancher/v2.x/en/istio/v2.3.x-v2.4.x/setup/view-traffic/
|
||||
---
|
||||
|
||||
This section describes how to view the traffic that is being managed by Istio.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,8 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/cluster-admin/tools/notifiers
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/notifiers
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/notifiers
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/notifiers/
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-alerts/default-alerts/
|
||||
---
|
||||
|
||||
Notifiers are services that inform you of alert events. You can configure notifiers to send alert notifications to staff best suited to take corrective action.
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
title: vSphere Node Template Configuration in Rancher before v2.0.4
|
||||
shortTitle: Before v2.0.4
|
||||
weight: 5
|
||||
aliases:
|
||||
- /rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/prior-to-2.0.4/
|
||||
---
|
||||
|
||||
- [Account access](#account-access)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
title: vSphere Node Template Configuration in Rancher v2.0.4
|
||||
shortTitle: v2.0.4
|
||||
weight: 4
|
||||
aliases:
|
||||
- /rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/v2.0.4/
|
||||
---
|
||||
- [Account access](#account-access)
|
||||
- [Scheduling](#scheduling)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
title: vSphere Node Template Configuration in Rancher v2.2.0
|
||||
shortTitle: v2.2.0
|
||||
weight: 3
|
||||
aliases:
|
||||
- /rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/v2.2.0/
|
||||
---
|
||||
- [Account Access](#account-access)
|
||||
- [Scheduling](#scheduling)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
title: vSphere Node Template Configuration in Rancher v2.3.0
|
||||
shortTitle: v2.3.0
|
||||
weight: 2
|
||||
aliases:
|
||||
- /rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/v2.3.0/
|
||||
---
|
||||
- [Account Access](#account-access)
|
||||
- [Scheduling](#scheduling)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,8 @@
|
|||
title: vSphere Node Template Configuration in Rancher v2.3.3
|
||||
shortTitle: v2.3.3
|
||||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/v2.3.3/
|
||||
---
|
||||
- [Account Access](#account-access)
|
||||
- [Scheduling](#scheduling)
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: v2.1.x and v2.2.x Windows Documentation (Experimental)
|
||||
weight: 9100
|
||||
aliases:
|
||||
- /rancher/v2.x/en/cluster-provisioning/rke-clusters/windows-clusters/docs-for-2.1-and-2.2/
|
||||
---
|
||||
|
||||
_Available from v2.1.0 to v2.1.9 and v2.2.0 to v2.2.3_
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: Questions about Upgrading to Rancher v2.x
|
||||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.x/en/faq/upgrades-to-2x/
|
||||
---
|
||||
|
||||
This page contains frequently asked questions about the changes between Rancher v1.x and v2.x, and how to upgrade from Rancher v1.x to v2.x.
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/installation/upgrades-rollbacks/upgrades/ha/helm2
|
||||
- /rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades-rollbacks/upgrades/ha/helm2
|
||||
- /rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades-rollbacks/upgrades/helm2
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-k8s/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.
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/upgrades/upgrades/migrating-from-rke-add-on
|
||||
- /rancher/v2.0-v2.4/en/installation/upgrades-rollbacks/upgrades/migrating-from-rke-add-on
|
||||
- /rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades-rollbacks/upgrades/migrating-from-rke-add-on
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/migrating-from-rke-add-on/
|
||||
---
|
||||
|
||||
> **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/upgrades/upgrades/namespace-migration
|
||||
- /rancher/v2.0-v2.4/en/installation/upgrades-rollbacks/upgrades/namespace-migration
|
||||
- /rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades-rollbacks/upgrades/namespace-migration
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/namespace-migration/
|
||||
---
|
||||
>This section applies only to Rancher upgrades from v2.0.6 or earlier to v2.0.7 or later. Upgrades from v2.0.7 to later version are unaffected.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,6 +6,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/installation/air-gap-high-availability/
|
||||
- /rancher/v2.0-v2.4/en/installation/air-gap-single-node/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/air-gap-helm2
|
||||
- /rancher/v2.x/en/installation/resources/advanced/air-gap-helm2/
|
||||
---
|
||||
|
||||
> After Helm 3 was released, the Rancher installation instructions were updated to use Helm 3.
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/installation/air-gap-single-node/install-rancher
|
||||
- /rancher/v2.0-v2.4/en/installation/air-gap/install-rancher
|
||||
- /rancher/v2.0-v2.4/en/installation/options/air-gap-helm2/install-rancher
|
||||
- /rancher/v2.x/en/installation/resources/advanced/air-gap-helm2/install-rancher/
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 300
|
|||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/air-gap-high-availability/install-kube
|
||||
- /rancher/v2.0-v2.4/en/installation/options/air-gap-helm2/launch-kubernetes
|
||||
- /rancher/v2.x/en/installation/resources/advanced/air-gap-helm2/launch-kubernetes/
|
||||
---
|
||||
|
||||
This section is about how to prepare to launch a Kubernetes cluster which is used to deploy Rancher server for your air gapped environment.
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/installation/air-gap-single-node/config-rancher-for-private-reg/
|
||||
- /rancher/v2.0-v2.4/en/installation/air-gap-high-availability/config-rancher-for-private-reg/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/air-gap-helm2/populate-private-registry
|
||||
- /rancher/v2.x/en/installation/resources/advanced/air-gap-helm2/populate-private-registry/
|
||||
---
|
||||
|
||||
> **Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/installation/air-gap-high-availability/provision-hosts
|
||||
- /rancher/v2.0-v2.4/en/installation/air-gap-single-node/provision-host
|
||||
- /rancher/v2.0-v2.4/en/installation/options/air-gap-helm2/prepare-nodes
|
||||
- /rancher/v2.x/en/installation/resources/advanced/air-gap-helm2/prepare-nodes/
|
||||
---
|
||||
|
||||
This section is about how to prepare your node(s) to install 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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Template for an RKE Cluster with a Certificate Signed by Recognized CA an
|
|||
weight: 3
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/cluster-yml-templates/3-node-certificate-recognizedca
|
||||
- /rancher/v2.x/en/installation/resources/advanced/cluster-yml-templates/3-node-certificate-recognizedca/
|
||||
---
|
||||
|
||||
RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Template for an RKE Cluster with a Self-signed Certificate and Layer 4 Lo
|
|||
weight: 2
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/cluster-yml-templates/3-node-certificate
|
||||
- /rancher/v2.x/en/installation/resources/advanced/cluster-yml-templates/3-node-certificate/
|
||||
---
|
||||
RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Template for an RKE Cluster with a Self-signed Certificate and SSL Termin
|
|||
weight: 3
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/cluster-yml-templates/3-node-externalssl-certificate
|
||||
- /rancher/v2.x/en/installation/resources/advanced/cluster-yml-templates/3-node-externalssl-certificate/
|
||||
---
|
||||
|
||||
RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Template for an RKE Cluster with a Recognized CA Certificate and SSL Term
|
|||
weight: 4
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/cluster-yml-templates/3-node-externalssl-recognizedca
|
||||
- /rancher/v2.x/en/installation/resources/advanced/cluster-yml-templates/3-node-externalssl-recognizedca/
|
||||
---
|
||||
|
||||
RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Kubernetes Installation Using Helm 2
|
|||
weight: 1
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/
|
||||
---
|
||||
|
||||
> After Helm 3 was released, the Rancher installation instructions were updated to use Helm 3.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: "1. Create Nodes and Load Balancer"
|
|||
weight: 185
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/create-nodes-lb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/create-nodes-lb/
|
||||
---
|
||||
|
||||
Use your provider of choice to provision 3 nodes and a Load Balancer endpoint for your RKE install.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: NGINX
|
|||
weight: 270
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/create-nodes-lb/nginx
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/create-nodes-lb/nginx/
|
||||
---
|
||||
NGINX will be configured as Layer 4 load balancer (TCP) that forwards connections to one of your Rancher nodes.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Amazon NLB
|
|||
weight: 277
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/create-nodes-lb/nlb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/create-nodes-lb/nlb/
|
||||
---
|
||||
## Objectives
|
||||
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ description: "With Helm, you can create configurable deployments instead of usin
|
|||
weight: 195
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/helm-init
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/helm-init/
|
||||
---
|
||||
|
||||
Helm is the package management tool of choice for Kubernetes. Helm "charts" provide templating syntax for Kubernetes YAML manifest documents. With Helm we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at [https://helm.sh/](https://helm.sh/). To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Troubleshooting
|
|||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/helm-init/troubleshooting
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/helm-init/troubleshooting/
|
||||
---
|
||||
|
||||
### Helm commands show forbidden
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: "4. Install Rancher"
|
|||
weight: 200
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/helm-rancher
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/helm-rancher/
|
||||
---
|
||||
|
||||
Rancher installation is managed using the Helm package manager for Kubernetes. Use `helm` to install the prerequisite and charts to install Rancher.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Chart Options
|
|||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/helm-rancher/chart-options
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/helm-rancher/chart-options/
|
||||
---
|
||||
|
||||
### Common Options
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ description: Read about how to populate the Kubernetes TLS secret for a Rancher
|
|||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/helm-rancher/tls-secrets
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Troubleshooting
|
|||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/helm-rancher/troubleshooting
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/helm-rancher/troubleshooting/
|
||||
---
|
||||
|
||||
### Where is everything
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: "2. Install Kubernetes with RKE"
|
|||
weight: 190
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/kubernetes-rke
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/kubernetes-rke/
|
||||
---
|
||||
|
||||
Use RKE to install Kubernetes with a high availability etcd configuration.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Troubleshooting
|
|||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/kubernetes-rke/troubleshooting
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/kubernetes-rke/troubleshooting/
|
||||
---
|
||||
|
||||
### canal Pods show READY 2/3
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: RKE Add-On Install
|
|||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 300
|
|||
aliases:
|
||||
- /rke/latest/en/config-options/add-ons/api-auditing/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/api-auditing
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/api-auditing/
|
||||
---
|
||||
|
||||
>**Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Kubernetes Install with External Load Balancer (TCP/Layer 4)
|
|||
weight: 275
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/layer-4-lb/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
title: Amazon NLB Configuration
|
||||
weight: 277
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install/nlb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-4-lb/nlb
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install/nlb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-4-lb/nlb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/layer-4-lb/nlb/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
title: Kubernetes Install with External Load Balancer (HTTPS/Layer 7)
|
||||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install-external-lb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-7-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install-external-lb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-7-lb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/layer-7-lb/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
title: Amazon ALB Configuration
|
||||
weight: 277
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install-external-lb/alb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-7-lb/alb
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install-external-lb/alb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-7-lb/alb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/layer-7-lb/alb/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
title: NGINX Configuration
|
||||
weight: 277
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install-external-lb/nginx/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-7-lb/nginx
|
||||
- /rancher/v2.0-v2.4/en/installation/ha-server-install-external-lb/nginx/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-7-lb/nginx
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/layer-7-lb/nginx/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: HTTP Proxy Configuration
|
|||
weight: 277
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/proxy
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/proxy/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: 404 - default backend
|
||||
weight: 30
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/404-default-backend/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting/404-default-backend
|
||||
- /404-default-backend/
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/404-default-backend/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting/404-default-backend
|
||||
- /404-default-backend/
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/troubleshooting/404-default-backend/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Troubleshooting HA RKE Add-On Install
|
||||
weight: 370
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting
|
||||
- /rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/rke-add-on/troubleshooting/404-default-backend/
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting
|
||||
- /rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/rke-add-on/troubleshooting/404-default-backend/
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/troubleshooting/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
title: Generic troubleshooting
|
||||
weight: 5
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/generic-troubleshooting/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting/generic-troubleshooting
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/generic-troubleshooting/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting/generic-troubleshooting
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/troubleshooting/generic-troubleshooting/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,8 +2,9 @@
|
|||
title: Failed to get job complete status
|
||||
weight: 20
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/job-complete-status/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting/job-complete-status
|
||||
- /rancher/v2.0-v2.4/en/installation/troubleshooting-ha/job-complete-status/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/troubleshooting/job-complete-status
|
||||
- /rancher/v2.x/en/installation/resources/advanced/helm2/rke-add-on/troubleshooting/job-complete-status/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Kubernetes Install with External Load Balancer (TCP/Layer 4)
|
||||
weight: 275
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/ha/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/options/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/ha/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/options/helm2/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/options/rke-add-on/layer-4-lb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/rke-add-on/layer-4-lb/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Kubernetes Install with External Load Balancer (HTTPS/Layer 7)
|
||||
weight: 276
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/ha/rke-add-on/layer-7-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/options/rke-add-on/layer-7-lb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/rke-add-on/layer-7-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/ha/rke-add-on/layer-7-lb
|
||||
- /rancher/v2.0-v2.4/en/installation/options/rke-add-on/layer-7-lb/
|
||||
- /rancher/v2.0-v2.4/en/installation/options/rke-add-on/layer-7-lb
|
||||
- /rancher/v2.x/en/installation/resources/advanced/rke-add-on/layer-7-lb/
|
||||
---
|
||||
|
||||
> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ weight: 2040
|
|||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/installation/options/upgrading-cert-manager/helm-2-instructions
|
||||
- /rancher/v2.0-v2.4/en/installation/resources/choosing-version/encryption/upgrading-cert-manager/helm-2-instructions
|
||||
- /rancher/v2.x/en/installation/resources/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:
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Manual HPA Installation for Clusters Created Before Rancher v2.0.7
|
|||
weight: 3050
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/k8s-in-rancher/horizontal-pod-autoscaler/hpa-for-rancher-before-2_0_7
|
||||
- /rancher/v2.x/en/k8s-in-rancher/horitzontal-pod-autoscaler/hpa-for-rancher-before-2_0_7/
|
||||
---
|
||||
|
||||
This section describes how to manually install HPAs for clusters created with Rancher before 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.
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/project-admin/tools/pipelines/docs-for-v2.0.x
|
||||
- /rancher/v2.0-v2.4/en/project-admin/pipelines/docs-for-v2.0.x
|
||||
- /rancher/v2.0-v2.4/en/k8s-in-rancher/pipelines/docs-for-v2.0.x
|
||||
- /rancher/v2.x/en/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]({{<baseurl>}}/rancher/v2.0-v2.4/en/k8s-in-rancher/pipelines/).
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/project-admin/tools/alerts
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/legacy/alerts/project-alerts
|
||||
- /rancher/v2.0-v2.4/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-alerts/project-alerts
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-alerts/project-alerts/
|
||||
---
|
||||
|
||||
To keep your clusters and applications healthy and driving your organizational productivity forward, you need to stay informed of events occurring in your clusters and projects, both planned and unplanned. When an event occurs, your alert is triggered, and you are sent a notification. You can then, if necessary, follow up with corrective actions.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,8 @@ aliases:
|
|||
- /rancher/v2.0-v2.4/en/project-admin/tools/logging
|
||||
- /rancher/v2.0-v2.4/en/logging/legacy/project-logging
|
||||
- /rancher/v2.0-v2.4/en/logging/v2.0.x-v2.4.x/project-logging
|
||||
- /rancher/v2.x/en/logging/v2.0.x-v2.4.x/project-logging/
|
||||
- /rancher/v2.x/en/monitoring-alerting/v2.0.x-v2.4.x/cluster-monitoring/project-monitoring/
|
||||
---
|
||||
|
||||
Rancher can integrate with a variety of popular logging services and tools that exist outside of your Kubernetes clusters.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: Rancher v2.1
|
||||
weight: 5
|
||||
aliases:
|
||||
- /rancher/v2.x/en/security/rancher-2.1/
|
||||
---
|
||||
|
||||
### Self Assessment Guide
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: CIS Benchmark Rancher Self-Assessment Guide v2.1
|
|||
weight: 209
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/security/benchmark-2.1
|
||||
- /rancher/v2.x/en/security/rancher-2.1/benchmark-2.1/
|
||||
---
|
||||
|
||||
This document is a companion to the Rancher v2.1 security hardening guide. The hardening guide provides prescriptive guidance for hardening a production installation of Rancher, and this benchmark guide is meant to help you evaluate the level of security of the hardened cluster against each control in the benchmark.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: Hardening Guide v2.1
|
|||
weight: 104
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/security/hardening-2.1
|
||||
- /rancher/v2.x/en/security/rancher-2.1/hardening-2.1/
|
||||
---
|
||||
|
||||
This document provides prescriptive guidance for hardening a production installation of Rancher v2.1.x. It outlines the configurations and controls required to address Kubernetes benchmark controls from the Center for Information Security (CIS).
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: Rancher v2.2
|
||||
weight: 4
|
||||
aliases:
|
||||
- /rancher/v2.x/en/security/rancher-2.2/
|
||||
---
|
||||
|
||||
### Self Assessment Guide
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@ title: CIS Benchmark Rancher Self-Assessment Guide v2.2
|
|||
weight: 208
|
||||
aliases:
|
||||
- /rancher/v2.0-v2.4/en/security/benchmark-2.2
|
||||
- /rancher/v2.x/en/security/rancher-2.2/benchmark-2.2/
|
||||
---
|
||||
|
||||
This document is a companion to the Rancher v2.2 security hardening guide. The hardening guide provides prescriptive guidance for hardening a production installation of Rancher, and this benchmark guide is meant to help you evaluate the level of security of the hardened cluster against each control in the benchmark.
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue