Skip to content

Commit f8372e2

Browse files
authored
Merge pull request #48209 from my-git9/pp-23181
[zh-cn]sync csi-node-v1.md
2 parents daef9cb + e53f9df commit f8372e2

File tree

1 file changed

+10
-2
lines changed
  • content/zh-cn/docs/reference/kubernetes-api/config-and-storage-resources

1 file changed

+10
-2
lines changed

content/zh-cn/docs/reference/kubernetes-api/config-and-storage-resources/csi-node-v1.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ api_metadata:
66
content_type: "api_reference"
77
description: "CSINode 包含节点上安装的所有 CSI 驱动有关的信息。"
88
title: "CSINode"
9-
weight: 9
9+
weight: 4
1010
---
1111
<!--
1212
api_metadata:
@@ -16,7 +16,7 @@ api_metadata:
1616
content_type: "api_reference"
1717
description: "CSINode holds information about all CSI drivers installed on a node."
1818
title: "CSINode"
19-
weight: 9
19+
weight: 4
2020
-->
2121

2222
`apiVersion: storage.k8s.io/v1`
@@ -68,6 +68,8 @@ CSINodeSpec 包含一个节点上安装的所有 CSI 驱动规约有关的信息
6868
6969
*Patch strategy: merge on key `name`*
7070
71+
*Map: unique values on key name will be kept during a merge*
72+
7173
drivers is a list of information of all CSI Drivers existing on a node. If all drivers in the list are uninstalled, this can become empty.
7274
7375
<a name="CSINodeDriver"></a>
@@ -81,6 +83,8 @@ CSINodeSpec 包含一个节点上安装的所有 CSI 驱动规约有关的信息
8183

8284
**补丁策略:按照键 `name` 合并**
8385

86+
**映射:键 `name` 的唯一值将在合并过程中保留**
87+
8488
drivers 是节点上存在的所有 CSI 驱动的信息列表。如果列表中的所有驱动均被卸载,则此字段可以为空。
8589

8690
<a name="CSINodeDriver"></a>
@@ -136,11 +140,15 @@ CSINodeSpec 包含一个节点上安装的所有 CSI 驱动规约有关的信息
136140
<!--
137141
- **drivers.topologyKeys** ([]string)
138142
143+
*Atomic: will be replaced during a merge*
144+
139145
topologyKeys is the list of keys supported by the driver. When a driver is initialized on a cluster, it provides a set of topology keys that it understands (e.g. "company.com/zone", "company.com/region"). When a driver is initialized on a node, it provides the same topology keys along with values. Kubelet will expose these topology keys as labels on its own node object. When Kubernetes does topology aware provisioning, it can use this list to determine which labels it should retrieve from the node object and pass back to the driver. It is possible for different nodes to use different topology keys. This can be empty if driver does not support topology.
140146
-->
141147

142148
- **drivers.topologyKeys** ([]string)
143149

150+
**原子性:合并期间将被替换**
151+
144152
topologyKeys 是驱动支持的键的列表。
145153
在集群上初始化一个驱动时,该驱动将提供一组自己理解的拓扑键
146154
(例如 “company.com/zone”、“company.com/region”)。

0 commit comments

Comments
 (0)