@@ -117,184 +117,69 @@ Kubernetes supports several types of volumes.
117
117
Kubernetes 支持下列类型的卷:
118
118
119
119
<!--
120
- ### awsElasticBlockStore (deprecated) {#awselasticblockstore}
121
-
122
- An `awsElasticBlockStore` volume mounts an Amazon Web Services (AWS)
123
- [EBS volume](https://aws.amazon.com/ebs/) into your pod. Unlike
124
- `emptyDir`, which is erased when a pod is removed, the contents of an EBS
125
- volume are persisted and the volume is unmounted. This means that an
126
- EBS volume can be pre-populated with data, and that data can be shared between pods.
127
- -->
128
- ### awsElasticBlockStore (已弃用) {#awselasticblockstore}
129
-
130
- {{< feature-state for_k8s_version="v1.17" state="deprecated" >}}
131
-
132
- ` awsElasticBlockStore ` 卷将 Amazon Web 服务(AWS)[ EBS 卷] ( https://aws.amazon.com/ebs/ ) 挂载到你的
133
- Pod 中。` emptyDir ` 在 Pod 被删除时也会一起被删除,但 EBS 卷的内容在删除
134
- Pod 时会被保留,卷只是被卸载掉了。
135
- 这意味着 EBS 卷可以预先填充数据,并且该数据可以在 Pod 之间共享。
136
-
137
- {{< note >}}
138
- <!--
139
- You must create an EBS volume by using `aws ec2 create-volume` or the AWS API before you can use it.
120
+ ### awsElasticBlockStore (removed) {#awselasticblockstore}
140
121
-->
141
- 你在使用 EBS 卷之前必须使用 ` aws ec2 create-volume ` 命令或者 AWS API 创建该卷。
142
- {{< /note >}}
143
-
144
- <!--
145
- There are some restrictions when using an `awsElasticBlockStore` volume:
146
-
147
- * the nodes on which pods are running must be AWS EC2 instances
148
- * those instances need to be in the same region and availability zone as the EBS volume
149
- * EBS only supports a single
150
- -->
151
- 使用 ` awsElasticBlockStore ` 卷时有一些限制:
152
-
153
- * Pod 运行所在的节点必须是 AWS EC2 实例。
154
- * 这些实例需要与 EBS 卷在相同的地域(Region)和可用区(Availability-Zone)。
155
- * EBS 卷只支持被挂载到单个 EC2 实例上。
156
-
157
- <!--
158
- #### Creating an AWS EBS volume
122
+ ### awsElasticBlockStore (已移除) {#awselasticblockstore}
159
123
160
- Before you can use an EBS volume with a pod, you need to create it.
161
- -->
162
- #### 创建 AWS EBS 卷
163
-
164
- 在将 EBS 卷用到 Pod 上之前,你首先要创建它。
165
-
166
- ``` shell
167
- aws ec2 create-volume --availability-zone=eu-west-1a --size=10 --volume-type=gp2
168
- ```
169
-
170
- <!--
171
- Make sure the zone matches the zone you brought up your cluster in. Check that the size and EBS volume
172
- type are suitable for your use.
173
- -->
174
- 确保该区域与你的集群所在的区域相匹配。还要检查卷的大小和 EBS 卷类型都适合你的用途。
124
+ <!-- maintenance note: OK to remove all mention of awsElasticBlockStore once the v1.27 release of
125
+ Kubernetes has gone out of support -->
175
126
176
127
<!--
177
- #### AWS EBS configuration example
178
- -->
179
- #### AWS EBS 配置示例
128
+ Kubernetes {{< skew currentVersion >}} does not include a `awsElasticBlockStore` volume type.
180
129
181
- ``` yaml
182
- apiVersion : v1
183
- kind : Pod
184
- metadata :
185
- name : test-ebs
186
- spec :
187
- containers :
188
- - image : registry.k8s.io/test-webserver
189
- name : test-container
190
- volumeMounts :
191
- - mountPath : /test-ebs
192
- name : test-volume
193
- volumes :
194
- - name : test-volume
195
- # 此 AWS EBS 卷必须已经存在
196
- awsElasticBlockStore :
197
- volumeID : " <volume id>"
198
- fsType : ext4
199
- ` ` `
200
- <!--
201
- If the EBS volume is partitioned, you can supply the optional field ` partition: "<partition number>"` to specify which partition to mount on.
202
- -->
203
- 如果 EBS 卷是分区的,你可以提供可选的字段 `partition : " <partition number>" ` 来指定要挂载到哪个分区上。
130
+ The AWSElasticBlockStore in-tree storage driver was deprecated in the Kubernetes v1.19 release
131
+ and then removed entirely in the v1.27 release.
204
132
205
- <!--
206
- #### AWS EBS CSI migration
133
+ The Kubernetes project suggests that you use the [AWS EBS](https://github.com/kubernetes-sigs/aws-ebs-csi-driver) third party
134
+ storage driver instead.
207
135
-->
208
- #### AWS EBS CSI 卷迁移
136
+ Kubernetes {{< skew currentVersion >}} 不包含 ` awsElasticBlockStore ` 卷类型。
209
137
210
- {{< feature-state for_k8s_version="v1.25" state="stable" >}}
138
+ AWSElasticBlockStore 树内存储驱动已在 Kubernetes v1.19 版本中废弃,
139
+ 并在 v1.27 版本中被完全移除。
211
140
212
- <!--
213
- The ` CSIMigration` feature for `awsElasticBlockStore`, when enabled, redirects
214
- all plugin operations from the existing in-tree plugin to the `ebs.csi.aws.com` Container
215
- Storage Interface (CSI) driver. In order to use this feature, the [AWS EBS CSI
216
- driver](https://github.com/kubernetes-sigs/aws-ebs-csi-driver)
217
- must be installed on the cluster.
218
- -->
219
- 启用 `awsElasticBlockStore` 的 `CSIMigration` 特性后,所有插件操作将从现有的树内插件重定向到
220
- ` ebs.csi.aws.com` 容器存储接口(CSI)驱动程序。
221
- 为了使用此特性,必须在集群中安装
222
- [AWS EBS CSI 驱动](https://github.com/kubernetes-sigs/aws-ebs-csi-driver)。
141
+ Kubernetes 项目建议你转为使用 [ AWS EBS] ( https://github.com/kubernetes-sigs/aws-ebs-csi-driver )
142
+ 第三方存储驱动。
223
143
224
144
<!--
225
- # ### AWS EBS CSI migration complete
145
+ ### azureDisk (removed) {#azuredisk}
226
146
-->
227
- # ### AWS EBS CSI 迁移结束
147
+ ### azureDisk (已移除) {#azuredisk}
228
148
229
- {{< feature-state for_k8s_version="v1.17" state="alpha" >}}
230
-
231
- <!--
232
- To disable the `awsElasticBlockStore` storage plugin from being loaded by the controller manager
233
- and the kubelet, set the `InTreePluginAWSUnregister` flag to `true`.
234
- -->
235
- 要禁止控制器管理器和 kubelet 加载 `awsElasticBlockStore` 存储插件,
236
- 请将 `InTreePluginAWSUnregister` 标志设置为 `true`。
149
+ <!-- maintenance note: OK to remove all mention of azureDisk once the v1.27 release of
150
+ Kubernetes has gone out of support -->
237
151
238
152
<!--
239
- # ## azureDisk (deprecated) {#azuredisk}
153
+ Kubernetes {{< skew currentVersion >}} does not include a `azureDisk` volume type.
240
154
241
- The `azureDisk` volume type mounts a Microsoft Azure [Data Disk](https://docs.microsoft.com/en-us/azure/aks/csi-storage-drivers) into a pod.
155
+ The AzureDisk in-tree storage driver was deprecated in the Kubernetes v1.19 release
156
+ and then removed entirely in the v1.27 release.
242
157
243
- For more details, see the [`azureDisk` volume plugin](https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_disk/README.md).
158
+ The Kubernetes project suggests that you use the [Azure Disk](https://github.com/kubernetes-sigs/azuredisk-csi-driver) third party
159
+ storage driver instead.
244
160
-->
245
- # ## azureDisk (已弃用) {#azuredisk}
161
+ Kubernetes {{< skew currentVersion >}} 不包含 ` azureDisk ` 卷类型。
246
162
247
- {{< feature-state for_k8s_version="v1.19" state="deprecated" >}}
248
-
249
- ` azureDisk` 卷类型用来在 Pod 上挂载 Microsoft Azure
250
- [数据盘(Data Disk)](https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-about-disks-vhds/) 。
251
- 若需了解更多详情,请参考 [`azureDisk` 卷插件](https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_disk/README.md)。
252
-
253
- <!--
254
- # ### azureDisk CSI migration
255
- -->
256
- # ### azureDisk 的 CSI 迁移 {#azuredisk-csi-migration}
163
+ AzureDisk 树内存储驱动已在 Kubernetes v1.19 版本中废弃,并在 v1.27 版本中被完全移除。
257
164
258
- {{< feature-state for_k8s_version="v1.24" state="stable" >}}
165
+ Kubernetes 项目建议你转为使用 [ Azure Disk] ( https://github.com/kubernetes-sigs/azuredisk-csi-driver )
166
+ 第三方存储驱动。
259
167
260
168
<!--
261
- The `CSIMigration` feature for `azureDisk`, when enabled, redirects all plugin operations
262
- from the existing in-tree plugin to the `disk.csi.azure.com` Container
263
- Storage Interface (CSI) Driver. In order to use this feature, the
264
- [Azure Disk CSI Driver](https://github.com/kubernetes-sigs/azuredisk-csi-driver)
265
- must be installed on the cluster.
266
- -->
267
- 启用 `azureDisk` 的 `CSIMigration` 特性后,所有插件操作从现有的树内插件重定向到
268
- ` disk.csi.azure.com` 容器存储接口(CSI)驱动程序。
269
- 为了使用此特性,必须在集群中安装
270
- [Azure 磁盘 CSI 驱动程序](https://github.com/kubernetes-sigs/azuredisk-csi-driver)。
271
-
272
- <!--
273
- # ### azureDisk CSI migration complete
274
-
275
- To disable the `azureDisk` storage plugin from being loaded by the controller manager
276
- and the kubelet, set the `InTreePluginAzureDiskUnregister` flag to `true`.
169
+ ### azureFile (deprecated) {#azurefile}
277
170
-->
278
- # ### azureDisk CSI 迁移完成
279
-
280
- {{< feature-state for_k8s_version="v1.21" state="alpha" >}}
171
+ ### azureFile (已弃用) {#azurefile}
281
172
282
- 要禁止控制器管理器和 kubelet 加载 `azureDisk` 存储插件,
283
- 请将 `InTreePluginAzureDiskUnregister` 标志设置为 `true`。
173
+ {{< feature-state for_k8s_version="v1.21" state="deprecated" >}}
284
174
285
175
<!--
286
- # ## azureFile (deprecated) {#azurefile}
287
-
288
176
The `azureFile` volume type mounts a Microsoft Azure File volume (SMB 2.1 and 3.0)
289
177
into a pod.
290
178
291
179
For more details, see the [`azureFile` volume plugin](https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_file/README.md).
292
180
-->
293
- # ## azureFile (已弃用) {#azurefile}
294
-
295
- {{< feature-state for_k8s_version="v1.21" state="deprecated" >}}
296
-
297
181
` azureFile ` 卷类型用来在 Pod 上挂载 Microsoft Azure 文件卷(File Volume)(SMB 2.1 和 3.0)。
182
+
298
183
更多详情请参考 [ ` azureFile ` 卷插件] ( https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_file/README.md ) 。
299
184
300
185
<!--
@@ -328,19 +213,30 @@ Azure 文件 CSI 驱动尚不支持为同一卷设置不同的 fsgroup。
328
213
329
214
<!--
330
215
#### azureFile CSI migration complete
331
-
332
- To disable the `azureFile` storage plugin from being loaded by the controller manager
333
- and the kubelet, set the `InTreePluginAzureFileUnregister` flag to `true`.
334
216
-->
335
217
#### azureFile CSI 迁移完成
336
218
337
219
{{< feature-state for_k8s_version="v1.21" state="alpha" >}}
338
220
221
+ <!--
222
+ To disable the `azureFile` storage plugin from being loaded by the controller manager
223
+ and the kubelet, set the `InTreePluginAzureFileUnregister` flag to `true`.
224
+ -->
339
225
要禁止控制器管理器和 kubelet 加载 ` azureFile ` 存储插件,
340
226
请将 ` InTreePluginAzureFileUnregister ` 标志设置为 ` true ` 。
341
227
342
228
### cephfs {#cephfs}
343
229
230
+ {{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
231
+
232
+ {{< note >}}
233
+ <!--
234
+ The Kubernetes project suggests that you use the [CephFS CSI](https://github.com/ceph/ceph-csi) third party
235
+ storage driver instead.
236
+ -->
237
+ Kubernetes 项目建议你转为使用 [ CephFS CSI] ( https://github.com/ceph/ceph-csi ) 第三方存储驱动。
238
+ {{< /note >}}
239
+
344
240
<!--
345
241
A `cephfs` volume allows an existing CephFS volume to be
346
242
mounted into your Pod. Unlike `emptyDir`, which is erased when a pod is
@@ -368,79 +264,31 @@ See the [CephFS example](https://github.com/kubernetes/examples/tree/master/volu
368
264
更多信息请参考 [ CephFS 示例] ( https://github.com/kubernetes/examples/tree/master/volumes/cephfs/ ) 。
369
265
370
266
<!--
371
- # ## cinder (deprecated ) {#cinder}
267
+ ### cinder (removed ) {#cinder}
372
268
-->
373
- # ## cinder (已弃用) {#cinder}
374
-
375
- {{< feature-state for_k8s_version="v1.18" state="deprecated" >}}
269
+ ### cinder(已移除) {#cinder}
376
270
377
- {{< note >}}
378
- <!--
379
- Kubernetes must be configured with the OpenStack cloud provider.
380
- -->
381
- Kubernetes 必须配置了 OpenStack Cloud Provider。
382
- {{< /note >}}
383
-
384
- <!--
385
- The `cinder` volume type is used to mount the OpenStack Cinder volume into your pod.
386
- -->
387
- ` cinder` 卷类型用于将 OpenStack Cinder 卷挂载到 Pod 中。
271
+ <!-- maintenance note: OK to remove all mention of cinder once the v1.26 release of
272
+ Kubernetes has gone out of support -->
388
273
389
274
<!--
390
- # ### Cinder volume configuration example
391
- -->
392
- # ### Cinder 卷示例配置 {#cinder-volume-example-configuration}
275
+ Kubernetes {{< skew currentVersion >}} does not include a `cinder` volume type.
393
276
394
- ` ` ` yaml
395
- apiVersion: v1
396
- kind: Pod
397
- metadata:
398
- name: test-cinder
399
- spec:
400
- containers:
401
- - image: registry.k8s.io/test-webserver
402
- name: test-cinder-container
403
- volumeMounts:
404
- - mountPath: /test-cinder
405
- name: test-volume
406
- volumes:
407
- - name: test-volume
408
- # 此 OpenStack 卷必须已经存在
409
- cinder:
410
- volumeID: "<volume id>"
411
- fsType: ext4
412
- ` ` `
277
+ The OpenStack Cinder in-tree storage driver was deprecated in the Kubernetes v1.11 release
278
+ and then removed entirely in the v1.26 release.
413
279
414
- <!--
415
- # ### OpenStack CSI migration
280
+ The Kubernetes project suggests that you use the
281
+ [OpenStack Cinder](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md)
282
+ third party storage driver instead.
416
283
-->
417
- # ### OpenStack CSI 迁移
284
+ Kubernetes {{< skew currentVersion >}} 不包含 ` cinder ` 卷类型。
418
285
419
- {{< feature-state for_k8s_version="v1.24" state="stable" >}}
286
+ OpenStack Cinder 树内存储驱动已在 Kubernetes v1.11 版本中废弃,
287
+ 并在 v1.26 版本中被完全移除。
420
288
421
- <!--
422
- The `CSIMigration` feature for Cinder is enabled by default since Kubernetes 1.21.
423
- It redirects all plugin operations from the existing in-tree plugin to the
424
- ` cinder.csi.openstack.org` Container Storage Interface (CSI) Driver.
425
- [OpenStack Cinder CSI Driver](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md)
426
- must be installed on the cluster.
427
- -->
428
- 自 Kubernetes 1.21 版本起,Cinder 的 `CSIMigration` 特性是默认被启用的。
429
- 此特性会将插件的所有操作从现有的树内插件重定向到
430
- ` cinder.csi.openstack.org` 容器存储接口(CSI)驱动程序。
431
- 为了使用此特性,必须在集群中安装
432
- [OpenStack Cinder CSI 驱动程序](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md),
433
- 你可以通过设置 `CSIMigrationOpenStack`
434
- [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)
435
- 为 `false` 来禁止 Cinder CSI 迁移。
436
-
437
- <!--
438
- To disable the in-tree Cinder plugin from being loaded by the controller manager
439
- and the kubelet, you can enable the `InTreePluginOpenStackUnregister`
440
- [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
441
- -->
442
- 要禁止控制器管理器和 kubelet 加载树内 Cinder 插件,你可以启用
443
- ` InTreePluginOpenStackUnregister` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
289
+ Kubernetes 项目建议你转为使用
290
+ [ OpenStack Cinder] ( https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md )
291
+ 第三方存储驱动。
444
292
445
293
### configMap
446
294
@@ -1411,6 +1259,16 @@ directory. For more details, see [projected volumes](/docs/concepts/storage/proj
1411
1259
1412
1260
# ## rbd
1413
1261
1262
+ {{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
1263
+
1264
+ {{< note >}}
1265
+ <!--
1266
+ The Kubernetes project suggests that you use the [Ceph CSI](https://github.com/ceph/ceph-csi)
1267
+ third party storage driver instead, in RBD mode.
1268
+ -->
1269
+ Kubernetes 项目建议你转为以 RBD 模式使用 [Ceph CSI](https://github.com/ceph/ceph-csi) 第三方存储驱动。
1270
+ {{< /note >}}
1271
+
1414
1272
<!--
1415
1273
An `rbd` volume allows a
1416
1274
[Rados Block Device](https://docs.ceph.com/en/latest/rbd/) (RBD) volume to mount
@@ -1452,7 +1310,7 @@ RBD 的一个特性是它可以同时被多个用户以只读方式挂载。
1452
1310
-->
1453
1311
# ### RBD CSI 迁移 {#rbd-csi-migration}
1454
1312
1455
- {{< feature-state for_k8s_version="v1.23 " state="alpha " >}}
1313
+ {{< feature-state for_k8s_version="v1.28 " state="deprecated " >}}
1456
1314
1457
1315
<!--
1458
1316
The `CSIMigration` feature for `RBD`, when enabled, redirects all plugin
@@ -1541,9 +1399,11 @@ For more details, see [Configuring Secrets](/docs/concepts/configuration/secret/
1541
1399
1542
1400
{{< note >}}
1543
1401
<!--
1544
- We recommend to use vSphere CSI out-of-tree driver instead.
1402
+ The Kubernetes project recommends using the [vSphere CSI](https://github.com/kubernetes-sigs/vsphere-csi-driver)
1403
+ out-of-tree storage driver instead.
1545
1404
-->
1546
- 建议你改用 vSphere CSI 树外驱动程序。
1405
+ Kubernetes 项目建议转为使用 [vSphere CSI](https://github.com/kubernetes-sigs/vsphere-csi-driver)
1406
+ 树外存储驱动。
1547
1407
{{< /note >}}
1548
1408
1549
1409
<!--
@@ -2094,8 +1954,6 @@ The following in-tree plugins support persistent storage on Windows nodes:
2094
1954
2095
1955
下面是支持 Windows 节点上持久性存储的树内插件:
2096
1956
2097
- * [`awsElasticBlockStore`](#awselasticblockstore)
2098
- * [`azureDisk`](#azuredisk)
2099
1957
* [`azureFile`](#azurefile)
2100
1958
* [`gcePersistentDisk`](#gcepersistentdisk)
2101
1959
* [`vsphereVolume`](#vspherevolume)
0 commit comments