mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
some fixes
Signed-off-by: zhuxiujuan28 <562873187@qq.com>
This commit is contained in:
zhuxiujuan28
parent
c30fff5d2d
commit
9aa6fdfc49
|
|
@ -179,7 +179,7 @@ include::../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
|||
. Enter `<Node IP>:<Node Port>` in the browser to access WordPress from outside the cluster, as shown below.
|
||||
+
|
||||
--
|
||||
image::/images/ks-qkcp/zh/v4.1/wordpress-page.png[]
|
||||
image:/images/ks-qkcp/zh/v4.1/wordpress-page.png[]
|
||||
|
||||
// Note
|
||||
include::../../../_ks_components-en/admonitions/note.adoc[]
|
||||
|
|
|
|||
|
|
@ -281,7 +281,7 @@ mvn -Dmaven.test.skip=true clean package
|
|||
docker build -f Dockerfile-online -t $REGISTRY/$DOCKERHUB_NAMESPACE/$APP_NAME:SNAPSHOT-$BUILD_NUMBER .
|
||||
----
|
||||
|
||||
image::/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/shell_command.png[100%]
|
||||
image:/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/shell_command.png[100%]
|
||||
--
|
||||
|
||||
. Once more, click **Add nesting steps**, select **WithCredential**. Fill in the following fields in the dialog that appears, and then click **OK**.
|
||||
|
|
@ -291,7 +291,7 @@ image::/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-g
|
|||
* **Username Variable**: Enter **DOCKER_USERNAME**.
|
||||
* **Password Variable**: Enter **DOCKER_PASSWORD**.
|
||||
|
||||
image::/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/docker_credential.png[100%]
|
||||
image:/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/docker_credential.png[100%]
|
||||
|
||||
|
||||
[.admon.note,cols="a"]
|
||||
|
|
@ -311,7 +311,7 @@ For security reasons, account information is displayed as variables in the scrip
|
|||
echo "$DOCKER_PASSWORD" | docker login $REGISTRY -u "$DOCKER_USERNAME" --password-stdin
|
||||
----
|
||||
|
||||
image::/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/login_docker_command.png[100%]
|
||||
image:/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/login_docker_command.png[100%]
|
||||
--
|
||||
|
||||
. In the **WithCredential** step, click **Add nesting steps**. Select **shell** and enter the following command to push the SNAPSHOT image to Docker Hub. Click **OK** to complete the operation.
|
||||
|
|
@ -322,7 +322,7 @@ image::/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-g
|
|||
docker push $REGISTRY/$DOCKERHUB_NAMESPACE/$APP_NAME:SNAPSHOT-$BUILD_NUMBER
|
||||
----
|
||||
|
||||
image::/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/push_to_docker.png[100%]
|
||||
image:/images/ks-qkcp/en/devops-user-guide/use-devops/create-a-pipeline-using-graphical-editing-panel/push_to_docker.png[100%]
|
||||
--
|
||||
|
||||
=== Stage 5: Artifacts
|
||||
|
|
|
|||
|
|
@ -0,0 +1,27 @@
|
|||
---
|
||||
title: "Overview"
|
||||
description: "Learn about the WhizardTelemetry Data Pipeline extension."
|
||||
weight: 01
|
||||
---
|
||||
|
||||
The WhizardTelemetry Data Pipeline is an extension that provides capabilities to collect, transform, and route observability data.
|
||||
|
||||
|
||||
//attention
|
||||
[.admon.attention,cols="a"]
|
||||
|===
|
||||
| Note
|
||||
|
||||
|
|
||||
* The WhizardTelemetry Data Pipeline is a common dependency for WhizardTelemetry Logging, WhizardTelemetry Events, WhizardTelemetry Auditing, WhizardTelemetry Notification, etc., so it must be installed before the above extensions, otherwise, the logging, notification, auditing, and event functions will not work properly!
|
||||
|
||||
* The WhizardTelemetry Observability Platform supports querying logs, audits, events, notification history, etc., from OpenSearch, so you need to configure the OpenSearch service information for receiving logs, audits, events, notification history, etc., in the WhizardTelemetry Data Pipeline. It can be a user-built OpenSearch service or an OpenSearch service installed by the “OpenSearch Distributed Search and Analytics Engine” extension.
|
||||
|===
|
||||
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
|
|
||||
For more information about extension configuration, see the details page of the "WhizardTelemetry Data Pipeline" extension in the Extensions Center.
|
||||
|===
|
||||
|
|
@ -1,30 +1,7 @@
|
|||
---
|
||||
title: "WhizardTelemetry Data Pipeline"
|
||||
keywords: "Kubernetes, {ks_product-en}, platform settings, notification management"
|
||||
description: "Learn how to use the WhizardTelemetry Data Pipeline."
|
||||
weight: 02
|
||||
layout: "second"
|
||||
---
|
||||
|
||||
|
||||
The WhizardTelemetry Data Pipeline is an extension that provides capabilities to collect, transform, and route observability data.
|
||||
|
||||
|
||||
//attention
|
||||
[.admon.attention,cols="a"]
|
||||
|===
|
||||
| Note
|
||||
|
||||
|
|
||||
* The WhizardTelemetry Data Pipeline is a common dependency for WhizardTelemetry Logging, WhizardTelemetry Events, WhizardTelemetry Auditing, WhizardTelemetry Notification, etc., so it must be installed before the above extensions, otherwise, the logging, notification, auditing, and event functions will not work properly!
|
||||
|
||||
* The WhizardTelemetry Observability Platform supports querying logs, audits, events, notification history, etc., from OpenSearch, so you need to configure the OpenSearch service information for receiving logs, audits, events, notification history, etc., in the WhizardTelemetry Data Pipeline. It can be a user-built OpenSearch service or an OpenSearch service installed by the “OpenSearch Distributed Search and Analytics Engine” extension.
|
||||
|===
|
||||
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
|
|
||||
For more information about extension configuration, see the details page of the "WhizardTelemetry Data Pipeline" extension in the Extensions Center.
|
||||
|===
|
||||
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: "概览"
|
||||
description: "介绍如何使用 WhizardTelemetry 数据流水线。"
|
||||
weight: 01
|
||||
---
|
||||
|
||||
|
||||
WhizardTelemetry 数据流水线是 WhizardTelemetry 可观测平台中提供可观测性数据的收集、转换和路由能力的扩展组件。
|
||||
|
||||
|
||||
//attention
|
||||
[.admon.attention,cols="a"]
|
||||
|===
|
||||
| 注意
|
||||
|
||||
|
|
||||
* WhizardTelemetry 数据流水线是 WhizardTelemetry 日志、WhizardTelemetry 事件、WhizardTelemetry 审计、WhizardTelemetry 通知等共同依赖的扩展组件，因此在安装上述几个扩展组件之前必须先安装 WhizardTelemetry 数据流水线扩展组件，否则日志、通知、审计、事件等功能无法正常使用！
|
||||
|
||||
* WhizardTelemetry 可观测平台支持从 OpenSearch 查询日志、审计、事件、通知历史等数据，因此需要在 WhizardTelemetry 数据流水线扩展组件里统一配置接收日志、审计、事件、通知历史等数据的 OpenSearch 服务的信息，可以是用户自行搭建的 OpenSearch 服务，也可以是通过 OpenSearch 分布式检索与分析引擎这个扩展组件安装的 OpenSearch 服务。
|
||||
|===
|
||||
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|
||||
|
|
||||
有关组件配置的更多信息，请参阅扩展中心“WhizardTelemetry 数据流水线”扩展组件的详情页说明。
|
||||
|===
|
||||
|
|
@ -1,30 +1,6 @@
|
|||
---
|
||||
title: "WhizardTelemetry 数据流水线"
|
||||
keywords: "Kubernetes, {ks_product}, 平台设置, 通知管理"
|
||||
description: "介绍如何使用 WhizardTelemetry 数据流水线。"
|
||||
weight: 1.5
|
||||
layout: "second"
|
||||
---
|
||||
|
||||
|
||||
WhizardTelemetry 数据流水线是 WhizardTelemetry 可观测平台中提供可观测性数据的收集、转换和路由能力的扩展组件。
|
||||
|
||||
|
||||
//attention
|
||||
[.admon.attention,cols="a"]
|
||||
|===
|
||||
| 注意
|
||||
|
||||
|
|
||||
* WhizardTelemetry 数据流水线是 WhizardTelemetry 日志、WhizardTelemetry 事件、WhizardTelemetry 审计、WhizardTelemetry 通知等共同依赖的扩展组件，因此在安装上述几个扩展组件之前必须先安装 WhizardTelemetry 数据流水线扩展组件，否则日志、通知、审计、事件等功能无法正常使用！
|
||||
|
||||
* WhizardTelemetry 可观测平台支持从 OpenSearch 查询日志、审计、事件、通知历史等数据，因此需要在 WhizardTelemetry 数据流水线扩展组件里统一配置接收日志、审计、事件、通知历史等数据的 OpenSearch 服务的信息，可以是用户自行搭建的 OpenSearch 服务，也可以是通过 OpenSearch 分布式检索与分析引擎这个扩展组件安装的 OpenSearch 服务。
|
||||
|===
|
||||
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|
||||
|
|
||||
有关组件配置的更多信息，请参阅扩展中心“WhizardTelemetry 数据流水线”扩展组件的详情页说明。
|
||||
|===
|
||||
---
|
||||
Loading…
Reference in New Issue