OKD supports AWS Elastic Block Store volumes (EBS). You can provision your OKD cluster with persistent storage by using Amazon EC2. Some familiarity with Kubernetes and AWS is assumed.
The Kubernetes persistent volume framework allows administrators to provision a cluster with persistent storage and gives users a way to request those resources without having any knowledge of the underlying infrastructure. AWS Elastic Block Store volumes can be provisioned dynamically. Persistent volumes are not bound to a single project or namespace; they can be shared across the OKD cluster. Persistent volume claims are specific to a project or namespace and can be requested by users.
OKD defaults to using an in-tree (non-CSI) plug-in to provision AWS EBS storage.
In future OKD versions, volumes provisioned using existing in-tree plug-ins are planned for migration to their equivalent CSI driver. CSI automatic migration should be seamless. Migration does not change how you use all existing API objects, such as persistent volumes, persistent volume claims, and storage classes. For more information about migration, see CSI automatic migration.
After full migration, in-tree plug-ins will eventually be removed in future versions of OKD.
High-availability of storage in the infrastructure is left to the underlying storage provider.
For OKD, automatic migration from AWS EBS in-tree to the Container Storage Interface (CSI) driver is available as a Technology Preview (TP) feature. With migration enabled, volumes provisioned using the existing in-tree driver are automatically migrated to use the AWS EBS CSI driver. For more information, see CSI automatic migration feature.
Storage classes are used to differentiate and delineate storage levels and usages. By defining a storage class, users can obtain dynamically provisioned persistent volumes.
In the OKD console, click Storage → Storage Classes.
On the StorageClasses overview page, click Create Storage Class.
On the StorageClasses create page, enter values as desired:
Enter a name to reference the storage class.
Enter an optional description.
Select the reclaim policy.
kubernetes.io/aws-ebs from the Provisioner drop-down list.
To create the storage class with the equivalent CSI driver, select
Enter additional parameters for the storage class as desired.
Storage must exist in the underlying infrastructure before it can be mounted as a volume in OKD.
In the OKD console, click Storage → Persistent Volume Claims.
In the persistent volume claims overview, click Create Persistent Volume Claim.
Define the desired options on the page that appears.
Select the storage class created previously from the drop-down menu.
Enter a unique name for the storage claim.
Select the access mode. This determines the read and write access for the created storage claim.
Define the size of the storage claim.
Click Create to create the persistent volume claim and generate a persistent volume.
Before OKD mounts the volume and passes it to a container, it
checks that it contains a file system as specified by the
parameter in the persistent volume definition. If the device is not
formatted with the file system, all data from the device is erased and the
device is automatically formatted with the given file system.
This allows using unformatted AWS volumes as persistent volumes, because OKD formats them before the first use.
By default, OKD supports a maximum of 39 EBS volumes attached to one node. This limit is consistent with the AWS volume limits. The volume limit depends on the instance type.
As a cluster administrator, you must use either in-tree or Container Storage Interface (CSI) volumes and their respective storage classes, but never both volume types at the same time. The maximum attached EBS volume number is counted separately for in-tree and CSI volumes.
See AWS Elastic Block Store CSI Driver Operator for information about accessing additional storage options, such as volume snapshots, that are not possible with in-tree volume plug-ins.