This is an automated email from the ASF dual-hosted git repository.
catpineapple 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 8cff8de70e0 [k8s](docs)Fix spelling errors (#2060)
8cff8de70e0 is described below
commit 8cff8de70e0ca4aa3932d93883b4a1b5058f92e2
Author: catpineapple <catpineapple1...@gmail.com>
AuthorDate: Tue Feb 18 10:14:54 2025 +0800
[k8s](docs)Fix spelling errors (#2060)
## Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [ ] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
docs/ecosystem/doris-operator/doris-operator-overview.md | 2 +-
.../current/ecosystem/doris-operator/doris-operator-overview.md | 2 +-
.../version-2.1/ecosystem/doris-operator/doris-operator-overview.md | 2 +-
.../version-3.0/ecosystem/doris-operator/doris-operator-overview.md | 2 +-
.../version-2.1/ecosystem/doris-operator/doris-operator-overview.md | 2 +-
.../version-3.0/ecosystem/doris-operator/doris-operator-overview.md | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/ecosystem/doris-operator/doris-operator-overview.md
b/docs/ecosystem/doris-operator/doris-operator-overview.md
index 81278f85a6a..048c166a316 100644
--- a/docs/ecosystem/doris-operator/doris-operator-overview.md
+++ b/docs/ecosystem/doris-operator/doris-operator-overview.md
@@ -67,7 +67,7 @@ Based on the deployment definition provided by Doris
Operator, users can customi
- **Runtime debugging**:
- One of the biggest challenges for Trouble Shorting with containerized
services is how to debug at runtime. While pursuing availability and ease of
use, Doris Operator also provides more convenient conditions for problem
location. In the basic image of Doris, a variety of tools for problem location
are pre-set. When you need to view the status in real time, you can enter the
container through the exec command provided by kubectl and use the built-in
tools for troubleshooting.
+ One of the biggest challenges for Trouble Shooting with containerized
services is how to debug at runtime. While pursuing availability and ease of
use, Doris Operator also provides more convenient conditions for problem
location. In the basic image of Doris, a variety of tools for problem location
are pre-set. When you need to view the status in real time, you can enter the
container through the exec command provided by kubectl and use the built-in
tools for troubleshooting.
When the service cannot be started for unknown reasons, Doris Operator
provides a Debug running mode. When a Pod is set to Debug startup mode, the
container will automatically enter the running state. At this time, you can
enter the container through the `exec` command, manually start the service and
locate the problem. For details, please refer to [this
document](../../install/deploy-on-kubernetes/compute-storage-coupled/cluster-operation.md#How-to-enter-the-container-when-the-pod-crashes)
## Compatibility
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/doris-operator/doris-operator-overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/doris-operator/doris-operator-overview.md
index 60610e8b165..39010bc1d0f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/doris-operator/doris-operator-overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/ecosystem/doris-operator/doris-operator-overview.md
@@ -67,7 +67,7 @@ Doris Operator 的设计基于二层调度器的原理。每个组件的第一
- **运行时调试**：
- 容器化服务对于 Trouble Shorting 来说最大挑战之一是如何在运行时进行调试。Doris Operator
在追求可用性和易用性的同时，也为问题定位提供了更便利的条件。在 Doris
的基础镜像中，预置了多种用于问题定位的工具。当需要实时查看状态时，可以通过kubectl提供的exec命令进入容器，使用内置工具进行故障排查。
+ 容器化服务对于 Trouble Shooting 来说最大挑战之一是如何在运行时进行调试。Doris Operator
在追求可用性和易用性的同时，也为问题定位提供了更便利的条件。在 Doris
的基础镜像中，预置了多种用于问题定位的工具。当需要实时查看状态时，可以通过kubectl提供的exec命令进入容器，使用内置工具进行故障排查。
当服务因未知原因无法启动时，Doris Operator 提供了 Debug 运行模式。当一个 Pod 被设置为 Debug
启动模式时，容器将自动进入运行状态。这时可通过 `exec` 命令进入容器，手动启动服务并进行问题定位。详细请参考
[此文档](../../install/deploy-on-kubernetes/compute-storage-coupled/cluster-operation.md#服务-crash-情况下如何进入容器)
## 兼容性
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
index 23db3ddb4d9..fbeff315955 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
@@ -67,7 +67,7 @@ Doris Operator 的设计基于二层调度器的原理。每个组件的第一
- **运行时调试**：
- 容器化服务对于 Trouble Shorting 来说最大挑战之一是如何在运行时进行调试。Doris Operator
在追求可用性和易用性的同时，也为问题定位提供了更便利的条件。在 Doris
的基础镜像中，预置了多种用于问题定位的工具。当需要实时查看状态时，可以通过kubectl提供的exec命令进入容器，使用内置工具进行故障排查。
+ 容器化服务对于 Trouble Shooting 来说最大挑战之一是如何在运行时进行调试。Doris Operator
在追求可用性和易用性的同时，也为问题定位提供了更便利的条件。在 Doris
的基础镜像中，预置了多种用于问题定位的工具。当需要实时查看状态时，可以通过kubectl提供的exec命令进入容器，使用内置工具进行故障排查。
当服务因未知原因无法启动时，Doris Operator 提供了 Debug 运行模式。当一个 Pod 被设置为 Debug
启动模式时，容器将自动进入运行状态。这时可通过 `exec` 命令进入容器，手动启动服务并进行问题定位。详细请参考
[此文档](../../install/deploy-on-kubernetes/cluster-operation.md#服务-crash-情况下如何进入容器)
## 兼容性
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
index 60610e8b165..39010bc1d0f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
@@ -67,7 +67,7 @@ Doris Operator 的设计基于二层调度器的原理。每个组件的第一
- **运行时调试**：
- 容器化服务对于 Trouble Shorting 来说最大挑战之一是如何在运行时进行调试。Doris Operator
在追求可用性和易用性的同时，也为问题定位提供了更便利的条件。在 Doris
的基础镜像中，预置了多种用于问题定位的工具。当需要实时查看状态时，可以通过kubectl提供的exec命令进入容器，使用内置工具进行故障排查。
+ 容器化服务对于 Trouble Shooting 来说最大挑战之一是如何在运行时进行调试。Doris Operator
在追求可用性和易用性的同时，也为问题定位提供了更便利的条件。在 Doris
的基础镜像中，预置了多种用于问题定位的工具。当需要实时查看状态时，可以通过kubectl提供的exec命令进入容器，使用内置工具进行故障排查。
当服务因未知原因无法启动时，Doris Operator 提供了 Debug 运行模式。当一个 Pod 被设置为 Debug
启动模式时，容器将自动进入运行状态。这时可通过 `exec` 命令进入容器，手动启动服务并进行问题定位。详细请参考
[此文档](../../install/deploy-on-kubernetes/compute-storage-coupled/cluster-operation.md#服务-crash-情况下如何进入容器)
## 兼容性
diff --git
a/versioned_docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
b/versioned_docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
index d8513c309a7..8e0cb1ade64 100644
---
a/versioned_docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
+++
b/versioned_docs/version-2.1/ecosystem/doris-operator/doris-operator-overview.md
@@ -67,7 +67,7 @@ Based on the deployment definition provided by Doris
Operator, users can customi
- **Runtime debugging**:
- One of the biggest challenges for Trouble Shorting with containerized
services is how to debug at runtime. While pursuing availability and ease of
use, Doris Operator also provides more convenient conditions for problem
location. In the basic image of Doris, a variety of tools for problem location
are pre-set. When you need to view the status in real time, you can enter the
container through the exec command provided by kubectl and use the built-in
tools for troubleshooting.
+ One of the biggest challenges for Trouble Shooting with containerized
services is how to debug at runtime. While pursuing availability and ease of
use, Doris Operator also provides more convenient conditions for problem
location. In the basic image of Doris, a variety of tools for problem location
are pre-set. When you need to view the status in real time, you can enter the
container through the exec command provided by kubectl and use the built-in
tools for troubleshooting.
When the service cannot be started for unknown reasons, Doris Operator
provides a Debug running mode. When a Pod is set to Debug startup mode, the
container will automatically enter the running state. At this time, you can
enter the container through the `exec` command, manually start the service and
locate the problem. For details, please refer to [this
document](../../install/deploy-on-kubernetes/cluster-operation.md#How-to-enter-the-container-when-the-pod-crashes)
## Compatibility
diff --git
a/versioned_docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
b/versioned_docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
index 81278f85a6a..048c166a316 100644
---
a/versioned_docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
+++
b/versioned_docs/version-3.0/ecosystem/doris-operator/doris-operator-overview.md
@@ -67,7 +67,7 @@ Based on the deployment definition provided by Doris
Operator, users can customi
- **Runtime debugging**:
- One of the biggest challenges for Trouble Shorting with containerized
services is how to debug at runtime. While pursuing availability and ease of
use, Doris Operator also provides more convenient conditions for problem
location. In the basic image of Doris, a variety of tools for problem location
are pre-set. When you need to view the status in real time, you can enter the
container through the exec command provided by kubectl and use the built-in
tools for troubleshooting.
+ One of the biggest challenges for Trouble Shooting with containerized
services is how to debug at runtime. While pursuing availability and ease of
use, Doris Operator also provides more convenient conditions for problem
location. In the basic image of Doris, a variety of tools for problem location
are pre-set. When you need to view the status in real time, you can enter the
container through the exec command provided by kubectl and use the built-in
tools for troubleshooting.
When the service cannot be started for unknown reasons, Doris Operator
provides a Debug running mode. When a Pod is set to Debug startup mode, the
container will automatically enter the running state. At this time, you can
enter the container through the `exec` command, manually start the service and
locate the problem. For details, please refer to [this
document](../../install/deploy-on-kubernetes/compute-storage-coupled/cluster-operation.md#How-to-enter-the-container-when-the-pod-crashes)
## Compatibility
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
