This is an automated email from the ASF dual-hosted git repository.
luzhijing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 0744683483e k8s docs modify doris-operator (#600)
0744683483e is described below
commit 0744683483e2a7fc33e4282bfcf8551435c18c05
Author: catpineapple <[email protected]>
AuthorDate: Sat May 4 22:19:25 2024 +0800
k8s docs modify doris-operator (#600)
---
.../cluster-deployment/k8s-deploy/doris-cluster-upgrade.md | 10 +++++-----
.../cluster-deployment/k8s-deploy/doris-cluster-upgrade.md | 8 ++++----
.../cluster-deployment/k8s-deploy/doris-cluster-upgrade.md | 10 +++++-----
.../cluster-deployment/k8s-deploy/doris-cluster-upgrade.md | 8 ++++----
.../cluster-deployment/k8s-deploy/doris-cluster-upgrade.md | 10 +++++-----
.../cluster-deployment/k8s-deploy/doris-cluster-upgrade.md | 10 +++++-----
6 files changed, 28 insertions(+), 28 deletions(-)
diff --git
a/docs/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
b/docs/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
index 43a714950ea..5f60190fee2 100644
--- a/docs/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
+++ b/docs/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
@@ -1,6 +1,6 @@
---
{
-"title": "Upgrade Apache Doris cluster deployed by Doris-Operator",
+"title": "Upgrade Apache Doris cluster deployed by Doris Operator",
"language": "en"
}
---
@@ -24,9 +24,9 @@ specific language governing permissions and limitations
under the License.
-->
-This document describes how to use updates to upgrade an Apache Doris cluster
based on a Doris-Operator deployment.
+This document describes how to use updates to upgrade an Apache Doris cluster
based on a Doris Operator deployment.
-Similar to conventionally deployed cluster upgrades, Doris clusters deployed
by Doris-Operator still require rolling upgrades from BE to FE nodes.
Doris-Operator is based on Kubernetes' [Performing a Rolling
Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
provides rolling upgrade capabilities.
+Similar to conventionally deployed cluster upgrades, Doris clusters deployed
by Doris Operator still require rolling upgrades from BE to FE nodes. Doris
Operator is based on Kubernetes' [Performing a Rolling
Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
provides rolling upgrade capabilities.
## Things to note before upgrading
@@ -52,7 +52,7 @@ It is recommended to modify the `image` of the corresponding
cluster components
### Upgrade BE
-If you retain the cluster's crd (Doris-Operator defines the abbreviation of
`DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
+If you retain the cluster's crd (Doris Operator defines the abbreviation of
`DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
1. Modify `spec.beSpec.image`
@@ -90,7 +90,7 @@ When all Pods are rebuilt and enter the Running state, the
upgrade is complete.
### Upgrade FE
-If you retain the cluster's crd (Doris-Operator defines the abbreviation of
the `DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
+If you retain the cluster's crd (Doris Operator defines the abbreviation of
the `DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
1. Modify `spec.feSpec.image`
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
index e8487d34b62..74038cb78ba 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
@@ -1,6 +1,6 @@
---
{
-"title": "升级基于 Doris-Operator 部署的 Apache Doris 集群",
+"title": "升级基于 Doris Operator 部署的 Apache Doris 集群",
"language": "zh-CN"
}
---
@@ -25,9 +25,9 @@ under the License.
-->
-本文介绍如何使用 更新来升级 基于 Doris-Operator 部署的 Apache Doris 集群。
+本文介绍如何使用 更新来升级 基于 Doris Operator 部署的 Apache Doris 集群。
-和常规部署的集群升级类似，Doris-Operator 部署的 Doris 集群依然需要 BE 到 FE 节点滚动升级，Doris-Operator 基于
Kubernetes 的
[滚动更新功能](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
提供了滚动升级能力。
+和常规部署的集群升级类似，Doris Operator 部署的 Doris 集群依然需要 BE 到 FE 节点滚动升级，Doris Operator 基于
Kubernetes 的
[滚动更新功能](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
提供了滚动升级能力。
## 升级前注意事项
@@ -53,7 +53,7 @@ admin set frontend config("disable_tablet_scheduler" =
"true");
### 升级 BE
-如果保留了集群的 crd（Doris-Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
+如果保留了集群的 crd（Doris Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
1. 修改 `spec.beSpec.image`
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
index e1a8e1e5b6a..0a4223be044 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
@@ -1,6 +1,6 @@
---
{
-"title": "升级基于 Doris-Operator 部署的 Apache Doris 集群",
+"title": "升级基于 Doris Operator 部署的 Apache Doris 集群",
"language": "zh-CN"
}
---
@@ -25,9 +25,9 @@ under the License.
-->
-本文介绍如何使用 更新来升级 基于 Doris-Operator 部署的 Apache Doris 集群。
+本文介绍如何使用 更新来升级 基于 Doris Operator 部署的 Apache Doris 集群。
-和常规部署的集群升级类似，Doris-Operator 部署的 Doris 集群依然需要 BE 到 FE 节点滚动升级，Doris-Operator 基于
Kubernetes 的
[滚动更新功能](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
提供了滚动升级能力。
+和常规部署的集群升级类似，Doris Operator 部署的 Doris 集群依然需要 BE 到 FE 节点滚动升级，Doris Operator 基于
Kubernetes 的
[滚动更新功能](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
提供了滚动升级能力。
## 升级前注意事项
@@ -58,7 +58,7 @@ admin set frontend config("disable_tablet_scheduler" =
"true");
### 升级 BE
-如果保留了集群的 crd（Doris-Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
+如果保留了集群的 crd（Doris Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
1. 修改 `spec.beSpec.image`
@@ -95,7 +95,7 @@ $ kubectl get pod -n doris
### 升级 FE
-如果保留了集群的 crd（Doris-Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
+如果保留了集群的 crd（Doris Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
1. 修改 `spec.feSpec.image`
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
index e8487d34b62..74038cb78ba 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
@@ -1,6 +1,6 @@
---
{
-"title": "升级基于 Doris-Operator 部署的 Apache Doris 集群",
+"title": "升级基于 Doris Operator 部署的 Apache Doris 集群",
"language": "zh-CN"
}
---
@@ -25,9 +25,9 @@ under the License.
-->
-本文介绍如何使用 更新来升级 基于 Doris-Operator 部署的 Apache Doris 集群。
+本文介绍如何使用 更新来升级 基于 Doris Operator 部署的 Apache Doris 集群。
-和常规部署的集群升级类似，Doris-Operator 部署的 Doris 集群依然需要 BE 到 FE 节点滚动升级，Doris-Operator 基于
Kubernetes 的
[滚动更新功能](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
提供了滚动升级能力。
+和常规部署的集群升级类似，Doris Operator 部署的 Doris 集群依然需要 BE 到 FE 节点滚动升级，Doris Operator 基于
Kubernetes 的
[滚动更新功能](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
提供了滚动升级能力。
## 升级前注意事项
@@ -53,7 +53,7 @@ admin set frontend config("disable_tablet_scheduler" =
"true");
### 升级 BE
-如果保留了集群的 crd（Doris-Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
+如果保留了集群的 crd（Doris Operator 定义了 `DorisCluster` 类型资源名称的简写）文件，则可以通过修改该配置文件并且
`kubectl apply` 的命令来进行升级。
1. 修改 `spec.beSpec.image`
diff --git
a/versioned_docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
b/versioned_docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
index 43a714950ea..5f60190fee2 100644
---
a/versioned_docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
+++
b/versioned_docs/version-2.0/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
@@ -1,6 +1,6 @@
---
{
-"title": "Upgrade Apache Doris cluster deployed by Doris-Operator",
+"title": "Upgrade Apache Doris cluster deployed by Doris Operator",
"language": "en"
}
---
@@ -24,9 +24,9 @@ specific language governing permissions and limitations
under the License.
-->
-This document describes how to use updates to upgrade an Apache Doris cluster
based on a Doris-Operator deployment.
+This document describes how to use updates to upgrade an Apache Doris cluster
based on a Doris Operator deployment.
-Similar to conventionally deployed cluster upgrades, Doris clusters deployed
by Doris-Operator still require rolling upgrades from BE to FE nodes.
Doris-Operator is based on Kubernetes' [Performing a Rolling
Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
provides rolling upgrade capabilities.
+Similar to conventionally deployed cluster upgrades, Doris clusters deployed
by Doris Operator still require rolling upgrades from BE to FE nodes. Doris
Operator is based on Kubernetes' [Performing a Rolling
Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
provides rolling upgrade capabilities.
## Things to note before upgrading
@@ -52,7 +52,7 @@ It is recommended to modify the `image` of the corresponding
cluster components
### Upgrade BE
-If you retain the cluster's crd (Doris-Operator defines the abbreviation of
`DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
+If you retain the cluster's crd (Doris Operator defines the abbreviation of
`DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
1. Modify `spec.beSpec.image`
@@ -90,7 +90,7 @@ When all Pods are rebuilt and enter the Running state, the
upgrade is complete.
### Upgrade FE
-If you retain the cluster's crd (Doris-Operator defines the abbreviation of
the `DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
+If you retain the cluster's crd (Doris Operator defines the abbreviation of
the `DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
1. Modify `spec.feSpec.image`
diff --git
a/versioned_docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
b/versioned_docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
index 43a714950ea..5f60190fee2 100644
---
a/versioned_docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
+++
b/versioned_docs/version-2.1/install/cluster-deployment/k8s-deploy/doris-cluster-upgrade.md
@@ -1,6 +1,6 @@
---
{
-"title": "Upgrade Apache Doris cluster deployed by Doris-Operator",
+"title": "Upgrade Apache Doris cluster deployed by Doris Operator",
"language": "en"
}
---
@@ -24,9 +24,9 @@ specific language governing permissions and limitations
under the License.
-->
-This document describes how to use updates to upgrade an Apache Doris cluster
based on a Doris-Operator deployment.
+This document describes how to use updates to upgrade an Apache Doris cluster
based on a Doris Operator deployment.
-Similar to conventionally deployed cluster upgrades, Doris clusters deployed
by Doris-Operator still require rolling upgrades from BE to FE nodes.
Doris-Operator is based on Kubernetes' [Performing a Rolling
Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
provides rolling upgrade capabilities.
+Similar to conventionally deployed cluster upgrades, Doris clusters deployed
by Doris Operator still require rolling upgrades from BE to FE nodes. Doris
Operator is based on Kubernetes' [Performing a Rolling
Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/)
provides rolling upgrade capabilities.
## Things to note before upgrading
@@ -52,7 +52,7 @@ It is recommended to modify the `image` of the corresponding
cluster components
### Upgrade BE
-If you retain the cluster's crd (Doris-Operator defines the abbreviation of
`DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
+If you retain the cluster's crd (Doris Operator defines the abbreviation of
`DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
1. Modify `spec.beSpec.image`
@@ -90,7 +90,7 @@ When all Pods are rebuilt and enter the Running state, the
upgrade is complete.
### Upgrade FE
-If you retain the cluster's crd (Doris-Operator defines the abbreviation of
the `DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
+If you retain the cluster's crd (Doris Operator defines the abbreviation of
the `DorisCluster` type resource name) file, you can upgrade by modifying the
configuration file and running the `kubectl apply` command.
1. Modify `spec.feSpec.image`
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
