Merge pull request #3900 from windsonsea/kant

update kant/intro/concepts

docs/en/docs/kant/intro/concepts.md

@@ -1,47 +1,70 @@
-# Basic Concepts
+---
+MTPE: windsonsea
+date: 2024-02-23
+---
 
-- Edge Unit
+# Concepts
 
-    Refers to the collection of computing resources required for container operation, including the cloud-based Master and edge-side working Node.
-    The Edge Unit is the same concept as the cluster in K8S, but the networking method is different. The Master node is deployed on the cloud, and one cloud-based Master (with multiple backups) corresponds to an edge cluster.
+- **Edge Unit**
 
-- Edge Node
+    Refers to the collection of computing resources required for container operation, including the cloud-based
+    Master and edge-side working Node. The Edge Unit is the same concept as the cluster in K8S, but the
+    networking method is different. The Master node is deployed on the cloud, and one cloud-based Master
+    (with multiple backups) corresponds to an edge cluster.
 
-    It is the basic element of a container cluster, which can be a cloud host or a physical machine used as a carrier for running containerized applications. The edge application will run on the node in the form of a Pod.
+- **Edge Node**
 
-- Batch Registered Nodes
+    It is the basic element of a container cluster, which can be a cloud host or a physical machine used as
+    a carrier for running containerized applications. The edge application will run on the node in the form of a Pod.
 
-    The same type of edge nodes can be pre-installed with software and automatically added to the platform after the nodes are booted and connected to the network.
-    Batch registered nodes have a one-to-many relationship with edge nodes, improving management efficiency and saving operation and maintenance costs.
+- **Batch Registered Nodes**
 
-- Edge Node Group
+    The same type of edge nodes can be pre-installed with software and automatically added to the platform after
+    the nodes are booted and connected to the network. Batch registered nodes have a one-to-many relationship
+    with edge nodes, improving management efficiency and saving operation and maintenance costs.
 
-    It abstracts nodes according to specific attributes into a node group concept to uniformly manage and operate nodes in different edge regions by node group dimensions.
+- **Edge Node Group**
 
-- End Device
+    It abstracts nodes according to specific attributes into a node group concept to uniformly manage and operate
+    nodes in different edge regions by node group dimensions.
 
-    An end device can be as small as a sensor or controller, or as large as a smart camera or industrial control machine. End device can be connected to edge nodes, support access through Modbus protocol, and be managed uniformly.
+- **End Device**
 
-- Workload
+    An end device can be as small as a sensor or controller, or as large as a smart camera or industrial control
+    machine. End devices can be connected to edge nodes, support access through the Modbus protocol, and be
+    managed uniformly.
 
-    It is an API object that manages application replicas. Specifically, it is a Pod without local state. These Pods are completely independent and have the same function. They can be updated in a rolling manner, and the number of instances can be flexibly expanded or reduced.
+- **Workload**
 
-- Batch Deployment
+    It is an API object that manages application replicas. Specifically, it is a Pod without local state.
+    These Pods are completely independent and have the same function. They can be updated in a rolling manner,
+    and the number of instances can be flexibly expanded or reduced.
 
-    Defining and deploying stateless workloads with the same configuration or small differences to a node group is a task or batch deployment action.
+- **Batch Deployment**
 
-- ConfigMap
+    Defining and deploying stateless workloads with the same configuration or small differences to a node group
+    is a task or batch deployment action.
 
-    It is non-sensitive configuration information saved in the form of key/value pairs. Pods can use it as configuration files in environment variables, command line parameters, or data volumes.
+- **ConfigMap**
 
-- Secret
+    It is non-sensitive configuration information saved in the form of key/value pairs. Pods can use it as
+    configuration files in environment variables, command line parameters, or data volumes.
 
-    It is an object that contains a small amount of sensitive information such as passwords, tokens, and keys saved in the form of key/value pairs. Decouple sensitive information from container images, and do not include confidential data in application code.
+- **Secret**
 
-- Rule Endpoint
+    It is an object that contains a small amount of sensitive information such as passwords, tokens, and keys
+    saved in the form of key/value pairs. Decouple sensitive information from container images, and do not
+    include confidential data in application code.
 
-    A regular endpoint for sending or receiving messages. It has three types: rest, eventbus, servicebus.
+- **Rule Endpoint**
 
-- Message Routing
+    This is a regular endpoint for sending or receiving messages. It has three types: rest, eventbus, servicebus.
 
-    Define how messages are delivered from the source message endpoint to the target message endpoint.
+- **Message Routing**
+
+    Defines how messages are delivered from the source message endpoint to the target message endpoint.
+
+- **Application Mesh**
+
+    Provides a non-intrusive microservice governance solution, achieving complete lifecycle management
+    and traffic governance, supporting various governance capabilities such as load balancing.

docs/zh/docs/kant/intro/concepts.md

@@ -1,47 +1,52 @@
 # 基本概念
 
-- 边缘单元
+- **边缘单元**
 
     指容器运行所需计算资源的集合，包括云端 Master 和边端工作节点 Node。
-    边缘单元跟 K8S 中的集群是同一概念，但组网方式有所不同，Master 节点部署在云端，一个云端 master (主备多台)对应一个边缘集群。
+    边缘单元跟 K8s 中的集群是同一概念，但组网方式有所不同。
+    Master 节点部署在云端，一个云端 master (主备多台)对应一个边缘集群。
 
-- 边缘节点
+- **边缘节点**
 
-    是容器集群组成的基本元素，既可以是云主机，也可以是物理机，用于运行容器化应用的载体，边缘应用将以 Pod 的形式在节点上运行。
+    这是容器集群组成的基本元素，既可以是云主机，也可以是物理机，用于运行容器化应用的载体，边缘应用将以 Pod 的形式在节点上运行。
 
-- 批量注册节点
+- **批量注册节点**
 
     相同类型的边缘节点能够预安装软件，在节点开机联网后能自动纳管到平台中。
     批量注册节点与边缘节点满足一对多的关系，提高管理效率，也节约了运维成本。
 
-- 边缘节点组
+- **边缘节点组**
 
     将节点按照特定属性抽象成节点组概念，以节点组的维度对不同边缘区域下的节点进行统一管理和运维。
 
-- 终端设备
+- **终端设备**
 
     终端设备可以小到传感器、控制器，大到智能摄像机或工控机床；终端设备可以连接到边缘节点，支持通过 Modbus 协议接入并进行统一管理。
 
-- 工作负载
+- **工作负载**
 
     是管理应用副本的一种 API 对象，具体表现为没有本地状态的 Pod，这些 Pod 之间完全独立、功能相同，能够滚动更新，其实例的数量可以灵活扩缩。
 
-- 批量工作负载
+- **批量工作负载**
 
     将相同配置或差异化较小的工作负载定义部署到节点组，是一个任务或批量部署动作。
 
-- 配置项
+- **配置项**
 
     是以键/值对形式保存的非机密性配置信息，Pod 可以将其用作环境变量、命令行参数或者数据卷中的配置文件。
 
-- 密钥
+- **密钥**
 
     是以键/值对形式保存的、包含密码、令牌、密钥等少量敏感信息的对象，将敏感信息和容器镜像解耦，不需要在应用程序代码中包含机密数据。
 
-- 消息端点
+- **消息端点**
 
     发送或接收消息的规则端点。它包含3种类型：rest、eventbus、servicebus。
 
-- 消息路由
+- **消息路由**
 
     定义如何将消息从源消息端点传送到目标消息端点
+
+- **应用网格**
+
+    提供非侵入式的微服务治理解决方案，实现完整的生命周期管理和流量治理，支持负载均衡等多种治理能力。