From 6e7c59fd929c795d8891dfd4b1a6d5e2946183e8 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Mon, 12 Jul 2021 13:10:42 -0700 Subject: [PATCH] Update version labels --- content/rancher/v2.5/_index.md | 2 +- content/rancher/v2.5/en/_index.md | 8 ++++---- .../editing-clusters/gke-config-reference/_index.md | 2 +- .../cluster-capabilities-table/index.md | 6 +++--- .../en/cluster-provisioning/registered-clusters/_index.md | 2 +- .../air-gap/install-rancher/_index.md | 2 +- .../en/installation/resources/feature-flags/_index.md | 2 +- content/rancher/v2.5/en/logging/_index.md | 4 ++-- .../en/logging/custom-resource-config/flows/_index.md | 2 +- .../en/logging/custom-resource-config/outputs/_index.md | 4 ++-- .../rancher/v2.5/en/logging/taints-tolerations/_index.md | 6 +++--- content/rancher/v2.5/en/monitoring-alerting/_index.md | 4 ++-- .../configuration/alertmanager/_index.md | 2 +- .../v2.5/en/monitoring-alerting/persist-grafana/_index.md | 2 +- 14 files changed, 24 insertions(+), 24 deletions(-) diff --git a/content/rancher/v2.5/_index.md b/content/rancher/v2.5/_index.md index fe8b9384414..207a806eab7 100644 --- a/content/rancher/v2.5/_index.md +++ b/content/rancher/v2.5/_index.md @@ -1,5 +1,5 @@ --- -title: Rancher 2.5.7-2.5.8+ (Latest) +title: Rancher 2.5.7-2.5.9 (Latest) weight: 1 showBreadcrumb: false --- diff --git a/content/rancher/v2.5/en/_index.md b/content/rancher/v2.5/en/_index.md index bf6da970e45..28a297cc6f9 100644 --- a/content/rancher/v2.5/en/_index.md +++ b/content/rancher/v2.5/en/_index.md @@ -1,8 +1,8 @@ --- -title: "Rancher 2.5.7-2.5.8+ (Latest)" -shortTitle: "Rancher 2.5.7-2.5.8+ (Latest)" +title: "Rancher 2.5.7-2.5.9 (Latest)" +shortTitle: "Rancher 2.5.7-2.5.9 (Latest)" description: "Rancher adds significant value on top of Kubernetes: managing hundreds of clusters from one interface, centralizing RBAC, enabling monitoring and alerting. Read more." -metaTitle: "Rancher 2.x Docs: What is New?" +metaTitle: "Rancher 2.5.7-2.5.9 Docs: What is New?" metaDescription: "Rancher 2 adds significant value on top of Kubernetes: managing hundreds of clusters from one interface, centralizing RBAC, enabling monitoring and alerting. Read more." insertOneSix: false weight: 1 @@ -18,4 +18,4 @@ Rancher adds significant value on top of Kubernetes, first by centralizing authe It then enables detailed monitoring and alerting for clusters and their resources, ships logs to external providers, and integrates directly with Helm via the Application Catalog. If you have an external CI/CD system, you can plug it into Rancher, but if you don't, Rancher even includes [Fleet](http://fleet.rancher.io/) to help you automatically deploy and upgrade workloads. -Rancher is a _complete_ container management platform for Kubernetes, giving you the tools to successfully run Kubernetes anywhere. \ No newline at end of file +Rancher is a _complete_ container management platform for Kubernetes, giving you the tools to successfully run Kubernetes anywhere. diff --git a/content/rancher/v2.5/en/cluster-admin/editing-clusters/gke-config-reference/_index.md b/content/rancher/v2.5/en/cluster-admin/editing-clusters/gke-config-reference/_index.md index f85340bf660..579905495ea 100644 --- a/content/rancher/v2.5/en/cluster-admin/editing-clusters/gke-config-reference/_index.md +++ b/content/rancher/v2.5/en/cluster-admin/editing-clusters/gke-config-reference/_index.md @@ -5,7 +5,7 @@ weight: 3 --- {{% tabs %}} -{{% tab "v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} # Changes in v2.5.8 diff --git a/content/rancher/v2.5/en/cluster-provisioning/cluster-capabilities-table/index.md b/content/rancher/v2.5/en/cluster-provisioning/cluster-capabilities-table/index.md index 5dd2664c8b7..3a16f3fece7 100644 --- a/content/rancher/v2.5/en/cluster-provisioning/cluster-capabilities-table/index.md +++ b/content/rancher/v2.5/en/cluster-provisioning/cluster-capabilities-table/index.md @@ -3,7 +3,7 @@ headless: true --- {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} | Action | Rancher Launched Kubernetes Clusters | EKS and GKE Clusters* | Other Hosted Kubernetes Clusters | Non-EKS or GKE Registered Clusters | | --- | --- | ---| ---|----| @@ -30,7 +30,7 @@ headless: true \* \* \* For registered cluster nodes, the Rancher UI exposes the ability to cordon drain, and edit the node. {{% /tab %}} -{{% tab "Rancher v2.5.0-v2.5.7" %}} +{{% tab "Rancher before v2.5.8" %}} | Action | Rancher Launched Kubernetes Clusters | Hosted Kubernetes Clusters | Registered EKS Clusters | All Other Registered Clusters | | --- | --- | ---| ---|----| @@ -56,4 +56,4 @@ headless: true {{% /tab %}} -{{% /tabs %}} \ No newline at end of file +{{% /tabs %}} diff --git a/content/rancher/v2.5/en/cluster-provisioning/registered-clusters/_index.md b/content/rancher/v2.5/en/cluster-provisioning/registered-clusters/_index.md index f8e7a29a2a8..6169ef70e45 100644 --- a/content/rancher/v2.5/en/cluster-provisioning/registered-clusters/_index.md +++ b/content/rancher/v2.5/en/cluster-provisioning/registered-clusters/_index.md @@ -125,7 +125,7 @@ The capabilities for registered clusters are listed in the table on [this page.] {{% /tab %}} -{{% tab "Rancher v2.5.0-v2.5.8" %}} +{{% tab "Rancher before v2.5.8" %}} - [Features for All Registered Clusters](#before-2-5-8-features-for-all-registered-clusters) - [Additional Features for Registered K3s Clusters](#before-2-5-8-additional-features-for-registered-k3s-clusters) diff --git a/content/rancher/v2.5/en/installation/other-installation-methods/air-gap/install-rancher/_index.md b/content/rancher/v2.5/en/installation/other-installation-methods/air-gap/install-rancher/_index.md index dda9e56d1ea..a2ce229ef2b 100644 --- a/content/rancher/v2.5/en/installation/other-installation-methods/air-gap/install-rancher/_index.md +++ b/content/rancher/v2.5/en/installation/other-installation-methods/air-gap/install-rancher/_index.md @@ -137,7 +137,7 @@ Placeholder | Description `` | Cert-manager version running on k8s cluster. {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} ```plain helm template rancher ./rancher-.tgz --output-dir . \ --no-hooks \ # prevent files for Helm hooks from being generated diff --git a/content/rancher/v2.5/en/installation/resources/feature-flags/_index.md b/content/rancher/v2.5/en/installation/resources/feature-flags/_index.md index 62f14aa8c15..83ad818ff6f 100644 --- a/content/rancher/v2.5/en/installation/resources/feature-flags/_index.md +++ b/content/rancher/v2.5/en/installation/resources/feature-flags/_index.md @@ -77,7 +77,7 @@ Here is an example of a command for passing in the feature flag names when rende The Helm 3 command is as follows: {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} ``` helm template rancher ./rancher-.tgz --output-dir . \ diff --git a/content/rancher/v2.5/en/logging/_index.md b/content/rancher/v2.5/en/logging/_index.md index 043f8d5d1d4..8684dbc462b 100644 --- a/content/rancher/v2.5/en/logging/_index.md +++ b/content/rancher/v2.5/en/logging/_index.md @@ -79,13 +79,13 @@ For a list of options that can be configured when the logging application is ins ### Windows Support {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} As of Rancher v2.5.8, logging support for Windows clusters has been added and logs can be collected from Windows nodes. For details on how to enable or disable Windows node logging, see [this section.](./helm-chart-options/#enable-disable-windows-node-logging) {{% /tab %}} -{{% tab "Rancher v2.5.0-2.5.7" %}} +{{% tab "Rancher before v2.5.8" %}} Clusters with Windows workers support exporting logs from Linux nodes, but Windows node logs are currently unable to be exported. Only Linux node logs are able to be exported. diff --git a/content/rancher/v2.5/en/logging/custom-resource-config/flows/_index.md b/content/rancher/v2.5/en/logging/custom-resource-config/flows/_index.md index a2d9489b218..7f2a7dc321c 100644 --- a/content/rancher/v2.5/en/logging/custom-resource-config/flows/_index.md +++ b/content/rancher/v2.5/en/logging/custom-resource-config/flows/_index.md @@ -74,7 +74,7 @@ Matches, filters and `Outputs` are configured for `ClusterFlows` in the same way After `ClusterFlow` selects logs from all namespaces in the cluster, logs from the cluster will be collected and logged to the selected `ClusterOutput`. {{% /tab %}} -{{% tab "Rancher v2.5.0-v2.5.7" %}} +{{% tab "Rancher before v2.5.8" %}} - [Flows](#flows-2-5-0) - [Matches](#matches-2-5-0) diff --git a/content/rancher/v2.5/en/logging/custom-resource-config/outputs/_index.md b/content/rancher/v2.5/en/logging/custom-resource-config/outputs/_index.md index c64e9ba7040..3f312d3e5b6 100644 --- a/content/rancher/v2.5/en/logging/custom-resource-config/outputs/_index.md +++ b/content/rancher/v2.5/en/logging/custom-resource-config/outputs/_index.md @@ -69,7 +69,7 @@ For example configuration for each logging plugin supported by the logging opera For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/) {{% /tab %}} -{{% tab "v2.5.0-v2.5.7" %}} +{{% tab "Rancher before v2.5.8" %}} - [Outputs](#outputs-2-5-0) @@ -343,4 +343,4 @@ spec: ignore_network_errors_at_startup: false ``` -Let's break down what is happening here. First, we create a deployment of a container that has the additional `syslog` plugin and accepts logs forwarded from another `fluentd`. Next we create an `Output` configured as a forwarder to our deployment. The deployment `fluentd` will then forward all logs to the configured `syslog` destination. \ No newline at end of file +Let's break down what is happening here. First, we create a deployment of a container that has the additional `syslog` plugin and accepts logs forwarded from another `fluentd`. Next we create an `Output` configured as a forwarder to our deployment. The deployment `fluentd` will then forward all logs to the configured `syslog` destination. diff --git a/content/rancher/v2.5/en/logging/taints-tolerations/_index.md b/content/rancher/v2.5/en/logging/taints-tolerations/_index.md index c851f4bc296..9e75640385e 100644 --- a/content/rancher/v2.5/en/logging/taints-tolerations/_index.md +++ b/content/rancher/v2.5/en/logging/taints-tolerations/_index.md @@ -20,13 +20,13 @@ Both provide choice for the what node(s) the pod will run on. ### Default Implementation in Rancher's Logging Stack {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes. The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes. Moreover, most logging stack pods run on Linux only and have a `nodeSelector` added to ensure they run on Linux nodes. {{% /tab %}} -{{% tab "Rancher v2.5.0-2.5.7" %}} +{{% tab "Rancher before v2.5.8" %}} By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes. The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes. Moreover, we can populate the `nodeSelector` to ensure that our pods *only* run on Linux nodes. @@ -74,4 +74,4 @@ However, if you would like to add tolerations for *only* the `fluentbit` contain ```yaml fluentbit_tolerations: # insert tolerations list for fluentbit containers only... -``` \ No newline at end of file +``` diff --git a/content/rancher/v2.5/en/monitoring-alerting/_index.md b/content/rancher/v2.5/en/monitoring-alerting/_index.md index e45f6b8a830..49d197877bd 100644 --- a/content/rancher/v2.5/en/monitoring-alerting/_index.md +++ b/content/rancher/v2.5/en/monitoring-alerting/_index.md @@ -63,7 +63,7 @@ As an [administrator]({{}}/rancher/v2.5/en/admin-settings/rbac/global-p > - When installing monitoring on an RKE cluster using RancherOS or Flatcar Linux nodes, change the etcd node certificate directory to `/opt/rke/etc/kubernetes/ssl`. {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} ### Enable Monitoring for use without SSL @@ -101,7 +101,7 @@ key.pfx=`base64-content` Then **Cert File Path** would be set to `/etc/alertmanager/secrets/cert.pem`. {{% /tab %}} -{{% tab "Rancher v2.5.0-2.5.7" %}} +{{% tab "Rancher before v2.5.8" %}} 1. In the Rancher UI, go to the cluster where you want to install monitoring and click **Cluster Explorer.** 1. Click **Apps.** diff --git a/content/rancher/v2.5/en/monitoring-alerting/configuration/alertmanager/_index.md b/content/rancher/v2.5/en/monitoring-alerting/configuration/alertmanager/_index.md index d2414bfd56b..61360d22196 100644 --- a/content/rancher/v2.5/en/monitoring-alerting/configuration/alertmanager/_index.md +++ b/content/rancher/v2.5/en/monitoring-alerting/configuration/alertmanager/_index.md @@ -91,7 +91,7 @@ Rancher v2.5.8 added Microsoft Teams and SMS as configurable receivers in the Ra Rancher v2.5.4 introduced the capability to configure receivers by filling out forms in the Rancher UI. {{% tabs %}} -{{% tab "Rancher v2.5.8" %}} +{{% tab "Rancher v2.5.8+" %}} The following types of receivers can be configured in the Rancher UI: diff --git a/content/rancher/v2.5/en/monitoring-alerting/persist-grafana/_index.md b/content/rancher/v2.5/en/monitoring-alerting/persist-grafana/_index.md index 95d45176ce5..c6db495d5ce 100644 --- a/content/rancher/v2.5/en/monitoring-alerting/persist-grafana/_index.md +++ b/content/rancher/v2.5/en/monitoring-alerting/persist-grafana/_index.md @@ -84,7 +84,7 @@ grafana.sidecar.dashboards.searchNamespace=ALL Note that the RBAC roles exposed by the Monitoring chart to add Grafana Dashboards are still restricted to giving permissions for users to add dashboards in the namespace defined in `grafana.dashboards.namespace`, which defaults to `cattle-dashboards`. {{% /tab %}} -{{% tab "Rancher v2.5.0-v2.5.8" %}} +{{% tab "Rancher before v2.5.8" %}} > **Prerequisites:** > > - The monitoring application needs to be installed.