mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Merge branch 'master' into exercise
This commit is contained in:
commit
2f5c22c1c3
|
|
@ -33,6 +33,7 @@ ignorefiles = [ ".*/_custom" ]
|
|||
ks_product_right = "KubeSphere "
|
||||
ks_product_both = " KubeSphere "
|
||||
ks_product_full = "KubeSphere"
|
||||
ks_product-en = "KubeSphere"
|
||||
ks_product_ver = "v4.1"
|
||||
|
||||
[security]
|
||||
|
|
@ -157,7 +158,13 @@ name = "Documentation"
|
|||
hasChildren = true
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v3.4 <img src='/images/header/star.svg' alt='star'>"
|
||||
name = "v4.1 <img src='/images/header/star.svg' alt='star'>"
|
||||
URL = "/docs/v4.1"
|
||||
weight = 42
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v3.4"
|
||||
URL = "/docs/v3.4"
|
||||
weight = 43
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1 @@
|
|||
|===
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|Note
|
||||
|
||||
|
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
[.admon.tip,cols="a"]
|
||||
|===
|
||||
|Tip
|
||||
|
||||
|
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
[.admon.warning,cols="a"]
|
||||
|===
|
||||
|Warning
|
||||
|
||||
|
|
||||
|
|
@ -0,0 +1,59 @@
|
|||
// :ks_include_id: b8d5e1c74e4a446384a0cc915298e456
|
||||
|
||||
= 术语和缩略语link:[id=9b8564b2818b4de5b00fb81c1989a9e9]
|
||||
|
||||
[role="glossary",cols="1a,5a,5a"]
|
||||
|===
|
||||
|
||||
|API
|
||||
|Application Programming Interface
|
||||
|应用程序编程接口
|
||||
|
||||
|CPU
|
||||
|Central Processing Unit
|
||||
|中央处理器
|
||||
|
||||
|DNS
|
||||
|Domain Name System
|
||||
|域名系统
|
||||
|
||||
|GPU
|
||||
|Graphics Processing Unit
|
||||
|图形处理器
|
||||
|
||||
|gRPC
|
||||
|gRPC Remote Procedure Calls
|
||||
|gRPC 远端程序呼叫协议
|
||||
|
||||
|HTTP
|
||||
|Hypertext Transfer Protocol
|
||||
|超文本传输协议
|
||||
|
||||
|HTTPS
|
||||
|Hypertext Transfer Protocol Secure
|
||||
|超文本传输安全协议
|
||||
|
||||
|ID
|
||||
|Identifier
|
||||
|标识符
|
||||
|
||||
|IOPS
|
||||
|Input/Output Operations Per Second
|
||||
|每秒输入输出操作数
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|
||||
|QoS
|
||||
|Quality of Service
|
||||
|服务质量
|
||||
|
||||
|TLS
|
||||
|Transport Layer Security
|
||||
|传输层安全协议
|
||||
|
||||
|WAL
|
||||
|Write Ahead Log
|
||||
|预写日志
|
||||
|===
|
||||
|
|
@ -0,0 +1,55 @@
|
|||
// :ks_include_id: 97d118168300404498cba8389b3a7499
|
||||
|
||||
= 术语和缩略语link:[id=e7d3a8242fc340318d7c62a4b31260fc]
|
||||
|
||||
[role="glossary",cols="1a,5a,5a"]
|
||||
|===
|
||||
|
||||
|API
|
||||
|Application Programming Interface
|
||||
|应用程序编程接口
|
||||
|
||||
|CSI
|
||||
|Container Storage Interface
|
||||
|容器存储接口
|
||||
|
||||
|ID
|
||||
|Identifier
|
||||
|标识符
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|
||||
|NFS
|
||||
|Network File System
|
||||
|网络文件系统
|
||||
|
||||
|NIC
|
||||
|Network Interface Card
|
||||
|网络接口卡
|
||||
|
||||
|RBD
|
||||
|Rados Block Device
|
||||
|Rados 块设备
|
||||
|
||||
|SSH
|
||||
|Secure Shell
|
||||
|安全外壳协议
|
||||
|
||||
|TCP
|
||||
|Transmission Control Protocol
|
||||
|传输控制协议
|
||||
|
||||
|UDP
|
||||
|User Datagram Protocol
|
||||
|用户数据报协议
|
||||
|
||||
|URL
|
||||
|Uniform Resource Locator
|
||||
|统一资源定位符
|
||||
|
||||
|VIP
|
||||
|Virtual Internet Protocol Address
|
||||
|虚拟 IP 地址
|
||||
|===
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
// :ks_include_id: c6c90ffe51d64b43a2d6226fdeda8dd3
|
||||
|
||||
= 术语和缩略语link:[id=59c65fc0d22a405f8a01aee13b88b437]
|
||||
|
||||
[role='glossary',cols='1a,5a,5a']
|
||||
|===
|
||||
|
||||
|CPU
|
||||
|Central Processing Unit
|
||||
|中央处理器
|
||||
|
||||
|HTTP
|
||||
|Hypertext Transfer Protocol
|
||||
|超文本传输协议
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|
||||
|JAR
|
||||
|Java Archive
|
||||
|Java 归档
|
||||
|
||||
|URL
|
||||
|Uniform Resource Locator
|
||||
|统一资源定位符
|
||||
|
||||
|WAR
|
||||
|Web Application Archive
|
||||
|Web 应用程序归档
|
||||
|===
|
||||
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
// :ks_include_id: c2039f04a78f4459a928dc18dd6833c8
|
||||
|
||||
= 术语和缩略语link:[id=3472972bef064e318fd5269270643e79]
|
||||
|
||||
[role='glossary',cols='1a,5a,5a']
|
||||
|===
|
||||
|
||||
|CPU
|
||||
|Central Processing Unit
|
||||
|中央处理器
|
||||
|
||||
|URL
|
||||
|Uniform Resource Locator
|
||||
|统一资源定位符
|
||||
|===
|
||||
|
|
@ -0,0 +1,55 @@
|
|||
// :ks_include_id: f74b6e7ec2b54e58893c8ba9fee38eb8
|
||||
|
||||
= 术语和缩略语link:[id=429ec86a5f354f008e4a72c1dac37ef9]
|
||||
|
||||
[role='glossary',cols='1a,5a,5a']
|
||||
|===
|
||||
|CD
|
||||
|Continuous Deployment
|
||||
|持续部署
|
||||
|
||||
|CI
|
||||
|Continuous Integration
|
||||
|持续集成
|
||||
|
||||
|ID
|
||||
|Identifier
|
||||
|标识符
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|
||||
|JAR
|
||||
|Java Archive
|
||||
|Java 归档
|
||||
|
||||
|JDK
|
||||
|Java Development Kit
|
||||
|Java 开发套件
|
||||
|
||||
|PR
|
||||
|Pull Request
|
||||
|拉取请求
|
||||
|
||||
|SCM
|
||||
|Source Code Management
|
||||
|源代码管理
|
||||
|
||||
|SMTP
|
||||
|Simple Mail Transfer Protocol
|
||||
|简单邮件传输协议
|
||||
|
||||
|SSH
|
||||
|Secure Shell
|
||||
|安全外壳协议
|
||||
|
||||
|SSL
|
||||
|Secure Socket Layer
|
||||
|安全套接层协议
|
||||
|
||||
|URL
|
||||
|Uniform Resource Locator
|
||||
|统一资源定位符
|
||||
|===
|
||||
|
||||
|
|
@ -0,0 +1,81 @@
|
|||
// :ks_include_id: 38b33a724ea748e79d4810f7d9fed6dd
|
||||
|
||||
:toc: macro
|
||||
:toc-title: 目录
|
||||
:toclevels: 5
|
||||
:figure-caption!:
|
||||
:sectnums:
|
||||
:sectnumlevels: 5
|
||||
|
||||
= {empty}
|
||||
|
||||
[.top_left]
|
||||
{ks_product_right}{ks_doc_type}
|
||||
|
||||
[.bottom_left]
|
||||
文档版本 01
|
||||
|
||||
[.bottom_center]
|
||||
版权所有 © 北京青云科技股份有限公司
|
||||
|
||||
[.cover_product_logo]
|
||||
--
|
||||
ifeval::["{ks_output_type}" == "md"]
|
||||
image::/images/ks-qkcp/pdf/kubesphere-logo.svg[]
|
||||
endif::[]
|
||||
ifeval::["{ks_output_type}" == "pdf"]
|
||||
image::/images/ks-qkcp/pdf/kubesphere-enterprise-logo.svg[]
|
||||
endif::[]
|
||||
--
|
||||
|
||||
[.cover_doc_image]
|
||||
image::/images/ks-qkcp/pdf/cover_doc_image.svg[]
|
||||
|
||||
[.cover_doc_name]
|
||||
{ks_product} +
|
||||
{ks_doc_type}
|
||||
|
||||
[.cover_footer,cols="2a,1a"]
|
||||
|===
|
||||
|
||||
|
|
||||
[.cover_qc_logo]
|
||||
image::/images/ks-qkcp/pdf/qingcloud-logo-color.png[]
|
||||
|
||||
北京青云科技股份有限公司
|
||||
|
||||
|
|
||||
文档版本:01
|
||||
|
||||
发布日期:{ks_release_date}
|
||||
|
||||
|===
|
||||
|
||||
[.legal_info]
|
||||
--
|
||||
版权所有 © 北京青云科技股份有限公司 {ks_year}。保留所有权利。
|
||||
|
||||
非经本公司书面许可,任何单位和个人不得摘抄、复制或以任何形式传播本文档的部分或全部内容。
|
||||
|
||||
{empty} +
|
||||
|
||||
**商标声明**
|
||||
|
||||
image:/images/ks-qkcp/pdf/qingcloud-logo-icon.png[qincloud-logo-icon,18,18] 和其他青云商标均由北京青云科技股份有限公司拥有。
|
||||
|
||||
本文档提及的其他商标或注册商标,由各自的所有人拥有。
|
||||
|
||||
{empty} +
|
||||
|
||||
**注意**
|
||||
|
||||
本文档描述的部分产品、服务和特性可能不在您的购买或使用范围之内,您购买的产品、服务或特性应受青云公司商业合同和条款的约束。
|
||||
|
||||
本文档内容会不定期进行更新。本文档仅作为使用指导,本文档中的所有陈述、信息和建议不构成任何明示或暗示的担保。
|
||||
|
||||
{empty} +
|
||||
|
||||
北京青云科技股份有限公司
|
||||
|
||||
网址:link:https://www.qingcloud.com[]
|
||||
--
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
// :ks_include_id: f758182e5c684e5ba39019679fb97491
|
||||
|
||||
= 术语和缩略语link:[id=0ee2fad5148241d3ba54758ec260b3d5]
|
||||
|
||||
[role='glossary',cols='1a,5a,5a']
|
||||
|===
|
||||
|
||||
|API
|
||||
|Application Programming Interface
|
||||
|应用程序编程接口
|
||||
|
||||
|ID
|
||||
|Identifier
|
||||
|标识符
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|
||||
|SMTP
|
||||
|Simple Mail Transfer Protocol
|
||||
|简单邮件传输协议
|
||||
|
||||
|SSL
|
||||
|Secure Socket Layer
|
||||
|安全套接层协议
|
||||
|
||||
|TLS
|
||||
|Transport Layer Security
|
||||
|传输层安全协议
|
||||
|
||||
|URL
|
||||
|Uniform Resource Locator
|
||||
|统一资源定位符
|
||||
|===
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
// :ks_include_id: 7b6a4a49214d4844b4f52db200abc0b9
|
||||
|
||||
= 术语和缩略语link:[id=a4986b482c4e4954965443673a2c3101]
|
||||
|
||||
[role='glossary',cols='1a,5a,5a']
|
||||
|===
|
||||
|CPU
|
||||
|Central Processing Unit
|
||||
|中央处理器
|
||||
|
||||
|HTTP
|
||||
|Hypertext Transfer Protocol
|
||||
|超文本传输协议
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|
||||
|TCP
|
||||
|Transmission Control Protocol
|
||||
|传输控制协议
|
||||
|===
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
// :ks_include_id: 63fbc621a65f4bf38d109b72a71cf170
|
||||
|
||||
|
||||
ifeval::["{ks_output_type}" == "md"]
|
||||
[subs=attributes]
|
||||
++++
|
||||
---
|
||||
title: "{ks_title}"
|
||||
linkTitle: "{ks_title}"
|
||||
keywords: "{ks_keywords}"
|
||||
description: "{ks_description}"
|
||||
weight: {ks_weight}
|
||||
layout: "second"
|
||||
icon: "{ks_icon}"
|
||||
---
|
||||
++++
|
||||
endif::[]
|
||||
ifeval::["{ks_output_type}" == "pdf"]
|
||||
= {ks_title}link:[id={ks_xref_id}]
|
||||
endif::[]
|
||||
|
|
@ -0,0 +1,31 @@
|
|||
// :ks_include_id: a01602c836d8452bad7f89c2081e09f6
|
||||
|
||||
= 术语和缩略语link:[id=9dfab7e9e67a4ae9929c1ad0214772be]
|
||||
|
||||
[role="glossary",cols="1a,5a,5a"]
|
||||
|===
|
||||
|
||||
|CPU
|
||||
|Central Processing Unit
|
||||
|中央处理器
|
||||
|
||||
|GPU
|
||||
|Graphics Processing Unit
|
||||
|图形处理器
|
||||
|
||||
|HTTP
|
||||
|Hypertext Transfer Protocol
|
||||
|超文本传输协议
|
||||
|
||||
|HTTPS
|
||||
|Hypertext Transfer Protocol Secure
|
||||
|超文本传输安全协议
|
||||
|
||||
|ID
|
||||
|Identifier
|
||||
|标识符
|
||||
|
||||
|IP
|
||||
|Internet Protocol
|
||||
|互联网协议
|
||||
|===
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
[source,shell,subs="+attributes"]
|
||||
----
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
[source,go,subs="+attributes"]
|
||||
----
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
[source,html,subs="+attributes"]
|
||||
----
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
[source,javascript,subs="+attributes"]
|
||||
----
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
[source,json,subs="+attributes"]
|
||||
----
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
[source,yaml,subs="+attributes"]
|
||||
----
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: ec0f4321f3a8496cb29e4a605d5d28bc
|
||||
* Click image:/images/ks-qkcp/zh/icons/start-dark.svg[start,18,18]/image:/images/ks-qkcp/zh/icons/pause.svg[pause,18,18] in the upper right corner to enable/disable real-time data refresh.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: d183e3529a4d49b0b7a05f96151355c1
|
||||
. Click **Create** on the page.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 09975a5d93ed49ddb6c7c3b42ec274f7
|
||||
. Click **Invite** on the right side of the page.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 42b64c64491a4e459b1d34958715d6f8
|
||||
* Click image:/images/ks-qkcp/zh/icons/cogwheel.svg[cogwheel,18,18] in the upper right corner of the list to customize the information displayed in the list.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: b773f29ad54e4ebd84187b0924c41f21
|
||||
. Click pass:a,q[{ks_navigation}] in the left navigation pane.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 4bba5db43c504475853edcfabbcf5652
|
||||
* Click image:/images/ks-qkcp/zh/icons/refresh-dark.svg[refresh,18,18] in the upper right corner to refresh data manually.
|
||||
|
|
@ -0,0 +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.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: f19343cbb46b40ed9e124afde952b084
|
||||
. Select pass:a,q[{ks_menu}] in the upper left corner of the page.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 9a5774e5ba9d4e5d950143cba4a5111d
|
||||
* Click image:/images/ks-qkcp/zh/icons/timed-task.svg[timed-task,18,18] in the upper right corner to set the time range.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 7a00832787eb484492170688816b225c
|
||||
本节介绍如何查看告警列表。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: a11cb13f4c4d44e59332bb4fe44859c0
|
||||
. 在**告警**页面点击**来源于自定义规则**或**来源于内置规则**打开告警列表。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: c6a3057001e24f3d85a69f8429cf509c
|
||||
* 在列表上方点击搜索框并设置搜索条件,可按告警状态、告警级别和规则名称搜索告警。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: c6a3057001e24f3d85a69f8429cf509c
|
||||
* 在列表上方点击搜索框并设置搜索条件,可按告警内容、告警状态、告警级别和规则名称搜索告警。
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
// :ks_include_id: 9bb30ff8148c403aa266fbe96dcaa2a8
|
||||
* 告警列表提供以下信息:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|消息
|
||||
|
|
||||
include::../ruleGroups/ruleGroups-para-message.adoc[]
|
||||
|
||||
|状态
|
||||
|
|
||||
告警当前的状态。
|
||||
|
||||
include::alerts-para-alertingStatus.adoc[]
|
||||
|
||||
|告警级别
|
||||
|
|
||||
include::../ruleGroups/ruleGroups-para-alertLevel.adoc[]
|
||||
|
||||
|规则名称
|
||||
|告警规则的名称。
|
||||
|
||||
|规则组
|
||||
|告警规则组的名称。
|
||||
|
||||
|监控目标
|
||||
|生成告警的监控目标的类型和名称。
|
||||
|
||||
|触发时间
|
||||
|
|
||||
include::../ruleGroups/ruleGroups-para-activationTime.adoc[]
|
||||
|===
|
||||
--
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: eb9742b579e948b29be0240b89d9335b
|
||||
* **验证中**:监控指标满足预设的条件,但未满足预设的持续时间。
|
||||
|
||||
* **已触发**:监控指标满足预设的条件,并且满足预设的持续时间。
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
// :ks_include_id: 156b3180d19240238f9195fd4cc024c5
|
||||
This section explains how to manage configuration resources.
|
||||
|
||||
KubeSphere supports managing the following three types of configuration resources:
|
||||
|
||||
* Secret: Contains Base64-encoded key-value pairs, used to store sensitive data such as passwords, tokens, and keys.
|
||||
|
||||
* ConfigMap: Contains plain-text key-value pairs, used to store regular configuration data.
|
||||
|
||||
* Service Account: Stores access information for the current KubeSphere cluster, used to provide access to the KubeSphere cluster for applications.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: ac11303d404249078087f1c605445e15
|
||||
. Log in to the {ks_product-en} web console with a user who has the pass:a,q[{ks_permission}] permission, and access your cluster.
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
// :ks_include_id: 28089246770746498a85c468382fdb76
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|Parameter |Description
|
||||
|
||||
|Type
|
||||
|The type of the event, including **Normal** and **Warning**.
|
||||
|
||||
|Reason
|
||||
|The reason for the event.
|
||||
|
||||
|Occurred
|
||||
|The time when the event occurred.
|
||||
|
||||
|Source
|
||||
|The component that reported the event.
|
||||
|
||||
|Message
|
||||
|The content of the event message.
|
||||
|===
|
||||
|
|
@ -0,0 +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[项目角色]。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: f3341457c4584e59b799240a35ca496d
|
||||
You should join a cluster and have the pass:a,q[{ks_permission}] permission within the cluster. For more information, refer to "Cluster Members" and "Cluster Roles".
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 498ec63e8fb645ccab190e0595b053f8
|
||||
In a multi-cluster environment, the user who adds a cluster is automatically designated as the cluster administrator. Additionally, the **admin** user by default has full permissions in all clusters. In the initial state of a cluster, the aforementioned users can invite other users to join the cluster and set the roles for these users within the cluster.
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
// :ks_include_id: 8fa15cb04f8048cfa5479d1a77ddf099
|
||||
KubeSphere provides the following built-in cluster roles:
|
||||
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
| Role | Description
|
||||
|
||||
| cluster-admin
|
||||
| Cluster administrator with all permissions within the cluster except creating and deleting clusters.
|
||||
|
||||
| cluster-viewer
|
||||
| Cluster viewer with permissions to view all resources within the cluster.
|
||||
|===
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
// :ks_include_id: 431b5c3a6af541aa9bf2e1607c05789d
|
||||
* **Active**: The user's current status is normal.
|
||||
|
||||
* **Waiting**: The system is creating the user.
|
||||
|
||||
* **Disabled**: The user is disabled by the platform administrator and cannot log in to the {ks_product-en} web console.
|
||||
|
||||
* **Restricted**: The user has failed to log in 10 times in 10 minutes and is blocked from logging in to the {ks_product-en} web console for 10 minutes.
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
// :ks_include_id: 532573492da34fcbb954ea832aa9fcd5
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|Parameter |Description
|
||||
|
||||
|Username
|
||||
|Name of the user who has been authorized.
|
||||
|
||||
|Status
|
||||
|Current status of the user who has been authorized.
|
||||
|
||||
include::../clusterMembers/clusterMembers-para-userStatus.adoc[]
|
||||
|
||||
|Last Login
|
||||
|The user's last login time on the {ks_product-en} platform.
|
||||
|===
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: c545dcba1c5d46908a87e91f9fc37f77
|
||||
* 在列表右上角点击**导出**可下载 JSON 格式的资源用量数据。
|
||||
|
|
@ -0,0 +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]可按升序/降序排序。
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
This section explains how to manage ConfigMaps.
|
||||
|
||||
ConfigMaps store non-sensitive data, such as environment variables, command-line parameters, and configuration files, in key-value pairs. ConfigMaps allow users to separate containers from configuration data, making it easier to manage configurations and ensure the portability of applications.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 9207e2fe36e84eb6bffadb973c32ac47
|
||||
This section explains how to create ConfigMaps.
|
||||
|
|
@ -0,0 +1,9 @@
|
|||
// :ks_include_id: 7758d91595c844e4b4614bb148e72c76
|
||||
This section explains how to delete a ConfigMap.
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
Once a ConfigMap is deleted, it cannot be recovered. Please proceed with caution when performing this operation.
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
This section explains how to edit ConfigMap information.
|
||||
|
||||
You can edit the alias and description of the ConfigMap. KubeSphere does not support editing the name of an already created ConfigMap.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 1c55971dc47241c0916ca8bb7a0877b2
|
||||
This section explains how to edit the data of a ConfigMap.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 25de9a77f93843dfb3408a738abd70c2
|
||||
This section explains how to view the list of ConfigMaps.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 1ca4dafa438c4ae7850540566a7de0e5
|
||||
This section explains how to view ConfigMap details.
|
||||
|
|
@ -0,0 +1,28 @@
|
|||
. On the **Basic Information** tab, set the basic information for the ConfigMap, and then click **Next**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1,4"]
|
||||
|===
|
||||
| Parameter | Description
|
||||
|
||||
| Name
|
||||
| The name of the ConfigMap. 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.
|
||||
|
||||
| Alias
|
||||
| The alias of the ConfigMap. Aliases can be the same for different ConfigMaps. 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.
|
||||
|
||||
| Project
|
||||
| The project to which the ConfigMap belongs.
|
||||
|
||||
| Description
|
||||
| The description of the ConfigMap. The description can contain any characters and can be up to 256 characters long.
|
||||
|===
|
||||
--
|
||||
|
||||
. On the **Data Settings** tab, set the key-value pair data for the ConfigMap, then click **Create**.
|
||||
+
|
||||
--
|
||||
include::../secrets/secrets-para-data.adoc[]
|
||||
|
||||
Once created, the ConfigMap will be displayed in the ConfigMap list.
|
||||
--
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: 971bac7a7fb84650bc6d4d9712a6b6b3
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the ConfigMap you want to delete, then choose **Delete** from the dropdown list.
|
||||
|
||||
. In the **Delete ConfigMap** dialog, enter the name of the ConfigMap, then click **OK**.
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
// :ks_include_id: 7120cca5f1fc4d69be0d4be24670e48b
|
||||
. Select the checkbox on the left of the ConfigMaps you want to delete, then click **Delete** above the ConfigMap list.
|
||||
|
||||
. In the **Delete Multiple ConfigMaps** dialog, enter the name of the ConfigMaps, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
--
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the ConfigMap you want to edit, then choose **Edit Information** from the dropdown list.
|
||||
|
||||
. In the **Edit Information** dialog, set the alias and description for the ConfigMap, then click **OK**.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
| Parameter | Description
|
||||
|
||||
| Alias
|
||||
| The alias of the ConfigMap. Aliases can be the same for different ConfigMaps. An alias can only contain Chinese characters, letters, numbers, and hyphens (-). It cannot start or end with a hyphen (-) and has a maximum length of 63 characters.
|
||||
|
||||
| Description
|
||||
| The description of the ConfigMap. The description can contain any characters, with a maximum length of 256 characters.
|
||||
|===
|
||||
--
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
// :ks_include_id: 713230cd132746e194d0cad61dade1d9
|
||||
. Click image:/images/ks-qkcp/zh/icons/more.svg[more,18,18] on the right of the ConfigMap you want to edit, then choose **Edit Settings** from the dropdown list.
|
||||
|
||||
. In the **Edit Settings** dialog, set the data for the ConfigMap, then click **OK**.
|
||||
+
|
||||
--
|
||||
include::../secrets/secrets-para-data.adoc[]
|
||||
--
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 4b348a728ca04df6ae2deda14d323b4c
|
||||
. Click the name of a ConfigMap in the list to open its details page.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: cb26ec7cf74d406f97f87eb302012018
|
||||
* Click the search box at the top of the list to search for ConfigMaps by name.
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
. View the resource attributes of the ConfigMap in the **Attributes** area on the left side of the ConfigMap details page.
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
| Parameter | Description
|
||||
|
||||
| Cluster
|
||||
| The cluster to which the ConfigMap belongs.
|
||||
|
||||
| Project
|
||||
| The project to which the ConfigMap belongs.
|
||||
|
||||
| Creation Time
|
||||
| The creation time of the ConfigMap.
|
||||
|
||||
| Creator
|
||||
| The user who created the ConfigMap.
|
||||
|===
|
||||
--
|
||||
|
||||
. On the **Data** tab on the right side of the ConfigMap details page, view the key-value pair data stored in the ConfigMap.
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
* The ConfigMaps list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
| Parameter | Description
|
||||
|
||||
| Name
|
||||
| The name and description of the ConfigMap.
|
||||
|
||||
| Project
|
||||
| The project to which the ConfigMap belongs.
|
||||
|
||||
| Fields
|
||||
|The key name of the key-value pair data stored in the ConfigMap. Different keys are separated by a comma (,).
|
||||
|
||||
| Creation Time
|
||||
|The creation time of the ConfigMap.
|
||||
|===
|
||||
--
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
* The ConfigMaps list provides the following information:
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
| Parameter | Description
|
||||
|
||||
| Name
|
||||
| The name and description of the ConfigMap.
|
||||
|
||||
// | Project
|
||||
// | The project to which the ConfigMap belongs.
|
||||
|
||||
| Fields
|
||||
|The key name of the key-value pair data stored in the ConfigMap. Different keys are separated by a comma (,).
|
||||
|
||||
| Creation Time
|
||||
|The creation time of the ConfigMap.
|
||||
|===
|
||||
--
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 58f8c216756e41e8976edccd0d0fe3be
|
||||
. Click the name of a custom resource definition in the list to open its details page.
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
// :ks_include_id: 6c86123b72d442d2af494a87b1b826cf
|
||||
The scope of custom resources created by custom resource definitions:
|
||||
|
||||
* **Namespaced**: Custom resources created by custom resource definitions belong to a specific project.
|
||||
|
||||
* **Cluster**: Custom resources created by custom resource definitions belong to the entire cluster.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 09ffce0603e5476d9b35342407c90402
|
||||
本节介绍如何创建自定义监控面板。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 3f3c9d810bbb43449843917a945b0d18
|
||||
本节介绍如何使用自定义监控面板。
|
||||
|
|
@ -0,0 +1,9 @@
|
|||
// :ks_include_id: ebf1355e06284d8a8c1f0d1c6ae2dcdf
|
||||
本节介绍如何删除自定义监控面板。
|
||||
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
自定义监控面板删除后无法恢复,请谨慎执行此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 0a4f15a804bd4a04b35fa4baec7bca69
|
||||
本节介绍如何编辑自定义监控面板。
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: fb5da34edef1455388ca60e23308095f
|
||||
. 配置运行在容器中的应用程序,将符合 Prometheus 规范的监控指标暴露在某个服务端路径下。有关更多信息,请参阅 link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus 官方文档]。
|
||||
|
||||
. 在 KubeSphere Web 控制台,在用于暴露工作负载的服务上设置监控导出器,以声明提供应用程序监控指标的路径。KubeSphere 将根据监控导出器的相关参数获取应用程序的监控指标。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 86dce4cf97db45baa0af638a00a5a435
|
||||
KubeSphere 支持通过自定义监控面板对应用程序的运行状态进行监控。您可以通过以下方式使用自定义监控面板:
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 459d38d3365247858833ed44c54b075d
|
||||
本节介绍如何查看自定义监控面板。
|
||||
|
|
@ -0,0 +1,42 @@
|
|||
// :ks_include_id: 5b3a15eedffe4ef39e6a46e6adc2b335
|
||||
. 在**创建自定义监控面板**对话框,设置监控面板的名称、描述和模板,然后点击**下一步**。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|名称
|
||||
|自定义监控面板的名称。名称只能包含小写字母、数字和连字符(-),必须以小写字母或数字开头和结尾,最长 63 个字符。
|
||||
|
||||
|描述
|
||||
|自定义监控面板的描述信息。描述可包含任意字符,最长 256 个字符。
|
||||
|
||||
|模板
|
||||
|自定义监控面板的模板。
|
||||
|
||||
* KubeSphere 提供预置了 Elasticsearch、MySQL、Redis、Jenkins 和 GPU 自定义监控面板的模板。每个模板都提供了一些预置的监控指标和监控图,您可以在模板的基础上进行定制以减少操作。
|
||||
|
||||
* 如需使用 Grafana 监控面板,您需要上传 Grafana 监控面板配置文件。
|
||||
|
||||
* 您也可以使用选择**自定义**使用空模板。
|
||||
|===
|
||||
--
|
||||
|
||||
. 在自定义监控面板编辑页面,根据需要设置监控图和以文本显示的监控指标。
|
||||
+
|
||||
====
|
||||
* 在页面左侧点击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]可创建以文本显示的监控指标。
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-textMetric.adoc[]
|
||||
--
|
||||
|
||||
* 在页面右下角点击**添加监控项**,选择**折线图**或**柱状图**,设置图表参数,然后点击image:/images/ks-qkcp/zh/icons/check-dark.svg[check-dark,18,18]可创建监控图。
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-monitoringChart.adoc[]
|
||||
--
|
||||
====
|
||||
|
||||
. 在页面右上角点击**保存模板**。监控面板创建完成后将显示在自定义监控面板列表中。
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: 91f54871ad6f447eaca67f6b1853872e
|
||||
. 在需要删除的自定义监控面板右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18],然后在下拉列表中选择**删除**。
|
||||
|
||||
. 在**删除自定义监控面板**对话框,输入自定义监控面板的名称,然后点击**确定**。
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
// :ks_include_id: da77b27e5b9840dab0503615aec625a4
|
||||
. 选择需要删除的自定义监控面板左侧的复选框,然后在自定义监控面板列表上方点击**删除**。
|
||||
|
||||
. 在**批量删除自定义监控面板**对话框,输入自定义监控面板的名称,然后点击**确定**。
|
||||
+
|
||||
--
|
||||
include::../../note-separateNamesByComma.adoc[]
|
||||
--
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
// :ks_include_id: 1762c0ce44e445d89cd9f2e5b34055fa
|
||||
. 在列表中点击一个自定义监控面板的名称打开自定义监控面板,然后在页面右上角点击**编辑模板**。
|
||||
|
||||
. 在页面左侧设置以文本显示的监控指标。
|
||||
+
|
||||
====
|
||||
* 点击image:/images/ks-qkcp/zh/icons/add-dark.svg[add-dark,18,18]可添加监控指标。
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-textMetric.adoc[]
|
||||
--
|
||||
|
||||
* 将光标悬停在监控指标上,然后点击image:/images/ks-qkcp/zh/icons/trash-dark.svg[trash-dark,18,18]可删除监控指标。
|
||||
|
||||
* 将光标悬停在监控指标上,然后点击image:/images/ks-qkcp/zh/icons/pen-dark.svg[pen-dark,18,18]可编辑监控指标。
|
||||
====
|
||||
|
||||
. 在页面右侧的监控图列表设置监控图。
|
||||
+
|
||||
====
|
||||
* 点击**添加监控项**可添加监控图。
|
||||
+
|
||||
--
|
||||
include::customMonitoringDashboards-para-monitoringChart.adoc[]
|
||||
--
|
||||
|
||||
* 将光标悬停在监控图名称上,然后点击image:/images/ks-qkcp/zh/icons/trash-light.svg[trash-light,18,18]可删除监控图。
|
||||
|
||||
* 将光标悬停在监控图名称上,然后点击image:/images/ks-qkcp/zh/icons/pen-light.svg[pen-light,18,18]可编辑监控图。
|
||||
====
|
||||
|
||||
. 在页面右上角点击**保存模板**完成编辑。
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
// :ks_include_id: f41b68cc492640acadc07b371d665ebb
|
||||
. 在需要操作的自定义监控面板右侧点击image:/images/ks-qkcp/zh/icons/more.svg[more,18,18],然后在下拉列表中选择**编辑信息**。
|
||||
|
||||
. 在**编辑信息**对话框,设置自定义监控面板的别名和描述,然后点击**确定**。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|别名
|
||||
|自定义监控面板的别名。不同自定义监控面板的别名可以相同。别名只能包含中文、字母、数字和连字符(-),不得以连字符(-)开头或结尾,最长 63 个字符。
|
||||
|
||||
|描述
|
||||
|自定义监控面板的描述信息。描述可包含任意字符,最多包含 256 个字符。
|
||||
|===
|
||||
--
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: b79841529a1d49a19e7e17eac5decf19
|
||||
. 在 KubeSphere Web 控制台,使用监控指标创建自定义监控面板,从而对应用程序的运行状况进行监控。
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
// :ks_include_id: d52d25b1598e4adb94ab8b79c98a1e00
|
||||
. 在列表中点击一个自定义监控面板的名称打开监控面板。
|
||||
+
|
||||
--
|
||||
* 在页面左侧区域可查看以文本显示的监控指标。
|
||||
|
||||
* 在页面中间区域可查看监控指标折线图或柱状图。
|
||||
|
||||
* 在页面右侧点击image:/images/ks-qkcp/zh/icons/chevron-right.svg[chevron-right,18,18]可查看每个监控指标的子指标及其在指定时间范围内的最大值、最小值、平均值和最后采样值。
|
||||
|
||||
* 在页面上方点击image:/images/ks-qkcp/zh/icons/theme.svg[theme,18,18]可切换浅色和深色主题。
|
||||
|
||||
* 在页面上方点击image:/images/ks-qkcp/zh/icons/calendar-dark.svg[calendar-dark,18,18]可设置数据的时间范围。
|
||||
|
||||
* 在页面上方点击image:/images/ks-qkcp/zh/icons/refresh-dark.svg[refresh-dark,18,18]可设置数据的刷新间隔。
|
||||
|
||||
* 在页面右上角点击image:/images/ks-qkcp/zh/icons/close-dark.svg[close,18,18]可返回自定义监控面板列表。
|
||||
--
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
// :ks_include_id: 02c275a851594f868957a3c32ff9f5cd
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|图例类型
|
||||
|监控图的纵向数据展示方式,可选类型包括**基础图**和**堆叠图**。
|
||||
|
||||
|图表配色
|
||||
|监控图的配色风格,可选类型包括**默认配色**、**冷色调**和**暖色调**。
|
||||
|
||||
|基本信息
|
||||
|用户自定义的监控图名称和描述信息。
|
||||
|
||||
|数据
|
||||
|监控图中显示的监控指标。
|
||||
|
||||
* **图例名称**:用户自定义的监控指标名称。
|
||||
|
||||
* **间隔**:监控图中数据的时间间隔,取值为 <数值><单位>,例如 **1m** 表示数据时间间隔为 1 分钟。
|
||||
|
||||
* **监控指标**:应用程序暴露的监控指标。您可以点击**监控指标**然后在下拉列表中选择监控指标,也可以手动输入 PromQL 语句。请确保您已配置应用程序暴露监控指标,并已配置监控导出器。有关 PromQL 表达式的更多信息,请参阅 link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus 官方文档]。
|
||||
|
||||
|Y 轴
|
||||
|监控图的纵坐标轴设置。
|
||||
|
||||
* **单位**:纵坐标轴的数据单位。
|
||||
|
||||
* **精确位**:纵坐标轴数据的有效小数位数。
|
||||
|===
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 5ed9a5c35fa945bc84988f238d7ab69a
|
||||
应用程序暴露的监控指标。您可以点击**监控指标**然后在下拉列表中选择监控指标,也可以手动输入 PromQL 语句。请确保您已配置应用程序暴露监控指标,并已配置监控导出器。有关 PromQL 表达式的更多信息,请参阅 link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus 官方文档]。
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
// :ks_include_id: 6d474f2ff06e43c7bc9003aaa10e29c2
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|图表名称
|
||||
|监控指标的名称。
|
||||
|
||||
|单位
|
||||
|指标数据的单位。
|
||||
|
||||
|精确位
|
||||
|指标数据的有效小数位数。
|
||||
|
||||
|监控指标
|
||||
|
|
||||
include::customMonitoringDashboards-para-monitoringMetric.adoc[]
|
||||
|
||||
|===
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 385623699d0d48bda614b5a8de5c062d
|
||||
* 您需要配置运行在容器中的应用程序将符合 Prometheus 规范的监控指标暴露在某个服务端路径下。有关更多信息,请参阅 link:https://prometheus.io/docs/instrumenting/clientlibs/[Prometheus 官方文档]。
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 854355fa9af44f41886ade72f0ee39da
|
||||
网关为 KubeSphere 平台上的服务提供反向代理。网关需要根据应用路由工作,来自客户端的业务流量先通过域名解析先发送给网关,网关再根据应用路由中定义的规则将业务流量转发给不同的服务。网关本身也是通过服务暴露的工作负载,因而网关也支持 NodePort 和 LoadBalancer 两种外部访问模式。
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: 7ea2a84e80b6439cb0d2da5db17f8e35
|
||||
. 在页面右侧选择**管理 > 禁用**。
|
||||
|
||||
. 在弹出的对话框点击**确定**。
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
// :ks_include_id: 17ab622bc96f45e68b3581c076cb1223
|
||||
. 在页面右侧选择**管理 > 编辑**。
|
||||
|
||||
. 在弹出的对话框,修改网关的参数,然后点击**确定**。
|
||||
+
|
||||
--
|
||||
include::gatewaySettings-para-enableGateway.adoc[]
|
||||
--
|
||||
|
|
@ -0,0 +1,34 @@
|
|||
// :ks_include_id: 17ab622bc96f45e68b3581c076cb1223
|
||||
. 在页面右侧选择**管理 > 编辑**。
|
||||
|
||||
. 在弹出的对话框,修改网关的参数,然后点击**确定**。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|IngressClassName
|
||||
|IngressClass 的名称。
|
||||
|
||||
|容器组副本数量
|
||||
|期望的容器组副本数量。
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|链路追踪
|
||||
|是否对网关启用链路追踪功能。如需使用链路追踪功能,KubeSphere 平台需要安装并启用 **KubeSphere 服务网格**扩展组件。
|
||||
|
||||
|配置选项
|
||||
|网关的配置选项。KubeSphere 的网关功能底层基于 Nginx Ingress Controller 实现,您可以设置网关的配置选项控制网关的行为。有关更多信息,请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|
||||
|负载均衡器提供商
|
||||
|网关的负载均衡器提供商。网关的外部访问模式为 LoadBalancer 时,您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。选择负载均衡器提供商后,设置网关服务注解时系统将提供注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。
|
||||
|
||||
|注解
|
||||
|网关服务的注解。如果已选择负载均衡器提供商,点击**键**文本框时系统将在下拉列表中显示注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。有关更多信息,请联系您的基础设施环境提供商。
|
||||
|===
|
||||
--
|
||||
|
|
@ -0,0 +1,109 @@
|
|||
// :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[]
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**元数据**页签查看网关服务的注解。
|
||||
|
|
@ -0,0 +1,125 @@
|
|||
// :ks_include_id: 2603654cc618449f9ae430c3041a361f
|
||||
. 在页面右侧选择**管理 > 查看详情**打开网关详情页面。
|
||||
|
||||
. 在网关详情页面左侧的**属性**区域查看网关的资源属性。
|
||||
+
|
||||
--
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|集群
|
||||
|网关所属的集群。
|
||||
|
||||
|创建时间
|
||||
|网关的创建时间。
|
||||
|
||||
|更新时间
|
||||
|网关的更新时间
|
||||
|
||||
|创建者
|
||||
|启用网关的用户。
|
||||
|===
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**配置选项**查看网关的配置选项。KubeSphere 的网关功能底层基于 Nginx Ingress Controller 实现,有关网关配置选项的更多信息,请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|
||||
. 在页面右侧的**监控**页签查看网关的请求数据。
|
||||
+
|
||||
====
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|
||||
|
|
||||
如需使用网关监控功能,KubeSphere 平台需要安装并启用 **WhizardTelemetry 监控**扩展组件。
|
||||
|===
|
||||
|
||||
* **概览**区域提供以下信息:
|
||||
+
|
||||
--
|
||||
[%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[]
|
||||
====
|
||||
|
||||
. 在网关详情页面右侧点击**网关日志**查看网关的日志。
|
||||
+
|
||||
--
|
||||
[.admon.note,cols="a"]
|
||||
|===
|
||||
|说明
|
||||
|
||||
|
|
||||
如需使用网关日志搜索功能,KubeSphere 平台需要安装并启用 **WhizardTelemetry 日志管理**扩展组件。
|
||||
|===
|
||||
|
||||
* 在**网关日志**页签上方点击搜索框并设置搜索条件,可按关键字、容器组或时间范围搜索日志数据。
|
||||
|
||||
* 在**网关日志**页签上方点击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[]
|
||||
--
|
||||
|
||||
. 在网关详情页面右侧点击**元数据**页签查看网关服务的注解。
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
// :ks_include_id: 09fe14af1fd747b8aad60c34a228e54e
|
||||
集群网关或项目网关的 IP 地址。
|
||||
|
||||
// tag::bullets[]
|
||||
* 如果网关的外部访问模式为 NodePort,**网关地址**为某一个集群节点的 IP 地址。客户端可以通过任意集群节点的 IP 地址和端口访问应用路由的后端服务。
|
||||
|
||||
* 如果网关的外部访问模式为 LoadBalancer,**网关地址**为负载均衡器的地址。
|
||||
|
||||
// * 如果网关地址未显示,可能是因为集群节点缺少 **node-role.kubernetes.io/master** 标签。点击**集群节点**页面,点击控制平面节点,选择**更多操作 > 编辑标签**添加 **node-role.kubernetes.io/master** 标签。v4.1 删除该行
|
||||
// end::bullets[]
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
// :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 时可用。有关更多信息,请联系您的基础设施环境提供商。
|
||||
|===
|
||||
|
|
@ -0,0 +1,31 @@
|
|||
// :ks_include_id: 70d685391e6d449cbdfb8a7f5e6e5dfa
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|Nginx Ingress 版本
|
||||
|Nginx Ingress 的版本。KubeSphere 网关扩展组件基于 Nginx Ingress 提供网关管理功能。
|
||||
|
||||
|IngressClassName
|
||||
|IngressClass 的名称。
|
||||
|
||||
|容器组副本数量
|
||||
|期望的容器组副本数量。
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|链路追踪
|
||||
|是否对网关启用链路追踪功能。如需使用链路追踪功能,{ks_product-en}平台需要安装并启用 **KubeSphere 服务网格**扩展组件。
|
||||
|
||||
|配置选项
|
||||
|网关的配置选项。{ks_product-en}的网关功能底层基于 Nginx Ingress Controller 实现,您可以设置网关的配置选项控制网关的行为。有关更多信息,请参阅 link:https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/[Nginx Ingress Controller 官方文档]。
|
||||
|
||||
|负载均衡器提供商
|
||||
|网关的负载均衡器提供商。网关的外部访问模式为 LoadBalancer 时,您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。选择负载均衡器提供商后,设置网关服务注解时系统将提供注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。
|
||||
|
||||
|注解
|
||||
|网关服务的注解。如果已选择负载均衡器提供商,点击**键**文本框时系统将在下拉列表中显示注解提示。仅在网关服务的外部访问模式为 LoadBalancer 时可用。有关更多信息,请联系您的基础设施环境提供商。
|
||||
|===
|
||||
|
|
@ -0,0 +1,37 @@
|
|||
// :ks_include_id: 6fca3db90bdf4fd8bb61eb771c1a7308
|
||||
[%header,cols="1a,4a"]
|
||||
|===
|
||||
|参数 |描述
|
||||
|
||||
|类型
|
||||
|网关的类型。
|
||||
|
||||
|创建者
|
||||
|启用网关的用户。
|
||||
|
||||
|创建时间
|
||||
|网关的启用时间。
|
||||
|
||||
|访问模式
|
||||
|网关服务的外部访问模式。
|
||||
|
||||
include::../services/services-para-externalAccess.adoc[tag=bullets]
|
||||
|
||||
|网关地址
|
||||
|
|
||||
网关的外部访问地址。
|
||||
|
||||
include::gatewaySettings-para-address.adoc[tag=bullets]
|
||||
|
||||
|节点端口
|
||||
|网关服务的 HTTP 和 HTTPS 节点端口。仅在网关的外部访问模式为 NodePort 时显示。
|
||||
|
||||
|副本
|
||||
|网关工作负载的副本数。
|
||||
|
||||
|链路追踪
|
||||
|网关是否已启用链路追踪功能。
|
||||
|
||||
|注解
|
||||
|网关服务的注解。网关的外部访问模式为 LoadBalancer 时,您需要根据负载均衡器插件和基础设施环境设置网关服务的注解以创建所需的负载均衡器。有关更多信息,请联系您的基础设施环境提供商。仅在网关的外部访问模式为 LoadBalancer 时显示。
|
||||
|===
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
// :ks_include_id: fbcc6577f08345e9a2b32a571da90898
|
||||
// Warning
|
||||
include::../../../../_ks_components-en/admonitions/warning.adoc[]
|
||||
|
||||
网关禁用后客户端将无法访问由网关反向代理的服务,相关业务可能会中断,请谨慎执行此操作。
|
||||
|
||||
include::../../../../_ks_components-en/admonitions/admonEnd.adoc[]
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
// :ks_include_id: 7f14023bc6974772b201bc6c0b92e13b
|
||||
This section explains how to create jobs.
|
||||
|
|
@ -0,0 +1,11 @@
|
|||
// :ks_include_id: 53cddf67368844919fec7ab2ca897ef6
|
||||
This section explains how to delete a job.
|
||||
|
||||
//warning
|
||||
[.admon.warning,cols="a"]
|
||||
|===
|
||||
| Warning
|
||||
|
||||
|
|
||||
This operation will delete the job and all pods managed by it. If the job is running, the business running in it will be interrupted. Please proceed with caution.
|
||||
|===
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: b4a8007c076840f1aaef0251117dd232
|
||||
This section explains how to edit job information.
|
||||
|
||||
You can edit the alias and description of the job. KubeSphere does not support editing the name of an already created job.
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
// :ks_include_id: 3965f0c407e24d6dae5c945b45abbd6e
|
||||
This section explains how to manage jobs.
|
||||
|
||||
In KubeSphere, applications run in pods. Jobs are used to manage pods that run either once or periodically. KubeSphere supports the following types of jobs:
|
||||
|
||||
* Jobs: Used to manage pods that run only once. If a pod runs failed, the system will restart the pod according to the policies set in the job until specific conditions are met.
|
||||
|
||||
* CronJobs: Used to manage pods that run periodically. The system creates regular jobs based on the schedule set in the CronJob and runs them accordingly. Each time when the pod runs, if it fails, the CronJob will restart the pod according to the policies set by the user until specific conditions are met.
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
// :ks_include_id: a773823d564e4c93b67e89f11ac3bc64
|
||||
This section explains how to pause a CronJob.
|
||||
|
||||
After pausing a CronJob, the system will not create and run jobs at the scheduled time in the future. Running jobs are not affected. This operation is only available for CronJobs.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue