oci-csi-driver Partner Validated

Use a PVC in pod definitions to mount persistent storage inside a container using persistentVolumeClaim.claimName. Attach volumes at custom paths using volumeMounts.mountPath in the pod spec, enabling seamless data persistence across pod restarts.

Configure StorageClass for OCI block volumes using the CSI plugin (blockvolume.csi.oraclecloud.com). Define performance levels, encryption keys (kms-key-id), and attachment type (iscsi or paravirtualized) to match workload and security needs.

Create a Kubernetes PVC from an existing OCI block volume or volume backup using the volume.beta.kubernetes.io/oci-volume-source annotation. Specify the OCID of the backup to dynamically provision a persistent volume, optionally targeting a specific availability domain using topology.kubernetes.io/zone.

Encrypt data transferred between compute instances and block volumes. Paravirtualized attachments support optional encryption enabled per node pool (isPvEncryptionInTransitEnabled), while some bare metal shapes support in-transit encryption for iSCSI volumes.

OCI block volumes offer configurable performance levels (Volume Performance Units, VPUs): Lower Cost (0), Balanced (10, default), Higher Performance (20), and Ultra High Performance (30–120). Set via StorageClass; performance cannot be altered after volume creation.

Choose from ext3, ext4, and XFS file systems for OCI block volumes. ext3 offers reliable journaling, ext4 adds performance and scalability features, and XFS delivers high throughput for large-scale, multi-threaded, and high-bandwidth applications.