@@ -62,102 +62,31 @@ a different volume.
62
62
63
63
Kubernetes supports several types of volumes.
64
64
65
- ### awsElasticBlockStore (deprecated ) {#awselasticblockstore}
65
+ ### awsElasticBlockStore (removed ) {#awselasticblockstore}
66
66
67
- {{< feature-state for_k8s_version="v1.17" state="deprecated" >}}
68
-
69
- An ` awsElasticBlockStore ` volume mounts an Amazon Web Services (AWS)
70
- [ EBS volume] ( https://aws.amazon.com/ebs/ ) into your pod. Unlike
71
- ` emptyDir ` , which is erased when a pod is removed, the contents of an EBS
72
- volume are persisted and the volume is unmounted. This means that an
73
- EBS volume can be pre-populated with data, and that data can be shared between pods.
74
-
75
- {{< note >}}
76
- You must create an EBS volume by using ` aws ec2 create-volume ` or the AWS API before you can use it.
77
- {{< /note >}}
78
-
79
- There are some restrictions when using an ` awsElasticBlockStore ` volume:
80
-
81
- * the nodes on which pods are running must be AWS EC2 instances
82
- * those instances need to be in the same region and availability zone as the EBS volume
83
- * EBS only supports a single EC2 instance mounting a volume
84
-
85
- #### Creating an AWS EBS volume
86
-
87
- Before you can use an EBS volume with a pod, you need to create it.
88
-
89
- ``` shell
90
- aws ec2 create-volume --availability-zone=eu-west-1a --size=10 --volume-type=gp2
91
- ```
92
-
93
- Make sure the zone matches the zone you brought up your cluster in. Check that the size and EBS volume
94
- type are suitable for your use.
95
-
96
- #### AWS EBS configuration example
97
-
98
- ``` yaml
99
- apiVersion : v1
100
- kind : Pod
101
- metadata :
102
- name : test-ebs
103
- spec :
104
- containers :
105
- - image : registry.k8s.io/test-webserver
106
- name : test-container
107
- volumeMounts :
108
- - mountPath : /test-ebs
109
- name : test-volume
110
- volumes :
111
- - name : test-volume
112
- # This AWS EBS volume must already exist.
113
- awsElasticBlockStore :
114
- volumeID : " <volume id>"
115
- fsType : ext4
116
- ` ` `
117
-
118
- If the EBS volume is partitioned, you can supply the optional field ` partition: "<partition number>"` to specify which partition to mount on.
119
-
120
- # ### AWS EBS CSI migration
121
-
122
- {{< feature-state for_k8s_version="v1.25" state="stable" >}}
123
-
124
- The `CSIMigration` feature for `awsElasticBlockStore`, when enabled, redirects
125
- all plugin operations from the existing in-tree plugin to the `ebs.csi.aws.com` Container
126
- Storage Interface (CSI) driver. In order to use this feature, the [AWS EBS CSI
127
- driver](https://github.com/kubernetes-sigs/aws-ebs-csi-driver)
128
- must be installed on the cluster.
129
-
130
- # ### AWS EBS CSI migration complete
131
-
132
- {{< feature-state for_k8s_version="v1.17" state="alpha" >}}
133
-
134
- To disable the `awsElasticBlockStore` storage plugin from being loaded by the controller manager
135
- and the kubelet, set the `InTreePluginAWSUnregister` flag to `true`.
136
-
137
- # ## azureDisk (deprecated) {#azuredisk}
67
+ <!-- maintenance note: OK to remove all mention of awsElasticBlockStore once the v1.27 release of
68
+ Kubernetes has gone out of support -->
138
69
139
- {{< feature-state for_k8s_version="v1.19" state="deprecated" >}}
70
+ Kubernetes {{< skew currentVersion >}} does not include a ` awsElasticBlockStore ` volume type.
140
71
141
- The `azureDisk` volume type mounts a Microsoft Azure [Data Disk](https://docs.microsoft.com/en-us/azure/aks/csi-storage-drivers) into a pod.
72
+ The AWSElasticBlockStore in-tree storage driver was deprecated in the Kubernetes v1.19 release
73
+ and then removed entirely in the v1.27 release.
142
74
143
- For more details, see the [`azureDisk` volume plugin](https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_disk/README.md).
75
+ The Kubernetes project suggests that you use the [ AWS EBS] ( https://github.com/kubernetes-sigs/aws-ebs-csi-driver ) third party
76
+ storage driver instead.
144
77
145
- # ### azureDisk CSI migration
78
+ ### azureDisk (removed) {#azuredisk}
146
79
147
- {{< feature-state for_k8s_version="v1.24" state="stable" >}}
80
+ <!-- maintenance note: OK to remove all mention of azureDisk once the v1.27 release of
81
+ Kubernetes has gone out of support -->
148
82
149
- The `CSIMigration` feature for `azureDisk`, when enabled, redirects all plugin operations
150
- from the existing in-tree plugin to the `disk.csi.azure.com` Container
151
- Storage Interface (CSI) Driver. In order to use this feature, the
152
- [Azure Disk CSI Driver](https://github.com/kubernetes-sigs/azuredisk-csi-driver)
153
- must be installed on the cluster.
83
+ Kubernetes {{< skew currentVersion >}} does not include a ` azureDisk ` volume type.
154
84
155
- # ### azureDisk CSI migration complete
85
+ The AzureDisk in-tree storage driver was deprecated in the Kubernetes v1.19 release
86
+ and then removed entirely in the v1.27 release.
156
87
157
- {{< feature-state for_k8s_version="v1.21" state="alpha" >}}
158
-
159
- To disable the `azureDisk` storage plugin from being loaded by the controller manager
160
- and the kubelet, set the `InTreePluginAzureDiskUnregister` flag to `true`.
88
+ The Kubernetes project suggests that you use the [ Azure Disk] ( https://github.com/kubernetes-sigs/azuredisk-csi-driver ) third party
89
+ storage driver instead.
161
90
162
91
### azureFile (deprecated) {#azurefile}
163
92
@@ -204,51 +133,19 @@ You must have your own Ceph server running with the share exported before you ca
204
133
205
134
See the [ CephFS example] ( https://github.com/kubernetes/examples/tree/master/volumes/cephfs/ ) for more details.
206
135
207
- # ## cinder (deprecated) {#cinder}
208
-
209
- {{< feature-state for_k8s_version="v1.18" state="deprecated" >}}
210
-
211
- {{< note >}}
212
- Kubernetes must be configured with the OpenStack cloud provider.
213
- {{< /note >}}
214
-
215
- The `cinder` volume type is used to mount the OpenStack Cinder volume into your pod.
216
-
217
- # ### Cinder volume configuration example
218
-
219
- ` ` ` yaml
220
- apiVersion: v1
221
- kind: Pod
222
- metadata:
223
- name: test-cinder
224
- spec:
225
- containers:
226
- - image: registry.k8s.io/test-webserver
227
- name: test-cinder-container
228
- volumeMounts:
229
- - mountPath: /test-cinder
230
- name: test-volume
231
- volumes:
232
- - name: test-volume
233
- # This OpenStack volume must already exist.
234
- cinder:
235
- volumeID: "<volume id>"
236
- fsType: ext4
237
- ` ` `
136
+ ### cinder (removed) {#cinder}
238
137
239
- # ### OpenStack CSI migration
138
+ <!-- maintenance note: OK to remove all mention of cinder once the v1.26 release of
139
+ Kubernetes has gone out of support -->
240
140
241
- {{< feature-state for_k8s_version="v1.24" state="stable" >}}
141
+ Kubernetes {{< skew currentVersion >}} does not include a ` cinder ` volume type.
242
142
243
- The `CSIMigration` feature for Cinder is enabled by default since Kubernetes 1.21.
244
- It redirects all plugin operations from the existing in-tree plugin to the
245
- ` cinder.csi.openstack.org` Container Storage Interface (CSI) Driver.
246
- [OpenStack Cinder CSI Driver](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md)
247
- must be installed on the cluster.
143
+ The OpenStack Cinder in-tree storage driver was deprecated in the Kubernetes v1.11 release
144
+ and then removed entirely in the v1.26 release.
248
145
249
- To disable the in-tree Cinder plugin from being loaded by the controller manager
250
- and the kubelet, you can enable the `InTreePluginOpenStackUnregister`
251
- [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) .
146
+ The Kubernetes project suggests that you use the
147
+ [ OpenStack Cinder ] ( https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md )
148
+ third party storage driver instead .
252
149
253
150
### configMap
254
151
@@ -1245,8 +1142,6 @@ are listed in [Types of Volumes](#volume-types).
1245
1142
1246
1143
The following in-tree plugins support persistent storage on Windows nodes :
1247
1144
1248
- * [`awsElasticBlockStore`](#awselasticblockstore)
1249
- * [`azureDisk`](#azuredisk)
1250
1145
* [`azureFile`](#azurefile)
1251
1146
* [`gcePersistentDisk`](#gcepersistentdisk)
1252
1147
* [`vsphereVolume`](#vspherevolume)
0 commit comments