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

Merge remote-tracking branch 'upstream/main' into main-to-release/v2.6.11

Browse Source
This commit is contained in:
Billy Tat
2023-03-06 11:00:07 -08:00
parent 0ef5082398 e022982b59
commit 59439e921d
78 changed files with 1247 additions and 1130 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -3
View File
@@ -36,7 +36,7 @@ First, install Docusaurus 2:
yarn start
```
This command starts a local development server for Docusuarus 2, and opens up a browser window. Most changes are reflected live without having to restart the server.
This command starts a local development server for Docusaurus 2, and opens up a browser window. Most changes are reflected live without having to restart the server.
**Note:** The `yarn start` command won't include some important static site features. For example, switching between languages from the site's dropdown menu is not available. If you need these features, use `yarn build`.
@@ -50,12 +50,16 @@ This command generates static content into the `build` directory and can be serv
### Launch With Docker
Use [Docker](https://www.docker.com/) to launch the website without needing to install and configure Yarn:
You can also use [Docker](https://www.docker.com/) to launch the website.
The below command can be used to install the dependencies and run the site inside a container:
```
docker run --rm -it -v $PWD:$PWD -w $PWD -p 3000:3000 node yarn start -h 0.0.0.0
docker run --rm -it -v $PWD:$PWD -w $PWD -p 3000:3000 node /bin/sh -c "yarn install && yarn start -h 0.0.0.0"
```
Subsequent executions will check for updated dependencies, if there are none, it will skip the updates and quickly start the server.
License
=======
Copyright (c) 2014-2022 [Rancher Labs, Inc.](https://rancher.com)
docs/getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md
-6
View File
@@ -1,6 +0,0 @@
---
title: Rancher AWS Marketplace Quick Start
description: Use Amazon EKS to deploy Rancher server.
---
There is now an additional way for you to deploy the Rancher server in AWS by using Amazon EKS. To learn more, see our [Amazon Marketplace listing](https://aws.amazon.com/marketplace/pp/prodview-go7ent7goo5ae).
docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
+21 -10
View File
@@ -160,11 +160,23 @@ You will need to also manually enter the Graph, Token, and Auth Endpoints.
From the Rancher UI, enter information about your AD instance hosted in Azure to complete configuration.
1. Log into Rancher.
1. In the top left corner, click **☰ > Users & Authentication**.
1. In the left navigation menu, click **Auth Provider**.
1. Click **AzureAD**.
1. Complete the **Configure Azure AD Account** form using the information you copied while completing [Copy Azure Application Data](#4-copy-azure-application-data).
:::caution
The Azure AD account will be granted administrator privileges, since its details will be mapped to the Rancher local principal account. Make sure that this level of privilege is appropriate before you continue.
:::
**For Standard or China Endpoints:**
The following table maps the values you copied in the Azure portal to the fields in Rancher:
| Rancher Field | Azure Value |
@@ -174,20 +186,19 @@ From the Rancher UI, enter information about your AD instance hosted in Azure to
| Application Secret | Key Value |
| Endpoint | https://login.microsoftonline.com/ |
**For Custom Endpoints:**
**For Custom Endpoints:**
The following table maps your custom config values to Rancher fields:
The following table maps the custom config values you copied in the Azure portal to the fields in Rancher:
| Rancher Field | Azure Value |
| ------------------ | ------------------------------------- |
| Graph Endpoint | Microsoft Graph API Endpoint |
| Token Endpoint | OAuth 2.0 Token Endpoint |
| Auth Endpoint | OAuth 2.0 Authorization Endpoint |
| Rancher Field | Azure Value |
| ------------------ | ------------------------------------- |
| Graph Endpoint | Microsoft Graph API Endpoint |
| Token Endpoint | OAuth 2.0 Token Endpoint |
| Auth Endpoint | OAuth 2.0 Authorization Endpoint |
**Important:** When entering the Graph Endpoint in a custom config, remove the tenant ID from the URL:
**Important:** When entering the Graph Endpoint in a custom config, remove the tenant ID from the URL, like below:
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
1. Click **Enable**.
docs/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets.md
+2
View File
@@ -63,6 +63,8 @@ Before v2.6, secrets were required to be in a project scope. Projects are no lon
**Result:** Your secret is added to the individual project you chose. You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**.
Since project-scoped secrets are set at the project level, any changes made at the namespace level will be overwritten.
:::note
Project-scoped secrets on the local cluster are only visible when a single project is selected.
docs/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/vsphere/create-credentials.md
+1
View File
@@ -8,6 +8,7 @@ The following table lists the permissions required for the vSphere user account:
| Privilege Group | Operations |
|:----------------------|:-----------------------------------------------------------------------|
| Cns Privileges | Searchable |
| Datastore | AllocateSpace <br/> Browse <br/> FileManagement (Low level file operations) <br/> UpdateVirtualMachineFiles <br/> UpdateVirtualMachineMetadata |
| Global | Set custom attribute |
| Network | Assign |
docs/how-to-guides/new-user-guides/manage-clusters/provisioning-storage-examples/vsphere-storage.md
+2 -2
View File
@@ -20,8 +20,8 @@ The following steps can also be performed using the `kubectl` command line tool.
:::
1. Click **☰ > Cluster Management**.
1. Go to the cluster where you want to provide vSphere storage.
1. In the left navigation bar, click **Storage > StorageClasses**.
1. Choose the cluster you want to provide vSphere storage to and click **Exlpore**.
1. In the left navigation bar, select **Storage > StorageClasses**.
1. Click **Create**.
3. Enter a **Name** for the StorageClass.
4. Under **Provisioner**, select **VMWare vSphere Volume**.
docs/integrations-in-rancher/logging/custom-resource-configuration/flows-and-clusterflows.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Flows and ClusterFlows
---
See the [Banzai Cloud Logging operator documentation](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See [Rancher Integration with Logging Services: Troubleshooting](../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
@@ -14,7 +14,7 @@ The `Flow` is a namespaced resource, which means logs will only be collected fro
`Flows` can be configured by filling out forms in the Rancher UI.
For more details about the `Flow` custom resource, see [FlowSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/)
For more details about the `Flow` custom resource, see [FlowSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/flow_types/)
### Matches
@@ -24,13 +24,13 @@ You can specify match statements to select or exclude logs according to Kubernet
Matches can be configured by filling out the `Flow` or `ClusterFlow` forms in the Rancher UI.
For detailed examples on using the match statement, see the [official documentation on log routing.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/)
For detailed examples on using the match statement, see the [official documentation on log routing.](https://kube-logging.github.io/docs/configuration/log-routing/)
### Filters
You can define one or more filters within a `Flow`. Filters can perform various actions on the logs, for example, add additional data, transform the logs, or parse values from the records. The filters in the `Flow` are applied in the order in the definition.
For a list of filters supported by the Banzai Cloud Logging operator, see [this page.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/)
For a list of filters supported by the Logging operator, see [the official documentation on Fluentd filters](https://kube-logging.github.io/docs/configuration/plugins/filters/).
Filters need to be configured in YAML.
docs/integrations-in-rancher/logging/custom-resource-configuration/outputs-and-clusteroutputs.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Outputs and ClusterOutputs
---
See the [Banzai Cloud Logging operator documentation](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See [Rancher Integration with Logging Services: Troubleshooting](../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
@@ -16,7 +16,7 @@ You can use secrets in these definitions, but they must also be in the same name
`Outputs` can be configured by filling out forms in the Rancher UI.
For the details of `Output` custom resource, see [OutputSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/).
For the details of `Output` custom resource, see [OutputSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/output_types/).
The Rancher UI provides forms for configuring the following `Output` types:
@@ -40,7 +40,7 @@ The Rancher UI provides forms for configuring the following `Output` types:
The Rancher UI provides forms for configuring the `Output` type, target, and access credentials if applicable.
For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/).
For example configuration for each logging plugin supported by the logging operator, see the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/plugins/outputs/).
## ClusterOutputs
@@ -48,7 +48,7 @@ For example configuration for each logging plugin supported by the logging opera
`ClusterOutputs` can be configured by filling out forms in the Rancher UI.
For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)
For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/clusteroutput_types/)
## YAML Examples
docs/integrations-in-rancher/logging/logging-architecture.md
+5 -5
View File
@@ -4,9 +4,9 @@ title: Architecture
This section summarizes the architecture of the Rancher logging application.
For more details about how the Banzai Cloud Logging operator works, see the [official documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)
For more details about how the Logging operator works, see the [official documentation.](https://kube-logging.github.io/docs/#architecture)
### How the Banzai Cloud Logging Operator Works
### How the Logging Operator Works
The Logging operator automates the deployment and configuration of a Kubernetes logging pipeline. It deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system.
@@ -21,8 +21,8 @@ The following custom resources are used to define how logs are filtered and sent
Each `Flow` must reference an `Output`, and each `ClusterFlow` must reference a `ClusterOutput`.
The following figure from the [Banzai documentation](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture) shows the new logging architecture:
The following figure from the [Logging Operator documentation](https://kube-logging.github.io/docs/#architecture) shows the new logging architecture:
<figcaption>How the Banzai Cloud Logging Operator Works with Fluentd and Fluent Bit</figcaption>
<figcaption>How the Logging Operator Works with Fluentd and Fluent Bit</figcaption>
![How the Banzai Cloud Logging Operator Works with Fluentd](/img/banzai-cloud-logging-operator.png)
![How the Logging Operator Works with Fluentd](/img/banzai-cloud-logging-operator.png)
docs/pages-for-subheaders/deploy-rancher-manager.md
-1
View File
@@ -5,7 +5,6 @@ title: Deploying Rancher Server
Use one of the following guides to deploy and provision Rancher and a Kubernetes cluster in the provider of your choice.
- [AWS](../getting-started/quick-start-guides/deploy-rancher-manager/aws.md) (uses Terraform)
- [AWS Marketplace](../getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md) (uses Amazon EKS)
- [Azure](../getting-started/quick-start-guides/deploy-rancher-manager/azure.md) (uses Terraform)
- [DigitalOcean](../getting-started/quick-start-guides/deploy-rancher-manager/digitalocean.md) (uses Terraform)
- [GCP](../getting-started/quick-start-guides/deploy-rancher-manager/gcp.md) (uses Terraform)
docs/pages-for-subheaders/installation-requirements.md
+9 -29
View File
@@ -11,41 +11,21 @@ If you install Rancher on a Kubernetes cluster, requirements are different from
:::
Make sure the node(s) for the Rancher server fulfill the following requirements:
The Rancher UI works best in Firefox or Chromium based browsers (Chrome, Edge, Opera, Brave, etc).
- [Operating Systems and Container Runtime Requirements](#operating-systems-and-container-runtime-requirements)
- [RKE Specific Requirements](#rke-specific-requirements)
- [K3s Specific Requirements](#k3s-specific-requirements)
- [RKE2 Specific Requirements](#rke2-specific-requirements)
- [Installing Docker](#installing-docker)
- [Hardware Requirements](#hardware-requirements)
- [CPU and Memory](#cpu-and-memory)
- [RKE and Hosted Kubernetes](#rke-and-hosted-kubernetes)
- [K3s Kubernetes](#k3s-kubernetes)
- [RKE2 Kubernetes](#rke2-kubernetes)
- [Docker](#docker)
- [Ingress](#ingress)
- [Disks](#disks)
- [Networking Requirements](#networking-requirements)
- [Node IP Addresses](#node-ip-addresses)
- [Port Requirements](#port-requirements)
- [Dockershim Support](#dockershim-support)
See our page on [best practices](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md) for a list of recommendations for running a Rancher server in production.
For a list of best practices that we recommend for running the Rancher server in production, refer to the [best practices section.](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)
## Kubernetes Compatibility with Rancher
The Rancher UI works best in Firefox or Chromium based browsers (Chrome, Edge, Opera, Brave, ...).
Rancher needs to be installed on a supported Kubernetes version. Consult the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix) to ensure that your intended version of Kubernetes is supported.
## Operating Systems and Container Runtime Requirements
Rancher should work with any modern Linux distribution.
All supported operating systems are 64-bit x86. Rancher should work with any modern Linux distribution.
Docker is required for nodes that will run RKE Kubernetes clusters. It is not required for RKE2 or K3s clusters.
The [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix) lists which OS and Docker versions were tested for each Rancher version.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
For details on which OS and Docker versions were tested with each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
All supported operating systems are 64-bit x86.
Docker is required for nodes that will run RKE clusters. It is not required for RKE2 or K3s clusters.
The `ntp` (Network Time Protocol) package should be installed. This prevents errors with certificate validation that can occur when the time is not synchronized between the client and server.
@@ -65,7 +45,7 @@ For more information see [Installing Docker,](../getting-started/installation-an
For the container runtime, K3s bundles its own containerd by default. Alternatively, you can configure K3s to use an already installed Docker runtime. For more information on using K3s with Docker see the [K3s documentation.](https://docs.k3s.io/advanced#using-docker-as-the-container-runtime)
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix). To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script.
If you are installing Rancher on a K3s cluster with **Raspbian Buster**, follow [these steps](https://rancher.com/docs/k3s/latest/en/advanced/#enabling-legacy-iptables-on-raspbian-buster) to switch to legacy iptables.
@@ -75,7 +55,7 @@ If you are installing Rancher on a K3s cluster with Alpine Linux, follow [these
For the container runtime, RKE2 bundles its own containerd. Docker is not required for RKE2 installs.
For details on which OS versions were tested with RKE2, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
For details on which OS versions were tested with RKE2, refer to the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix).
## Hardware Requirements
docs/pages-for-subheaders/logging.md
+2 -2
View File
@@ -3,7 +3,7 @@ title: Rancher Integration with Logging Services
description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster.
---
The [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) now powers Rancher's logging solution in place of the former, in-house solution.
The [Logging operator](https://kube-logging.github.io/docs/) now powers Rancher's logging solution in place of the former, in-house solution.
For an overview of the changes in v2.5, see [this section.](../integrations-in-rancher/logging/logging-architecture.md#changes-in-rancher-v2-5)
@@ -88,7 +88,7 @@ By default, Rancher collects logs for control plane components and node componen
Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once.
For a more complete description of how to configure the logging buffer to suit your organization's needs, see the official BanzaiCloud documentation on [buffers](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/buffer/) and on [Fluentd configuration](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/fluentd/).
For a more complete description of how to configure the logging buffer to suit your organization's needs, see the official Logging operator documentation on [buffers](https://kube-logging.github.io/docs/configuration/plugins/outputs/buffer/) and on [Fluentd configuration](https://kube-logging.github.io/docs/logging-infrastructure/fluentd/).
### The `cattle-logging` Namespace Being Recreated
docs/pages-for-subheaders/manage-project-resource-quotas.md
+7 -1
View File
@@ -20,7 +20,13 @@ Edit resource quotas when:
1. In the upper left corner, click **☰ > Cluster Management**.
1. On the **Clusters** page, go to the cluster where you want to apply a resource quota and click **Explore**.
1. Click **Cluster > Projects/Namespaces**.
1. Find the project that you want to add a resource quota to. From that project, select **⋮ > Edit Config**.
1. Make sure that the **Projects/Namespaces** page is in **Group by Project** view mode.
![Screenshot highlighting the "Group by Project" icon, above the list of projects. It resembles a folder.](/img/edit-project-config-for-resource-quotas-group-by-project.png)
1. Find the project that you want to add a resource quota to, and select the **⋮** that's on the same row as the project's name.
![Screenshot highlighting triple dots icon at the end of the same row as the project name.](/img/edit-project-config-for-resource-quotas-dots.png)
1. Select **Edit Config**.
1. Expand **Resource Quotas** and click **Add Resource**. Alternatively, you can edit existing quotas.
docs/reference-guides/backup-restore-configuration/backup-configuration.md
+2 -2
View File
@@ -73,7 +73,7 @@ The S3 storage location contains the following configuration fields:
1. **Credential Secret** (optional): If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) The Credential Secret dropdown lists the secrets in all namespaces.
1. **Bucket Name**: The name of the S3 bucket where backup files will be stored.
1. **Region** (optional): The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. This field isn't needed for configuring MinIO.
1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported.
1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket.
1. **Endpoint**: The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket.
1. **Endpoint CA** (optional): This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration)
1. **Skip TLS Verifications** (optional): Set to true if you are not using TLS.
@@ -84,7 +84,7 @@ The S3 storage location contains the following configuration fields:
| `credentialSecretName` | If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace as long as you provide that namespace in `credentialSecretNamespace`. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | |
| `credentialSecretNamespace` | The namespace of the secret containing the credentials to access S3. This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | |
| `bucketName` | The name of the S3 bucket where backup files will be stored. | ✓ |
| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. | |
| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket. | |
| `region` | The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. | ✓ |
| `endpoint` | The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket. | ✓ |
| `endpointCA` | This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration) | |
docs/reference-guides/backup-restore-configuration/storage-configuration.md
+1 -1
View File
@@ -20,7 +20,7 @@ You can choose to not have any operator-level storage location configured. If yo
| Credential Secret | Choose the credentials for S3 from your secrets in Rancher. [Example](examples.md#example-credential-secret-for-storing-backups-in-s3). |
| Bucket Name | Enter the name of the [S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html) where the backups will be stored. Default: `rancherbackups`. |
| Region | The [AWS region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. |
| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. |
| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket. |
| Endpoint | The [S3 endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) For example, `s3.us-west-2.amazonaws.com`. |
| Endpoint CA | The CA cert used to for the S3 endpoint. Default: base64 encoded CA cert |
| insecureTLSSkipVerify | Set to true if you are not using TLS. |
docs/reference-guides/best-practices/rancher-managed-clusters/logging-best-practices.md
+2 -2
View File
@@ -12,7 +12,7 @@ Before Rancher v2.5, logging in Rancher has historically been a pretty static in
Rancher provides a flexible experience for log aggregation. With the logging feature, administrators and users alike can deploy logging that meets fine-grained collection criteria while offering a wider array of destinations and configuration options.
"Under the hood", Rancher logging uses the Banzai Cloud logging operator. We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters.
"Under the hood", Rancher logging uses the [Logging operator](https://github.com/kube-logging/logging-operator). We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters.
## Cluster-level Logging
@@ -44,7 +44,7 @@ Rancher logging will read all log entries in `/var/log/containers`, ensuring tha
Log collection only retrieves `stdout`/`stderr` logs from pods in Kubernetes. But what if we want to collect logs from other files that are generated by applications? Here, a log streaming sidecar (or two) may come in handy.
The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Banzai Logging Operator can pick up those logs and send them to your desired output.
The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Logging Operator can pick up those logs and send them to your desired output.
To set this up, edit your workload resource (e.g. Deployment) and add the following sidecar definition:
i18n/zh/code.json
+124
View File
@@ -268,5 +268,129 @@
"theme.SearchPage.fetchingNewResults": {
"message": "正在获取新的搜索结果...",
"description": "The paragraph for fetching new search results"
},
"theme.admonition.note": {
"message": "备注",
"description": "The default label used for the Note admonition (:::note)"
},
"theme.admonition.tip": {
"message": "提示",
"description": "The default label used for the Tip admonition (:::tip)"
},
"theme.admonition.danger": {
"message": "危险",
"description": "The default label used for the Danger admonition (:::danger)"
},
"theme.admonition.info": {
"message": "信息",
"description": "The default label used for the Info admonition (:::info)"
},
"theme.admonition.caution": {
"message": "警告",
"description": "The default label used for the Caution admonition (:::caution)"
},
"theme.docs.sidebar.closeSidebarButtonAriaLabel": {
"message": "关闭导航栏",
"description": "The ARIA label for close button of mobile sidebar"
},
"theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
"message": "切换导航栏",
"description": "The ARIA label for hamburger menu button of mobile navigation"
},
"theme.SearchModal.searchBox.resetButtonTitle": {
"message": "清除查询",
"description": "The label and ARIA label for search box reset button"
},
"theme.SearchModal.searchBox.cancelButtonText": {
"message": "取消",
"description": "The label and ARIA label for search box cancel button"
},
"theme.SearchModal.startScreen.recentSearchesTitle": {
"message": "最近搜索",
"description": "The title for recent searches"
},
"theme.SearchModal.startScreen.noRecentSearchesText": {
"message": "没有最近搜索",
"description": "The text when no recent searches"
},
"theme.SearchModal.startScreen.saveRecentSearchButtonTitle": {
"message": "保存这个搜索",
"description": "The label for save recent search button"
},
"theme.SearchModal.startScreen.removeRecentSearchButtonTitle": {
"message": "从历史记录中删除这个搜索",
"description": "The label for remove recent search button"
},
"theme.SearchModal.startScreen.favoriteSearchesTitle": {
"message": "收藏",
"description": "The title for favorite searches"
},
"theme.SearchModal.startScreen.removeFavoriteSearchButtonTitle": {
"message": "从收藏列表中删除这个搜索",
"description": "The label for remove favorite search button"
},
"theme.SearchModal.errorScreen.titleText": {
"message": "无法获取结果",
"description": "The title for error screen of search modal"
},
"theme.SearchModal.errorScreen.helpText": {
"message": "你可能需要检查网络连接。",
"description": "The help text for error screen of search modal"
},
"theme.SearchModal.footer.selectText": {
"message": "选中",
"description": "The explanatory text of the action for the enter key"
},
"theme.SearchModal.footer.selectKeyAriaLabel": {
"message": "Enter 键",
"description": "The ARIA label for the Enter key button that makes the selection"
},
"theme.SearchModal.footer.navigateText": {
"message": "导航",
"description": "The explanatory text of the action for the Arrow up and Arrow down key"
},
"theme.SearchModal.footer.navigateUpKeyAriaLabel": {
"message": "向上键",
"description": "The ARIA label for the Arrow up key button that makes the navigation"
},
"theme.SearchModal.footer.navigateDownKeyAriaLabel": {
"message": "向下键",
"description": "The ARIA label for the Arrow down key button that makes the navigation"
},
"theme.SearchModal.footer.closeText": {
"message": "关闭",
"description": "The explanatory text of the action for Escape key"
},
"theme.SearchModal.footer.closeKeyAriaLabel": {
"message": "Esc 键",
"description": "The ARIA label for the Escape key button that close the modal"
},
"theme.SearchModal.footer.searchByText": {
"message": "搜索提供",
"description": "The text explain that the search is making by Algolia"
},
"theme.SearchModal.noResultsScreen.noResultsText": {
"message": "没有结果：",
"description": "The text explains that there are no results for the following search"
},
"theme.SearchModal.noResultsScreen.suggestedQueryText": {
"message": "试试搜索",
"description": "The text for the suggested query when no results are found for the following search"
},
"theme.SearchModal.noResultsScreen.reportMissingResultsText": {
"message": "认为这个查询应该有结果？",
"description": "The text for the question where the user thinks there are missing results"
},
"theme.SearchModal.noResultsScreen.reportMissingResultsLinkText": {
"message": "请告知我们。",
"description": "The text for the link to report missing results"
},
"theme.SearchModal.placeholder": {
"message": "搜索文档",
"description": "The placeholder of the input of the DocSearch pop-up modal"
},
"theme.tags.tagsPageTitle": {
"message": "标签",
"description": "The title of the tag list page"
}
}
i18n/zh/docusaurus-plugin-content-docs/current.json
+376 -377
View File
@@ -1,379 +1,378 @@
{
"version.label": {
"message": "v2.7",
"description": "The label for version current"
},
"sidebar.tutorialSidebar.category.Getting Started": {
"message": "开始使用",
"description": "The label for category Getting Started in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Quick Start Guides": {
"message": "快速入门指南",
"description": "The label for category Quick Start Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Manager": {
"message": "部署 Rancher Manager",
"description": "The label for category Deploy Rancher Manager in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Workloads": {
"message": "部署 Rancher 工作负载",
"description": "The label for category Deploy Rancher Workloads in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation and Upgrade": {
"message": "安装和升级",
"description": "The label for category Installation and Upgrade in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation Requirements": {
"message": "安装要求",
"description": "The label for category Installation Requirements in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation References": {
"message": "安装参考",
"description": "The label for category Installation References in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install/Upgrade on a Kubernetes Cluster": {
"message": "在 Kubernetes 集群上安装\/升级",
"description": "The label for category Install/Upgrade on a Kubernetes Cluster in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Installation Methods": {
"message": "其他安装方式",
"description": "The label for category Other Installation Methods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Air-Gapped Helm CLI Install": {
"message": "离线 Helm CLI 安装",
"description": "The label for category Air-Gapped Helm CLI Install in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher on a Single Node with Docker": {
"message": "使用 Docker 将 Rancher 安装到单个节点中",
"description": "The label for category Rancher on a Single Node with Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Behind an HTTP Proxy": {
"message": "HTTP 代理后的 Rancher",
"description": "The label for category Rancher Behind an HTTP Proxy in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Resources": {
"message": "资源",
"description": "The label for category Resources in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.How-to Guides": {
"message": "操作指南",
"description": "The label for category How-to Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.New User Guides": {
"message": "新用户指南",
"description": "The label for category New User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication, Permissions, and Global Configuration": {
"message": "身份验证、权限和全局配置",
"description": "The label for category Authentication, Permissions, and Global Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication Config": {
"message": "身份验证配置",
"description": "The label for category Authentication Config in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure OpenLDAP": {
"message": "配置 OpenLDAP",
"description": "The label for category Configure OpenLDAP in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Microsoft AD Federation Service (SAML)": {
"message": "配置 Microsoft AD FS (SAML)",
"description": "The label for category Configure Microsoft AD Federation Service (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Shibboleth (SAML)": {
"message": "配置 Shibboleth (SAML)",
"description": "The label for category Configure Shibboleth (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Role-Based Access Control (RBAC)": {
"message": "管理 RBAC",
"description": "The label for category Manage Role-Based Access Control (RBAC) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About Provisioning Drivers": {
"message": "关于 Provisioning 驱动",
"description": "The label for category About Provisioning Drivers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About RKE1 Templates": {
"message": "关于 RKE1 模板",
"description": "The label for category About RKE1 Templates in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Clusters": {
"message": "管理集群",
"description": "The label for category Manage Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Access Clusters": {
"message": "访问集群",
"description": "The label for category Access Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install Cluster Autoscaler": {
"message": "安装 Cluster Autoscaler",
"description": "The label for category Install Cluster Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Create Kubernetes Persistent Storage": {
"message": "创建 Kubernetes 持久存储",
"description": "The label for category Create Kubernetes Persistent Storage in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Provisioning Storage Examples": {
"message": "配置存储示例",
"description": "The label for category Provisioning Storage Examples in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Cluster Setup": {
"message": "Kubernetes 集群设置",
"description": "The label for category Kubernetes Cluster Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Infrastructure Setup": {
"message": "基础设施设置",
"description": "The label for category Infrastructure Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Clusters in Rancher Setup": {
"message": "Rancher 设置中的 Kubernetes 集群",
"description": "The label for category Kubernetes Clusters in Rancher Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Checklist for Production-Ready Clusters": {
"message": "生产就绪集群检查清单",
"description": "The label for category Checklist for Production-Ready Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Clusters from Hosted Kubernetes Providers": {
"message": "通过托管 Kubernetes 提供商设置集群",
"description": "The label for category Set Up Clusters from Hosted Kubernetes Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Windows Clusters": {
"message": "使用 Windows 集群",
"description": "The label for category Use Windows Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Cloud Providers": {
"message": "设置 Cloud Provider",
"description": "The label for category Set Up Cloud Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Launch Kubernetes with Rancher": {
"message": "使用 Rancher 启动 Kubernetes",
"description": "The label for category Launch Kubernetes with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use New Nodes in an Infra Provider": {
"message": "在基础设施提供商中使用新节点",
"description": "The label for category Use New Nodes in an Infra Provider in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.vSphere": {
"message": "vSphere",
"description": "The label for category vSphere in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Nutanix": {
"message": "Nutanix",
"description": "The label for category Nutanix in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Resources Setup": {
"message": "Kubernetes 资源设置",
"description": "The label for category Kubernetes Resources Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Workloads and Pods": {
"message": "工作负载和 Pod",
"description": "The label for category Workloads and Pods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Horizontal Pod Autoscaler": {
"message": "Horizontal Pod Autoscaler",
"description": "The label for category Horizontal Pod Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Load Balancer and Ingress Controller": {
"message": "负载均衡和 Ingress Controller",
"description": "The label for category Load Balancer and Ingress Controller in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Helm Charts in Rancher": {
"message": "Rancher 中的 Helm Chart",
"description": "The label for category Helm Charts in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Apps Across Clusters": {
"message": "跨集群部署应用",
"description": "The label for category Deploy Apps Across Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup, Restore, and Disaster Recovery": {
"message": "备份、还原和灾难恢复",
"description": "The label for category Backup, Restore, and Disaster Recovery in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced User Guides": {
"message": "高级用户指南",
"description": "The label for category Advanced User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Projects": {
"message": "管理项目",
"description": "The label for category Manage Projects in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Project Resource Quotas": {
"message": "管理项目资源配额",
"description": "The label for category Manage Project Resource Quotas in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring/Alerting Guides": {
"message": "Monitoring\/Alerting 指南",
"description": "The label for category Monitoring/Alerting Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator Guides": {
"message": "Prometheus Federator 指南",
"description": "The label for category Prometheus Federator Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration Guides": {
"message": "Monitoring V2 配置指南",
"description": "The label for category Monitoring V2 Configuration Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced Configuration": {
"message": "高级配置",
"description": "The label for category Advanced Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio Setup Guide": {
"message": "Istio 设置指南",
"description": "The label for category Istio Setup Guide in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scan Guides": {
"message": "CIS 扫描指南",
"description": "The label for category CIS Scan Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Enable Experimental Features": {
"message": "启用实验功能",
"description": "The label for category Enable Experimental Features in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Reference Guides": {
"message": "参考指南",
"description": "The label for category Reference Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Best Practices": {
"message": "最佳实践",
"description": "The label for category Best Practices in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server": {
"message": "Rancher Server",
"description": "The label for category Rancher Server in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher-Managed Clusters": {
"message": "Rancher 管理的集群",
"description": "The label for category Rancher-Managed Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Manager Architecture": {
"message": "Rancher Manager 架构",
"description": "The label for category Rancher Manager Architecture in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cluster Configuration": {
"message": "集群配置",
"description": "The label for category Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server Configuration": {
"message": "Rancher Server 配置",
"description": "The label for category Rancher Server Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.GKE Cluster Configuration": {
"message": "GKE 集群配置",
"description": "The label for category GKE Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Existing Nodes": {
"message": "使用现有节点",
"description": "The label for category Use Existing Nodes in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Downstream Cluster Configuration": {
"message": "下游集群配置",
"description": "The label for category Downstream Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Node Template Configuration": {
"message": "节点模板配置",
"description": "The label for category Node Template Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Machine Configuration": {
"message": "主机配置",
"description": "The label for category Machine Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Single-Node Rancher in Docker": {
"message": "Docker 中的单节点 Rancher",
"description": "The label for category Single-Node Rancher in Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Amazon EKS Permissions": {
"message": "Amazon EKS 权限",
"description": "The label for category Amazon EKS Permissions in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup & Restore Configuration": {
"message": "备份和恢复配置",
"description": "The label for category Backup & Restore Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration": {
"message": "Monitoring V2 配置",
"description": "The label for category Monitoring V2 Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator": {
"message": "Prometheus Federator",
"description": "The label for category Prometheus Federator in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.User Settings": {
"message": "用户设置",
"description": "The label for category User Settings in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CLI with Rancher": {
"message": "Rancher CLI",
"description": "The label for category CLI with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About the API": {
"message": "关于 API",
"description": "The label for category About the API in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Security": {
"message": "Rancher 安全",
"description": "The label for category Rancher Security in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher v2.6 Hardening Guides": {
"message": "Rancher 2.6 强化指南",
"description": "The label for category Rancher v2.6 Hardening Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.SELinux RPM": {
"message": "SELinux RPM",
"description": "The label for category SELinux RPM in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Integrations in Rancher": {
"message": "Rancher 中的集成",
"description": "The label for category Integrations in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cloud Marketplace Integration": {
"message": "云市场集成",
"description": "The label for category Cloud Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.AWS Marketplace Integration": {
"message": "AWS Marketplace 集成",
"description": "The label for category AWS Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scans": {
"message": "CIS 扫描",
"description": "The label for category CIS Scans in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Fleet - GitOps at Scale": {
"message": "Fleet - 大规模的 GitOps",
"description": "The label for category Fleet - GitOps at Scale in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio": {
"message": "Istio",
"description": "The label for category Istio in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configuration Options": {
"message": "配置选项",
"description": "The label for category Configuration Options in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Logging": {
"message": "Logging",
"description": "The label for category Logging in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Custom Resource Configuration": {
"message": "自定义资源配置",
"description": "The label for category Custom Resource Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring and Alerting": {
"message": "监控和告警",
"description": "The label for category Monitoring and Alerting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.FAQ": {
"message": "常见问题",
"description": "The label for category FAQ in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Troubleshooting": {
"message": "故障排除",
"description": "The label for category Troubleshooting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Components": {
"message": "Kubernetes 组件",
"description": "The label for category Kubernetes Components in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Troubleshooting Tips": {
"message": "其他故障排除提示",
"description": "The label for category Other Troubleshooting Tips in sidebar tutorialSidebar"
}
"version.label": {
"message": "v2.7",
"description": "The label for version current"
},
"sidebar.tutorialSidebar.category.Getting Started": {
"message": "开始使用",
"description": "The label for category Getting Started in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Quick Start Guides": {
"message": "快速入门指南",
"description": "The label for category Quick Start Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Manager": {
"message": "部署 Rancher Manager",
"description": "The label for category Deploy Rancher Manager in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Workloads": {
"message": "部署 Rancher 工作负载",
"description": "The label for category Deploy Rancher Workloads in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation and Upgrade": {
"message": "安装和升级",
"description": "The label for category Installation and Upgrade in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation Requirements": {
"message": "安装要求",
"description": "The label for category Installation Requirements in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation References": {
"message": "安装参考",
"description": "The label for category Installation References in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install/Upgrade on a Kubernetes Cluster": {
"message": "在 Kubernetes 集群上安装/升级",
"description": "The label for category Install/Upgrade on a Kubernetes Cluster in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Installation Methods": {
"message": "其他安装方式",
"description": "The label for category Other Installation Methods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Air-Gapped Helm CLI Install": {
"message": "离线 Helm CLI 安装",
"description": "The label for category Air-Gapped Helm CLI Install in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher on a Single Node with Docker": {
"message": "使用 Docker 将 Rancher 安装到单个节点中",
"description": "The label for category Rancher on a Single Node with Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Behind an HTTP Proxy": {
"message": "HTTP 代理后的 Rancher",
"description": "The label for category Rancher Behind an HTTP Proxy in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Resources": {
"message": "资源",
"description": "The label for category Resources in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.How-to Guides": {
"message": "操作指南",
"description": "The label for category How-to Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.New User Guides": {
"message": "新用户指南",
"description": "The label for category New User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication, Permissions, and Global Configuration": {
"message": "身份验证、权限和全局配置",
"description": "The label for category Authentication, Permissions, and Global Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication Config": {
"message": "身份验证配置",
"description": "The label for category Authentication Config in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure OpenLDAP": {
"message": "配置 OpenLDAP",
"description": "The label for category Configure OpenLDAP in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Microsoft AD Federation Service (SAML)": {
"message": "配置 Microsoft AD FS (SAML)",
"description": "The label for category Configure Microsoft AD Federation Service (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Shibboleth (SAML)": {
"message": "配置 Shibboleth (SAML)",
"description": "The label for category Configure Shibboleth (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Role-Based Access Control (RBAC)": {
"message": "管理 RBAC",
"description": "The label for category Manage Role-Based Access Control (RBAC) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About Provisioning Drivers": {
"message": "关于 Provisioning 驱动",
"description": "The label for category About Provisioning Drivers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About RKE1 Templates": {
"message": "关于 RKE1 模板",
"description": "The label for category About RKE1 Templates in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Clusters": {
"message": "管理集群",
"description": "The label for category Manage Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Access Clusters": {
"message": "访问集群",
"description": "The label for category Access Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install Cluster Autoscaler": {
"message": "安装 Cluster Autoscaler",
"description": "The label for category Install Cluster Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Create Kubernetes Persistent Storage": {
"message": "创建 Kubernetes 持久存储",
"description": "The label for category Create Kubernetes Persistent Storage in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Provisioning Storage Examples": {
"message": "配置存储示例",
"description": "The label for category Provisioning Storage Examples in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Cluster Setup": {
"message": "Kubernetes 集群设置",
"description": "The label for category Kubernetes Cluster Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Infrastructure Setup": {
"message": "基础设施设置",
"description": "The label for category Infrastructure Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Clusters in Rancher Setup": {
"message": "Rancher 设置中的 Kubernetes 集群",
"description": "The label for category Kubernetes Clusters in Rancher Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Checklist for Production-Ready Clusters": {
"message": "生产就绪集群检查清单",
"description": "The label for category Checklist for Production-Ready Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Clusters from Hosted Kubernetes Providers": {
"message": "通过托管 Kubernetes 提供商设置集群",
"description": "The label for category Set Up Clusters from Hosted Kubernetes Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Windows Clusters": {
"message": "使用 Windows 集群",
"description": "The label for category Use Windows Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Cloud Providers": {
"message": "设置 Cloud Provider",
"description": "The label for category Set Up Cloud Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Launch Kubernetes with Rancher": {
"message": "使用 Rancher 启动 Kubernetes",
"description": "The label for category Launch Kubernetes with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use New Nodes in an Infra Provider": {
"message": "在基础设施提供商中使用新节点",
"description": "The label for category Use New Nodes in an Infra Provider in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.vSphere": {
"message": "vSphere",
"description": "The label for category vSphere in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Nutanix": {
"message": "Nutanix",
"description": "The label for category Nutanix in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Resources Setup": {
"message": "Kubernetes 资源设置",
"description": "The label for category Kubernetes Resources Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Workloads and Pods": {
"message": "工作负载和 Pod",
"description": "The label for category Workloads and Pods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Horizontal Pod Autoscaler": {
"message": "Horizontal Pod Autoscaler",
"description": "The label for category Horizontal Pod Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Load Balancer and Ingress Controller": {
"message": "负载均衡和 Ingress Controller",
"description": "The label for category Load Balancer and Ingress Controller in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Helm Charts in Rancher": {
"message": "Rancher 中的 Helm Chart",
"description": "The label for category Helm Charts in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Apps Across Clusters": {
"message": "跨集群部署应用",
"description": "The label for category Deploy Apps Across Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup, Restore, and Disaster Recovery": {
"message": "备份、还原和灾难恢复",
"description": "The label for category Backup, Restore, and Disaster Recovery in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced User Guides": {
"message": "高级用户指南",
"description": "The label for category Advanced User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Projects": {
"message": "管理项目",
"description": "The label for category Manage Projects in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Project Resource Quotas": {
"message": "管理项目资源配额",
"description": "The label for category Manage Project Resource Quotas in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring/Alerting Guides": {
"message": "Monitoring/Alerting 指南",
"description": "The label for category Monitoring/Alerting Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator Guides": {
"message": "Prometheus Federator 指南",
"description": "The label for category Prometheus Federator Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration Guides": {
"message": "Monitoring V2 配置指南",
"description": "The label for category Monitoring V2 Configuration Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced Configuration": {
"message": "高级配置",
"description": "The label for category Advanced Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio Setup Guide": {
"message": "Istio 设置指南",
"description": "The label for category Istio Setup Guide in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scan Guides": {
"message": "CIS 扫描指南",
"description": "The label for category CIS Scan Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Enable Experimental Features": {
"message": "启用实验功能",
"description": "The label for category Enable Experimental Features in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Reference Guides": {
"message": "参考指南",
"description": "The label for category Reference Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Best Practices": {
"message": "最佳实践",
"description": "The label for category Best Practices in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server": {
"message": "Rancher Server",
"description": "The label for category Rancher Server in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher-Managed Clusters": {
"message": "Rancher 管理的集群",
"description": "The label for category Rancher-Managed Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Manager Architecture": {
"message": "Rancher Manager 架构",
"description": "The label for category Rancher Manager Architecture in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cluster Configuration": {
"message": "集群配置",
"description": "The label for category Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server Configuration": {
"message": "Rancher Server 配置",
"description": "The label for category Rancher Server Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.GKE Cluster Configuration": {
"message": "GKE 集群配置",
"description": "The label for category GKE Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Existing Nodes": {
"message": "使用现有节点",
"description": "The label for category Use Existing Nodes in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Downstream Cluster Configuration": {
"message": "下游集群配置",
"description": "The label for category Downstream Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Node Template Configuration": {
"message": "节点模板配置",
"description": "The label for category Node Template Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Machine Configuration": {
"message": "主机配置",
"description": "The label for category Machine Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Single-Node Rancher in Docker": {
"message": "Docker 中的单节点 Rancher",
"description": "The label for category Single-Node Rancher in Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup & Restore Configuration": {
"message": "备份和恢复配置",
"description": "The label for category Backup & Restore Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration": {
"message": "Monitoring V2 配置",
"description": "The label for category Monitoring V2 Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator": {
"message": "Prometheus Federator",
"description": "The label for category Prometheus Federator in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.User Settings": {
"message": "用户设置",
"description": "The label for category User Settings in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CLI with Rancher": {
"message": "Rancher CLI",
"description": "The label for category CLI with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About the API": {
"message": "关于 API",
"description": "The label for category About the API in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Security": {
"message": "Rancher 安全",
"description": "The label for category Rancher Security in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher v2.6 Hardening Guides": {
"message": "Rancher 2.6 强化指南",
"description": "The label for category Rancher v2.6 Hardening Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.SELinux RPM": {
"message": "SELinux RPM",
"description": "The label for category SELinux RPM in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Integrations in Rancher": {
"message": "Rancher 中的集成",
"description": "The label for category Integrations in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cloud Marketplace Integration": {
"message": "云市场集成",
"description": "The label for category Cloud Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.AWS Marketplace Integration": {
"message": "AWS Marketplace 集成",
"description": "The label for category AWS Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scans": {
"message": "CIS 扫描",
"description": "The label for category CIS Scans in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Fleet - GitOps at Scale": {
"message": "Fleet - 大规模的 GitOps",
"description": "The label for category Fleet - GitOps at Scale in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio": {
"message": "Istio",
"description": "The label for category Istio in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configuration Options": {
"message": "配置选项",
"description": "The label for category Configuration Options in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Logging": {
"message": "Logging",
"description": "The label for category Logging in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Custom Resource Configuration": {
"message": "自定义资源配置",
"description": "The label for category Custom Resource Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring and Alerting": {
"message": "监控和告警",
"description": "The label for category Monitoring and Alerting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.FAQ": {
"message": "常见问题",
"description": "The label for category FAQ in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Troubleshooting": {
"message": "故障排除",
"description": "The label for category Troubleshooting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Components": {
"message": "Kubernetes 组件",
"description": "The label for category Kubernetes Components in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Troubleshooting Tips": {
"message": "其他故障排除提示",
"description": "The label for category Other Troubleshooting Tips in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher v2.7 Hardening Guides": {
"message": "Rancher v2.7 强化指南",
"description": "The label for category Rancher v2.7 Hardening Guides in sidebar tutorialSidebar"
}
}
i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
+21 -10
View File
@@ -159,11 +159,23 @@ Rancher 不会验证你授予 Azure 应用程序的权限。我们仅支持使
在 Rancher UI 中，输入托管在 Azure 中的 AD 实例的信息以完成配置。
1. 登录到 Rancher。
1. 在左上角，单击 **☰ > 用户 & 认证**。
1. 在左侧导航栏，单击**认证**。
1. 单击 **AzureAD**。
1. 使用你在[复制 Azure 应用数据](#4-复制-azure-应用数据)时复制的信息，填写**配置 Azure AD 账号**的表单。
:::caution
Azure AD 帐户将被授予管理员权限，因为其详细信息将映射到 Rancher 本地主体帐户。在继续之前确保此权限级别是适当的。
:::
**对于标准或中国端点：**
下表介绍了你在 Azure 门户中复制的值与 Rancher 中字段的映射：
| Rancher 字段 | Azure 值 |
@@ -173,20 +185,19 @@ Rancher 不会验证你授予 Azure 应用程序的权限。我们仅支持使
| 应用密文 | Key Value |
| 端点 | https://login.microsoftonline.com/ |
**对于自定义端点**：
**对于自定义端点**：
下表将你的自定义配置值映射到 Rancher 字段：
下表介绍了你在 Azure 门户中复制的自定义配置值与 Rancher 中字段的映射：
| Rancher 字段 | Azure 值 |
| ------------------ | ------------------------------------- |
| Graph 端点 | Microsoft Graph API Endpoint |
| Token 端点 | OAuth 2.0 Token Endpoint |
| Auth 端点 | OAuth 2.0 Authorization Endpoint |
| Rancher 字段 | Azure 值 |
| ------------------ | ------------------------------------- |
| Graph 端点 | Microsoft Graph API Endpoint |
| Token 端点 | OAuth 2.0 Token Endpoint |
| Auth 端点 | OAuth 2.0 Authorization Endpoint |
**重要提示**：在自定义配置中输入 Graph Endpoint 时，请从 URL 中删除 Tenant ID：
**重要提示**：在自定义配置中输入 Graph Endpoint 时，请从 URL 中删除 Tenant ID，如下所示：
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
1. 点击**启用**。
i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets.md
+2
View File
@@ -63,6 +63,8 @@ title: 密文
**结果**：密文已添加到你选择的项目中。你可以在 Rancher UI 中单击**存储 > 密文**或**更多资源 > 核心 > 密文**来查看密文。
由于项目范围的 Secret 是在项目级别设置的，因此在命名空间级别所做的任何更改都将被覆盖。
:::note
local 集群上的项目级别密文仅在选择单个项目时可见。
i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/vsphere/create-credentials.md
+1
View File
@@ -8,6 +8,7 @@ title: 在 vSphere 控制台中创建凭证
| 特权组 | 操作 |
|:----------------------|:-----------------------------------------------------------------------|
| Cns Privileges | Searchable |
| Datastore | AllocateSpace <br/> Browse <br/> FileManagement (Low level file operations) <br/> UpdateVirtualMachineFiles <br/> UpdateVirtualMachineMetadata |
| 全局 | Set custom attribute |
| 网络 | Assign |
i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/manage-clusters/provisioning-storage-examples/vsphere-storage.md
+2 -2
View File
@@ -20,8 +20,8 @@ title: vSphere 存储
:::
1. 点击 **☰ > 集群管理**。
1. 转到要配置 vSphere 存储的集群。
1. 在左侧导航栏中，单击**存储 > 存储类**。
1. 选择要使用 vSphere 存储的集群，然后单击**浏览**。
1. 在左侧导航栏中，选择**存储 > StorageClass**。
1. 单击**创建**。
3. 输入存储类的**名称**。
4. 在 **Provisioner**下，选择 **VMWare vSphere 卷**。
i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/custom-resource-configuration/flows-and-clusterflows.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Flows 和 ClusterFlows
---
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Banzai Cloud Logging Operator 文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/)。
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Logging Operator 文档](https://kube-logging.github.io/docs/configuration/flow/)。
有关如何解决 Logging 缓冲区的内存问题，请参阅 [Rancher 与 Logging 服务的集成：故障排除](../../../pages-for-subheaders/logging.md#日志缓冲区导致-pod-过载)。
@@ -14,7 +14,7 @@ title: Flows 和 ClusterFlows
你可以通过在 Rancher UI 中填写表单来配置 `Flow`。
有关 `Flow` 自定义资源的更多详细信息，请参阅 [FlowSpec](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/)。
有关 `Flow` 自定义资源的更多详细信息，请参阅 [FlowSpec](https://kube-logging.github.io/docs/configuration/crds/v1beta1/flow_types/)。
### Matches
@@ -24,13 +24,13 @@ title: Flows 和 ClusterFlows
你可以通过填写 Rancher UI 中的 `Flow` 或 `ClusterFlow` 表单来配置匹配。
使用 match 语句的详细示例，请参阅[日志路由的官方文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/)。
使用 match 语句的详细示例，请参阅[日志路由的官方文档](https://kube-logging.github.io/docs/configuration/log-routing/)。
### Filters
你可以在 `Flow` 中定义一个或多个过滤器。过滤器可以对日志执行各种操作，例如，添加其他数据、转换日志或解析记录中的值。`Flow` 中的过滤器会按定义的顺序应用。
有关 Banzai Cloud Logging Operator 支持的过滤器列表，请参阅[此页面](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/)。
有关 Logging Operator 支持的过滤器列表，请参阅 [Fluentd 过滤器的官方文档](https://kube-logging.github.io/docs/configuration/plugins/filters/)。
过滤器需要在 YAML 中配置。
i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/custom-resource-configuration/outputs-and-clusteroutputs.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Outputs 和 ClusterOutputs
---
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Banzai Cloud Logging Operator 文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/)。
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Logging Operator 文档](https://kube-logging.github.io/docs/configuration/flow/)。
有关如何解决 Logging 缓冲区的内存问题，请参阅 [Rancher 与 Logging 服务的集成：故障排除](../../../pages-for-subheaders/logging.md#日志缓冲区导致-pod-过载)。
@@ -16,7 +16,7 @@ title: Outputs 和 ClusterOutputs
你可以通过在 Rancher UI 中填写表单来配置 `Output`。
有关 `Output` 自定义资源的更多详细信息，请参阅 [OutputSpec](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/)。
有关 `Output` 自定义资源的更多详细信息，请参阅 [OutputSpec](https://kube-logging.github.io/docs/configuration/crds/v1beta1/output_types/)。
Rancher UI 提供了用于配置以下类型 `Output` 的表单：
@@ -40,7 +40,7 @@ Rancher UI 提供了用于配置以下类型 `Output` 的表单：
Rancher UI 提供了用于配置 `Output` 类型、目标和访问凭证（如果适用）的表单。
有关 Logging Operator 支持的日志插件配置示例，请参阅 [Logging Operator 文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/)。
有关 Logging Operator 支持的日志插件配置示例，请参阅 [Logging Operator 文档](https://kube-logging.github.io/docs/configuration/plugins/outputs/)。
## ClusterOutputs
@@ -48,7 +48,7 @@ Rancher UI 提供了用于配置 `Output` 类型、目标和访问凭证（如
你可以通过在 Rancher UI 中填写表单来配置 `ClusterOutput`。
有关 `ClusterOutput` 自定义资源的更多详细信息，请参阅 [ClusterOutput](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)。
有关 `ClusterOutput` 自定义资源的更多详细信息，请参阅 [ClusterOutput](https://kube-logging.github.io/docs/configuration/crds/v1beta1/clusteroutput_types/)。
## YAML 示例
i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging-architecture.md
+5 -5
View File
@@ -4,9 +4,9 @@ title: 架构
本节介绍了 Rancher Logging 应用程序的架构。
有关 Banzai Cloud Logging Operator 工作原理的更多详细信息，请参阅[官方文档](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)。
有关 Logging Operator 工作原理的更多详细信息，请参阅[官方文档](https://kube-logging.github.io/docs/#architecture)。
### Banzai Cloud Logging Operator 工作原理
### Logging Operator 工作原理
Logging Operator 自动部署和配置 Kubernetes 日志流水线。它会在每个节点上部署和配置一个 Fluent Bit DaemonSet，从而收集节点文件系统中的容器和应用程序日志。
@@ -21,8 +21,8 @@ Fluent Bit 查询 Kubernetes API 并使用 pod 的元数据来丰富日志，然
每个 `Flow` 都必须引用一个 `Output`，而每个 `ClusterFlow` 都必须引用一个 `ClusterOutput`。
[Banzai 文档](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)中的下图显示了新的 Logging 架构：
[Logging Operator 文档](https://kube-logging.github.io/docs/#architecture)中的下图显示了新的 Logging 架构：
<figcaption>Banzai Cloud Logging Operator 如何与 Fluentd 和 Fluent Bit 一起使用</figcaption>
<figcaption>Logging Operator 如何与 Fluentd 和 Fluent Bit 一起使用</figcaption>
![Banzai Cloud Logging Operator 如何与 Fluentd 一起使用](/img/banzai-cloud-logging-operator.png)
![Logging Operator 如何与 Fluentd 一起使用](/img/banzai-cloud-logging-operator.png)
i18n/zh/docusaurus-plugin-content-docs/current/pages-for-subheaders/deploy-rancher-manager.md
-1
View File
@@ -5,7 +5,6 @@ title: 部署 Rancher Server
你可使用以下指南之一，在你选择的提供商中部署和配置 Rancher 和 Kubernetes 集群。
- [AWS](../getting-started/quick-start-guides/deploy-rancher-manager/aws.md)（使用 Terraform）
- [AWS Marketplace](../getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md)（使用 Amazon EKS）
- [Azure](../getting-started/quick-start-guides/deploy-rancher-manager/azure.md)（使用 Terraform）
- [DigitalOcean](../getting-started/quick-start-guides/deploy-rancher-manager/digitalocean.md)（使用 Terraform）
- [GCP](../getting-started/quick-start-guides/deploy-rancher-manager/gcp.md)（使用 Terraform）
i18n/zh/docusaurus-plugin-content-docs/current/pages-for-subheaders/installation-requirements.md
+9 -29
View File
@@ -11,41 +11,21 @@ description: 如果 Rancher 配置在 Docker 或 Kubernetes 中运行时，了
:::
请确保安装 Rancher Server 的节点满足以下要求：
Rancher UI 在基于 Firefox 或 Chromium 的浏览器（Chrome、Edge、Opera、Brave）中效果最佳。
- [操作系统和容器运行时要求](#操作系统和容器运行时要求)
- [RKE 要求](#rke-要求)
- [K3s 要求](#k3s-要求)
- [RKE2 要求](#rke2-要求)
- [安装 Docker](#安装-docker)
- [硬件要求](#硬件要求)
- [CPU 和内存](#cpu-和内存)
- [RKE 和托管 Kubernetes](#rke-和托管-kubernetes)
- [K3s Kubernetes](#k3s-kubernetes)
- [RKE2 Kubernetes](#rke2-kubernetes)
- [Docker](#docker)
- [Ingress](#ingress)
- [磁盘](#磁盘)
- [网络要求](#网络要求)
- [节点 IP 地址](#节点-ip-地址)
- [端口要求](#端口要求)
- [Dockershim 支持](#dockershim-支持)
查看我们的[最佳实践](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)页面，获取在生产环境中运行 Rancher Server 的建议。
如需获取在生产环境中运行 Rancher Server 的最佳实践列表，请参见[最佳实践](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)。
## Kubernetes 与 Rancher 的兼容性
Rancher UI 在基于 Firefox 或 Chromium 的浏览器（Chrome、Edge、Opera、Brave 等）中效果最佳。
Rancher 需要安装在支持的 Kubernetes 版本上。请查阅 [Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix)，确保你的 Kubernetes 版本受支持。
## 操作系统和容器运行时要求
Rancher 兼容当前所有的主流 Linux 发行版。
所有支持的操作系统都使用 64-bit x86 架构。Rancher 兼容当前所有的主流 Linux 发行版。
运行 RKE Kubernetes 集群的节点需要安装 Docker。RKE2 或 K3s 集群不需要它。
[Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix)列出了每个 Rancher 版本测试过的操作系统和 Docker 版本。
Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的 Rancher 版本支持哪些 Kubernetes 版本，请参见[支持维护条款](https://rancher.com/support-maintenance-terms/)。
如需了解各个 Rancher 版本通过了哪些操作系统和 Docker 版本测试，请参见[支持和维护条款](https://rancher.com/support-maintenance-terms/)。
所有支持的操作系统都使用 64-bit x86 架构。
运行 RKE 集群的节点需要安装 Docker。RKE2 或 K3s 集群不需要它。
请安装 `ntp`（Network Time Protocol），以防止在客户端和服务器之间由于时间不同步造成的证书验证错误。
@@ -65,7 +45,7 @@ Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的
对于容器运行时，K3s 默认附带了自己的 containerd。你也可以将 K3s 配置为使用已安装的 Docker 运行时。有关在 Docker 中使用 K3s 的更多信息，请参阅 [K3s 文档](https://docs.k3s.io/advanced#using-docker-as-the-container-runtime)。
Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的 Rancher 版本支持哪些 Kubernetes 版本，请参见[支持维护条款](https://rancher.com/support-maintenance-terms/)。如需指定 K3s 版本，请在运行 K3s 安装脚本时，使用 `INSTALL_K3S_VERSION` 环境变量。
Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的 Rancher 版本支持哪些 Kubernetes 版本，请参见 [Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix)。如需指定 K3s 版本，在运行 K3s 安装脚本时，使用 `INSTALL_K3S_VERSION` 环境变量。
如果你使用 **Raspbian Buster** 在 K3s 集群上安装 Rancher，请按照[这些步骤](https://rancher.com/docs/k3s/latest/en/advanced/#enabling-legacy-iptables-on-raspbian-buster)切换到旧版 iptables。
@@ -75,7 +55,7 @@ Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的
对于容器运行时，RKE2 附带了自己的 containerd。RKE2 安装不需要 Docker。
如需了解 RKE2 通过了哪些操作系统版本的测试，请参见[支持和维护条款](https://rancher.com/support-maintenance-terms/)。
如需了解 RKE2 通过了哪些操作系统版本的测试，请参见 [Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix)。
## 硬件要求
i18n/zh/docusaurus-plugin-content-docs/current/pages-for-subheaders/logging.md
+2 -2
View File
@@ -3,7 +3,7 @@ title: Rancher Logging 集成
description: Rancher 集成了主流的日志服务。了解集成日志服务的要求和优势，并在你的集群上启用 Logging。
---
现在，Rancher 的日志管理由 [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) 提供支持，它取代了以前的内部解决方案。
现在，Rancher 的日志管理由 [Logging operator](https://kube-logging.github.io/docs/) 提供支持，它取代了以前的内部解决方案。
有关 Rancher 2.5 更改的概述，请参阅[本节](../integrations-in-rancher/logging/logging-architecture.md#rancher-2-5-变更)。
@@ -88,7 +88,7 @@ Windows 集群支持 Logging，你可以收集 Windows 节点的日志。
根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。
有关如何配置日志缓冲区来满足企业需求的更完整说明，请参阅 [缓冲区](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/buffer/)和 [Fluentd 配置](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/fluentd/)的官方 BanzaiCloud 文档。
有关如何配置日志缓冲区来满足企业需求的更完整说明，请参阅[缓冲区](https://kube-logging.github.io/docs/configuration/plugins/outputs/buffer/)和 [Fluentd 配置](https://kube-logging.github.io/docs/logging-infrastructure/fluentd/)的官方 Logging Operator 文档。
### `cattle-logging` 命名空间正在重新创建
i18n/zh/docusaurus-plugin-content-docs/current/pages-for-subheaders/manage-project-resource-quotas.md
+7 -1
View File
@@ -20,7 +20,13 @@ Rancher 中的资源配额包含与 [Kubernetes 原生版本](https://kubernetes
1. 在左上角，单击 **☰ > 集群管理**。
1. 在**集群**页面，进入要应用资源配额的集群，然后单击 **Explore**。
1. 单击**集群 > 项目/命名空间**。
1. 找到要添加资源配额的项目。在该项目中选择 **⋮ > 编辑配置**。
1. 确保 **Projects/Namespaces** 页面处于 **Group by Project** 视图模式。
![Screenshot highlighting the "Group by Project" icon, above the list of projects. It resembles a folder.](/img/edit-project-config-for-resource-quotas-group-by-project.png)
1. 找到要添加资源配额的项目，选择与项目名称同行的 **⋮**。
![Screenshot highlighting triple dots icon at the end of the same row as the project name.](/img/edit-project-config-for-resource-quotas-dots.png)
1. 选择**编辑配置**。
1. 展开**资源限额**并单击**添加资源**。你也可以编辑现有配额。
i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/backup-restore-configuration/backup-configuration.md
+2 -2
View File
@@ -73,7 +73,7 @@ S3 存储位置包含以下配置字段：
1. **凭证密文**（可选）：如果你需要使用 AWS 访问密钥（access key）和密文密钥（secret key）来访问 S3 存储桶，请使用带有密钥和指令 `accessKey` 和 `secretKey` 的凭证来创建密文。它可以是任意一个命名空间。你可以点击[此处](#credentialsecret-示例)查看示例密文。如果运行 operator 的节点在 EC2 中，并且设置了允许它们访问 S3 的 IAM 权限，则此指令是不必要的（如[本节](#ec2-节点访问-s3-的-iam-权限)所述）。凭证密文下拉菜单列出了所有命名空间的密文。
1. **存储桶名称**：存储备份文件的 S3 存储桶的名称。
1. **区域**（可选）：S3 存储桶所在的 AWS [区域](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/)。配置 MinIO 时不需要该字段。
1. **文件夹**（可选）：S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。
1. **文件夹**（可选）：S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。如果此字段留空，则默认将备份文件存储在 S3 存储桶的根文件夹中。
1. **端点**：用于访问存储桶区域中的 S3 的[端点](https://docs.aws.amazon.com/general/latest/gr/s3.html)。
1. **端点 CA**（可选）：Base64 编码的 CA 证书。如需获取示例，请参见 [S3 兼容配置示例](#s3-存储配置示例)。
1. **跳过 TLS 验证**（可选）：如果你不使用 TLS，则设置为 `true`。
@@ -84,7 +84,7 @@ S3 存储位置包含以下配置字段：
| `credentialSecretName` | 如果你需要使用 AWS 访问密钥（access key）和密文密钥（secret key）来访问 S3 存储桶，请使用带有密钥和指令 `accessKey` 和 `secretKey` 的凭证来创建密文。它可以在任何命名空间中，只要你在 `credentialSecretNamespace` 中提供该命名空间。点击[这里](#credentialsecret-示例)查看示例密文。如果运行 operator 的节点在 EC2 中，并且设置了允许它们访问 S3 的 IAM 权限，则此指令是不必要的（如[本节](#ec2-节点访问-s3-的-iam-权限)所述）。 | |
| `credentialSecretNamespace` | 包含访问 S3 的凭证的密文的命名空间。如果运行 operator 的节点在 EC2 中，并且设置了允许它们访问 S3 的 IAM 权限，则此指令是不必要的（如[本节](#ec2-节点访问-s3-的-iam-权限)所述）。 | |
| `bucketName` | 存储备份文件的 S3 存储桶的名称。 | ✓ |
| `folder` | S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。 | |
| `folder` | S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。如果此字段留空，则默认将备份文件存储在 S3 存储桶的根文件夹中。 | |
| `region` | S3 存储桶所在的 AWS [区域](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/)。 | ✓ |
| `endpoint` | 用于访问存储桶区域中的 S3 的[端点](https://docs.aws.amazon.com/general/latest/gr/s3.html)。 | ✓ |
| `endpointCA` | Base64 编码的 CA 证书。如需获取示例，请参见 [S3 兼容配置示例](#s3-存储配置示例)。 | |
i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/backup-restore-configuration/storage-configuration.md
+1 -1
View File
@@ -20,7 +20,7 @@ title: 备份存储位置配置
| 凭证密文 | 从 Rancher 的密文中选择 S3 的凭证。[示例](examples.md#在-s3-中存储备份的凭证密文示例)。 |
| 存储桶名称 | 存储备份的 [S3 存储桶](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html)的名称。默认值：`rancherbackups`。 |
| 区域 | S3 存储桶所在的 [AWS 区域](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/)。 |
| 文件夹 | 存储备份的 [S3 存储桶中的文件夹](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html)。 |
| 文件夹 | 存储备份的 [S3 存储桶中的文件夹](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html)。如果此字段留空，则默认将备份文件存储在 S3 存储桶的根文件夹中。 |
| 端点 | [S3 端点](https://docs.aws.amazon.com/general/latest/gr/s3.html)，例如 `s3.us-west-2.amazonaws.com`。 |
| Endpoint CA | 用于 S3 端点的 CA 证书。默认值：base64 编码的 CA 证书。 |
| insecureTLSSkipVerify | 如果你不使用 TLS，则设置为 `true`。 |
i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/best-practices/rancher-managed-clusters/logging-best-practices.md
+2 -2
View File
@@ -12,7 +12,7 @@ title: Logging 最佳实践
现在，Rancher 的日志聚合更加灵活。通过新的 Logging 的功能，管理员和用户都可以部署符合细粒度收集标准的日志记录，同时提供更多的目标和配置选项。
Rancher 的 Logging 使用的是 Banzai Cloud logging operator。我们让你可以管理这个 operator 及其资源，并将它的管理功能和 Rancher 集群管理联系起来。
Rancher Logging 使用的是 [Logging Operator](https://github.com/kube-logging/logging-operator)。我们让你可以管理这个 operator 及其资源，并将它的管理功能和 Rancher 集群管理联系起来。
## 集群级别日志
@@ -44,7 +44,7 @@ Rancher 的 Logging 将读取 `/var/log/containers` 中的所有日志条目，
日志收集仅从 Kubernetes 中的 Pod 中检索 `stdout`/`stderr` 日志。但是，我们也可能想从应用生成的其他文件中收集日志。在这种情况下，你可以使用一个（或两个）日志流 Sidecar。
设置日志流 Sidecar 的目的是获取写入磁盘的日志文件，并将其内容传输到 `stdout`。这样一来，Banzai Logging Operator 就可以接收这些日志，并把日志发送到目标输出位置。
设置日志流 Sidecar 的目的是获取写入磁盘的日志文件，并将其内容传输到 `stdout`。这样一来，Logging Operator 就可以接收这些日志，并把日志发送到目标输出位置。
要进行设置，编辑你的工作负载资源（例如 Deployment）并添加以下 Sidecar 定义：
i18n/zh/docusaurus-plugin-content-docs/version-2.5.json
-4
View File
@@ -315,10 +315,6 @@
"message": "About the API",
"description": "The label for category About the API in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Pipelines": {
"message": "Pipelines",
"description": "The label for category Pipelines in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Security": {
"message": "Rancher Security",
"description": "The label for category Rancher Security in sidebar tutorialSidebar"
i18n/zh/docusaurus-plugin-content-docs/version-2.6.json
+376 -381
View File
@@ -1,383 +1,378 @@
{
"version.label": {
"message": "v2.6",
"description": "The label for version 2.6"
},
"sidebar.tutorialSidebar.category.Getting Started": {
"message": "开始使用",
"description": "The label for category Getting Started in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Quick Start Guides": {
"message": "快速入门指南",
"description": "The label for category Quick Start Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Manager": {
"message": "部署 Rancher Manager",
"description": "The label for category Deploy Rancher Manager in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Workloads": {
"message": "部署 Rancher 工作负载",
"description": "The label for category Deploy Rancher Workloads in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation and Upgrade": {
"message": "安装和升级",
"description": "The label for category Installation and Upgrade in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation Requirements": {
"message": "安装要求",
"description": "The label for category Installation Requirements in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation References": {
"message": "安装参考",
"description": "The label for category Installation References in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install/Upgrade on a Kubernetes Cluster": {
"message": "在 Kubernetes 集群上安装\/升级",
"description": "The label for category Install/Upgrade on a Kubernetes Cluster in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Installation Methods": {
"message": "其他安装方式",
"description": "The label for category Other Installation Methods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Air-Gapped Helm CLI Install": {
"message": "离线 Helm CLI 安装",
"description": "The label for category Air-Gapped Helm CLI Install in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher on a Single Node with Docker": {
"message": "使用 Docker 将 Rancher 安装到单个节点中",
"description": "The label for category Rancher on a Single Node with Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Behind an HTTP Proxy": {
"message": "HTTP 代理后的 Rancher",
"description": "The label for category Rancher Behind an HTTP Proxy in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Resources": {
"message": "资源",
"description": "The label for category Resources in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.How-to Guides": {
"message": "操作指南",
"description": "The label for category How-to Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.New User Guides": {
"message": "新用户指南",
"description": "The label for category New User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication, Permissions, and Global Configuration": {
"message": "身份验证、权限和全局配置",
"description": "The label for category Authentication, Permissions, and Global Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication Config": {
"message": "身份验证配置",
"description": "The label for category Authentication Config in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure OpenLDAP": {
"message": "配置 OpenLDAP",
"description": "The label for category Configure OpenLDAP in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Microsoft AD Federation Service (SAML)": {
"message": "配置 Microsoft AD FS (SAML)",
"description": "The label for category Configure Microsoft AD Federation Service (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Shibboleth (SAML)": {
"message": "配置 Shibboleth (SAML)",
"description": "The label for category Configure Shibboleth (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Role-Based Access Control (RBAC)": {
"message": "管理 RBAC",
"description": "The label for category Manage Role-Based Access Control (RBAC) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About Provisioning Drivers": {
"message": "关于 Provisioning 驱动",
"description": "The label for category About Provisioning Drivers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About RKE1 Templates": {
"message": "关于 RKE1 模板",
"description": "The label for category About RKE1 Templates in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Clusters": {
"message": "管理集群",
"description": "The label for category Manage Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Access Clusters": {
"message": "访问集群",
"description": "The label for category Access Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install Cluster Autoscaler": {
"message": "安装 Cluster Autoscaler",
"description": "The label for category Install Cluster Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Create Kubernetes Persistent Storage": {
"message": "创建 Kubernetes 持久存储",
"description": "The label for category Create Kubernetes Persistent Storage in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Provisioning Storage Examples": {
"message": "配置存储示例",
"description": "The label for category Provisioning Storage Examples in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Cluster Setup": {
"message": "Kubernetes 集群设置",
"description": "The label for category Kubernetes Cluster Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Infrastructure Setup": {
"message": "基础设施设置",
"description": "The label for category Infrastructure Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Clusters in Rancher Setup": {
"message": "Rancher 设置中的 Kubernetes 集群",
"description": "The label for category Kubernetes Clusters in Rancher Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Checklist for Production-Ready Clusters": {
"message": "生产就绪集群检查清单",
"description": "The label for category Checklist for Production-Ready Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Clusters from Hosted Kubernetes Providers": {
"message": "通过托管 Kubernetes 提供商设置集群",
"description": "The label for category Set Up Clusters from Hosted Kubernetes Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Windows Clusters": {
"message": "使用 Windows 集群",
"description": "The label for category Use Windows Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Cloud Providers": {
"message": "设置 Cloud Provider",
"description": "The label for category Set Up Cloud Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Launch Kubernetes with Rancher": {
"message": "使用 Rancher 启动 Kubernetes",
"description": "The label for category Launch Kubernetes with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use New Nodes in an Infra Provider": {
"message": "在基础设施提供商中使用新节点",
"description": "The label for category Use New Nodes in an Infra Provider in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.vSphere": {
"message": "vSphere",
"description": "The label for category vSphere in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Nutanix": {
"message": "Nutanix",
"description": "The label for category Nutanix in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Resources Setup": {
"message": "Kubernetes 资源设置",
"description": "The label for category Kubernetes Resources Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Workloads and Pods": {
"message": "工作负载和 Pod",
"description": "The label for category Workloads and Pods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Horizontal Pod Autoscaler": {
"message": "Horizontal Pod Autoscaler",
"description": "The label for category Horizontal Pod Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Load Balancer and Ingress Controller": {
"message": "负载均衡和 Ingress Controller",
"description": "The label for category Load Balancer and Ingress Controller in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Helm Charts in Rancher": {
"message": "Rancher 中的 Helm Chart",
"description": "The label for category Helm Charts in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Apps Across Clusters": {
"message": "跨集群部署应用",
"description": "The label for category Deploy Apps Across Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup, Restore, and Disaster Recovery": {
"message": "备份、还原和灾难恢复",
"description": "The label for category Backup, Restore, and Disaster Recovery in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced User Guides": {
"message": "高级用户指南",
"description": "The label for category Advanced User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Projects": {
"message": "管理项目",
"description": "The label for category Manage Projects in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Project Resource Quotas": {
"message": "管理项目资源配额",
"description": "The label for category Manage Project Resource Quotas in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring/Alerting Guides": {
"message": "Monitoring\/Alerting 指南",
"description": "The label for category Monitoring/Alerting Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator Guides": {
"message": "Prometheus Federator 指南",
"description": "The label for category Prometheus Federator Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration Guides": {
"message": "Monitoring V2 配置指南",
"description": "The label for category Monitoring V2 Configuration Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced Configuration": {
"message": "高级配置",
"description": "The label for category Advanced Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio Setup Guide": {
"message": "Istio 设置指南",
"description": "The label for category Istio Setup Guide in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scan Guides": {
"message": "CIS 扫描指南",
"description": "The label for category CIS Scan Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Enable Experimental Features": {
"message": "启用实验功能",
"description": "The label for category Enable Experimental Features in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Reference Guides": {
"message": "参考指南",
"description": "The label for category Reference Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Best Practices": {
"message": "最佳实践",
"description": "The label for category Best Practices in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server": {
"message": "Rancher Server",
"description": "The label for category Rancher Server in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher-Managed Clusters": {
"message": "Rancher 管理的集群",
"description": "The label for category Rancher-Managed Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Manager Architecture": {
"message": "Rancher Manager 架构",
"description": "The label for category Rancher Manager Architecture in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cluster Configuration": {
"message": "集群配置",
"description": "The label for category Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server Configuration": {
"message": "Rancher Server 配置",
"description": "The label for category Rancher Server Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.GKE Cluster Configuration": {
"message": "GKE 集群配置",
"description": "The label for category GKE Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Existing Nodes": {
"message": "使用现有节点",
"description": "The label for category Use Existing Nodes in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Downstream Cluster Configuration": {
"message": "下游集群配置",
"description": "The label for category Downstream Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Node Template Configuration": {
"message": "节点模板配置",
"description": "The label for category Node Template Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Machine Configuration": {
"message": "主机配置",
"description": "The label for category Machine Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Single-Node Rancher in Docker": {
"message": "Docker 中的单节点 Rancher",
"description": "The label for category Single-Node Rancher in Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Amazon EKS Permissions": {
"message": "Amazon EKS 权限",
"description": "The label for category Amazon EKS Permissions in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup & Restore Configuration": {
"message": "备份和恢复配置",
"description": "The label for category Backup & Restore Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration": {
"message": "Monitoring V2 配置",
"description": "The label for category Monitoring V2 Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator": {
"message": "Prometheus Federator",
"description": "The label for category Prometheus Federator in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.User Settings": {
"message": "用户设置",
"description": "The label for category User Settings in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CLI with Rancher": {
"message": "Rancher CLI",
"description": "The label for category CLI with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About the API": {
"message": "关于 API",
"description": "The label for category About the API in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Pipelines": {
"message": "流水线",
"description": "The label for category Pipelines in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Security": {
"message": "Rancher 安全",
"description": "The label for category Rancher Security in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher v2.6 Hardening Guides": {
"message": "Rancher 2.6 强化指南",
"description": "The label for category Rancher v2.6 Hardening Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.SELinux RPM": {
"message": "SELinux RPM",
"description": "The label for category SELinux RPM in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Integrations in Rancher": {
"message": "Rancher 中的集成",
"description": "The label for category Integrations in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cloud Marketplace Integration": {
"message": "云市场集成",
"description": "The label for category Cloud Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.AWS Marketplace Integration": {
"message": "AWS Marketplace 集成",
"description": "The label for category AWS Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scans": {
"message": "CIS 扫描",
"description": "The label for category CIS Scans in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Fleet - GitOps at Scale": {
"message": "Fleet - 大规模的 GitOps",
"description": "The label for category Fleet - GitOps at Scale in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio": {
"message": "Istio",
"description": "The label for category Istio in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configuration Options": {
"message": "配置选项",
"description": "The label for category Configuration Options in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Logging": {
"message": "Logging",
"description": "The label for category Logging in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Custom Resource Configuration": {
"message": "自定义资源配置",
"description": "The label for category Custom Resource Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring and Alerting": {
"message": "监控和告警",
"description": "The label for category Monitoring and Alerting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.FAQ": {
"message": "常见问题",
"description": "The label for category FAQ in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Troubleshooting": {
"message": "故障排除",
"description": "The label for category Troubleshooting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Components": {
"message": "Kubernetes 组件",
"description": "The label for category Kubernetes Components in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Troubleshooting Tips": {
"message": "其他故障排除提示",
"description": "The label for category Other Troubleshooting Tips in sidebar tutorialSidebar"
}
"version.label": {
"message": "v2.6",
"description": "The label for version 2.6"
},
"sidebar.tutorialSidebar.category.Getting Started": {
"message": "开始使用",
"description": "The label for category Getting Started in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Quick Start Guides": {
"message": "快速入门指南",
"description": "The label for category Quick Start Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Manager": {
"message": "部署 Rancher Manager",
"description": "The label for category Deploy Rancher Manager in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Rancher Workloads": {
"message": "部署 Rancher 工作负载",
"description": "The label for category Deploy Rancher Workloads in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation and Upgrade": {
"message": "安装和升级",
"description": "The label for category Installation and Upgrade in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation Requirements": {
"message": "安装要求",
"description": "The label for category Installation Requirements in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Installation References": {
"message": "安装参考",
"description": "The label for category Installation References in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install/Upgrade on a Kubernetes Cluster": {
"message": "在 Kubernetes 集群上安装/升级",
"description": "The label for category Install/Upgrade on a Kubernetes Cluster in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Installation Methods": {
"message": "其他安装方式",
"description": "The label for category Other Installation Methods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Air-Gapped Helm CLI Install": {
"message": "离线 Helm CLI 安装",
"description": "The label for category Air-Gapped Helm CLI Install in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher on a Single Node with Docker": {
"message": "使用 Docker 将 Rancher 安装到单个节点中",
"description": "The label for category Rancher on a Single Node with Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Behind an HTTP Proxy": {
"message": "HTTP 代理后的 Rancher",
"description": "The label for category Rancher Behind an HTTP Proxy in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Resources": {
"message": "资源",
"description": "The label for category Resources in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.How-to Guides": {
"message": "操作指南",
"description": "The label for category How-to Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.New User Guides": {
"message": "新用户指南",
"description": "The label for category New User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication, Permissions, and Global Configuration": {
"message": "身份验证、权限和全局配置",
"description": "The label for category Authentication, Permissions, and Global Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Authentication Config": {
"message": "身份验证配置",
"description": "The label for category Authentication Config in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure OpenLDAP": {
"message": "配置 OpenLDAP",
"description": "The label for category Configure OpenLDAP in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Microsoft AD Federation Service (SAML)": {
"message": "配置 Microsoft AD FS (SAML)",
"description": "The label for category Configure Microsoft AD Federation Service (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configure Shibboleth (SAML)": {
"message": "配置 Shibboleth (SAML)",
"description": "The label for category Configure Shibboleth (SAML) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Role-Based Access Control (RBAC)": {
"message": "管理 RBAC",
"description": "The label for category Manage Role-Based Access Control (RBAC) in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About Provisioning Drivers": {
"message": "关于 Provisioning 驱动",
"description": "The label for category About Provisioning Drivers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About RKE1 Templates": {
"message": "关于 RKE1 模板",
"description": "The label for category About RKE1 Templates in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Clusters": {
"message": "管理集群",
"description": "The label for category Manage Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Access Clusters": {
"message": "访问集群",
"description": "The label for category Access Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Install Cluster Autoscaler": {
"message": "安装 Cluster Autoscaler",
"description": "The label for category Install Cluster Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Create Kubernetes Persistent Storage": {
"message": "创建 Kubernetes 持久存储",
"description": "The label for category Create Kubernetes Persistent Storage in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Provisioning Storage Examples": {
"message": "配置存储示例",
"description": "The label for category Provisioning Storage Examples in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Cluster Setup": {
"message": "Kubernetes 集群设置",
"description": "The label for category Kubernetes Cluster Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Infrastructure Setup": {
"message": "基础设施设置",
"description": "The label for category Infrastructure Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Clusters in Rancher Setup": {
"message": "Rancher 设置中的 Kubernetes 集群",
"description": "The label for category Kubernetes Clusters in Rancher Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Checklist for Production-Ready Clusters": {
"message": "生产就绪集群检查清单",
"description": "The label for category Checklist for Production-Ready Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Clusters from Hosted Kubernetes Providers": {
"message": "通过托管 Kubernetes 提供商设置集群",
"description": "The label for category Set Up Clusters from Hosted Kubernetes Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Windows Clusters": {
"message": "使用 Windows 集群",
"description": "The label for category Use Windows Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Set Up Cloud Providers": {
"message": "设置 Cloud Provider",
"description": "The label for category Set Up Cloud Providers in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Launch Kubernetes with Rancher": {
"message": "使用 Rancher 启动 Kubernetes",
"description": "The label for category Launch Kubernetes with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use New Nodes in an Infra Provider": {
"message": "在基础设施提供商中使用新节点",
"description": "The label for category Use New Nodes in an Infra Provider in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.vSphere": {
"message": "vSphere",
"description": "The label for category vSphere in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Nutanix": {
"message": "Nutanix",
"description": "The label for category Nutanix in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Resources Setup": {
"message": "Kubernetes 资源设置",
"description": "The label for category Kubernetes Resources Setup in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Workloads and Pods": {
"message": "工作负载和 Pod",
"description": "The label for category Workloads and Pods in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Horizontal Pod Autoscaler": {
"message": "Horizontal Pod Autoscaler",
"description": "The label for category Horizontal Pod Autoscaler in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Load Balancer and Ingress Controller": {
"message": "负载均衡和 Ingress Controller",
"description": "The label for category Load Balancer and Ingress Controller in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Helm Charts in Rancher": {
"message": "Rancher 中的 Helm Chart",
"description": "The label for category Helm Charts in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Deploy Apps Across Clusters": {
"message": "跨集群部署应用",
"description": "The label for category Deploy Apps Across Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup, Restore, and Disaster Recovery": {
"message": "备份、还原和灾难恢复",
"description": "The label for category Backup, Restore, and Disaster Recovery in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced User Guides": {
"message": "高级用户指南",
"description": "The label for category Advanced User Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Projects": {
"message": "管理项目",
"description": "The label for category Manage Projects in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Manage Project Resource Quotas": {
"message": "管理项目资源配额",
"description": "The label for category Manage Project Resource Quotas in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring/Alerting Guides": {
"message": "Monitoring/Alerting 指南",
"description": "The label for category Monitoring/Alerting Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator Guides": {
"message": "Prometheus Federator 指南",
"description": "The label for category Prometheus Federator Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration Guides": {
"message": "Monitoring V2 配置指南",
"description": "The label for category Monitoring V2 Configuration Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Advanced Configuration": {
"message": "高级配置",
"description": "The label for category Advanced Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio Setup Guide": {
"message": "Istio 设置指南",
"description": "The label for category Istio Setup Guide in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scan Guides": {
"message": "CIS 扫描指南",
"description": "The label for category CIS Scan Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Enable Experimental Features": {
"message": "启用实验功能",
"description": "The label for category Enable Experimental Features in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Reference Guides": {
"message": "参考指南",
"description": "The label for category Reference Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Best Practices": {
"message": "最佳实践",
"description": "The label for category Best Practices in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server": {
"message": "Rancher Server",
"description": "The label for category Rancher Server in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher-Managed Clusters": {
"message": "Rancher 管理的集群",
"description": "The label for category Rancher-Managed Clusters in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Manager Architecture": {
"message": "Rancher Manager 架构",
"description": "The label for category Rancher Manager Architecture in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cluster Configuration": {
"message": "集群配置",
"description": "The label for category Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Server Configuration": {
"message": "Rancher Server 配置",
"description": "The label for category Rancher Server Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.GKE Cluster Configuration": {
"message": "GKE 集群配置",
"description": "The label for category GKE Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Use Existing Nodes": {
"message": "使用现有节点",
"description": "The label for category Use Existing Nodes in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Downstream Cluster Configuration": {
"message": "下游集群配置",
"description": "The label for category Downstream Cluster Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Node Template Configuration": {
"message": "节点模板配置",
"description": "The label for category Node Template Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Machine Configuration": {
"message": "主机配置",
"description": "The label for category Machine Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Single-Node Rancher in Docker": {
"message": "Docker 中的单节点 Rancher",
"description": "The label for category Single-Node Rancher in Docker in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Backup & Restore Configuration": {
"message": "备份和恢复配置",
"description": "The label for category Backup & Restore Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring V2 Configuration": {
"message": "Monitoring V2 配置",
"description": "The label for category Monitoring V2 Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Prometheus Federator": {
"message": "Prometheus Federator",
"description": "The label for category Prometheus Federator in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.User Settings": {
"message": "用户设置",
"description": "The label for category User Settings in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CLI with Rancher": {
"message": "Rancher CLI",
"description": "The label for category CLI with Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.About the API": {
"message": "关于 API",
"description": "The label for category About the API in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Pipelines": {
"message": "流水线",
"description": "The label for category Pipelines in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher Security": {
"message": "Rancher 安全",
"description": "The label for category Rancher Security in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Rancher v2.6 Hardening Guides": {
"message": "Rancher 2.6 强化指南",
"description": "The label for category Rancher v2.6 Hardening Guides in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.SELinux RPM": {
"message": "SELinux RPM",
"description": "The label for category SELinux RPM in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Integrations in Rancher": {
"message": "Rancher 中的集成",
"description": "The label for category Integrations in Rancher in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Cloud Marketplace Integration": {
"message": "云市场集成",
"description": "The label for category Cloud Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.AWS Marketplace Integration": {
"message": "AWS Marketplace 集成",
"description": "The label for category AWS Marketplace Integration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.CIS Scans": {
"message": "CIS 扫描",
"description": "The label for category CIS Scans in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Fleet - GitOps at Scale": {
"message": "Fleet - 大规模的 GitOps",
"description": "The label for category Fleet - GitOps at Scale in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Istio": {
"message": "Istio",
"description": "The label for category Istio in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Configuration Options": {
"message": "配置选项",
"description": "The label for category Configuration Options in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Logging": {
"message": "Logging",
"description": "The label for category Logging in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Custom Resource Configuration": {
"message": "自定义资源配置",
"description": "The label for category Custom Resource Configuration in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Monitoring and Alerting": {
"message": "监控和告警",
"description": "The label for category Monitoring and Alerting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.FAQ": {
"message": "常见问题",
"description": "The label for category FAQ in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Troubleshooting": {
"message": "故障排除",
"description": "The label for category Troubleshooting in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Kubernetes Components": {
"message": "Kubernetes 组件",
"description": "The label for category Kubernetes Components in sidebar tutorialSidebar"
},
"sidebar.tutorialSidebar.category.Other Troubleshooting Tips": {
"message": "其他故障排除提示",
"description": "The label for category Other Troubleshooting Tips in sidebar tutorialSidebar"
}
}
i18n/zh/docusaurus-plugin-content-docs/version-2.6/getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md
+1 -1
View File
@@ -3,4 +3,4 @@ title: Rancher AWS Marketplace 快速入门
description: 使用 Amazon EKS 部署 Rancher Server。
---
你可以在 AWS 中使用 Amazon EKS 部署 Rancher Server。详情请参见我们的 [Amazon Marketplace 列表](https://aws.amazon.com/marketplace/pp/prodview-go7ent7goo5ae)。
Amazon Elastic Kubernetes Service (EKS) 可以快速[将 Rancher 部署到 Amazon Web Services (AWS)](https://documentation.suse.com/trd/kubernetes/single-html/gs_rancher_aws-marketplace/)。详情请参见我们的 [Amazon Marketplace 列表](https://aws.amazon.com/marketplace/pp/prodview-go7ent7goo5ae)。观看 [demo](https://youtu.be/9dznJ7Ons0M)，了解 AWS Marketplace SUSE Rancher 设置的演练。
i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
+22 -15
View File
@@ -127,8 +127,6 @@ Microsoft Graph API 现在是设置 Azure AD 的流程。下文将帮助[新用
#### 4. 复制 Azure 应用数据
这是在 Azure 中执行的的最后一步。你需要复制用于配置 Rancher 以进行 Azure AD 身份验证的数据，并将其粘贴到一个空文本文件中。
1. 获取你的 Rancher **租户 ID**。
1. 使用搜索打开 **App registrations**。
@@ -176,14 +174,24 @@ Microsoft Graph API 现在是设置 Azure AD 的流程。下文将帮助[新用
在 Rancher UI 中，输入托管在 Azure 中的 AD 实例的信息以完成配置。
输入你复制到[文本文件](#tip)的值。
1. 登录到 Rancher。
1. 在左上角，单击 **☰ > 用户 & 认证**。
1. 在左侧导航栏，单击**认证**。
1. 单击 **AzureAD**。
1. 使用你在[复制 Azure 应用数据](#4-复制-azure-应用数据)时复制的信息，填写**配置 Azure AD 账号**的表单。
:::caution
Azure AD 帐户将被授予管理员权限，因为其详细信息将映射到 Rancher 本地主体帐户。在继续之前确保此权限级别是适当的。
:::
**对于标准或中国端点：**
下表介绍了你在 Azure 门户中复制的值与 Rancher 中字段的映射：
| Rancher 字段 | Azure 值 |
@@ -193,20 +201,19 @@ Microsoft Graph API 现在是设置 Azure AD 的流程。下文将帮助[新用
| 应用密文 | Key Value |
| 端点 | https://login.microsoftonline.com/ |
**对于自定义端点**：
**对于自定义端点**：
下表介绍了你在 Azure 门户中复制的自定义配置值与 Rancher 中字段的映射：
下表介绍了你在 Azure 门户中复制的自定义配置值与 Rancher 中字段的映射：
| Rancher 字段 | Azure 值 |
| ------------------ | ------------------------------------- |
| Graph 端点 | Microsoft Graph API Endpoint |
| Token 端点 | OAuth 2.0 Token Endpoint |
| Auth 端点 | OAuth 2.0 Authorization Endpoint |
| Rancher 字段 | Azure 值 |
| ------------------ | ------------------------------------- |
| Graph 端点 | Microsoft Graph API Endpoint |
| Token 端点 | OAuth 2.0 Token Endpoint |
| Auth 端点 | OAuth 2.0 Authorization Endpoint |
**重要提示**：在自定义配置中输入 Graph Endpoint 时，请从 URL 中删除 Tenant ID：
**重要提示**：在自定义配置中输入 Graph Endpoint 时，请从 URL 中删除 Tenant ID，如下所示：
<code>http<span>s://g</span>raph.microsoft.com/<del>abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
1. 点击**启用**。
@@ -309,4 +316,4 @@ Token 端点 | https://login.chinacloudapi.cn/{tenantID}/oauth2/token
> - 使用另一个第三方身份验证系统并在 Rancher 中进行设置。请参阅[身份验证文档](../../../../pages-for-subheaders/authentication-config.md)，了解如何配置其他开放式身份验证提供程序。
</TabItem>
</Tabs>
</Tabs>
i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets.md
+2
View File
@@ -63,6 +63,8 @@ title: 密文
**结果**：密文已添加到你选择的项目中。你可以在 Rancher UI 中单击**存储 > 密文**或**更多资源 > 核心 > 密文**来查看密文。
由于项目范围的 Secret 是在项目级别设置的，因此在命名空间级别所做的任何更改都将被覆盖。
:::note
local 集群上的项目级别密文仅在选择单个项目时可见。
i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/vsphere/create-credentials.md
+1
View File
@@ -8,6 +8,7 @@ title: 在 vSphere 控制台中创建凭证
| 特权组 | 操作 |
|:----------------------|:-----------------------------------------------------------------------|
| Cns Privileges | Searchable |
| Datastore | AllocateSpace <br/> Browse <br/> FileManagement (Low level file operations) <br/> UpdateVirtualMachineFiles <br/> UpdateVirtualMachineMetadata |
| 全局 | Set custom attribute |
| 网络 | Assign |
i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/manage-clusters/provisioning-storage-examples/vsphere-storage.md
+2 -2
View File
@@ -20,8 +20,8 @@ title: vSphere 存储
:::
1. 点击 **☰ > 集群管理**。
1. 转到要配置 vSphere 存储的集群。
1. 在左侧导航栏中，单击**存储 > 存储类**。
1. 选择要使用 vSphere 存储的集群，然后单击**浏览**。
1. 在左侧导航栏中，选择**存储 > StorageClass**。
1. 单击**创建**。
3. 输入存储类的**名称**。
4. 在 **Provisioner**下，选择 **VMWare vSphere 卷**。
i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/logging/custom-resource-configuration/flows-and-clusterflows.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Flows 和 ClusterFlows
---
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Banzai Cloud Logging Operator 文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/)。
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Logging Operator 文档](https://kube-logging.github.io/docs/configuration/flow/)。
有关如何解决 Logging 缓冲区的内存问题，请参阅 [Rancher 与 Logging 服务的集成：故障排除](../../../pages-for-subheaders/logging.md#日志缓冲区导致-pod-过载)。
@@ -14,7 +14,7 @@ title: Flows 和 ClusterFlows
你可以通过在 Rancher UI 中填写表单来配置 `Flow`。
有关 `Flow` 自定义资源的更多详细信息，请参阅 [FlowSpec](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/)。
有关 `Flow` 自定义资源的更多详细信息，请参阅 [FlowSpec](https://kube-logging.github.io/docs/configuration/crds/v1beta1/flow_types/)。
### Matches
@@ -24,13 +24,13 @@ title: Flows 和 ClusterFlows
你可以通过填写 Rancher UI 中的 `Flow` 或 `ClusterFlow` 表单来配置匹配。
使用 match 语句的详细示例，请参阅[日志路由的官方文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/)。
使用 match 语句的详细示例，请参阅[日志路由的官方文档](https://kube-logging.github.io/docs/configuration/log-routing/)。
### Filters
你可以在 `Flow` 中定义一个或多个过滤器。过滤器可以对日志执行各种操作，例如，添加其他数据、转换日志或解析记录中的值。`Flow` 中的过滤器会按定义的顺序应用。
有关 Banzai Cloud Logging Operator 支持的过滤器列表，请参阅[此页面](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/)。
有关 Logging Operator 支持的过滤器列表，请参阅 [Fluentd 过滤器的官方文档](https://kube-logging.github.io/docs/configuration/plugins/filters/)。
过滤器需要在 YAML 中配置。
i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/logging/custom-resource-configuration/outputs-and-clusteroutputs.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Outputs 和 ClusterOutputs
---
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Banzai Cloud Logging Operator 文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/)。
有关如何配置 `Flow` 和 `ClusterFlow` 的完整详细信息，请参阅 [Logging Operator 文档](https://kube-logging.github.io/docs/configuration/flow/)。
有关如何解决 Logging 缓冲区的内存问题，请参阅 [Rancher 与 Logging 服务的集成：故障排除](../../../pages-for-subheaders/logging.md#日志缓冲区导致-pod-过载)。
@@ -16,7 +16,7 @@ title: Outputs 和 ClusterOutputs
你可以通过在 Rancher UI 中填写表单来配置 `Output`。
有关 `Output` 自定义资源的更多详细信息，请参阅 [OutputSpec](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/)。
有关 `Output` 自定义资源的更多详细信息，请参阅 [OutputSpec](https://kube-logging.github.io/docs/configuration/crds/v1beta1/output_types/)。
Rancher UI 提供了用于配置以下类型 `Output` 的表单：
@@ -40,7 +40,7 @@ Rancher UI 提供了用于配置以下类型 `Output` 的表单：
Rancher UI 提供了用于配置 `Output` 类型、目标和访问凭证（如果适用）的表单。
有关 Logging Operator 支持的日志插件配置示例，请参阅 [Logging Operator 文档](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/)。
有关 Logging Operator 支持的日志插件配置示例，请参阅 [Logging Operator 文档](https://kube-logging.github.io/docs/configuration/plugins/outputs/)。
## ClusterOutputs
@@ -48,7 +48,7 @@ Rancher UI 提供了用于配置 `Output` 类型、目标和访问凭证（如
你可以通过在 Rancher UI 中填写表单来配置 `ClusterOutput`。
有关 `ClusterOutput` 自定义资源的更多详细信息，请参阅 [ClusterOutput](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)。
有关 `ClusterOutput` 自定义资源的更多详细信息，请参阅 [ClusterOutput](https://kube-logging.github.io/docs/configuration/crds/v1beta1/clusteroutput_types/)。
## YAML 示例
i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/logging/logging-architecture.md
+5 -5
View File
@@ -4,9 +4,9 @@ title: 架构
本节介绍了 Rancher Logging 应用程序的架构。
有关 Banzai Cloud Logging Operator 工作原理的更多详细信息，请参阅[官方文档](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)。
有关 Logging Operator 工作原理的更多详细信息，请参阅[官方文档](https://kube-logging.github.io/docs/#architecture)。
### Banzai Cloud Logging Operator 工作原理
### Logging Operator 工作原理
Logging Operator 自动部署和配置 Kubernetes 日志流水线。它会在每个节点上部署和配置一个 Fluent Bit DaemonSet，从而收集节点文件系统中的容器和应用程序日志。
@@ -21,8 +21,8 @@ Fluent Bit 查询 Kubernetes API 并使用 pod 的元数据来丰富日志，然
每个 `Flow` 都必须引用一个 `Output`，而每个 `ClusterFlow` 都必须引用一个 `ClusterOutput`。
[Banzai 文档](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)中的下图显示了新的 Logging 架构：
[Logging Operator 文档](https://kube-logging.github.io/docs/#architecture)中的下图显示了新的 Logging 架构：
<figcaption>Banzai Cloud Logging Operator 如何与 Fluentd 和 Fluent Bit 一起使用</figcaption>
<figcaption>Logging Operator 如何与 Fluentd 和 Fluent Bit 一起使用</figcaption>
![Banzai Cloud Logging Operator 如何与 Fluentd 一起使用](/img/banzai-cloud-logging-operator.png)
![Logging Operator 如何与 Fluentd 一起使用](/img/banzai-cloud-logging-operator.png)
i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md
+1 -1
View File
@@ -1,7 +1,7 @@
---
title: 迁移到 Rancher 2.5 Logging
---
Rancher 2.5 彻底修改了 Logging 功能。我们现在使用了 Banzai Cloud 的 [logging operator](https://github.com/banzaicloud/logging-operator)，Rancher 配置了此工具以供部署 Logging 使用。
Rancher 2.5 彻底修改了 Logging 功能。我们现在使用了 [Logging Operator](https://github.com/kube-logging/logging-operator)，Rancher 配置了此工具以供部署 Logging 使用。
在新的 Logging 功能的众多特性和变化中，其中一项是取消了项目级别的 Logging 配置。取而代之的是在命名空间级别配置 Logging。集群级日志仍然可用，但配置选项不同。
i18n/zh/docusaurus-plugin-content-docs/version-2.6/pages-for-subheaders/installation-requirements.md
+9 -29
View File
@@ -11,41 +11,21 @@ description: 如果 Rancher 配置在 Docker 或 Kubernetes 中运行时，了
:::
请确保安装 Rancher Server 的节点满足以下要求：
Rancher UI 在基于 Firefox 或 Chromium 的浏览器（Chrome、Edge、Opera、Brave）中效果最佳。
- [操作系统和容器运行时要求](#操作系统和容器运行时要求)
- [RKE 要求](#rke-要求)
- [K3s 要求](#k3s-要求)
- [RKE2 要求](#rke2-要求)
- [安装 Docker](#安装-docker)
- [硬件要求](#硬件要求)
- [CPU 和内存](#cpu-和内存)
- [RKE 和托管 Kubernetes](#rke-和托管-kubernetes)
- [K3s Kubernetes](#k3s-kubernetes)
- [RKE2 Kubernetes](#rke2-kubernetes)
- [Docker](#docker)
- [Ingress](#ingress)
- [磁盘](#磁盘)
- [网络要求](#网络要求)
- [节点 IP 地址](#节点-ip-地址)
- [端口要求](#端口要求)
- [Dockershim 支持](#dockershim-支持)
查看我们的[最佳实践](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)页面，获取在生产环境中运行 Rancher Server 的建议。
如需获取在生产环境中运行 Rancher Server 的最佳实践列表，请参见[最佳实践](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)。
## Kubernetes 与 Rancher 的兼容性
Rancher UI 在基于 Firefox 或 Chromium 的浏览器（Chrome、Edge、Opera、Brave 等）中效果最佳。
Rancher 需要安装在支持的 Kubernetes 版本上。请查阅 [Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/)，确保你的 Kubernetes 版本受支持。
## 操作系统和容器运行时要求
Rancher 兼容当前所有的主流 Linux 发行版。
所有支持的操作系统都使用 64-bit x86 架构。Rancher 兼容当前所有的主流 Linux 发行版。
运行 RKE Kubernetes 集群的节点需要安装 Docker。RKE2 或 K3s 集群不需要它。
[Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/)列出了每个 Rancher 版本测试过的操作系统和 Docker 版本。
Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的 Rancher 版本支持哪些 Kubernetes 版本，请参见[支持维护条款](https://rancher.com/support-maintenance-terms/)。
如需了解各个 Rancher 版本通过了哪些操作系统和 Docker 版本测试，请参见[支持和维护条款](https://rancher.com/support-maintenance-terms/)。
所有支持的操作系统都使用 64-bit x86 架构。
运行 RKE 集群的节点需要安装 Docker。RKE2 或 K3s 集群不需要它。
请安装 `ntp`（Network Time Protocol），以防止在客户端和服务器之间由于时间不同步造成的证书验证错误。
@@ -65,7 +45,7 @@ Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的
对于容器运行时，K3s 默认附带了自己的 containerd。你也可以将 K3s 配置为使用已安装的 Docker 运行时。有关在 Docker 中使用 K3s 的更多信息，请参阅 [K3s 文档](https://docs.k3s.io/advanced#using-docker-as-the-container-runtime)。
Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的 Rancher 版本支持哪些 Kubernetes 版本，请参见[支持维护条款](https://rancher.com/support-maintenance-terms/)。如需指定 K3s 版本，请在运行 K3s 安装脚本时，使用 `INSTALL_K3S_VERSION` 环境变量。
Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的 Rancher 版本支持哪些 Kubernetes 版本，请参见 [Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/)。如需指定 K3s 版本，在运行 K3s 安装脚本时，使用 `INSTALL_K3S_VERSION` 环境变量。
如果你使用 **Raspbian Buster** 在 K3s 集群上安装 Rancher，请按照[这些步骤](https://rancher.com/docs/k3s/latest/en/advanced/#enabling-legacy-iptables-on-raspbian-buster)切换到旧版 iptables。
@@ -75,7 +55,7 @@ Rancher 需要安装在支持的 Kubernetes 版本上。如需了解你使用的
对于容器运行时，RKE2 附带了自己的 containerd。RKE2 安装不需要 Docker。
如需了解 RKE2 通过了哪些操作系统版本的测试，请参见[支持和维护条款](https://rancher.com/support-maintenance-terms/)。
如需了解 RKE2 通过了哪些操作系统版本的测试，请参见 [Rancher 支持矩阵](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/)。
## 硬件要求
i18n/zh/docusaurus-plugin-content-docs/version-2.6/pages-for-subheaders/logging.md
+2 -2
View File
@@ -3,7 +3,7 @@ title: Rancher Logging 集成
description: Rancher 集成了主流的日志服务。了解集成日志服务的要求和优势，并在你的集群上启用 Logging。
---
现在，Rancher 的日志管理由 [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) 提供支持，它取代了以前的内部解决方案。
现在，Rancher 的日志管理由 [Logging operator](https://kube-logging.github.io/docs/) 提供支持，它取代了以前的内部解决方案。
有关 Rancher 2.5 更改的概述，请参阅[本节](../integrations-in-rancher/logging/logging-architecture.md#rancher-2-5-变更)。有关迁移 Logging V1 的更多信息，请参阅[本页](../integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md)。
@@ -117,7 +117,7 @@ Windows 集群支持 Logging，你可以收集 Windows 节点的日志。
根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。
有关如何配置日志缓冲区来满足企业需求的更完整说明，请参阅 [缓冲区](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/buffer/)和 [Fluentd 配置](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/fluentd/)的官方 BanzaiCloud 文档。
有关如何配置日志缓冲区来满足企业需求的更完整说明，请参阅[缓冲区](https://kube-logging.github.io/docs/configuration/plugins/outputs/buffer/)和 [Fluentd 配置](https://kube-logging.github.io/docs/logging-infrastructure/fluentd/)的官方 Logging Operator 文档。
### `cattle-logging` 命名空间正在重新创建
i18n/zh/docusaurus-plugin-content-docs/version-2.6/pages-for-subheaders/manage-project-resource-quotas.md
+7 -1
View File
@@ -20,7 +20,13 @@ Rancher 中的资源配额包含与 [Kubernetes 原生版本](https://kubernetes
1. 在左上角，单击 **☰ > 集群管理**。
1. 在**集群**页面，进入要应用资源配额的集群，然后单击 **Explore**。
1. 单击**集群 > 项目/命名空间**。
1. 找到要添加资源配额的项目。在该项目中选择 **⋮ > 编辑配置**。
1. 确保 **Projects/Namespaces** 页面处于 **Group by Project** 视图模式。
![Screenshot highlighting the "Group by Project" icon, above the list of projects. It resembles a folder.](/img/edit-project-config-for-resource-quotas-group-by-project.png)
1. 找到要添加资源配额的项目，选择与项目名称同行的 **⋮**。
![Screenshot highlighting triple dots icon at the end of the same row as the project name.](/img/edit-project-config-for-resource-quotas-dots.png)
1. 选择**编辑配置**。
1. 展开**资源限额**并单击**添加资源**。你也可以编辑现有配额。
i18n/zh/docusaurus-plugin-content-docs/version-2.6/reference-guides/backup-restore-configuration/backup-configuration.md
+2 -2
View File
@@ -73,7 +73,7 @@ S3 存储位置包含以下配置字段：
1. **凭证密文**（可选）：如果你需要使用 AWS 访问密钥（access key）和密文密钥（secret key）来访问 S3 存储桶，请使用带有密钥和指令 `accessKey` 和 `secretKey` 的凭证来创建密文。它可以是任意一个命名空间。你可以点击[此处](#credentialsecret-示例)查看示例密文。如果运行 operator 的节点在 EC2 中，并且设置了允许它们访问 S3 的 IAM 权限，则此指令是不必要的（如[本节](#ec2-节点访问-s3-的-iam-权限)所述）。凭证密文下拉菜单列出了所有命名空间的密文。
1. **存储桶名称**：存储备份文件的 S3 存储桶的名称。
1. **区域**（可选）：S3 存储桶所在的 AWS [区域](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/)。配置 MinIO 时不需要该字段。
1. **文件夹**（可选）：S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。
1. **文件夹**（可选）：S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。如果此字段留空，则默认将备份文件存储在 S3 存储桶的根文件夹中。
1. **端点**：用于访问存储桶区域中的 S3 的[端点](https://docs.aws.amazon.com/general/latest/gr/s3.html)。
1. **端点 CA**（可选）：Base64 编码的 CA 证书。如需获取示例，请参见 [S3 兼容配置示例](#s3-存储配置示例)。
1. **跳过 TLS 验证**（可选）：如果你不使用 TLS，则设置为 `true`。
@@ -84,7 +84,7 @@ S3 存储位置包含以下配置字段：
| `credentialSecretName` | 如果你需要使用 AWS 访问密钥（access key）和密文密钥（secret key）来访问 S3 存储桶，请使用带有密钥和指令 `accessKey` 和 `secretKey` 的凭证来创建密文。它可以在任何命名空间中，只要你在 `credentialSecretNamespace` 中提供该命名空间。点击[这里](#credentialsecret-示例)查看示例密文。如果运行 operator 的节点在 EC2 中，并且设置了允许它们访问 S3 的 IAM 权限，则此指令是不必要的（如[本节](#ec2-节点访问-s3-的-iam-权限)所述）。 | |
| `credentialSecretNamespace` | 包含访问 S3 的凭证的密文的命名空间。如果运行 operator 的节点在 EC2 中，并且设置了允许它们访问 S3 的 IAM 权限，则此指令是不必要的（如[本节](#ec2-节点访问-s3-的-iam-权限)所述）。 | |
| `bucketName` | 存储备份文件的 S3 存储桶的名称。 | ✓ |
| `folder` | S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。 | |
| `folder` | S3 存储桶中存储备份文件的文件夹名称。不支持嵌套文件夹（例如， `rancher/cluster1`）。如果此字段留空，则默认将备份文件存储在 S3 存储桶的根文件夹中。 | |
| `region` | S3 存储桶所在的 AWS [区域](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/)。 | ✓ |
| `endpoint` | 用于访问存储桶区域中的 S3 的[端点](https://docs.aws.amazon.com/general/latest/gr/s3.html)。 | ✓ |
| `endpointCA` | Base64 编码的 CA 证书。如需获取示例，请参见 [S3 兼容配置示例](#s3-存储配置示例)。 | |
i18n/zh/docusaurus-plugin-content-docs/version-2.6/reference-guides/backup-restore-configuration/storage-configuration.md
+1 -1
View File
@@ -20,7 +20,7 @@ title: 备份存储位置配置
| 凭证密文 | 从 Rancher 的密文中选择 S3 的凭证。[示例](examples.md#在-s3-中存储备份的凭证密文示例)。 |
| 存储桶名称 | 存储备份的 [S3 存储桶](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html)的名称。默认值：`rancherbackups`。 |
| 区域 | S3 存储桶所在的 [AWS 区域](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/)。 |
| 文件夹 | 存储备份的 [S3 存储桶中的文件夹](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html)。 |
| 文件夹 | 存储备份的 [S3 存储桶中的文件夹](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html)。如果此字段留空，则默认将备份文件存储在 S3 存储桶的根文件夹中。 |
| 端点 | [S3 端点](https://docs.aws.amazon.com/general/latest/gr/s3.html)，例如 `s3.us-west-2.amazonaws.com`。 |
| Endpoint CA | 用于 S3 端点的 CA 证书。默认值：base64 编码的 CA 证书。 |
| insecureTLSSkipVerify | 如果你不使用 TLS，则设置为 `true`。 |
i18n/zh/docusaurus-plugin-content-docs/version-2.6/reference-guides/best-practices/rancher-managed-clusters/logging-best-practices.md
+2 -2
View File
@@ -12,7 +12,7 @@ title: Logging 最佳实践
现在，Rancher 的日志聚合更加灵活。通过新的 Logging 的功能，管理员和用户都可以部署符合细粒度收集标准的日志记录，同时提供更多的目标和配置选项。
Rancher 的 Logging 使用的是 Banzai Cloud logging operator。我们让你可以管理这个 operator 及其资源，并将它的管理功能和 Rancher 集群管理联系起来。
Rancher Logging 使用的是 [Logging Operator](https://github.com/kube-logging/logging-operator)。我们让你可以管理这个 operator 及其资源，并将它的管理功能和 Rancher 集群管理联系起来。
## 集群级别日志
@@ -44,7 +44,7 @@ Rancher 的 Logging 将读取 `/var/log/containers` 中的所有日志条目，
日志收集仅从 Kubernetes 中的 Pod 中检索 `stdout`/`stderr` 日志。但是，我们也可能想从应用生成的其他文件中收集日志。在这种情况下，你可以使用一个（或两个）日志流 Sidecar。
设置日志流 Sidecar 的目的是获取写入磁盘的日志文件，并将其内容传输到 `stdout`。这样一来，Banzai Logging Operator 就可以接收这些日志，并把日志发送到目标输出位置。
设置日志流 Sidecar 的目的是获取写入磁盘的日志文件，并将其内容传输到 `stdout`。这样一来，Logging Operator 就可以接收这些日志，并把日志发送到目标输出位置。
要进行设置，编辑你的工作负载资源（例如 Deployment）并添加以下 Sidecar 定义：
i18n/zh/docusaurus-theme-classic/navbar.json
+4 -4
View File
@@ -1,10 +1,10 @@
{
"item.label.Docs": {
"message": "文档",
"description": "Navbar item with label Docs"
},
"item.label.GitHub": {
"message": "GitHub",
"description": "Navbar item with label GitHub"
},
"item.label.Rancher Home": {
"message": "Rancher 主页",
"description": "Navbar item with label Rancher Home"
}
}
sidebars.js
-1
View File
@@ -42,7 +42,6 @@ const sidebars = {
},
items: [
"getting-started/quick-start-guides/deploy-rancher-manager/aws",
"getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace",
"getting-started/quick-start-guides/deploy-rancher-manager/azure",
"getting-started/quick-start-guides/deploy-rancher-manager/digitalocean",
"getting-started/quick-start-guides/deploy-rancher-manager/gcp",
src/pages/versions.md
+54 -24
View File
@@ -8,6 +8,42 @@ title: Rancher Documentation Versions
Below are the documentation and release notes for the currently released version of Rancher 2.7.x:
<table>
<tr>
<td><b>v2.7.1</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/">Documentation</a></td>
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.7.1">Release Notes</a></td>
<td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-1/">Support Matrix</a></td>
</tr>
</table>
Below are the documentation and release notes for the currently released version of Rancher 2.6.x:
<table>
<tr>
<td><b>v2.6.10</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.6">Documentation</a></td>
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.6.10">Release Notes</a></td>
<td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/">Support Matrix</a></td>
</tr>
</table>
Below are the documentation and release notes for the currently released version of Rancher 2.5.x:
<table>
<tr>
<td><b>v2.5.17</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.5">Documentation</a></td>
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.5.17">Release Notes</a></td>
</tr>
</table>
<br/>
### Past versions
Below are the documentation and release notes for previous versions of Rancher 2.7.x:
<table>
<tr>
<td><b>v2.7.0</b></td>
@@ -17,7 +53,9 @@ Below are the documentation and release notes for the currently released version
</tr>
</table>
Below are the documentation and release notes for the currently released version of Rancher 2.6.x:
<br/>
Below are the documentation and release notes for previous versions of Rancher 2.6.x:
<table>
<tr>
@@ -26,26 +64,6 @@ Below are the documentation and release notes for the currently released version
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.6.9">Release Notes</a></td>
<td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-9/">Support Matrix</a></td>
</tr>
</table>
Below are the documentation and release notes for the currently released version of Rancher 2.5.x:
<table>
<tr>
<td><b>v2.5.16</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.5">Documentation</a></td>
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.5.16">Release Notes</a></td>
<td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-5-16/">Support Matrix</a></td>
</tr>
</table>
<br/>
### Past versions
Below are the documentation and release notes for previous versions of Rancher 2.6.x:
<table>
<tr>
<td><b>v2.6.8</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.6">Documentation</a></td>
@@ -104,9 +122,23 @@ Below are the documentation and release notes for previous versions of Rancher 2
<br/>
Below are the documentation and release notes for previous versions of Rancher 2.5.x:
### Legacy versions (EOL)
Below are the documentation and release notes for legacy versions of Rancher 2.5.x:
<table>
<tr>
<td><b>v2.5.17</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.5">Documentation</a></td>
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.5.17">Release Notes</a></td>
<td><center>N / A</center></td>
</tr>
<tr>
<td><b>v2.5.16</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.5">Documentation</a></td>
<td><a href="https://github.com/rancher/rancher/releases/tag/v2.5.16">Release Notes</a></td>
<td><a href="https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-5-16/">Support Matrix</a></td>
</tr>
<tr>
<td><b>v2.5.15</b></td>
<td><a href="https://ranchermanager.docs.rancher.com/v2.5">Documentation</a></td>
@@ -207,8 +239,6 @@ Below are the documentation and release notes for previous versions of Rancher 2
<br/>
### Legacy versions (EOL)
Below is the documentation for legacy versions of Rancher 2.0 - 2.4.x:
<table>
static/img/edit-project-config-for-resource-quotas-dots.png
Executable
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

static/img/edit-project-config-for-resource-quotas-group-by-project.png
Executable
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

versioned_docs/version-2.5/explanations/integrations-in-rancher/logging/custom-resource-configuration/flows-and-clusterflows.md
+8 -8
View File
@@ -2,9 +2,9 @@
title: Flows and ClusterFlows
---
See the [Banzai Cloud Logging operator documentation](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See [Rancher Integration with Logging Services: Troubleshooting](../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
See [Rancher Integration with Logging Services: Troubleshooting](../../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
- [Configuration](#configuration)
- [YAML Example](#yaml-example)
@@ -33,7 +33,7 @@ A `Flow` defines which logs to collect and filter and which output to send the l
The `Flow` is a namespaced resource, which means logs will only be collected from the namespace that the `Flow` is deployed in.
For more details about the `Flow` custom resource, see [FlowSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/)
For more details about the `Flow` custom resource, see [FlowSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/flow_types/)
<a id="matches-2-5-8"></a>
@@ -46,7 +46,7 @@ You can specify match statements to select or exclude logs according to Kubernet
Matches can be configured by filling out the `Flow` or `ClusterFlow` forms in the Rancher UI.
For detailed examples on using the match statement, see the [official documentation on log routing.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/)
For detailed examples on using the match statement, see the [official documentation on log routing.](https://kube-logging.github.io/docs/configuration/log-routing/)
<a id="filters-2-5-8"></a>
@@ -54,7 +54,7 @@ For detailed examples on using the match statement, see the [official documentat
You can define one or more filters within a `Flow`. Filters can perform various actions on the logs, for example, add additional data, transform the logs, or parse values from the records. The filters in the `Flow` are applied in the order in the definition.
For a list of filters supported by the Banzai Cloud Logging operator, see [this page.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/)
For a list of filters supported by the Logging operator, see [the official documentation on Fluentd filters](https://kube-logging.github.io/docs/configuration/plugins/filters/).
Filters need to be configured in YAML.
@@ -93,7 +93,7 @@ A `Flow` defines which logs to collect and filter and which `Output` to send the
`Flows` need to be defined in YAML.
For more details about the `Flow` custom resource, see [FlowSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/)
For more details about the `Flow` custom resource, see [FlowSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/flow_types/)
<a id="matches-2-5-0"></a>
@@ -104,7 +104,7 @@ Match statements are used to select which containers to pull logs from.
You can specify match statements to select or exclude logs according to Kubernetes labels, container and host names. Match statements are evaluated in the order they are defined and processed only until the first matching select or exclude rule applies.
For detailed examples on using the match statement, see the [official documentation on log routing.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/)
For detailed examples on using the match statement, see the [official documentation on log routing.](https://kube-logging.github.io/docs/configuration/log-routing/)
<a id="filters-2-5-0"></a>
@@ -112,7 +112,7 @@ For detailed examples on using the match statement, see the [official documentat
You can define one or more filters within a `Flow`. Filters can perform various actions on the logs, for example, add additional data, transform the logs, or parse values from the records. The filters in the `Flow` are applied in the order in the definition.
For a list of filters supported by the Banzai Cloud Logging operator, see [this page.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/)
For a list of filters supported by the Logging operator, see [this page.](https://kube-logging.github.io/docs/configuration/plugins/filters/)
<a id="outputs-2-5-0"></a>
versioned_docs/version-2.5/explanations/integrations-in-rancher/logging/custom-resource-configuration/outputs-and-clusteroutputs.md
+11 -9
View File
@@ -2,9 +2,9 @@
title: Outputs and ClusterOutputs
---
See the [Banzai Cloud Logging operator documentation](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See [Rancher Integration with Logging Services: Troubleshooting](../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
See [Rancher Integration with Logging Services: Troubleshooting](../../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
## Configuration
@@ -20,6 +20,7 @@ The `Outputs` and `ClusterOutputs` can now be configured by filling out forms in
<a id="outputs-2-5-8"></a>
## Outputs
The `Output` resource defines where your `Flows` can send the log messages. `Outputs` are the final stage for a logging `Flow`.
@@ -28,7 +29,7 @@ The `Output` is a namespaced resource, which means only a `Flow` within the same
You can use secrets in these definitions, but they must also be in the same namespace.
For the details of `Output` custom resource, see [OutputSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/).
For the details of `Output` custom resource, see [OutputSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/output_types/).
The Rancher UI provides forms for configuring the following `Output` types:
@@ -52,7 +53,7 @@ The Rancher UI provides forms for configuring the following `Output` types:
The Rancher UI provides forms for configuring the `Output` type, target, and access credentials if applicable.
For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/).
For example configuration for each logging plugin supported by the logging operator, see the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/plugins/outputs/).
<a id="clusteroutputs-2-5-8"></a>
@@ -60,7 +61,7 @@ For example configuration for each logging plugin supported by the logging opera
`ClusterOutput` defines an `Output` without namespace restrictions. It is only effective when deployed in the same namespace as the logging operator.
For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)
For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/clusteroutput_types/)
</TabItem>
<TabItem value="Rancher before v2.5.8">
@@ -70,6 +71,7 @@ For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](htt
<a id="outputs-2-5-0"></a>
## Outputs
The `Output` resource defines where your `Flows` can send the log messages. `Outputs` are the final stage for a logging `Flow`.
@@ -78,9 +80,9 @@ The `Output` is a namespaced resource, which means only a `Flow` within the same
You can use secrets in these definitions, but they must also be in the same namespace.
`Outputs` are configured in YAML. For the details of `Output` custom resource, see [OutputSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/)
`Outputs` are configured in YAML. For the details of `Output` custom resource, see [OutputSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/output_types/)
For examples of configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/)
For examples of configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://kube-logging.github.io/docs/configuration/plugins/outputs/)
<a id="clusteroutputs-2-5-0"></a>
@@ -90,9 +92,9 @@ For examples of configuration for each logging plugin supported by the logging o
The Rancher UI provides forms for configuring the `ClusterOutput` type, target, and access credentials if applicable.
`ClusterOutputs` are configured in YAML. For the details of `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)
`ClusterOutputs` are configured in YAML. For the details of `ClusterOutput` custom resource, see [ClusterOutput.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/clusteroutput_types/)
For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/)
For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://kube-logging.github.io/docs/configuration/plugins/outputs/)
</TabItem>
</Tabs>
versioned_docs/version-2.5/explanations/integrations-in-rancher/logging/logging-architecture.md
+6 -6
View File
@@ -4,20 +4,20 @@ title: Architecture
This section summarizes the architecture of the Rancher logging application.
For more details about how the Banzai Cloud Logging operator works, see the [official documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)
For more details about how the Logging operator works, see the [official documentation.](https://kube-logging.github.io/docs/#architecture)
### Changes in Rancher v2.5
The following changes were introduced to logging in Rancher v2.5:
- The [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) now powers Rancher's logging solution in place of the former, in-house solution.
- The [Logging operator](https://kube-logging.github.io/docs/) now powers Rancher's logging solution in place of the former, in-house solution.
- [Fluent Bit](https://fluentbit.io/) is now used to aggregate the logs, and [Fluentd](https://www.fluentd.org/) is used for filtering the messages and routing them to the `Outputs`. Previously, only Fluentd was used.
- Logging can be configured with a Kubernetes manifest, because logging now uses a Kubernetes operator with Custom Resource Definitions.
- We now support filtering logs.
- We now support writing logs to multiple `Outputs`.
- We now always collect Control Plane and etcd logs.
### How the Banzai Cloud Logging Operator Works
### How the Logging Operator Works
The Logging operator automates the deployment and configuration of a Kubernetes logging pipeline. It deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system.
@@ -32,8 +32,8 @@ The following custom resources are used to define how logs are filtered and sent
Each `Flow` must reference an `Output`, and each `ClusterFlow` must reference a `ClusterOutput`.
The following figure from the [Banzai documentation](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture) shows the new logging architecture:
The following figure from the [Logging operator documentation](https://kube-logging.github.io/docs/#architecture) shows the new logging architecture:
<figcaption>How the Banzai Cloud Logging Operator Works with Fluentd and Fluent Bit</figcaption>
<figcaption>How the Logging Operator Works with Fluentd and Fluent Bit</figcaption>
![How the Banzai Cloud Logging Operator Works with Fluentd](/img/banzai-cloud-logging-operator.png)
![How the Logging Operator Works with Fluentd](/img/banzai-cloud-logging-operator.png)
versioned_docs/version-2.5/explanations/integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md
+1 -1
View File
@@ -2,7 +2,7 @@
title: Migrating to Rancher v2.5 Logging
---
Starting in v2.5, the logging feature available within Rancher has been completely overhauled. The [logging operator](https://github.com/banzaicloud/logging-operator) from Banzai Cloud has been adopted; Rancher configures this tooling for use when deploying logging.
Starting in v2.5, the logging feature available within Rancher has been completely overhauled. The [Logging operator](https://github.com/kube-logging/logging-operator) has been adopted; Rancher configures this tooling for use when deploying logging.
Among the many features and changes in the new logging functionality is the removal of project-specific logging configurations. Instead, one now configures logging at the namespace level. Cluster-level logging remains available, but configuration options differ.
versioned_docs/version-2.5/pages-for-subheaders/installation-requirements.md
+15 -35
View File
@@ -5,47 +5,27 @@ description: Learn the node requirements for each node running Rancher server wh
This page describes the software, hardware, and networking requirements for the nodes where the Rancher server will be installed. The Rancher server can be installed on a single node or a high-availability Kubernetes cluster.
> It is important to note that if you install Rancher on a Kubernetes cluster, requirements are different from the [node requirements for downstream user clusters,](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md) which will run your apps and services.
:::note Important:
Make sure the node(s) for the Rancher server fulfill the following requirements:
If you install Rancher on a Kubernetes cluster, requirements are different from the [node requirements for downstream user clusters,](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md) which will run your apps and services.
- [Operating Systems and Container Runtime Requirements](#operating-systems-and-container-runtime-requirements)
- [RKE Specific Requirements](#rke-specific-requirements)
- [K3s Specific Requirements](#k3s-specific-requirements)
- [RancherD Specific Requirements](#rancherd-specific-requirements)
- [RKE2 Specific Requirements](#rke2-specific-requirements)
- [Installing Docker](#installing-docker)
- [Hardware Requirements](#hardware-requirements)
- [CPU and Memory](#cpu-and-memory)
- [RKE and Hosted Kubernetes](#rke-and-hosted-kubernetes)
- [K3s Kubernetes](#k3s-kubernetes)
- [RancherD](#rancherd)
- [RKE2 Kubernetes](#rke2-kubernetes)
- [Docker](#docker)
- [Ingress](#ingress)
- [Ingress for RKE2](#ingress-for-rke2)
- [Ingress for EKS](#ingress-for-eks)
- [Disks](#disks)
- [Networking Requirements](#networking-requirements)
- [Node IP Addresses](#node-ip-addresses)
- [Port Requirements](#port-requirements)
- [RancherD on SELinux Enforcing CentOS 8 or RHEL 8 Nodes](#rancherd-on-selinux-enforcing-centos-8-or-rhel-8-nodes)
:::
For a list of best practices that we recommend for running the Rancher server in production, refer to the [best practices section.](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)
The Rancher UI works best in Firefox or Chromium based browsers (Chrome, Edge, Opera, Brave, etc).
The Rancher UI works best in Firefox or Chrome.
See our page on [best practices](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md) for a list of recommendations for running a Rancher server in production.
## Kubernetes Compatibility with Rancher
Rancher needs to be installed on a supported Kubernetes version. Consult the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-5-16/) to ensure that your intended version of Kubernetes is supported.
## Operating Systems and Container Runtime Requirements
Rancher should work with any modern Linux distribution.
All supported operating systems are 64-bit x86. Rancher should work with any modern Linux distribution.
Docker is required for nodes that will run RKE Kubernetes clusters. It is not required for RancherD or RKE2 Kubernetes installs.
The [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-5-16/) lists which OS and Docker versions were tested for each Rancher version.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
For details on which OS and Docker versions were tested with each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
All supported operating systems are 64-bit x86.
Docker is required for nodes that will run RKE clusters. It is not required for RKE2 or K3s clusters.
The `ntp` (Network Time Protocol) package should be installed. This prevents errors with certificate validation that can occur when the time is not synchronized between the client and server.
@@ -69,7 +49,7 @@ net.bridge.bridge-nf-call-iptables=1
For the container runtime, K3s should work with any modern version of Docker or containerd.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-5-16/). To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script.
If you are installing Rancher on a K3s cluster with **Raspbian Buster**, follow [these steps](https://rancher.com/docs/k3s/latest/en/advanced/#enabling-legacy-iptables-on-raspbian-buster) to switch to legacy iptables.
@@ -89,7 +69,7 @@ Docker is not required for RancherD installs.
_The RKE2 install is available as of v2.5.6._
For details on which OS versions were tested with RKE2, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
For details on which OS versions were tested with RKE2, refer to the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-5-16/).
Docker is not required for RKE2 installs.
@@ -176,7 +156,7 @@ The Ingress should be deployed as DaemonSet to ensure your load balancer can suc
For RKE, K3s and RancherD installations, you don't have to install the Ingress manually because it is installed by default.
For hosted Kubernetes clusters (EKS, GKE, AKS) and RKE2 Kubernetes installations, you will need to set up the ingress.
For hosted Kubernetes clusters (EKS, GKE, AKS) and RKE2 installations, you will need to set up the ingress.
### Ingress for RKE2
versioned_docs/version-2.5/pages-for-subheaders/logging.md
+2 -2
View File
@@ -3,7 +3,7 @@ title: Rancher Integration with Logging Services
description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster.
---
The [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) now powers Rancher's logging solution in place of the former, in-house solution.
The [Logging operator](https://kube-logging.github.io/docs/) now powers Rancher's logging solution in place of the former, in-house solution.
For an overview of the changes in v2.5, see [this section.](../explanations/integrations-in-rancher/logging/logging-architecture.md#changes-in-rancher-v25) For information about migrating from Logging V1, see [this page.](../explanations/integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md)
@@ -104,7 +104,7 @@ By default, Rancher collects logs for control plane components and node componen
Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once.
For a more complete description of how to configure the logging buffer to suit your organization's needs, see the official BanzaiCloud documentation on [buffers](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/buffer/) and on [Fluentd configuration](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/fluentd/).
For a more complete description of how to configure the logging buffer to suit your organization's needs, see the official Logging operator documentation on [buffers](https://kube-logging.github.io/docs/configuration/plugins/outputs/buffer/) and on [Fluentd configuration](https://kube-logging.github.io/docs/logging-infrastructure/fluentd/).
### The `cattle-logging` Namespace Being Recreated
versioned_docs/version-2.5/reference-guides/backup-restore-configuration/backup-configuration.md
+2 -2
View File
@@ -74,7 +74,7 @@ The S3 storage location contains the following configuration fields:
1. **Credential Secret** (optional): If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) The Credential Secret dropdown lists the secrets in all namespaces.
1. **Bucket Name**: The name of the S3 bucket where backup files will be stored.
1. **Region** (optional): The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. This field isn't needed for configuring MinIO.
1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported.
1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket.
1. **Endpoint**: The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket.
1. **Endpoint CA** (optional): This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration)
1. **Skip TLS Verifications** (optional): Set to true if you are not using TLS.
@@ -85,7 +85,7 @@ The S3 storage location contains the following configuration fields:
| `credentialSecretName` | If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace as long as you provide that namespace in `credentialSecretNamespace`. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | |
| `credentialSecretNamespace` | The namespace of the secret containing the credentials to access S3. This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | |
| `bucketName` | The name of the S3 bucket where backup files will be stored. | ✓ |
| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. | |
| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket. | |
| `region` | The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. | ✓ |
| `endpoint` | The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket. | ✓ |
| `endpointCA` | This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration) | |
versioned_docs/version-2.5/reference-guides/backup-restore-configuration/storage-configuration.md
+1 -1
View File
@@ -20,7 +20,7 @@ You can choose to not have any operator-level storage location configured. If yo
| Credential Secret | Choose the credentials for S3 from your secrets in Rancher. [Example](./examples.md#example-credential-secret-for-storing-backups-in-s3). |
| Bucket Name | Enter the name of the [S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html) where the backups will be stored. Default: `rancherbackups`. |
| Region | The [AWS region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. |
| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. |
| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket. |
| Endpoint | The [S3 endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) For example, `s3.us-west-2.amazonaws.com`. |
| Endpoint CA | The CA cert used to for the S3 endpoint. Default: base64 encoded CA cert |
| insecureTLSSkipVerify | Set to true if you are not using TLS. |
versioned_docs/version-2.5/reference-guides/best-practices/rancher-managed-clusters/logging-best-practices.md
+2 -2
View File
@@ -15,7 +15,7 @@ Before Rancher v2.5, logging in Rancher has historically been a pretty static in
Logging in 2.5 has been completely overhauled to provide a more flexible experience for log aggregation. With the new logging feature, administrators and users alike can deploy logging that meets fine-grained collection criteria while offering a wider array of destinations and configuration options.
"Under the hood", Rancher logging uses the Banzai Cloud logging operator. We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters.
"Under the hood", Rancher logging uses the [Logging operator](https://github.com/kube-logging/logging-operator). We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters.
## Cluster-level Logging
@@ -47,7 +47,7 @@ Rancher logging will read all log entries in `/var/log/containers`, ensuring tha
Log collection only retrieves `stdout`/`stderr` logs from pods in Kubernetes. But what if we want to collect logs from other files that are generated by applications? Here, a log streaming sidecar (or two) may come in handy.
The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Banzai Logging Operator can pick up those logs and send them to your desired output.
The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Logging Operator can pick up those logs and send them to your desired output.
To set this up, edit your workload resource (e.g. Deployment) and add the following sidecar definition:
versioned_docs/version-2.6/getting-started/quick-start-guides/deploy-rancher-manager/aws-marketplace.md
+1 -1
View File
@@ -3,4 +3,4 @@ title: Rancher AWS Marketplace Quick Start
description: Use Amazon EKS to deploy Rancher server.
---
There is now an additional way for you to deploy the Rancher server in AWS by using Amazon EKS. To learn more, see our [Amazon Marketplace listing](https://aws.amazon.com/marketplace/pp/prodview-go7ent7goo5ae).
Amazon Elastic Kubernetes Service (EKS) can quickly [deploy Rancher to Amazon Web Services (AWS)](https://documentation.suse.com/trd/kubernetes/single-html/gs_rancher_aws-marketplace/). To learn more, see our [Amazon Marketplace listing](https://aws.amazon.com/marketplace/pp/prodview-go7ent7goo5ae). Watch the [demo](https://youtu.be/9dznJ7Ons0M) for a walkthrough of AWS Marketplace SUSE Rancher setup.
versioned_docs/version-2.6/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
+26 -15
View File
@@ -167,14 +167,26 @@ You'll also need to manually enter the Graph, Token, and Auth Endpoints.
#### 5. Configure Azure AD in Rancher
To complete configuration, enter information about your AD instance in the Rancher UI.
From the Rancher UI, enter information about your AD instance hosted in Azure to complete configuration.
1. Log into Rancher.
1. In the upper left corner of the toolbar, click **☰ > Users & Authentication**.
1. In the nav menu, click **Auth Provider**.
1. In the top left corner, click **☰ > Users & Authentication**.
1. In the left navigation menu, click **Auth Provider**.
1. Click **AzureAD**.
1. Complete the **Configure Azure AD Account** form using the information you copied while completing [Copy Azure Application Data](#4-copy-azure-application-data).
:::caution
The Azure AD account will be granted administrator privileges, since its details will be mapped to the Rancher local principal account. Make sure that this level of privilege is appropriate before you continue.
:::
**For Standard or China Endpoints:**
The following table maps the values you copied in the Azure portal to the fields in Rancher:
| Rancher Field | Azure Value |
@@ -184,20 +196,19 @@ To complete configuration, enter information about your AD instance in the Ranch
| Application Secret | Key Value |
| Endpoint | https://login.microsoftonline.com/ |
**For Custom Endpoints:**
**For Custom Endpoints:**
The following table maps the custom config values you copied in the Azure portal to the fields in Rancher:
The following table maps the custom config values you copied in the Azure portal to the fields in Rancher:
| Rancher Field | Azure Value |
| ------------------ | ------------------------------------- |
| Graph Endpoint | Microsoft Graph API Endpoint |
| Token Endpoint | OAuth 2.0 Token Endpoint |
| Auth Endpoint | OAuth 2.0 Authorization Endpoint |
| Rancher Field | Azure Value |
| ------------------ | ------------------------------------- |
| Graph Endpoint | Microsoft Graph API Endpoint |
| Token Endpoint | OAuth 2.0 Token Endpoint |
| Auth Endpoint | OAuth 2.0 Authorization Endpoint |
**Important:** When entering the Graph Endpoint in a custom config, remove the tenant ID from the URL:
**Important:** When entering the Graph Endpoint in a custom config, remove the tenant ID from the URL, like below:
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
<code>http<span>s://g</span>raph.microsoft.com<del>/abb5adde-bee8-4821-8b03-e63efdc7701c</del></code>
1. Click **Enable**.
@@ -206,8 +217,8 @@ The following table maps the custom config values you copied in the Azure portal
### Migrating from Azure AD Graph API to Microsoft Graph API
Since the [Azure AD Graph API](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview) is deprecated and slated to retire in June 2023, admins should update their Azure AD App to use the [Microsoft Graph API](https://docs.microsoft.com/en-us/graph/use-the-api) in Rancher.
This needs to be done well in advance of the endpoint being retired.
Since the [Azure AD Graph API](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview) is deprecated and slated to retire in June 2023, admins should update their Azure AD App to use the [Microsoft Graph API](https://docs.microsoft.com/en-us/graph/use-the-api) in Rancher.
This needs to be done well in advance of the endpoint being retired.
If Rancher is still configured to use the Azure AD Graph API when it is retired, users may not be able to log into Rancher using Azure AD.
#### Updating Endpoints in the Rancher UI
versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets.md
+2
View File
@@ -63,6 +63,8 @@ Before v2.6, secrets were required to be in a project scope. Projects are no lon
**Result:** Your secret is added to the individual project you chose. You can view the secret in the Rancher UI by clicking either **Storage > Secrets** or **More Resources > Core > Secrets**.
Since project-scoped secrets are set at the project level, any changes made at the namespace level will be overwritten.
:::note
Project-scoped secrets on the local cluster are only visible when a single project is selected.
versioned_docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/vsphere/create-credentials.md
+1
View File
@@ -8,6 +8,7 @@ The following table lists the permissions required for the vSphere user account:
| Privilege Group | Operations |
|:----------------------|:-----------------------------------------------------------------------|
| Cns Privileges | Searchable |
| Datastore | AllocateSpace <br/> Browse <br/> FileManagement (Low level file operations) <br/> UpdateVirtualMachineFiles <br/> UpdateVirtualMachineMetadata |
| Global | Set custom attribute |
| Network | Assign |
versioned_docs/version-2.6/how-to-guides/new-user-guides/manage-clusters/provisioning-storage-examples/vsphere-storage.md
+2 -2
View File
@@ -20,8 +20,8 @@ The following steps can also be performed using the `kubectl` command line tool.
:::
1. Click **☰ > Cluster Management**.
1. Go to the cluster where you want to provide vSphere storage.
1. In the left navigation bar, click **Storage > StorageClasses**.
1. Choose the cluster you want to provide vSphere storage to and click **Exlpore**.
1. In the left navigation bar, select **Storage > StorageClasses**.
1. Click **Create**.
3. Enter a **Name** for the StorageClass.
4. Under **Provisioner**, select **VMWare vSphere Volume**.
versioned_docs/version-2.6/integrations-in-rancher/logging/custom-resource-configuration/flows-and-clusterflows.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Flows and ClusterFlows
---
See the [Banzai Cloud Logging operator documentation](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See [Rancher Integration with Logging Services: Troubleshooting](../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
@@ -14,7 +14,7 @@ The `Flow` is a namespaced resource, which means logs will only be collected fro
`Flows` can be configured by filling out forms in the Rancher UI.
For more details about the `Flow` custom resource, see [FlowSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/flow_types/)
For more details about the `Flow` custom resource, see [FlowSpec.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/flow_types/)
### Matches
@@ -24,13 +24,13 @@ You can specify match statements to select or exclude logs according to Kubernet
Matches can be configured by filling out the `Flow` or `ClusterFlow` forms in the Rancher UI.
For detailed examples on using the match statement, see the [official documentation on log routing.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/log-routing/)
For detailed examples on using the match statement, see the [official documentation on log routing.](https://kube-logging.github.io/docs/configuration/log-routing/)
### Filters
You can define one or more filters within a `Flow`. Filters can perform various actions on the logs, for example, add additional data, transform the logs, or parse values from the records. The filters in the `Flow` are applied in the order in the definition.
For a list of filters supported by the Banzai Cloud Logging operator, see [this page.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/filters/)
For a list of filters supported by the Logging operator, see [the official documentation on Fluentd filters](https://kube-logging.github.io/docs/configuration/plugins/filters/).
Filters need to be configured in YAML.
versioned_docs/version-2.6/integrations-in-rancher/logging/custom-resource-configuration/outputs-and-clusteroutputs.md
+4 -4
View File
@@ -2,7 +2,7 @@
title: Outputs and ClusterOutputs
---
See the [Banzai Cloud Logging operator documentation](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/flow/) for the full details on how to configure `Flows` and `ClusterFlows`.
See [Rancher Integration with Logging Services: Troubleshooting](../../../pages-for-subheaders/logging.md#The-Logging-Buffer-Overloads-Pods) for how to resolve memory problems with the logging buffer.
@@ -16,7 +16,7 @@ You can use secrets in these definitions, but they must also be in the same name
`Outputs` can be configured by filling out forms in the Rancher UI.
For the details of `Output` custom resource, see [OutputSpec.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/output_types/).
For the details of `Output` custom resource, see [OutputSpec](https://kube-logging.github.io/docs/configuration/crds/v1beta1/output_types/).
The Rancher UI provides forms for configuring the following `Output` types:
@@ -40,7 +40,7 @@ The Rancher UI provides forms for configuring the following `Output` types:
The Rancher UI provides forms for configuring the `Output` type, target, and access credentials if applicable.
For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/).
For example configuration for each logging plugin supported by the logging operator, see the [Logging operator documentation](https://kube-logging.github.io/docs/configuration/plugins/outputs/).
## ClusterOutputs
@@ -48,7 +48,7 @@ For example configuration for each logging plugin supported by the logging opera
`ClusterOutputs` can be configured by filling out forms in the Rancher UI.
For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)
For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://kube-logging.github.io/docs/configuration/crds/v1beta1/clusteroutput_types/)
## YAML Examples
versioned_docs/version-2.6/integrations-in-rancher/logging/logging-architecture.md
+5 -5
View File
@@ -4,9 +4,9 @@ title: Architecture
This section summarizes the architecture of the Rancher logging application.
For more details about how the Banzai Cloud Logging operator works, see the [official documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture)
For more details about how the Logging operator works, see the [official documentation.](https://kube-logging.github.io/docs/#architecture)
### How the Banzai Cloud Logging Operator Works
### How the Logging Operator Works
The Logging operator automates the deployment and configuration of a Kubernetes logging pipeline. It deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system.
@@ -21,8 +21,8 @@ The following custom resources are used to define how logs are filtered and sent
Each `Flow` must reference an `Output`, and each `ClusterFlow` must reference a `ClusterOutput`.
The following figure from the [Banzai documentation](https://banzaicloud.com/docs/one-eye/logging-operator/#architecture) shows the new logging architecture:
The following figure from the [Logging operator documentation](https://kube-logging.github.io/docs/#architecture) shows the new logging architecture:
<figcaption>How the Banzai Cloud Logging Operator Works with Fluentd and Fluent Bit</figcaption>
<figcaption>How the Logging Operator Works with Fluentd and Fluent Bit</figcaption>
![How the Banzai Cloud Logging Operator Works with Fluentd](/img/banzai-cloud-logging-operator.png)
![How the Logging Operator Works with Fluentd](/img/banzai-cloud-logging-operator.png)
versioned_docs/version-2.6/integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md
+1 -1
View File
@@ -1,7 +1,7 @@
---
title: Migrating to Rancher v2.5 Logging
---
Starting in v2.5, the logging feature available within Rancher has been completely overhauled. The [logging operator](https://github.com/banzaicloud/logging-operator) from Banzai Cloud has been adopted; Rancher configures this tooling for use when deploying logging.
Starting in v2.5, the logging feature available within Rancher has been completely overhauled. The [Logging operator](https://github.com/kube-logging/logging-operator) has been adopted; Rancher configures this tooling for use when deploying logging.
Among the many features and changes in the new logging functionality is the removal of project-specific logging configurations. Instead, one now configures logging at the namespace level. Cluster-level logging remains available, but configuration options differ.
versioned_docs/version-2.6/pages-for-subheaders/installation-requirements.md
+9 -29
View File
@@ -11,41 +11,21 @@ If you install Rancher on a Kubernetes cluster, requirements are different from
:::
Make sure the node(s) for the Rancher server fulfill the following requirements:
The Rancher UI works best in Firefox or Chromium based browsers (Chrome, Edge, Opera, Brave, etc).
- [Operating Systems and Container Runtime Requirements](#operating-systems-and-container-runtime-requirements)
- [RKE Specific Requirements](#rke-specific-requirements)
- [K3s Specific Requirements](#k3s-specific-requirements)
- [RKE2 Specific Requirements](#rke2-specific-requirements)
- [Installing Docker](#installing-docker)
- [Hardware Requirements](#hardware-requirements)
- [CPU and Memory](#cpu-and-memory)
- [RKE and Hosted Kubernetes](#rke-and-hosted-kubernetes)
- [K3s Kubernetes](#k3s-kubernetes)
- [RKE2 Kubernetes](#rke2-kubernetes)
- [Docker](#docker)
- [Ingress](#ingress)
- [Disks](#disks)
- [Networking Requirements](#networking-requirements)
- [Node IP Addresses](#node-ip-addresses)
- [Port Requirements](#port-requirements)
- [Dockershim Support](#dockershim-support)
See our page on [best practices](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md) for a list of recommendations for running a Rancher server in production.
For a list of best practices that we recommend for running the Rancher server in production, refer to the [best practices section.](../reference-guides/best-practices/rancher-server/tips-for-running-rancher.md)
## Kubernetes Compatibility with Rancher
The Rancher UI works best in Firefox or Chromium based browsers (Chrome, Edge, Opera, Brave, ...).
Rancher needs to be installed on a supported Kubernetes version. Consult the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/) to ensure that your intended version of Kubernetes is supported.
## Operating Systems and Container Runtime Requirements
Rancher should work with any modern Linux distribution.
All supported operating systems are 64-bit x86. Rancher should work with any modern Linux distribution.
Docker is required for nodes that will run RKE Kubernetes clusters. It is not required for RKE2 or K3s clusters.
The [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/) lists which OS and Docker versions were tested for each Rancher version.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
For details on which OS and Docker versions were tested with each Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
All supported operating systems are 64-bit x86.
Docker is required for nodes that will run RKE clusters. It is not required for RKE2 or K3s clusters.
The `ntp` (Network Time Protocol) package should be installed. This prevents errors with certificate validation that can occur when the time is not synchronized between the client and server.
@@ -65,7 +45,7 @@ For more information see [Installing Docker,](../getting-started/installation-an
For the container runtime, K3s bundles its own containerd by default. Alternatively, you can configure K3s to use an already installed Docker runtime. For more information on using K3s with Docker see the [K3s documentation.](https://docs.k3s.io/advanced#using-docker-as-the-container-runtime)
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/) To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script.
Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/). To specify the K3s version, use the INSTALL_K3S_VERSION environment variable when running the K3s installation script.
If you are installing Rancher on a K3s cluster with **Raspbian Buster**, follow [these steps](https://rancher.com/docs/k3s/latest/en/advanced/#enabling-legacy-iptables-on-raspbian-buster) to switch to legacy iptables.
@@ -75,7 +55,7 @@ If you are installing Rancher on a K3s cluster with Alpine Linux, follow [these
For the container runtime, RKE2 bundles its own containerd. Docker is not required for RKE2 installs.
For details on which OS versions were tested with RKE2, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
For details on which OS versions were tested with RKE2, refer to the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-10/).
## Hardware Requirements
versioned_docs/version-2.6/pages-for-subheaders/logging.md
+2 -2
View File
@@ -3,7 +3,7 @@ title: Rancher Integration with Logging Services
description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster.
---
The [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) now powers Rancher's logging solution in place of the former, in-house solution.
The [Logging operator](https://kube-logging.github.io/docs/) now powers Rancher's logging solution in place of the former, in-house solution.
For an overview of the changes in v2.5, see [this section.](../integrations-in-rancher/logging/logging-architecture.md#changes-in-rancher-v2-5) For information about migrating from Logging V1, see [this page.](../integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md)
@@ -117,7 +117,7 @@ By default, Rancher collects logs for control plane components and node componen
Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once.
For a more complete description of how to configure the logging buffer to suit your organization's needs, see the official BanzaiCloud documentation on [buffers](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/buffer/) and on [Fluentd configuration](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/fluentd/).
For a more complete description of how to configure the logging buffer to suit your organization's needs, see the official Logging operator documentation on [buffers](https://kube-logging.github.io/docs/configuration/plugins/outputs/buffer/) and on [Fluentd configuration](https://kube-logging.github.io/docs/logging-infrastructure/fluentd/).
### The `cattle-logging` Namespace Being Recreated
versioned_docs/version-2.6/pages-for-subheaders/manage-project-resource-quotas.md
+7 -1
View File
@@ -20,7 +20,13 @@ Edit resource quotas when:
1. In the upper left corner, click **☰ > Cluster Management**.
1. On the **Clusters** page, go to the cluster where you want to apply a resource quota and click **Explore**.
1. Click **Cluster > Projects/Namespaces**.
1. Find the project that you want to add a resource quota to. From that project, select **⋮ > Edit Config**.
1. Make sure that the **Projects/Namespaces** page is in **Group by Project** view mode.
![Screenshot highlighting the "Group by Project" icon, above the list of projects. It resembles a folder.](/img/edit-project-config-for-resource-quotas-group-by-project.png)
1. Find the project that you want to add a resource quota to, and select the **⋮** that's on the same row as the project's name.
![Screenshot highlighting triple dots icon at the end of the same row as the project name.](/img/edit-project-config-for-resource-quotas-dots.png)
1. Select **Edit Config**.
1. Expand **Resource Quotas** and click **Add Resource**. Alternatively, you can edit existing quotas.
versioned_docs/version-2.6/reference-guides/backup-restore-configuration/backup-configuration.md
+2 -2
View File
@@ -73,7 +73,7 @@ The S3 storage location contains the following configuration fields:
1. **Credential Secret** (optional): If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) The Credential Secret dropdown lists the secrets in all namespaces.
1. **Bucket Name**: The name of the S3 bucket where backup files will be stored.
1. **Region** (optional): The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. This field isn't needed for configuring MinIO.
1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported.
1. **Folder** (optional): The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket.
1. **Endpoint**: The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket.
1. **Endpoint CA** (optional): This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration)
1. **Skip TLS Verifications** (optional): Set to true if you are not using TLS.
@@ -84,7 +84,7 @@ The S3 storage location contains the following configuration fields:
| `credentialSecretName` | If you need to use the AWS Access keys Secret keys to access s3 bucket, create a secret with your credentials with keys and the directives `accessKey` and `secretKey`. It can be in any namespace as long as you provide that namespace in `credentialSecretNamespace`. An example secret is [here.](#example-credentialsecret) This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | |
| `credentialSecretNamespace` | The namespace of the secret containing the credentials to access S3. This directive is unnecessary if the nodes running your operator are in EC2 and set up with IAM permissions that allow them to access S3, as described in [this section.](#iam-permissions-for-ec2-nodes-to-access-s3) | |
| `bucketName` | The name of the S3 bucket where backup files will be stored. | ✓ |
| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. | |
| `folder` | The name of the folder in the S3 bucket where backup files will be stored. Nested folders (e.g., `rancher/cluster1`) are not supported. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket. | |
| `region` | The AWS [region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. | ✓ |
| `endpoint` | The [endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) that is used to access S3 in the region of your bucket. | ✓ |
| `endpointCA` | This should be the Base64 encoded CA cert. For an example, refer to the [example S3 compatible configuration.](#example-s3-storage-configuration) | |
versioned_docs/version-2.6/reference-guides/backup-restore-configuration/storage-configuration.md
+1 -1
View File
@@ -20,7 +20,7 @@ You can choose to not have any operator-level storage location configured. If yo
| Credential Secret | Choose the credentials for S3 from your secrets in Rancher. [Example](examples.md#example-credential-secret-for-storing-backups-in-s3). |
| Bucket Name | Enter the name of the [S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html) where the backups will be stored. Default: `rancherbackups`. |
| Region | The [AWS region](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) where the S3 bucket is located. |
| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. |
| Folder | The [folder in the S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html) where the backups will be stored. If this field is left empty, the default behavior is to store the backup files in the root folder of the S3 bucket. |
| Endpoint | The [S3 endpoint](https://docs.aws.amazon.com/general/latest/gr/s3.html) For example, `s3.us-west-2.amazonaws.com`. |
| Endpoint CA | The CA cert used to for the S3 endpoint. Default: base64 encoded CA cert |
| insecureTLSSkipVerify | Set to true if you are not using TLS. |
versioned_docs/version-2.6/reference-guides/best-practices/rancher-managed-clusters/logging-best-practices.md
+2 -2
View File
@@ -12,7 +12,7 @@ Before Rancher v2.5, logging in Rancher has historically been a pretty static in
Rancher provides a flexible experience for log aggregation. With the logging feature, administrators and users alike can deploy logging that meets fine-grained collection criteria while offering a wider array of destinations and configuration options.
"Under the hood", Rancher logging uses the Banzai Cloud logging operator. We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters.
"Under the hood", Rancher logging uses the [Logging operator](https://github.com/kube-logging/logging-operator). We provide manageability of this operator (and its resources), and tie that experience in with managing your Rancher clusters.
## Cluster-level Logging
@@ -44,7 +44,7 @@ Rancher logging will read all log entries in `/var/log/containers`, ensuring tha
Log collection only retrieves `stdout`/`stderr` logs from pods in Kubernetes. But what if we want to collect logs from other files that are generated by applications? Here, a log streaming sidecar (or two) may come in handy.
The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Banzai Logging Operator can pick up those logs and send them to your desired output.
The goal of setting up a streaming sidecar is to take log files that are written to disk, and have their contents streamed to `stdout`. This way, the Logging Operator can pick up those logs and send them to your desired output.
To set this up, edit your workload resource (e.g. Deployment) and add the following sidecar definition: