mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Merge pull request #3217 from zhuxiujuan28/docs
【documentation】finish translation of extensions
This commit is contained in:
KubeSphere CI Bot
GitHub
commit
a4f17952f2
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 28a65f11229c45f0bcd1b632d006acbb
|
||||
* Click image:/images/ks-qkcp/zh/icons/refresh-light.svg[refresh,18,18] in the upper right corner of the list to refresh the list information.
|
||||
* Click image:/images/ks-qkcp/zh/icons/refresh-light.svg[refresh,18,18] in the upper right corner of the list to refresh the list information.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 7a00832787eb484492170688816b225c
|
||||
本节介绍如何查看告警列表。
|
||||
This section describes how to view the alert list.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: a11cb13f4c4d44e59332bb4fe44859c0
|
||||
. 在**告警**页面点击**来源于自定义规则**或**来源于内置规则**打开告警列表。
|
||||
. On the **Alerts** page, click **From Custom Rules** or **From Built-in Rules** to open the alert list.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: c6a3057001e24f3d85a69f8429cf509c
|
||||
* 在列表上方点击搜索框并设置搜索条件，可按告警内容、告警状态、告警级别和规则名称搜索告警。
|
||||
* Click the search box above the list to search for alerts by alert content, alert status, severity, and rule name.
|
||||
|
|
@ -1,36 +1,36 @@
|
|||
// :ks_include_id: 9bb30ff8148c403aa266fbe96dcaa2a8
|
||||
* 告警列表提供以下信息：
|
||||
* The alert list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|消息
|
||||
|Message
|
||||
|
|
||||
include::../ruleGroups/ruleGroups-para-message.adoc[]
|
||||
|
||||
|状态
|
||||
|Status
|
||||
|
|
||||
告警当前的状态。
|
||||
The current status of the alert.
|
||||
|
||||
include::alerts-para-alertingStatus.adoc[]
|
||||
|
||||
|告警级别
|
||||
|Severity
|
||||
|
|
||||
include::../ruleGroups/ruleGroups-para-alertLevel.adoc[]
|
||||
|
||||
|规则名称
|
||||
|告警规则的名称。
|
||||
|Alerting Name
|
||||
|The name of the alert rule.
|
||||
|
||||
|规则组
|
||||
|告警规则组的名称。
|
||||
|Rule Group
|
||||
|The name of the alerting rule group.
|
||||
|
||||
|监控目标
|
||||
|生成告警的监控目标的类型和名称。
|
||||
|Monitored Target
|
||||
|The type and name of the monitored target that generated the alert.
|
||||
|
||||
|触发时间
|
||||
|Trigger Time
|
||||
|
|
||||
include::../ruleGroups/ruleGroups-para-activationTime.adoc[]
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: eb9742b579e948b29be0240b89d9335b
|
||||
* **验证中**：监控指标满足预设的条件，但未满足预设的持续时间。
|
||||
* **Pending**: The monitoring metrics meet the preset conditions but do not meet the preset duration.
|
||||
|
||||
* **已触发**：监控指标满足预设的条件，并且满足预设的持续时间。
|
||||
* **Firing**: The monitoring metrics meet the preset conditions and the preset duration.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: f3341457c4584e59b799240a35ca496d
|
||||
您需要加入一个集群或项目，并在集群或项目中具有pass:a,q[{ks_permission}]权限。有关更多信息，请参阅xref:07-cluster-management/09-cluster-settings/04-cluster-roles/_index.adoc[集群角色]和xref:09-project-management/06-project-settings/02-project-roles/_index.adoc[项目角色]。
|
||||
You should join a cluster or a project and have the pass:a,q[{ks_permission}] permission within the cluster or the project. For more information, refer to "Cluster Roles" and "Project Roles".
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: c545dcba1c5d46908a87e91f9fc37f77
|
||||
* 在列表右上角点击**导出**可下载 JSON 格式的资源用量数据。
|
||||
* Click **Export** in the upper right corner of the list to download the resource usage data in JSON format.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 3a85d5dfa0a2462c87c54f9779cfbdc6
|
||||
* 在列表左上角点击image:/images/ks-qkcp/zh/icons/sort-ascending.svg[sort-ascending,18,18]/image:/images/ks-qkcp/zh/icons/sort-descending.svg[sort-descending,18,18]可按升序/降序排序。
|
||||
* Click image:/images/ks-qkcp/zh/icons/sort-ascending.svg[sort-ascending,18,18]/image:/images/ks-qkcp/zh/icons/sort-descending.svg[sort-descending,18,18] in the upper left corner of the list to sort in ascending/descending order.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 09ffce0603e5476d9b35342407c90402
|
||||
本节介绍如何创建自定义监控面板。
|
||||
This section introduces how to create a custom monitoring dashboard.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 3f3c9d810bbb43449843917a945b0d18
|
||||
本节介绍如何使用自定义监控面板。
|
||||
This section introduces how to use custom monitoring dashboards.
|
||||
|
|
@ -1,9 +1,9 @@
|
|||
// :ks_include_id: ebf1355e06284d8a8c1f0d1c6ae2dcdf
|
||||
本节介绍如何删除自定义监控面板。
|
||||
This section introduces how to delete a custom monitoring dashboard.
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
自定义监控面板删除后无法恢复，请谨慎执行此操作。
|
||||
Custom monitoring dashboards cannot be recovered after deletion, so please proceed with caution.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 0a4f15a804bd4a04b35fa4baec7bca69
|
||||
本节介绍如何编辑自定义监控面板。
|
||||
This section introduces how to edit a custom monitoring dashboard.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: fb5da34edef1455388ca60e23308095f
|
||||
. 配置运行在容器中的应用程序，将符合 Prometheus 规范的监控指标暴露在某个服务端路径下。有关更多信息，请参阅 link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus 官方文档]。
|
||||
. Configure applications running in containers to expose monitoring metrics that conform to the Prometheus specification at a certain service endpoint. For more information, see the link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus Documentation].
|
||||
|
||||
. 在 KubeSphere Web 控制台，在用于暴露工作负载的服务上设置监控导出器，以声明提供应用程序监控指标的路径。KubeSphere 将根据监控导出器的相关参数获取应用程序的监控指标。
|
||||
. In the {ks_product-en} web console, set up a monitoring exporter on the service exposing the workload to declare the path providing application monitoring metrics. KubeSphere will get the application's monitoring metrics based on the relevant parameters of the monitoring exporter.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 86dce4cf97db45baa0af638a00a5a435
|
||||
KubeSphere 支持通过自定义监控面板对应用程序的运行状态进行监控。您可以通过以下方式使用自定义监控面板：
|
||||
KubeSphere supports monitoring the running status of applications through custom monitoring dashboards. You can use custom monitoring dashboards in the following ways:
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 459d38d3365247858833ed44c54b075d
|
||||
本节介绍如何查看自定义监控面板。
|
||||
This section introduces how to view a custom monitoring dashboard.
|
||||
|
|
@ -1,42 +1,42 @@
|
|||
// :ks_include_id: 5b3a15eedffe4ef39e6a46e6adc2b335
|
||||
. 在**创建自定义监控面板**对话框，设置监控面板的名称、描述和模板，然后点击**下一步**。
|
||||
. In the **Create Custom Monitoring Dashboard** dialog, set the name, description, and template of the monitoring dashboard, then click **Next**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|自定义监控面板的名称。名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 63 个字符。
|
||||
|Name
|
||||
|The name of the custom monitoring dashboard. The name can only contain lowercase letters, numbers, and hyphens (-), must start and end with a lowercase letter or number, and can be up to 63 characters long.
|
||||
|
||||
|描述
|
||||
|自定义监控面板的描述信息。描述可包含任意字符，最长 256 个字符。
|
||||
|Description
|
||||
|The description of the custom monitoring dashboard. The description can contain any characters and can be up to 256 characters long.
|
||||
|
||||
|模板
|
||||
|自定义监控面板的模板。
|
||||
|Template
|
||||
|The template of the custom monitoring dashboard.
|
||||
|
||||
* KubeSphere 提供预置了 Elasticsearch、MySQL、Redis、Jenkins 和 GPU 自定义监控面板的模板。每个模板都提供了一些预置的监控指标和监控图，您可以在模板的基础上进行定制以减少操作。
|
||||
* KubeSphere provides templates with preset custom monitoring dashboards for Elasticsearch, MySQL, Redis, Jenkins, and GPU. Each template provides some preset monitoring metrics and monitoring charts, which you can customize on top of to reduce operations.
|
||||
|
||||
* 如需使用 Grafana 监控面板，您需要上传 Grafana 监控面板配置文件。
|
||||
* To use a Grafana dashboard, you need to upload the Grafana dashboard configuration file.
|
||||
|
||||
* 您也可以使用选择**自定义**使用空模板。
|
||||
* You can also choose **Custom** to use an empty template.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在自定义监控面板编辑页面，根据需要设置监控图和以文本显示的监控指标。
|
||||
. On the custom monitoring dashboard editing page, set the monitoring charts and text-displayed monitoring metrics as needed.
|
||||
+
|
||||
====
|
||||
* 在页面左侧点击image:/images/ks-qkcp/zh/icons/add-dark.svg[add-dark,18,18]，设置指标参数，然后点击image:/images/ks-qkcp/zh/icons/check-dark.svg[check-dark,18,18]可创建以文本显示的监控指标。
|
||||
* Click image:/images/ks-qkcp/zh/icons/add-dark.svg[add-dark,18,18] on the left side of the page, set the metric parameters, then click image:/images/ks-qkcp/zh/icons/check-dark.svg[check-dark,18,18] to create text-displayed monitoring metrics.
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-textMetric.adoc[]
|
||||
--
|
||||
|
||||
* 在页面右下角点击**添加监控项**，选择**折线图**或**柱状图**，设置图表参数，然后点击image:/images/ks-qkcp/zh/icons/check-dark.svg[check-dark,18,18]可创建监控图。
|
||||
* Click **Add Monitoring Item** in the lower right corner of the page, select **Line Chart** or **Bar Chart**, set the chart parameters, then click image:/images/ks-qkcp/zh/icons/check-dark.svg[check-dark,18,18] to create monitoring charts.
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-monitoringChart.adoc[]
|
||||
--
|
||||
====
|
||||
|
||||
. 在页面右上角点击**保存模板**。监控面板创建完成后将显示在自定义监控面板列表中。
|
||||
. Click **Save Template** in the upper right corner of the page. After the monitoring dashboard is created, it will be displayed in the custom monitoring dashboard list.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 91f54871ad6f447eaca67f6b1853872e
|
||||
. 在需要删除的自定义监控面板右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**删除**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the custom monitoring dashboard you want to delete, then select **Delete** from the dropdown list.
|
||||
|
||||
. 在**删除自定义监控面板**对话框，输入自定义监控面板的名称，然后点击**确定**。
|
||||
. In the **Delete Custom Monitoring Dashboard** dialog, enter the name of the custom monitoring dashboard, then click **OK**.
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
// :ks_include_id: da77b27e5b9840dab0503615aec625a4
|
||||
. 选择需要删除的自定义监控面板左侧的复选框，然后在自定义监控面板列表上方点击**删除**。
|
||||
. Select the checkbox on the left side of the custom monitoring dashboards you want to delete, then click **Delete** above the custom monitoring dashboard list.
|
||||
|
||||
. 在**批量删除自定义监控面板**对话框，输入自定义监控面板的名称，然后点击**确定**。
|
||||
. In the **Delete Multiple Custom Monitoring Dashboards** dialog, enter the names of the custom monitoring dashboards, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
|
|
|
|||
|
|
@ -1,32 +1,34 @@
|
|||
// :ks_include_id: 1762c0ce44e445d89cd9f2e5b34055fa
|
||||
. 在列表中点击一个自定义监控面板的名称打开自定义监控面板，然后在页面右上角点击**编辑模板**。
|
||||
. Click the name of a custom monitoring dashboard in the list to open the custom monitoring dashboard, then click **Edit Template** in the upper right corner of the page.
|
||||
|
||||
. 在页面左侧设置以文本显示的监控指标。
|
||||
. Set the text-displayed monitoring metrics on the left side of the page.
|
||||
+
|
||||
====
|
||||
* 点击image:/images/ks-qkcp/zh/icons/add-dark.svg[add-dark,18,18]可添加监控指标。
|
||||
* Click image:/images/ks-qkcp/zh/icons/add-dark.svg[add-dark,18,18] to add monitoring metrics.
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-textMetric.adoc[]
|
||||
--
|
||||
|
||||
* 将光标悬停在监控指标上，然后点击image:/images/ks-qkcp/zh/icons/trash-dark.svg[trash-dark,18,18]可删除监控指标。
|
||||
* Hover the cursor over a monitoring metric, then click image:/images/ks-qkcp/zh/icons/trash-dark.svg[trash-dark,18,18] to delete the monitoring metric.
|
||||
|
||||
* 将光标悬停在监控指标上，然后点击image:/images/ks-qkcp/zh/icons/pen-dark.svg[pen-dark,18,18]可编辑监控指标。
|
||||
* Hover the cursor over a monitoring metric, then click image:/images/ks-qkcp/zh/icons/pen-dark.svg[pen-dark,18,18] to edit the monitoring metric.
|
||||
====
|
||||
|
||||
. 在页面右侧的监控图列表设置监控图。
|
||||
. Set the monitoring charts in the monitoring chart list on the right side of the page.
|
||||
+
|
||||
====
|
||||
* 点击**添加监控项**可添加监控图。
|
||||
* Click **Add Monitoring Item** to add monitoring charts.
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-monitoringChart.adoc[]
|
||||
--
|
||||
|
||||
* 将光标悬停在监控图名称上，然后点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除监控图。
|
||||
* Hover the cursor over the monitoring chart name, then click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] to delete the monitoring chart.
|
||||
|
||||
* 将光标悬停在监控图名称上，然后点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen-light,18,18]可编辑监控图。
|
||||
* Hover the cursor over the monitoring chart name, then click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen-light,18,18] to edit the monitoring chart.
|
||||
|
||||
* Drag image:/images/ks-qkcp/zh/icons/drag-handle.svg[drag-handle,18,18] on the right side to adjust the sorting of the monitoring charts.
|
||||
====
|
||||
|
||||
. 在页面右上角点击**保存模板**完成编辑。
|
||||
. Click **Save Template** in the upper right corner of the page to complete the editing.
|
||||
|
|
@ -1,17 +1,17 @@
|
|||
// :ks_include_id: f41b68cc492640acadc07b371d665ebb
|
||||
. 在需要操作的自定义监控面板右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**编辑信息**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the custom monitoring dashboard you want to edit, then select **Edit Information** from the dropdown list.
|
||||
|
||||
. 在**编辑信息**对话框，设置自定义监控面板的别名和描述，然后点击**确定**。
|
||||
. In the **Edit Information** dialog, set the alias and description of the custom monitoring dashboard, then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|别名
|
||||
|自定义监控面板的别名。不同自定义监控面板的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
|Alias
|
||||
|The alias of the custom monitoring dashboard. Different custom monitoring dashboards can have the same alias. The alias can only contain Chinese characters, letters, numbers, and hyphens (-), and cannot start or end with a hyphen (-), with a maximum of 63 characters.
|
||||
|
||||
|描述
|
||||
|自定义监控面板的描述信息。描述可包含任意字符，最多包含 256 个字符。
|
||||
|Description
|
||||
|The description of the custom monitoring dashboard. The description can contain any characters, with a maximum of 256 characters.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: b79841529a1d49a19e7e17eac5decf19
|
||||
. 在 KubeSphere Web 控制台，使用监控指标创建自定义监控面板，从而对应用程序的运行状况进行监控。
|
||||
. In the {ks_product-en} web console, create custom monitoring dashboards using monitoring metrics to monitor the running status of applications.
|
||||
|
|
@ -1,18 +1,18 @@
|
|||
// :ks_include_id: d52d25b1598e4adb94ab8b79c98a1e00
|
||||
. 在列表中点击一个自定义监控面板的名称打开监控面板。
|
||||
. Click the name of a custom monitoring dashboard in the list to open the dashboard.
|
||||
+
|
||||
--
|
||||
* 在页面左侧区域可查看以文本显示的监控指标。
|
||||
* View text-displayed monitoring metrics in the left area of the page.
|
||||
|
||||
* 在页面中间区域可查看监控指标折线图或柱状图。
|
||||
* View line charts or bar charts of monitoring metrics in the middle area of the page.
|
||||
|
||||
* 在页面右侧点击image:/images/ks-qkcp/zh/icons/chevron-right.svg[chevron-right,18,18]可查看每个监控指标的子指标及其在指定时间范围内的最大值、最小值、平均值和最后采样值。
|
||||
* Click image:/images/ks-qkcp/zh/icons/chevron-right.svg[chevron-right,18,18] on the right side of the page to view sub-metrics of each monitoring metric and their maximum, minimum, average, and last sampled values within the specified time range.
|
||||
|
||||
* 在页面上方点击image:/images/ks-qkcp/zh/icons/theme.svg[theme,18,18]可切换浅色和深色主题。
|
||||
* Click image:/images/ks-qkcp/zh/icons/theme.svg[theme,18,18] at the top of the page to switch between light and dark themes.
|
||||
|
||||
* 在页面上方点击image:/images/ks-qkcp/zh/icons/calendar-dark.svg[calendar-dark,18,18]可设置数据的时间范围。
|
||||
* Click image:/images/ks-qkcp/zh/icons/calendar-dark.svg[calendar-dark,18,18] at the top of the page to set the time range of the data.
|
||||
|
||||
* 在页面上方点击image:/images/ks-qkcp/zh/icons/refresh-dark.svg[refresh-dark,18,18]可设置数据的刷新间隔。
|
||||
* Click image:/images/ks-qkcp/zh/icons/refresh-dark.svg[refresh-dark,18,18] at the top of the page to set the refresh interval of the data.
|
||||
|
||||
* 在页面右上角点击image:/images/ks-qkcp/zh/icons/close-dark.svg[close,18,18]可返回自定义监控面板列表。
|
||||
--
|
||||
* Click image:/images/ks-qkcp/zh/icons/close-dark.svg[close,18,18] in the upper right corner of the page to return to the custom monitoring dashboard list.
|
||||
--
|
||||
|
|
@ -1,30 +1,30 @@
|
|||
// :ks_include_id: 02c275a851594f868957a3c32ff9f5cd
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|图例类型
|
||||
|监控图的纵向数据展示方式，可选类型包括**基础图**和**堆叠图**。
|
||||
|Graph Types
|
||||
|The vertical data display method of the monitoring chart, with options including **Basic Chart** and **Stacked Chart**.
|
||||
|
||||
|图表配色
|
||||
|监控图的配色风格，可选类型包括**默认配色**、**冷色调**和**暖色调**。
|
||||
|Chart Colors
|
||||
|The color scheme of the monitoring chart, with options including **Default Colors**, **Cool Colors**, and **Warm Colors**.
|
||||
|
||||
|基本信息
|
||||
|用户自定义的监控图名称和描述信息。
|
||||
|Basic Information
|
||||
|User-defined name and description for the monitoring chart.
|
||||
|
||||
|数据
|
||||
|监控图中显示的监控指标。
|
||||
|Data
|
||||
|The monitoring metrics displayed in the monitoring chart.
|
||||
|
||||
* **图例名称**：用户自定义的监控指标名称。
|
||||
* **Metric Name**: User-defined name for the monitoring metric.
|
||||
|
||||
* **间隔**：监控图中数据的时间间隔，取值为 <数值><单位>，例如 **1m** 表示数据时间间隔为 1 分钟。
|
||||
* **Interval**: The time interval of the data in the monitoring chart, with a value of <number><unit>, for example, **1m** means the data time interval is 1 minute.
|
||||
|
||||
* **监控指标**：应用程序暴露的监控指标。您可以点击**监控指标**然后在下拉列表中选择监控指标，也可以手动输入 PromQL 语句。请确保您已配置应用程序暴露监控指标，并已配置监控导出器。有关 PromQL 表达式的更多信息，请参阅 link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus 官方文档]。
|
||||
* **Monitoring Metric**: The monitoring metrics exposed by the application. You can click **Monitoring Metric** and then select a monitoring metric from the dropdown list, or manually enter a PromQL statement. Ensure that you have configured the application to expose monitoring metrics and have set up the monitoring exporter. For more information about PromQL expressions, see the link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus Documentation].
|
||||
|
||||
|Y 轴
|
||||
|监控图的纵坐标轴设置。
|
||||
|Y Axis
|
||||
|Settings for the vertical axis of the monitoring chart.
|
||||
|
||||
* **单位**：纵坐标轴的数据单位。
|
||||
* **Unit**: The unit of the data on the vertical axis.
|
||||
|
||||
* **精确位**：纵坐标轴数据的有效小数位数。
|
||||
* **Decimal Places**: The number of significant decimal places in the data on the vertical axis.
|
||||
|===
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 5ed9a5c35fa945bc84988f238d7ab69a
|
||||
应用程序暴露的监控指标。您可以点击**监控指标**然后在下拉列表中选择监控指标，也可以手动输入 PromQL 语句。请确保您已配置应用程序暴露监控指标，并已配置监控导出器。有关 PromQL 表达式的更多信息，请参阅 link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus 官方文档]。
|
||||
The monitoring metrics exposed by the application. You can click **Monitoring Metric** and then select a monitoring metric from the dropdown list, or manually enter a PromQL statement. Ensure that you have configured the application to expose monitoring metrics and have set up the monitoring exporter. For more information about PromQL expressions, see the link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus Documentation].
|
||||
|
|
@ -1,18 +1,18 @@
|
|||
// :ks_include_id: 6d474f2ff06e43c7bc9003aaa10e29c2
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|图表名称
|
||||
|监控指标的名称。
|
||||
|Chart Name
|
||||
|The name of the monitoring metric.
|
||||
|
||||
|单位
|
||||
|指标数据的单位。
|
||||
|Unit
|
||||
|The unit of the metric data.
|
||||
|
||||
|精确位
|
||||
|指标数据的有效小数位数。
|
||||
|Decimal Places
|
||||
|The number of significant decimal places in the metric data.
|
||||
|
||||
|监控指标
|
||||
|Monitoring Metric
|
||||
|
|
||||
include::customMonitoringDashboards-para-monitoringMetric.adoc[]
|
||||
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 385623699d0d48bda614b5a8de5c062d
|
||||
* 您需要配置运行在容器中的应用程序将符合 Prometheus 规范的监控指标暴露在某个服务端路径下。有关更多信息，请参阅 link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus 官方文档]。
|
||||
* Configure applications running in containers to expose monitoring metrics that conform to the Prometheus specification at a certain service endpoint. For more information, see the link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus Documentation].
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 854355fa9af44f41886ade72f0ee39da
|
||||
网关为 KubeSphere 平台上的服务提供反向代理。网关需要根据应用路由工作，来自客户端的业务流量先通过域名解析先发送给网关，网关再根据应用路由中定义的规则将业务流量转发给不同的服务。网关本身也是通过服务暴露的工作负载，因而网关也支持 NodePort 和 LoadBalancer 两种外部访问模式。
|
||||
The gateway provides reverse proxy for services on the KubeSphere platform. The gateway needs to work according to the Ingresses. Business traffic from clients is first sent to the gateway through domain name resolution, and then the gateway forwards the business traffic to different services according to the rules defined in the Ingresses. The gateway itself is also a workload exposed through services, so the gateway also supports two external access modes: NodePort and LoadBalancer.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 7ea2a84e80b6439cb0d2da5db17f8e35
|
||||
. 在页面右侧选择**管理 > 禁用**。
|
||||
. On the right side of the page, select **Manage > Disable**.
|
||||
|
||||
. 在弹出的对话框点击**确定**。
|
||||
. In the pop-up dialog box, click **OK**.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
// :ks_include_id: 17ab622bc96f45e68b3581c076cb1223
|
||||
. 在页面右侧选择**管理 > 编辑**。
|
||||
|
||||
. 在弹出的对话框，修改网关的参数，然后点击**确定**。
|
||||
+
|
||||
--
|
||||
include::gatewaySettings-para-enableGateway.adoc[]
|
||||
--
|
||||
|
|
@ -1,34 +1,33 @@
|
|||
// :ks_include_id: 17ab622bc96f45e68b3581c076cb1223
|
||||
. 在页面右侧选择**管理 > 编辑**。
|
||||
. On the right side of the page, select **Manage > Edit**.
|
||||
|
||||
. 在弹出的对话框，修改网关的参数，然后点击**确定**。
|
||||
. In the pop-up dialog box, modify the parameters of the gateway, and then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|IngressClassName
|
||||
|IngressClass 的名称。
|
||||
|The name of the IngressClass.
|
||||
|
||||
|容器组副本数量
|
||||
|期望的容器组副本数量。
|
||||
|Pod Replicas
|
||||
|The desired number of pod replicas.
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|Access Mode
|
||||
|The external access mode of the gateway service.
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|链路追踪
|
||||
|是否对网关启用链路追踪功能。如需使用链路追踪功能，KubeSphere 平台需要安装并启用 **KubeSphere 服务网格**扩展组件。
|
||||
|Tracing
|
||||
|Whether to enable tracing for the gateway. To use the tracing function, **KubeSphere Service Mesh** should be installed and enabled.
|
||||
|
||||
|配置选项
|
||||
|网关的配置选项。KubeSphere 的网关功能底层基于 Nginx Ingress Controller 实现，您可以设置网关的配置选项控制网关的行为。有关更多信息，请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|Configuration Options
|
||||
|The configuration options for the gateway. The gateway functionality of KubeSphere is based on Nginx Ingress Controller. You can set the configuration options for the gateway to control its behavior. For more information, please refer to the link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller Documentation].
|
||||
|
||||
|负载均衡器提供商
|
||||
|网关的负载均衡器提供商。网关的外部访问模式为 LoadBalancer 时，您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。选择负载均衡器提供商后，设置网关服务注解时系统将提供注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。
|
||||
|Load Balancer Provider
|
||||
|The load balancer provider for the gateway. When the external access mode of the gateway service is LoadBalancer, you need to set the annotations of the gateway service according to the load balancer plugin and infrastructure environment to create the required load balancer. After selecting the load balancer provider, the system will provide annotation hints when setting the gateway service annotations. Only available when the external access mode of the gateway service is LoadBalancer.
|
||||
|
||||
|注解
|
||||
|网关服务的注解。如果已选择负载均衡器提供商，点击**键**文本框时系统将在下拉列表中显示注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。有关更多信息，请联系您的基础设施环境提供商。
|
||||
|Annotations
|
||||
|The annotations of the gateway service. If a load balancer provider has been selected, the system will display annotation hints in the dropdown list when clicking the **Key** text box. Only available when the external access mode of the gateway service is LoadBalancer. For more information, please contact your infrastructure environment provider.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,109 +0,0 @@
|
|||
// :ks_include_id: 2603654cc618449f9ae430c3041a361f
|
||||
. 在页面右侧选择**管理 > 查看详情**打开网关详情页面。
|
||||
|
||||
. 在网关详情页面左侧的**属性**区域查看网关的资源属性。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|集群
|
||||
|网关所属的集群。
|
||||
|
||||
|创建时间
|
||||
|网关的创建时间。
|
||||
|
||||
|更新时间
|
||||
|网关的更新时间
|
||||
|
||||
|创建者
|
||||
|启用网关的用户。
|
||||
|===
|
||||
--
|
||||
|
||||
. 在页面右侧的**监控**页签查看网关的请求数据。
|
||||
+
|
||||
====
|
||||
* **概览**区域提供以下信息：
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|总请求数量
|
||||
|指定时间范围内网关接收的请求总数。
|
||||
|
||||
|请求数量
|
||||
|指定时间范围内响应状态码为 4XX 或 5XX 的请求数量。点击下拉列表可分别查看 4XX 请求和 5XX 请求的数量。
|
||||
|
||||
|成功请求
|
||||
|指定时间范围内成功请求的百分比。
|
||||
|
||||
|平均延迟
|
||||
|指定时间范围内所有请求的平均延迟。
|
||||
|
||||
|P50 延迟
|
||||
|指定时间范围内所有请求延迟的中位数。
|
||||
|
||||
|P95 延迟
|
||||
|指定时间范围内所有请求的 95% 分位延迟，即 95% 的请求的延迟小于或等于该数值。
|
||||
|
||||
|P99 延迟
|
||||
|指定时间范围内所有请求的 99% 分位延迟，即 99% 的请求的延迟小于或等于该数量。
|
||||
|===
|
||||
--
|
||||
|
||||
* 页面下方以折线图显示动态的请求数据。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|请求数量
|
||||
|指定时间范围内网关接收的每秒请求数量。
|
||||
|
||||
|连接数量
|
||||
|指定时间范围内网关接收的每秒连接数量。
|
||||
|
||||
|请求延迟
|
||||
|指定时间范围内所有请求的延迟中位数、95% 分位延迟、99% 分位延迟和平均延迟。
|
||||
|
||||
|失败请求数量
|
||||
|指定时间范围内网关接收的失败请求的数量。
|
||||
|
||||
|网络流量
|
||||
|指定时间范围内网关的每秒入站流量。
|
||||
|===
|
||||
--
|
||||
|
||||
include::../../../../_ks_components-en/oper-selectTimeRange.adoc[]
|
||||
|
||||
include::../../../../_ks_components-en/oper-Autorefresh.adoc[]
|
||||
|
||||
include::../../../../_ks_components-en/oper-refreshData.adoc[]
|
||||
====
|
||||
|
||||
. 在网关详情页面右侧点击**配置选项**查看网关的配置选项。KubeSphere 的网关功能底层基于 Nginx Ingress Controller 实现，有关网关配置选项的更多信息，请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|
||||
. 在网关详情页面右侧点击**网关日志**查看网关的日志。
|
||||
+
|
||||
--
|
||||
* 在**网关日志**页签上方点击搜索框并设置搜索条件，可按关键字、容器组或时间范围搜索日志数据。
|
||||
|
||||
* 在**网关日志**页签上方点击image:/images/ks-qkcp/zh/icons/start-dark.svg[start-dark,18,18]/image:/images/ks-qkcp/zh/icons/stop-dark-white.svg[stop-dark-white,18,18]可开启/停止实时数据刷新。
|
||||
|
||||
* 在**网关日志**页签上方点击**刷新间隔**可设置数据刷新间隔为 5s、10s 或 20s。
|
||||
|
||||
* 在**网关日志**页签上方点击image:/images/ks-qkcp/zh/icons/export.svg[export,18,18]可将日志文件下载到本地。
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**资源状态**页签查看网关工作负载的容器组副本数、容器端口和容器组。
|
||||
+
|
||||
--
|
||||
include::../../para-replicasPortsPods.adoc[]
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**元数据**页签查看网关服务的注解。
|
||||
|
|
@ -1,91 +1,90 @@
|
|||
// :ks_include_id: 2603654cc618449f9ae430c3041a361f
|
||||
. 在页面右侧选择**管理 > 查看详情**打开网关详情页面。
|
||||
. On the right side of the page, select **Manage > View Details** to open the gateway details page.
|
||||
|
||||
. 在网关详情页面左侧的**属性**区域查看网关的资源属性。
|
||||
. On the gateway details page, view the resource attributes of the gateway in the **Attributes** area on the left.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|集群
|
||||
|网关所属的集群。
|
||||
|Cluster
|
||||
|The cluster to which the gateway belongs.
|
||||
|
||||
|创建时间
|
||||
|网关的创建时间。
|
||||
|Creation Time
|
||||
|The creation time of the gateway.
|
||||
|
||||
|更新时间
|
||||
|网关的更新时间
|
||||
|Update Time
|
||||
|The update time of the gateway.
|
||||
|
||||
|创建者
|
||||
|启用网关的用户。
|
||||
|Creator
|
||||
|The user who enabled the gateway.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**配置选项**查看网关的配置选项。KubeSphere 的网关功能底层基于 Nginx Ingress Controller 实现，有关网关配置选项的更多信息，请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
. On the gateway details page, click the **Configuration Options** tab to view the configuration options of the gateway. The gateway functionality of KubeSphere is based on Nginx Ingress Controller. For more information about gateway configuration options, please refer to the link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller Documentation].
|
||||
|
||||
. 在页面右侧的**监控**页签查看网关的请求数据。
|
||||
. On the right side of the page, click the **Monitoring** tab to view the request data of the gateway.
|
||||
+
|
||||
====
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|Note
|
||||
|
||||
|
|
||||
如需使用网关监控功能，KubeSphere 平台需要安装并启用 **WhizardTelemetry 监控**扩展组件。
|
||||
To use the gateway monitoring function, the **WhizardTelemetry Monitoring** extension should be installed and enabled.
|
||||
|===
|
||||
|
||||
* **概览**区域提供以下信息：
|
||||
* The **Overview** area provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|总请求数量
|
||||
|指定时间范围内网关接收的请求总数。
|
||||
|Total Requests
|
||||
|The total number of requests received by the gateway within the specified time range.
|
||||
|
||||
|请求数量
|
||||
|指定时间范围内响应状态码为 4XX 或 5XX 的请求数量。点击下拉列表可分别查看 4XX 请求和 5XX 请求的数量。
|
||||
|Request Count
|
||||
|The number of requests with response status codes of 4XX or 5XX within the specified time range. Click the dropdown list to view the number of 4XX requests and 5XX requests separately.
|
||||
|
||||
|成功请求
|
||||
|指定时间范围内成功请求的百分比。
|
||||
|Successful Requests
|
||||
|The percentage of successful requests within the specified time range.
|
||||
|
||||
|平均延迟
|
||||
|指定时间范围内所有请求的平均延迟。
|
||||
|Average Latency
|
||||
|The average latency of all requests within the specified time range.
|
||||
|
||||
|P50 延迟
|
||||
|指定时间范围内所有请求延迟的中位数。
|
||||
|P50 Latency
|
||||
|The median latency of all requests within the specified time range.
|
||||
|
||||
|P95 延迟
|
||||
|指定时间范围内所有请求的 95% 分位延迟，即 95% 的请求的延迟小于或等于该数值。
|
||||
|P95 Latency
|
||||
|The 95th percentile latency of all requests within the specified time range, i.e., 95% of the requests have a latency less than or equal to this value.
|
||||
|
||||
|P99 延迟
|
||||
|指定时间范围内所有请求的 99% 分位延迟，即 99% 的请求的延迟小于或等于该数量。
|
||||
|P99 Latency
|
||||
|The 99th percentile latency of all requests within the specified time range, i.e., 99% of the requests have a latency less than or equal to this value.
|
||||
|===
|
||||
--
|
||||
|
||||
* 页面下方以折线图显示动态的请求数据。
|
||||
* The line charts at the bottom of the page display dynamic request data.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|请求数量
|
||||
|指定时间范围内网关接收的每秒请求数量。
|
||||
|Request Count
|
||||
|The number of requests per second received by the gateway within the specified time range.
|
||||
|
||||
|连接数量
|
||||
|指定时间范围内网关接收的每秒连接数量。
|
||||
|Connection Count
|
||||
|The number of connections per second received by the gateway within the specified time range.
|
||||
|
||||
|请求延迟
|
||||
|指定时间范围内所有请求的延迟中位数、95% 分位延迟、99% 分位延迟和平均延迟。
|
||||
|Request Latency
|
||||
|The median latency, 95th percentile latency, 99th percentile latency, and average latency of all requests within the specified time range.
|
||||
|
||||
|失败请求数量
|
||||
|指定时间范围内网关接收的失败请求的数量。
|
||||
|Failed Request Count
|
||||
|The number of failed requests received by the gateway within the specified time range.
|
||||
|
||||
|网络流量
|
||||
|指定时间范围内网关的每秒入站流量。
|
||||
|Network Traffic
|
||||
|The inbound traffic per second of the gateway within the specified time range.
|
||||
|===
|
||||
--
|
||||
|
||||
|
|
@ -96,30 +95,30 @@ include::../../../../_ks_components-en/oper-Autorefresh.adoc[]
|
|||
include::../../../../_ks_components-en/oper-refreshData.adoc[]
|
||||
====
|
||||
|
||||
. 在网关详情页面右侧点击**网关日志**查看网关的日志。
|
||||
. On the gateway details page, click the **Gateway Logs** tab to view the logs of the gateway.
|
||||
+
|
||||
--
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|Note
|
||||
|
||||
|
|
||||
如需使用网关日志搜索功能，KubeSphere 平台需要安装并启用 **WhizardTelemetry 日志管理**扩展组件。
|
||||
To use the gateway log search function, the **WhizardTelemetry Logging** extension should be installed and enabled.
|
||||
|===
|
||||
|
||||
* 在**网关日志**页签上方点击搜索框并设置搜索条件，可按关键字、容器组或时间范围搜索日志数据。
|
||||
* Click the search box at the top of the **Gateway Logs** tab and set the search conditions to search for log data by keywords, pods, or time range.
|
||||
|
||||
* 在**网关日志**页签上方点击image:/images/ks-qkcp/zh/icons/start-dark.svg[start-dark,18,18]/image:/images/ks-qkcp/zh/icons/stop-dark-white.svg[stop-dark-white,18,18]可开启/停止实时数据刷新。
|
||||
* Click image:/images/ks-qkcp/zh/icons/start-dark.svg[start-dark,18,18]/image:/images/ks-qkcp/zh/icons/stop-dark-white.svg[stop-dark-white,18,18] to start/stop real-time data refresh.
|
||||
|
||||
* 在**网关日志**页签上方点击**刷新间隔**可设置数据刷新间隔为 5s、10s 或 20s。
|
||||
* Click **Refresh Interval** to set the data refresh interval to 5s, 10s, or 20s.
|
||||
|
||||
* 在**网关日志**页签上方点击image:/images/ks-qkcp/zh/icons/export.svg[export,18,18]可将日志文件下载到本地。
|
||||
* Click image:/images/ks-qkcp/zh/icons/export.svg[export,18,18] to download the log file to your local machine.
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**资源状态**页签查看网关工作负载的容器组副本数、容器端口和容器组。
|
||||
. On the gateway details page, click the **Resource Status** tab to view the number of pod replicas, container ports, and pods of the gateway workload.
|
||||
+
|
||||
--
|
||||
include::../../para-replicasPortsPods.adoc[]
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**元数据**页签查看网关服务的注解。
|
||||
. On the gateway details page, click the **Metadata** tab to view the annotations of the gateway service.
|
||||
|
|
@ -1,10 +1,8 @@
|
|||
// :ks_include_id: 09fe14af1fd747b8aad60c34a228e54e
|
||||
集群网关或项目网关的 IP 地址。
|
||||
The IP address of the cluster gateway or project gateway.
|
||||
|
||||
// tag::bullets[]
|
||||
* 如果网关的外部访问模式为 NodePort，**网关地址**为某一个集群节点的 IP 地址。客户端可以通过任意集群节点的 IP 地址和端口访问应用路由的后端服务。
|
||||
* If the external access mode of the gateway is **NodePort**, the **Gateway Address** is the IP address of one of the cluster nodes. Clients can access the backend services of the Ingresses through the IP address and port of any cluster node.
|
||||
|
||||
* 如果网关的外部访问模式为 LoadBalancer，**网关地址**为负载均衡器的地址。
|
||||
* If the external access mode of the gateway is **LoadBalancer**, the **Gateway Address** is the address of the load balancer.
|
||||
|
||||
// * 如果网关地址未显示，可能是因为集群节点缺少 **node-role.kubernetes.io/master** 标签。点击**集群节点**页面，点击控制平面节点，选择**更多操作 > 编辑标签**添加 **node-role.kubernetes.io/master** 标签。v4.1 删除该行
|
||||
// end::bullets[]
|
||||
// end::bullets[]
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
// :ks_include_id: 70d685391e6d449cbdfb8a7f5e6e5dfa
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|链路追踪
|
||||
|是否对网关启用链路追踪功能。
|
||||
|
||||
|配置选项
|
||||
|网关的配置选项。{ks_product-en}的网关功能底层基于 Nginx Ingress Controller 实现，您可以设置网关的配置选项控制网关的行为。有关更多信息，请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|
||||
|负载均衡器提供商
|
||||
|网关的负载均衡器提供商。网关的外部访问模式为 LoadBalancer 时，您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。选择负载均衡器提供商后，设置网关服务注解时系统将提供注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。
|
||||
|
||||
|注解
|
||||
|网关服务的注解。如果已选择负载均衡器提供商，点击**键**文本框时系统将在下拉列表中显示注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。有关更多信息，请联系您的基础设施环境提供商。
|
||||
|===
|
||||
|
|
@ -1,31 +1,30 @@
|
|||
// :ks_include_id: 70d685391e6d449cbdfb8a7f5e6e5dfa
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|Nginx Ingress 版本
|
||||
|Nginx Ingress 的版本。KubeSphere 网关扩展组件基于 Nginx Ingress 提供网关管理功能。
|
||||
|Nginx Ingress Version
|
||||
|The version of Nginx Ingress. The KubeSphere Gateway extension provides gateway management based on Nginx Ingress.
|
||||
|
||||
|IngressClassName
|
||||
|IngressClass 的名称。
|
||||
|The name of the IngressClass.
|
||||
|
||||
|容器组副本数量
|
||||
|期望的容器组副本数量。
|
||||
|Pod Replicas
|
||||
|The desired number of pod replicas.
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|Access Mode
|
||||
|The external access mode of the gateway service.
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|链路追踪
|
||||
|是否对网关启用链路追踪功能。如需使用链路追踪功能，{ks_product-en}平台需要安装并启用 **KubeSphere 服务网格**扩展组件。
|
||||
|Tracing
|
||||
|Whether to enable tracing for the gateway. To use the tracing function, the **KubeSphere Service Mesh** extension should be installed and enabled.
|
||||
|
||||
|配置选项
|
||||
|网关的配置选项。{ks_product-en}的网关功能底层基于 Nginx Ingress Controller 实现，您可以设置网关的配置选项控制网关的行为。有关更多信息，请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|Configuration Options
|
||||
|The configuration options for the gateway. The gateway functionality of KubeSphere is based on Nginx Ingress Controller. You can set the configuration options for the gateway to control its behavior. For more information, please refer to the link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller Documentation].
|
||||
|
||||
|负载均衡器提供商
|
||||
|网关的负载均衡器提供商。网关的外部访问模式为 LoadBalancer 时，您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。选择负载均衡器提供商后，设置网关服务注解时系统将提供注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。
|
||||
|Load Balancer Provider
|
||||
|The load balancer provider for the gateway. When the external access mode of the gateway service is LoadBalancer, you need to set the annotations of the gateway service according to the load balancer plugin and infrastructure environment to create the required load balancer. After selecting the load balancer provider, the system will provide annotation hints when setting the gateway service annotations. Only available when the external access mode of the gateway service is LoadBalancer.
|
||||
|
||||
|注解
|
||||
|网关服务的注解。如果已选择负载均衡器提供商，点击**键**文本框时系统将在下拉列表中显示注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。有关更多信息，请联系您的基础设施环境提供商。
|
||||
|Annotations
|
||||
|The annotations of the gateway service. If a load balancer provider has been selected, the system will display annotation hints in the dropdown list when clicking the **Key** text box. Only available when the external access mode of the gateway service is LoadBalancer. For more information, please contact your infrastructure environment provider.
|
||||
|===
|
||||
|
|
@ -1,37 +1,36 @@
|
|||
// :ks_include_id: 6fca3db90bdf4fd8bb61eb771c1a7308
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|类型
|
||||
|网关的类型。
|
||||
|Type
|
||||
|The type of the gateway.
|
||||
|
||||
|创建者
|
||||
|启用网关的用户。
|
||||
|Creator
|
||||
|The user who enabled the gateway.
|
||||
|
||||
|创建时间
|
||||
|网关的启用时间。
|
||||
|Creation Time
|
||||
|The time when the gateway was enabled.
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|Access Mode
|
||||
|The external access mode of the gateway service.
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|网关地址
|
||||
|Gateway Address
|
||||
|
|
||||
网关的外部访问地址。
|
||||
The external access address of the gateway.
|
||||
|
||||
include::gatewaySettings-para-address.adoc[tag=bullets]
|
||||
|
||||
|节点端口
|
||||
|网关服务的 HTTP 和 HTTPS 节点端口。仅在网关的外部访问模式为 NodePort 时显示。
|
||||
|Node Ports
|
||||
|The HTTP and HTTPS node ports of the gateway service. Only displayed when the external access mode of the gateway is NodePort.
|
||||
|
||||
|副本
|
||||
|网关工作负载的副本数。
|
||||
|Replicas
|
||||
|The number of replicas of the gateway workload.
|
||||
|
||||
|链路追踪
|
||||
|网关是否已启用链路追踪功能。
|
||||
|Tracing
|
||||
|Whether the gateway has tracing enabled.
|
||||
|
||||
|注解
|
||||
|网关服务的注解。网关的外部访问模式为 LoadBalancer 时，您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。有关更多信息，请联系您的基础设施环境提供商。仅在网关的外部访问模式为 LoadBalancer 时显示。
|
||||
|===
|
||||
|Annotations
|
||||
|The annotations of the gateway service. When the external access mode of the gateway is LoadBalancer, you need to set the annotations of the gateway service according to the load balancer plugin and infrastructure environment to create the required load balancer. For more information, please contact your infrastructure environment provider. Only displayed when the external access mode of the gateway is LoadBalancer.
|
||||
|===
|
||||
|
|
@ -2,6 +2,6 @@
|
|||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
网关禁用后客户端将无法访问由网关反向代理的服务，相关业务可能会中断，请谨慎执行此操作。
|
||||
After disabling the gateway, clients will not be able to access the services reverse-proxied by the gateway, and related business may be interrupted. Please proceed with caution.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -1,15 +1,15 @@
|
|||
// :ks_include_id: 66ed1f4913ff42b5b26a407b2ce28c78
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|服务地址
|
||||
|Address
|
||||
|
|
||||
include::logReceivers-para-address.adoc[]
|
||||
|
||||
|索引前缀
|
||||
|日志数据的索引前缀，用于区分不同类型的日志。仅对 Elasticsearch 和 OpenSearch 可用。
|
||||
|Index Prefix
|
||||
|The index prefix of log data, used to distinguish different types of logs. Only available for Elasticsearch and OpenSearch.
|
||||
|
||||
|主题
|
||||
|日志数据的主题，用于区分不同类型的日志。仅对 Kafka 可用。
|
||||
|Topic
|
||||
|The topic of log data, used to distinguish different types of logs. Only available for Kafka.
|
||||
|===
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 52e9e8100b4444ebb9fbb42175d917f3
|
||||
日志接收器的服务地址和服务端口。{ks_product-en}会将日志发送给该地址和端口。{ks_product-en}默认使用的 OpenSearch 的服务地址和服务端口为 **opensearch-cluster-data.kubesphere-logging-system.svc:9200**。
|
||||
The service address and port of the log receiver. {ks_product-en} will send logs to this address and port. The default service address and port of OpenSearch used by {ks_product-en} is **opensearch-cluster-data.kubesphere-logging-system.svc:9200**.
|
||||
|
|
@ -1,9 +1,8 @@
|
|||
// :ks_include_id: 9f53c0bd64274d80baa502171017a705
|
||||
|名称
|
||||
|网络策略的名称。
|
||||
|Name
|
||||
|The name of the network policy.
|
||||
|
||||
|项目
|
||||
|网络策略所属的项目。
|
||||
|Project
|
||||
|The project to which the network policy belongs.
|
||||
|
||||
|创建时间
|
||||
|网络策略的创建时间。
|
||||
|Creation Time
|
||||
|The creation time of the network policy.
|
||||
|
|
@ -1,6 +1,5 @@
|
|||
// :ks_include_id: ff94c103e4f841cfa4bed82610aac7a6
|
||||
规则适用的容器组的信息。
|
||||
Information about the pods to which the rule applies.
|
||||
|
||||
* **项目**：规则所属的项目。网络策略中的规则仅适用于网络策略所属项目中的容器组。
|
||||
* **Project**: The project to which the rule belongs. Rules in a network policy only apply to pods in the project to which the network policy belongs.
|
||||
|
||||
* **标签**：规则适用的容器组所具有的标签。如果未设置标签，则规则适用于网络策略所属的项目中的所有容器组。
|
||||
* **Labels**: The labels of the pods to which the rule applies. If no labels are set, the rule applies to all pods in the project to which the network policy belongs.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 10cd1bc2be6f48dd994fe2be6c747e10
|
||||
本节介绍如何创建卷快照。
|
||||
This section describes how to create a volume snapshot.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
// :ks_include_id: f523ebef727d479488a3ad33a373f462
|
||||
. 在持久卷声明详情页面的左上角，选择**更多操作 > 创建快照**。
|
||||
. In the upper-left corner of the details page, select **More > Create Snapshot**.
|
||||
|
||||
. 在**创建快照**对话框，设置卷快照的名称和卷快照类，然后点击**确定**。
|
||||
. In the **Create Snapshot** dialog, set the name of the volume snapshot and the volume snapshot class, then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1,4"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|卷快照的名称。名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 253 个字符。
|
||||
|Name
|
||||
|The name of the volume snapshot. The name can only contain lowercase letters, numbers, and hyphens (-), must start and end with a lowercase letter or number, and can be up to 253 characters long.
|
||||
|
||||
|卷快照类
|
||||
|Volume Snapshot Class
|
||||
|
|
||||
include::persistentVolumeClaims-para-volumeSnapshotClass.adoc[]
|
||||
|===
|
||||
|
||||
卷快照创建后将显示在**卷快照**页面的卷快照列表中。
|
||||
--
|
||||
After the volume snapshot is created, it will be displayed in the volume snapshot list on the **Volume Snapshots** page.
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 7d428de9ff3a4f0fbd1cd48e49749f27
|
||||
卷快照保存了存储卷的当前数据，可用于创建持久卷声明以及对应的持久卷。
|
||||
A volume snapshot saves the current data of a storage volume, which can be used to create a persistent volume claim and the corresponding persistent volume.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 308d3cded9ea45a5a0a4475b02e53d57
|
||||
用于创建卷快照的卷快照类。请确保卷快照类的供应者与持久卷对应的存储类的供应者一致，否则卷快照将创建失败。
|
||||
The volume snapshot class used to create the volume snapshot. Ensure that the provider of the volume snapshot class matches the provider of the storage class corresponding to the persistent volume; otherwise, the volume snapshot creation will fail.
|
||||
|
|
@ -1,2 +1 @@
|
|||
// :ks_include_id: 46eb4a2a26af4ed48dea4d01cf866136
|
||||
* 容器组 IP 池未被任何容器组使用。如果存在正在使用容器组 IP 池的容器组，您需要为容器组指定其他容器组 IP 池或删除容器组。
|
||||
* The pod IP pool is not used by any pods. If there are pods using the pod IP pool, you need to specify another pod IP pool for the pods or delete the pods.
|
||||
|
|
@ -1,35 +1,35 @@
|
|||
// :ks_include_id: 9b12ede280884331985685925cf5dfc4
|
||||
* 容器组列表提供以下信息：
|
||||
* The pod list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|容器组的名称。
|
||||
|Name
|
||||
|The name of the pod.
|
||||
|
||||
|状态
|
||||
|容器组的状态。
|
||||
|Status
|
||||
|The status of the pod.
|
||||
|
||||
include::pods-para-podStatus_overview.adoc[]
|
||||
// pod 状态不一样
|
||||
// pod status is different
|
||||
|
||||
|节点
|
||||
|容器组所在的节点和节点的 IP 地址。
|
||||
|Node
|
||||
|The node where the pod is located and the node's IP address.
|
||||
|
||||
include::pods-para-podIpPool.adoc[]
|
||||
|
||||
// |应用
|
||||
// |容器组所属的应用。
|
||||
// |Application
|
||||
// |The application the pod belongs to.
|
||||
|
||||
|项目
|
||||
|容器组所属的项目。
|
||||
|Project
|
||||
|The project the pod belongs to.
|
||||
|
||||
|集群
|
||||
|容器组所属的集群。
|
||||
|Cluster
|
||||
|The cluster the pod belongs to.
|
||||
|
||||
|更新时间
|
||||
|容器组的更新时间。
|
||||
|Update Time
|
||||
|The update time of the pod.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,13 +1,11 @@
|
|||
// :ks_include_id: 8cc83a9c58b8460cbcf369b1a07288b1
|
||||
|
||||
* **运行中**：容器组已分配给某个节点，容器组中的所有容器都已被创建，至少有一个容器正在运行、启动或重启。
|
||||
* **Running**: The pod has been assigned to a node, all containers in the pod have been created, and at least one container is running, starting, or restarting.
|
||||
|
||||
* **等待中**：容组器已被系统接受，但有至少一个容器尚未创建也未运行。此状态下，容器组可能正在等待调度，或等待容器镜像下载完成。
|
||||
* **Pending**: The pod has been accepted by the system, but at least one container has not been created or is not running. This state may indicate that the pod is waiting for scheduling or for the container image to be downloaded.
|
||||
|
||||
* **成功完成**：容器组中的所有容器都成功终止（以 0 退出码终止），并且不再重启。
|
||||
* **Completed**: All containers in the pod have terminated successfully (with an exit code of 0) and will not be restarted.
|
||||
|
||||
* **失败**：容器组中的所有容器都已终止，并且至少有一个容器以非 0 退出码终止。
|
||||
* **Failed**: All containers in the pod have terminated, and at least one container has terminated with a non-zero exit code.
|
||||
|
||||
* **未知**：系统无法获取容器组状态。出现这种状态通常是由于系统与容器组所在的主机通信失败。
|
||||
|
||||
// 已完成 vs 成功完成：https://github.com/kubesphere/project/issues/3983#issuecomment-2246982909
|
||||
* **Unknown**: The system is unable to get the status of the pod. This state usually occurs when the system fails to communicate with the host where the pod is located.
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
// :ks_include_id: 5bc648d25864430e9749aa0c567555f3
|
||||
本节介绍如何访问应用路由的后端服务。
|
||||
This section describes how to access the backend service of an Ingress.
|
||||
|
||||
应用路由创建完成后，您可通过任意 HTTP 或 HTTPS 客户端访问应用路由的后端服务。取决于集群网关或项目网关的外部访问模式，您可以使用以下访问方式：
|
||||
After the Ingress is created, you can access the backend service of the Ingress through any HTTP or HTTPS client. Depending on the external access mode of the cluster gateway or project gateway, you can use the following access methods:
|
||||
|
||||
* 如果集群网关或项目网关的外部访问模式为 NodePort，您可以通过域名、路径和端口号（例如 **example.com/test:30240**）访问应用路由的后端服务。
|
||||
* If the external access mode of the cluster gateway or project gateway is NodePort, you can access the backend service of the Ingress through the domain name, path, and port number (e.g., **example.com/test:30240**).
|
||||
|
||||
* 如果集群网关或项目网关的外部访问模式为 LoadBalancer，您可以通过域名和路径（例如 **example.com/test**）访问应用路由的后端服务。
|
||||
* If the external access mode of the cluster gateway or project gateway is LoadBalancer, you can access the backend service of the Ingress through the domain name and path (e.g., **example.com/test**).
|
||||
|
||||
以下仅演示如何在{ks_product-en} Web 控制台测试应用路由是否设置正确。
|
||||
The following only demonstrates how to test whether the Ingress is set correctly in the {ks_product-en} web console.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: b4c404ff621146f799e720597d3aac84
|
||||
This section describes how to edit routing rules.
|
||||
This section describes how to edit routing rules.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: c69900173bca4b109a4b8a178ce15e64
|
||||
This section describes how to manage ingresses.
|
||||
This section describes how to manage Ingresses.
|
||||
|
||||
Ingresses are used to aggregate services and provide external access. Each ingress contains a domain name and its sub-paths mapped to different services. Business traffic from clients is first sent to the cluster gateway or project gateway, which then forwards the traffic to different services based on the rules defined in the ingress, thereby achieving reverse proxy for multiple services.
|
||||
Ingresses are used to aggregate services and provide external access. Each Ingress contains a domain name and its sub-paths mapped to different services. Business traffic from clients is first sent to the cluster gateway or project gateway, which then forwards the traffic to different services based on the rules defined in the Ingress, thereby achieving reverse proxy for multiple services.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: f51f45c2029a4242ad04da5a1fe817c7
|
||||
. 在**资源状态**页签，在需要访问的路由规则右侧点击**访问服务**。
|
||||
. In the **Resource Status** tab, click **Access Service** on the right side of the routing rule you want to access.
|
||||
+
|
||||
--
|
||||
如果应用路由设置正确，浏览器将显示后端服务的响应信息。
|
||||
--
|
||||
If the Ingress is set correctly, the browser will display the response information from the backend service.
|
||||
--
|
||||
|
|
@ -1,24 +1,24 @@
|
|||
// :ks_include_id: 570405898db841389a0ce7ed42a9a8e3
|
||||
. 在**基本信息**页签，设置应用路由的基本信息，然后点击**下一步**。
|
||||
. On the **Basic Information** tab, set the basic information for the Ingress, then click **Next**.
|
||||
+
|
||||
--
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|应用路由的名称。名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 253 个字符。
|
||||
|Name
|
||||
|The name of the Ingress. The name can only contain lowercase letters, numbers, and hyphens (-), must start and end with a lowercase letter or number, and can be up to 253 characters long.
|
||||
|
||||
|别名
|
||||
|应用路由的别名。不同应用路由的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
|Alias
|
||||
|The alias of the Ingress. Different Ingresses can have the same alias. The alias can only contain Chinese characters, letters, numbers, and hyphens (-), cannot start or end with a hyphen (-), and can be up to 63 characters long.
|
||||
|
||||
|描述
|
||||
|应用路由的描述。描述可包含任意字符，最长 256 个字符。
|
||||
|Description
|
||||
|The description of the Ingress. The description can contain any characters and can be up to 256 characters long.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在**路由规则**页签，点击**添加路由规则**，设置路由规则参数，然后点击**下一步**。
|
||||
. On the **Routing Rules** tab, click **Add Routing Rule**, set the routing rule parameters, then click **Next**.
|
||||
+
|
||||
--
|
||||
ifdef::multicluster[]
|
||||
|
|
@ -28,22 +28,22 @@ endif::[]
|
|||
include::routes-para-routingRules.adoc[]
|
||||
--
|
||||
|
||||
. 在**高级设置**页签，为应用路由设置标签和注解，然后点击**创建**。
|
||||
. On the **Advanced Settings** tab, set labels and annotations for the Ingress, then click **Create**.
|
||||
+
|
||||
--
|
||||
* 点击**添加**可设置多条标签或注解。
|
||||
* Click **Add** to set multiple labels or annotations.
|
||||
|
||||
* 在已创建的标签或注解右侧点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除标签或注解。
|
||||
* Click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] on the right side of a created label or annotation to delete it.
|
||||
|
||||
include::routes-note-annotations.adoc[]
|
||||
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|Note
|
||||
|
||||
|
|
||||
安装“KubeSphere 网关”扩展组件，并启用集群网关、企业空间网关、或项目网关后，创建应用路由时，需要在**高级设置**页签选择对应网关的 IngressClassName。
|
||||
After installing the "KubeSphere Gateway" extension and enabling the cluster gateway, workspace gateway, or project gateway, you need to select the corresponding IngressClassName in the **Advanced Settings** tab when creating an Ingress.
|
||||
|===
|
||||
|
||||
应用路由创建完成后将显示在应用路由列表中。
|
||||
After the Ingress is created, it will be displayed in the Ingress list.
|
||||
--
|
||||
|
|
|
|||
|
|
@ -1,70 +1,70 @@
|
|||
// :ks_include_id: 02ac1cebc06f4893a036c2e77c21d999
|
||||
. 在应用路由详情页面左侧的**属性**区域查看应用路由的详细信息。
|
||||
. View the detailed information of the Ingress in the **Attributes** area on the left side of the Ingress details page.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|集群
|
||||
|应用路由的所属集群。
|
||||
|Cluster
|
||||
|The cluster to which the Ingress belongs.
|
||||
|
||||
|项目
|
||||
|应用路由的所属项目。
|
||||
|Project
|
||||
|The project to which the Ingress belongs.
|
||||
|
||||
|应用
|
||||
|应用路由对应的应用。
|
||||
|Application
|
||||
|The application corresponding to the Ingress.
|
||||
|
||||
|网关地址
|
||||
|Gateway Address
|
||||
|
|
||||
include::../gatewaySettings/gatewaySettings-para-address.adoc[]
|
||||
|
||||
|创建时间
|
||||
|应用路由的创建时间。
|
||||
|Creation Time
|
||||
|The creation time of the Ingress.
|
||||
|
||||
|创建者
|
||||
|创建应用路由的用户。
|
||||
|Creator
|
||||
|The user who created the Ingress.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在应用路由详情页面右侧的**资源状态**页签查看应用路由的路由规则。
|
||||
. View the routing rules of the Ingress in the **Resource Status** tab on the right side of the Ingress details page.
|
||||
+
|
||||
--
|
||||
**资源状态**页签显示当前应用路由的所有路由规则。
|
||||
The **Resource Status** tab displays all routing rules of the current Ingress.
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|域名和端口
|
||||
|应用路由的域名和节点端口号。节点端口号仅在集群网关或项目网关的外部访问为 NodePort 时显示。
|
||||
|Domain and Port
|
||||
|The domain name and node port of the Ingress. The node port is only displayed when the external access of the cluster gateway or project gateway is NodePort.
|
||||
|
||||
* 如果集群网关或项目网关的外部访问模式为 NodePort，客户端需要通过 DNS 服务或本地 **hosts** 文件将域名解析为集群中任意节点的 IP 地址，并通过域名、路径和端口号（例如 **example.com/test:30240**）访问应用路由。
|
||||
* If the external access mode of the cluster gateway or project gateway is NodePort, the client needs to resolve the domain name to the IP address of any node in the cluster through the DNS service or the local **hosts** file, and access the Ingress through the domain name, path, and port number (e.g., **example.com/test:30240**).
|
||||
|
||||
* 如果集群网关或项目网关的外部访问模式为 LoadBalancer，客户端需要通过 DNS 服务或本地 **hosts** 文件将域名解析为项目网关负载均衡器的 IP 地址，并通过域名和路径（例如 **example.com/test**）访问应用路由。
|
||||
* If the external access mode of the cluster gateway or project gateway is LoadBalancer, the client needs to resolve the domain name to the IP address of the project gateway load balancer through the DNS service or the local **hosts** file, and access the Ingress through the domain name and path (e.g., **example.com/test**).
|
||||
|
||||
|协议
|
||||
|应用路由支持的协议，取值为**HTTP** 或 **HTTPS**。
|
||||
|Protocol
|
||||
|The protocol supported by the Ingress, which can be **HTTP** or **HTTPS**.
|
||||
|
||||
|证书
|
||||
|应用路由协议为 HTTPS 时，所使用的包含证书和私钥的保密字典的名称。仅在应用路由协议为 HTTPS 时显示。
|
||||
|Certificate
|
||||
|The name of the Secret containing the certificate and private key used when the Ingress protocol is HTTPS. Only displayed when the Ingress protocol is HTTPS.
|
||||
|
||||
|路径
|
||||
|域名的路径，每条路径对应一个服务。
|
||||
|Path
|
||||
|The path of the domain name, each path corresponds to a service.
|
||||
|
||||
|服务
|
||||
|域名路径所对应的服务的名称。
|
||||
|Service
|
||||
|The name of the service corresponding to the domain name path.
|
||||
|
||||
|端口
|
||||
|域名路径所对应的服务的端口号。
|
||||
|Port
|
||||
|The port number of the service corresponding to the domain name path.
|
||||
|===
|
||||
|
||||
在路由规则右侧点击**访问服务**可访问应用路由的后端服务。
|
||||
Click **Access Service** on the right side of the routing rule to access the backend service of the Ingress.
|
||||
--
|
||||
|
||||
. 在应用路由详情页面右侧点击**元数据**页签查看应用路由的**标签**和**注解**。
|
||||
. Click the **Metadata** tab on the right side of the Ingress details page to view the **Labels** and **Annotations** of the Ingress.
|
||||
|
||||
. 在应用路由详情页面右侧点击**事件**页签查看应用路由的事件。
|
||||
. Click the **Events** tab on the right side of the Ingress details page to view the events of the Ingress.
|
||||
+
|
||||
--
|
||||
include::../clusterManagement-para-eventsTab.adoc[]
|
||||
--
|
||||
--
|
||||
|
|
@ -1,22 +1,22 @@
|
|||
// :ks_include_id: ae74df332c484c09b5ea8272c0d8193c
|
||||
* 应用路由列表提供以下信息：
|
||||
* The Ingress list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|应用路由的名称和描述。
|
||||
|Name
|
||||
|The name and description of the Ingress.
|
||||
|
||||
|网关地址
|
||||
|Gateway Address
|
||||
|
|
||||
include::../gatewaySettings/gatewaySettings-para-address.adoc[]
|
||||
|
||||
|应用
|
||||
|应用路由所对应的应用名称。
|
||||
|Application
|
||||
|The name of the application corresponding to the Ingress.
|
||||
|
||||
|创建时间
|
||||
|应用路由的创建时间。
|
||||
|Creation Time
|
||||
|The creation time of the Ingress.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: d8a06afae96b4c0bbb29c390f1fe18f5
|
||||
* 客户端必须通过本地 **hosts** 文件或 DNS 服务将域名解析为网关 IP 地址。
|
||||
* The client must resolve the domain name to the gateway IP address through the local **hosts** file or DNS service.
|
||||
|
||||
* 客户端必须与网关 IP 地址网络连通。有关更多信息，请联系您的网络环境管理员。
|
||||
* The client must have network connectivity to the gateway IP address. For more information, contact your network environment administrator.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: e19cfac61c85491d9f631ba61f012c62
|
||||
本节介绍如何创建告警规则组。
|
||||
This section introduces how to create an alert rule group.
|
||||
|
||||
{ks_product-en}的监控告警功能底层基于 Promtheus 实现，每个规则组可包含多条告警规则。您可以使用系统提供的规则模板创建告警规则，也可手动输入 PromQL 表达式创建告警规则。有关更多信息，请参阅 link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus 官方文档]。
|
||||
The monitoring and alerting functions of {ks_product-en} are implemented based on Prometheus. Each rule group can contain multiple alert rules. You can create alert rules using the rule templates provided by the system or manually enter PromQL expressions to create alert rules. For more information, see the link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus Documentation].
|
||||
|
|
@ -1,16 +1,16 @@
|
|||
// :ks_include_id: afa42dbe50664f968d66928b7d9b75d6
|
||||
本节介绍如何删除告警规则组。
|
||||
This section describes how to delete alert rule groups.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
|
||||
{ks_product-en}仅支持删除自定义规则组，不支持删除内置规则组。
|
||||
{ks_product-en} only supports deleting custom rule groups, not built-in rule groups.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
规则组删除后不能恢复，请谨慎执行此操作。
|
||||
Rule groups cannot be recovered after deletion, so please proceed with caution.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 43829ece490644d8ba2c2e823ad90719
|
||||
本节介绍如何启用和禁用告警规则组。规则组禁用后，系统将不再根据规则组生成告警。
|
||||
This section describes how to enable and disable alerting rule groups. After a rule group is disabled, the system will no longer generate alerts based on the rule group.
|
||||
|
|
@ -1,9 +1,9 @@
|
|||
// :ks_include_id: 50920b439c7f4f4e996fecec215f24ed
|
||||
本节介绍如何编辑规则组中的告警规则。
|
||||
This section describes how to edit alert rules in a rule group.
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
|
||||
{ks_product-en}仅支持编辑自定义规则组，不支持编辑内置规则组。
|
||||
{ks_product-en} only supports editing custom rule groups, not built-in rule groups.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: d62dbb9307bf4f21a25a732737dbe531
|
||||
本节介绍如何编辑告警规则组信息。
|
||||
This section introduces how to edit the information of an alert rule group.
|
||||
|
||||
您可以编辑告警规则组的别名、检查周期和描述。{ks_product-en}不支持编辑规则组的名称。
|
||||
You can edit the alias, check interval, and description of the alert rule group. KubeSphere does not support editing the name of a rule group.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 60f5fd04585b4a97bb5c99721f03edcb
|
||||
本节介绍如何查看告警规则组详情。
|
||||
This section introduces how to view the details of an alert rule group.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 75e22548eee741e48e1bcf6c7499fc65
|
||||
本节介绍如何查看告警规则组列表。
|
||||
This section introduces how to view the alert rule group list.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: b8f6aaa1104a42b3a0856ce1f21e1cea
|
||||
. 在**告警规则**页签，点击**添加告警规则**，根据需要选择**规则模板**或**自定义规则**设置告警规则。
|
||||
. On the **Alert Rules** tab, click **Add Alert Rule** and select **Rule Template** or **Custom Rule** as needed to set the alert rule.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 1f7f6ffdb0cb446689a451e85ddf8d11
|
||||
. 在需要编辑的规则组右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**编辑信息**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the rule group you need to edit, and then select **Edit Information** from the dropdown list.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: 513da96dc1b64eb9af9a791f349a9fce
|
||||
. 完成告警规则设置后点击image:/images/ks-qkcp/zh/icons/check-dark.svg[check,18,18]保存设置，然后点击**创建**。
|
||||
. After completing the alert rule settings, click image:/images/ks-qkcp/zh/icons/check-dark.svg[check,18,18] to save the settings, then click **Create**.
|
||||
+
|
||||
--
|
||||
规则组创建完成后将显示在规则组列表中。
|
||||
--
|
||||
The rule group will be displayed in the rule group list after creation.
|
||||
--
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 0b6f7a63668142ce8f5d70a7f013a852
|
||||
. 在需要删除的规则组右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**删除**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the rule group you need to delete, and then select **Delete** from the dropdown list.
|
||||
|
||||
. 在**删除规则组**对话框，输入规则组的名称，然后点击**确定**。
|
||||
. In the **Delete Rule Group** dialog, enter the name of the rule group, and then click **OK**.
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
// :ks_include_id: c98f892c063d4948889dcb04d2bef599
|
||||
. 勾选需要删除的规则组左侧的复选框，然后在规则组列表上方点击**删除**。
|
||||
. Select the checkbox on the left side of the rule groups you need to delete, and then click **Delete** above the rule group list.
|
||||
|
||||
. 在**批量删除规则组**对话框，输入规则组的名称，然后点击**确定**。
|
||||
. In the **Delete Multiple Rule Groups** dialog, enter the names of the rule groups, and then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
--
|
||||
--
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: 8e195bed54da4a4d8f7337f34ddec2ec
|
||||
. 在需要禁用的规则组右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**禁用**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the rule group you need to disable, and then select **Disable** from the dropdown list.
|
||||
|
||||
. 在**禁用规则组**对话框，输入规则组的名称，然后点击**确定**。
|
||||
. In the **Disable Rule Group** dialog, enter the name of the rule group, and then click **OK**.
|
||||
|
||||
. 在已禁用的规则组右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**启用**可启用规则组。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the disabled rule group, and then select **Enable** from the dropdown list to enable the rule group.
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
// :ks_include_id: 76fde78ac7ba4fef9a7a125fa849713d
|
||||
. 勾选需要禁用的规则组左侧的复选框，然后在规则组列表上方点击**禁用**。
|
||||
. Select the checkbox on the left side of the rule groups you need to disable, and then click **Disable** above the rule group list.
|
||||
|
||||
. 在**批量禁用规则组**对话框，输入规则组的名称，然后点击**确定**。
|
||||
. In the **Disable Multiple Rule Groups** dialog, enter the names of the rule groups, and then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
--
|
||||
|
||||
. 勾选已禁用的规则组左侧的复选框，然后在规则组列表上方点击**启用**可批量启用规则组。
|
||||
. Select the checkbox on the left side of the disabled rule groups, and then click **Enable** above the rule group list to batch enable the rule groups.
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
// :ks_include_id: af3bb03cf3e148bfa42409178889df61
|
||||
. 在**编辑告警规则**对话框，编辑已有的告警规则或创建新告警规则，然后点击**确定**。
|
||||
. In the **Edit Alert Rules** dialog, edit existing alert rules or create new alert rules, and then click **OK**.
|
||||
+
|
||||
--
|
||||
* 将光标悬停在已有的告警规则上，点击切换开关可启用/禁用告警规则。
|
||||
* Hover over an existing alert rule and click the toggle switch to enable/disable the alert rule.
|
||||
|
||||
* 将光标悬停在已有的告警规则上，点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除告警规则。
|
||||
* Hover over an existing alert rule and click image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18] to delete the alert rule.
|
||||
|
||||
* 将光标悬停在已有的告警规则上，点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18]可修改告警规则的设置。
|
||||
* Hover over an existing alert rule and click image:/images/ks-qkcp/zh/icons/pen-light.svg[pen,18,18] to modify the settings of the alert rule.
|
||||
|
||||
* 点击**添加告警规则**可创建新告警规则。
|
||||
--
|
||||
* Click **Add Alert Rule** to create a new alert rule.
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 3f022ef6620a4e01a4946d45ee3e93ce
|
||||
. 在需要编辑的规则组右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18]，然后在下拉列表中选择**编辑告警规则**。
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right side of the rule group you need to edit, and then select **Edit Alert Rules** from the dropdown list.
|
||||
|
|
@ -1,11 +1,11 @@
|
|||
// :ks_include_id: 33d094f3069e40519db31aec587457b4
|
||||
. 在**编辑信息**对话框，设置规则组的基本信息，然后点击**确定**。
|
||||
. In the **Edit Information** dialog, set the basic information for the rule group, and then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
include::ruleGroups-para-aliasCheckIntervalDescription.adoc[]
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 8ada03e949d64141806728273792c325
|
||||
. 在**规则组**页面，点击**自定义规则组**或**内置规则组**，然后在列表中点击一个规则组的名称打开其详情页面。
|
||||
. On the **Rule Groups** page, click **Custom Rule Groups** or **Built-in Rule Groups**, then click the name of a rule group in the list to open its details page.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 6b961b60bdf64acab9b19b9c28b5fb3e
|
||||
. 在**规则组**页面，点击**自定义规则组**或**内置规则组**打开规则组列表。
|
||||
. On the **Rule Groups** page, click **Custom Rule Groups** or **Built-in Rule Groups** to open the rule group list.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: d6ed4db86bde40cbaa6d3dbebecda452
|
||||
* 在列表上方点击搜索框并输入关键字，可搜索名称包含特定关键字的规则组。
|
||||
* Click the search box at the top of the list to search for rule groups by name.
|
||||
|
|
@ -1,16 +1,16 @@
|
|||
// :ks_include_id: 0909f39a50384c55b38d52472ab4085e
|
||||
. 在**基本信息**页签，设置规则组的基本信息，然后点击**下一步**。
|
||||
. On the **Basic Information** tab, set the basic information of the rule group, then click **Next**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|规则组的名称。
|
||||
|Name
|
||||
|The name of the rule group.
|
||||
|
||||
名称只能包含小写字母、数字和连字符（-），必须以小写字母或数字开头和结尾，最长 63 个字符。
|
||||
The name can only contain lowercase letters, numbers, and hyphens (-), must start and end with a lowercase letter or number, and can be up to 63 characters long.
|
||||
|
||||
include::ruleGroups-para-aliasCheckIntervalDescription.adoc[]
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,56 +1,56 @@
|
|||
// :ks_include_id: 539c72cb8f884103bce5d979f3b31d09
|
||||
. 在规则组详情页面左侧的**属性**区域查看规则组的资源属性。
|
||||
. View the resource attributes of the rule group in the **Attributes** area on the left side of the details page.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
include::ruleGroups-para-ruleGroupStatus.adoc[]
|
||||
|
||||
|检查间隔
|
||||
|指标检查之间的时间间隔。
|
||||
|Check Interval
|
||||
|The time interval between metric checks.
|
||||
|
||||
include::ruleGroups-para-timeSpent.adoc[]
|
||||
|
||||
|创建时间
|
||||
|规则组的创建时间。
|
||||
|Creation Time
|
||||
|The creation time of the rule group.
|
||||
|
||||
|创建者
|
||||
|规则组的创建者。
|
||||
|Creator
|
||||
|The creator of the rule group.
|
||||
|===
|
||||
--
|
||||
|
||||
. 在规则组详情页面右侧的**告警规则**页签查看规则组中设置的告警规则。
|
||||
. View the alert rules set in the rule group in the **Alert Rules** tab on the right side of the rule group details page.
|
||||
+
|
||||
--
|
||||
**告警规则**页签显示告警规则的名称、告警级别、触发状态、监控目标和最近检查时间。
|
||||
The **Alert Rules** tab displays the name, severity, trigger status, monitoring target, and last check time of the alert rules.
|
||||
|
||||
* 在告警规则名称右侧点击image:/images/ks-qkcp/zh/icons/monitor.svg[monitor,18,18]可查看监控指标数据。
|
||||
* Click image:/images/ks-qkcp/zh/icons/monitor.svg[monitor,18,18] on the right side of the alert rule name to view the metric data.
|
||||
|
||||
* 在告警规则右侧点击image:/images/ks-qkcp/zh/icons/chevron-down.svg["chevron-down",18,18]可查看告警规则的触发条件、PromSQL 表达式和告警消息内容。
|
||||
* Click image:/images/ks-qkcp/zh/icons/chevron-down.svg["chevron-down",18,18] on the right side of the alert rule to view the trigger condition, PromSQL expression, and alert message content of the alert rule.
|
||||
--
|
||||
|
||||
. 在规则组详情页面右侧点击**告警**页签查看当前生成的告警。
|
||||
. Click the **Alerts** tab on the right side of the details page to view the currently generated alerts.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|消息
|
||||
|Message
|
||||
|
|
||||
include::ruleGroups-para-message.adoc[]
|
||||
|
||||
|告警级别
|
||||
|Severity
|
||||
|
|
||||
include::ruleGroups-para-alertLevel.adoc[]
|
||||
|
||||
|监控目标
|
||||
|规则组的监控目标。
|
||||
|Monitoring Target
|
||||
|The monitoring target of the rule group.
|
||||
|
||||
|触发时间
|
||||
|Trigger Time
|
||||
|
|
||||
include::ruleGroups-para-activationTime.adoc[]
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: c3b29bad32424d7abc3be2e77357df17
|
||||
规则组由**未触发**状态变为**验证中**状态的时间。
|
||||
The time when the rule group changed from the **Inactive** state to the **Pending** state.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 63afbb864bc3418ca45d632bcda4ba1d
|
||||
告警的级别，包括**提醒、警告、重要、紧急**。
|
||||
The level of the alert, including **Info, Warning, Error, Critical**.
|
||||
|
|
@ -1,18 +1,18 @@
|
|||
// :ks_include_id: 9e29dba51eed467195d8b4402adcee08
|
||||
* 规则组列表提供以下信息：
|
||||
* The rule group list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|规则组的名称。
|
||||
|Name
|
||||
|The name of the rule group.
|
||||
|
||||
include::ruleGroups-para-ruleGroupStatus.adoc[]
|
||||
|
||||
|规则状态
|
||||
|规则组中包含的告警规则的状态。
|
||||
|Rule Status
|
||||
|The status of the alert rules contained in the rule group.
|
||||
|
||||
include::ruleGroups-para-alertingStatusInactive.adoc[]
|
||||
|
||||
|
|
@ -22,10 +22,10 @@ include::ruleGroups-para-alertingStatusDisabled.adoc[]
|
|||
|
||||
include::ruleGroups-para-timeSpent.adoc[]
|
||||
|
||||
// |集群
|
||||
// |使用该规则组进行资源监控的集群。
|
||||
// |Cluster
|
||||
// |The cluster using this rule group for resource monitoring.
|
||||
|
||||
|最近检查
|
||||
|最近一次指标检查的执行时间。
|
||||
|Last Check
|
||||
|The execution time of the most recent metric check.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,18 +1,18 @@
|
|||
// :ks_include_id: 9e29dba51eed467195d8b4402adcee08
|
||||
* 规则组列表提供以下信息：
|
||||
* The rule group list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|名称
|
||||
|规则组的名称。
|
||||
|Name
|
||||
|The name of the rule group.
|
||||
|
||||
include::ruleGroups-para-ruleGroupStatus.adoc[]
|
||||
|
||||
|规则状态
|
||||
|规则组中包含的告警规则的状态。
|
||||
|Rule Status
|
||||
|The status of the alert rules contained in the rule group.
|
||||
|
||||
include::ruleGroups-para-alertingStatusInactive.adoc[]
|
||||
|
||||
|
|
@ -22,10 +22,10 @@ include::ruleGroups-para-alertingStatusDisabled.adoc[]
|
|||
|
||||
// include::ruleGroups-para-timeSpent.adoc[]
|
||||
|
||||
|集群
|
||||
|使用该规则组进行资源监控的集群。
|
||||
|Cluster
|
||||
|The clusters using this rule group for resource monitoring.
|
||||
|
||||
|最近检查
|
||||
|最近一次指标检查的执行时间。
|
||||
|Last Check
|
||||
|The execution time of the most recent metric check.
|
||||
|===
|
||||
--
|
||||
--
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: a88a0cc5a6db44ab923dd629c50bafd4
|
||||
* **已禁用**：告警规则已被禁用。
|
||||
* **Disabled**: The alert rule has been disabled.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 6bf2b0acd7e043fc8ef1328d3b45bec3
|
||||
* **未触发**：监控指标未满足预设的条件。此状态下系统不生成告警。
|
||||
* **Inactive**: The monitoring metrics do not meet the preset conditions. No alerts are generated in this state.
|
||||
|
|
@ -1,11 +1,11 @@
|
|||
// :ks_include_id: 154069b262b94648a55d983b0875f8c6
|
||||
|别名
|
||||
|规则组的别名。不同规则组的别名可以相同。别名只能包含中文、字母、数字和连字符（-），不得以连字符（-）开头或结尾，最长 63 个字符。
|
||||
|Alias
|
||||
|The alias of the rule group. Different rule groups can have the same alias. The alias can only contain Chinese characters, letters, numbers, and hyphens (-), and cannot start or end with a hyphen (-), with a maximum of 63 characters.
|
||||
|
||||
|检查间隔
|
||||
|指标检查之间的时间间隔。默认值为 1 分钟。
|
||||
|Check Interval
|
||||
|The time interval between metric checks. The default value is 1 minute.
|
||||
|
||||
|描述
|
||||
|规则组的描述信息。
|
||||
|Description
|
||||
|The description of the rule group.
|
||||
|
||||
描述可包含任意字符，最长 256 个字符。
|
||||
The description can contain any characters, with a maximum of 256 characters.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 5f7a598e105f43558afe250665ee56d2
|
||||
告警消息的概要和详情。如果未设置消息的详情，**消息**列将显示告警规则组的概要。
|
||||
The summary and details of the alert message. If the details of the message are not set, the **Message** column will display the summary of the rule group.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: d4684807ee1d4a93ac734c072d1ce511
|
||||
|规则组状态
|
||||
|规则组当前是否已启用。
|
||||
|Rule Group Status
|
||||
|Whether the rule group is currently enabled.
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
// :ks_include_id: 83be107bbcde41f7a4e73bae25c1e923
|
||||
|耗时
|
||||
|最近一次指标检查所花费的时间。
|
||||
|Time Spent
|
||||
|The time spent on the most recent metric check.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: 6aade36eb695477ab6e8a0eda652c52e
|
||||
本节介绍如何编辑监控导出器。
|
||||
This section introduces how to edit a metrics exporter.
|
||||
|
||||
监控导出器用于对应用程序进行监控。{ks_product-en}平台的监控告警功能底层通过 Prometheus 实现。为监控应用程序的运行状况，您需要进行以下操作：
|
||||
A metrics exporter is used to monitor applications. The monitoring and alerting functions of KubeSphere are implemented through Prometheus at the bottom layer. To monitor the running status of applications, you need to perform the following operations:
|
||||
|
|
@ -1,47 +1,48 @@
|
|||
// :ks_include_id: f0e2bbaddcbd4d3db4ce4f3625f57ca1
|
||||
. 在服务详情页面左上角选择**更多操作 > 编辑监控导出器**。
|
||||
. Select **More > Edit Metrics Exporter** in the upper left corner of the service details page.
|
||||
|
||||
. 在**编辑监控导出器**页面，设置监控指标的收集路径、收集间隔和超时时间，然后点击**确定**。
|
||||
. On the **Edit Metrics Exporter** page, set the collection path, collection interval, and timeout for the monitoring metrics, then click **OK**.
|
||||
+
|
||||
--
|
||||
{ks_product-en}的监控告警模块将根据此处设置的参数访问服务并收集应用程序的监控指标。
|
||||
The monitoring and alerting module of KubeSphere will access the service and collect the application's monitoring metrics based on the parameters set here.
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|Parameter |Description
|
||||
|
||||
|协议
|
||||
|用于通信的协议，取值可以为 **HTTP** 或 **HTTPS**。
|
||||
|Protocol
|
||||
|The protocol used for communication, which can be **HTTP** or **HTTPS**.
|
||||
|
||||
|端口
|
||||
|用于通信的服务端口。
|
||||
|Port
|
||||
|The service port used for communication.
|
||||
|
||||
|路径
|
||||
|暴露应用程序监控指标的路径。
|
||||
|Path
|
||||
|The path exposing the application's monitoring metrics.
|
||||
|
||||
|认证方式
|
||||
|收集应用程序监控指标过程的通信认证方式。
|
||||
|Authentication Method
|
||||
|The communication authentication method for the process of collecting application monitoring metrics.
|
||||
|
||||
* **无需认证**：不采用任何认证手段。此方式可能存在信息安全隐患。
|
||||
* **No Authentication**: No authentication method is used. This method may have information security risks.
|
||||
|
||||
* **TLS**：收集应用程序监控指标的过程通过 TLS 协议进程认证。
|
||||
* **TLS**: The process of collecting application monitoring metrics is authenticated through the TLS protocol.
|
||||
|
||||
* **Bear 令牌**：通过令牌进行认证。
|
||||
* **Bearer Token**: Authentication is performed through a token.
|
||||
|
||||
* **基础认证**：通过用户名和密码认证。
|
||||
* **Basic Authentication**: Authentication is performed through a username and password.
|
||||
|
||||
除**无需认证**外，其他认证方式都需要在应用程序中配置对应的认证逻辑，并提前创建包含认证信息的保密字典。
|
||||
Except for **No Authentication**, other authentication methods require corresponding authentication logic to be configured in the application and a Secret containing the authentication information to be created in advance.
|
||||
|
||||
|收集间隔
|
||||
|应用程序监控指标的收集间隔，单位为分钟。
|
||||
|Collection Interval
|
||||
|The collection interval for application monitoring metrics, in minutes.
|
||||
|
||||
|超时时间
|
||||
|每次收集应用程序监控指标的超时时间，单位为秒。
|
||||
|Timeout
|
||||
|The timeout for each collection of application monitoring metrics, in seconds.
|
||||
|===
|
||||
--
|
||||
|
||||
// Note
|
||||
include::../../../../_ks_components-en/admonitions/note.adoc[]
|
||||
|
||||
监控导出器创建完成后，您还需要在{ks_product-en} Web 控制台使用监控指标进一步创建规则组或自定义监控面板，以对应用程序的运行状态进行监控。
|
||||
After the metrics exporter is created, you also need to use the monitoring metrics to further create rule groups or custom monitoring dashboards in the {ks_product-en} web console to monitor the running status of the application.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 9014ea6811834538b9c5b7fe24097a91
|
||||
. 在{ks_product-en} Web 控制台，使用监控指标创建规则组或自定义监控面板，从而对应用程序的运行状况进行监控。
|
||||
. In the {ks_product-en} web console, create rule groups or custom monitoring dashboards using monitoring metrics to monitor the running status of applications.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: f845b7136ccc47a59ea94257751c74cc
|
||||
* 您需要配置目标应用程序将符合 Prometheus 规范的监控指标暴露在某个服务端路径下。有关更多信息，请参阅 link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus 官方文档]。
|
||||
* You should configure the application to expose monitoring metrics that conform to the Prometheus specification at a certain service endpoint. For more information, see the link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus Documentation].
|
||||
|
||||
* 如果监控指标采集过程需要认证，您还需要在目标应用程序中配置相关认证逻辑，并在{ks_product-en}平台提前创建包含认证信息的保密字典。
|
||||
* If the monitoring metric collection process requires authentication, you also need to configure the relevant authentication logic in the target application and create a Secret containing the authentication information in the {ks_product-en} platform in advance.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: 8780fa783a634e2ea7e02b71327c3608
|
||||
. 在**卷快照**页面点击**卷快照内容**打开卷快照内容列表。
|
||||
. Click **Volume Snapshot Content** on the **Volume Snapshots** page to open the volume snapshot content list.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: a2112616394340108e2af64c91d2c33d
|
||||
卷快照内容对应的持久卷的容量。
|
||||
The capacity of the persistent volume corresponding to the volume snapshot content.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: a1caf9b38b4a4e0ab7bd462783b840a5
|
||||
删除卷快照时对卷快照内容采取的策略。删除策略在对应的卷快照类中设置。
|
||||
The policy for handling the volume snapshot content when the volume snapshot is deleted. The deletion policy is set in the corresponding volume snapshot class.
|
||||
|
||||
* **Delete**：卷快照被删除后，系统自动删除卷快照内容。
|
||||
* **Delete**: The volume snapshot content is automatically deleted by the system after the volume snapshot is deleted.
|
||||
|
||||
* **Retain**：卷快照被删除后，系统不自动删除卷快照内容。
|
||||
* **Retain**: The volume snapshot content is not deleted by the system after the volume snapshot is deleted.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
// :ks_include_id: 6967c031afb24424b3fdd01250460660
|
||||
卷快照内容的状态。
|
||||
The status of the volume snapshot content.
|
||||
|
||||
* **就绪**：卷快照内容已创建成功，并且快照数据已保存到后端存储系统。
|
||||
* **Ready**: The volume snapshot content has been successfully created, and the snapshot data has been saved to the backend storage system.
|
||||
|
||||
* **未就绪**：卷快照内容正在创建或正在删除中。
|
||||
* **Not Ready**: The volume snapshot content is being created or is being deleted.
|
||||
|
|
@ -1,2 +1,2 @@
|
|||
// :ks_include_id: fc3e0f0606144b55b1662409e2c4b5cb
|
||||
创建卷快照所使用的卷快照类。
|
||||
The volume snapshot class used to create the volume snapshot.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
// :ks_include_id: e8fdffd5e61b45e99c5afd2ae8efb5ec
|
||||
本节介绍如何使用卷快照创建持久卷。
|
||||
This section describes how to create a persistent volume using a volume snapshot.
|
||||
|
||||
卷快照创建后，您可以使用卷快照创建持久卷声明和持久卷。
|
||||
After a volume snapshot is created, you can use it to create a persistent volume claim and a persistent volume.
|
||||
|
|
@ -1,9 +1,9 @@
|
|||
// :ks_include_id: 3603af7c772d428bb6e514c29c8eb747
|
||||
本节介绍如何删除卷快照。
|
||||
This section describes how to delete a volume snapshot.
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
卷快照删除后不能恢复，请谨慎执行此操作以免数据丢失。
|
||||
Volume snapshots cannot be recovered after deletion. Please proceed with caution to avoid data loss.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue