Oracle Cloud Infrastructure Documentation
Try Free Tier

Setting Up Storage for OpenShift Clusters

Find out how to define and apply persistent volume claims to clusters you created using OpenShift Container Platform on OCI. You can provision persistent volume claims by attaching volumes from the Block Volume service or by mounting file systems from the File Storage service.

Container storage using a container's root file system is ephemeral, and can disappear upon container deletion. To provide a durable location that prevents data from being lost, you can use persistent volumes to store data outside of containers.

A persistent volume offers storage that lets your data remain intact even if the containers to which the storage is connected are deleted. A persistent volume claim (PVC) is a request for storage, which is met by binding the PVC to a persistent volume. A PVC provides an abstraction layer to the underlying storage.

With Oracle Cloud Infrastructure (OCI), you can provision persistent volume claims:

  • By mounting file systems in the OCI File Storage service. The File Storage service file systems are mounted inside containers running on clusters using a CSI plugin deployed on the clusters. See Provisioning PVCs on the File Storage Service.

By default, Oracle encrypts customer data at rest in persistent storage. Oracle manages this default encryption with no action required on your part.

For more information about persistent volumes, persistent volume claims, and volume plugins, see the Kubernetes documentation.

Upgrading CSI and CCM Plugins

This section provides step-by-step instructions for upgrading CSI and Cloud Controller Manager (CCM) plugins on OpenShift clusters.

Prerequisites

To upgrade CSI and CCM plugins on OpenShift clusters, complete the following prerequisites:

  • OpenShift Access: Ensure you have OpenShift CLI (oc) access to the OpenShift cluster and sufficient privileges to manage plugin installations.
  • Backup Configurations: Back up any critical configurations and manifests, because upgrades can alter default settings.
  • Check Compatibility: Verify the compatibility of the plugin versions with the OpenShift version.

Updating Plugins

To update CSI and CCM plugins on OpenShift clusters, follow these steps:

  1. Retrieve the current plugin version by identifying the current version installed in the cluster.
  2. Find the required manifests in the Oracle Quick Start GitHub repository (oracle-quickstart / oci-openshift).
  3. Download the required manifests from the oci-ccm-csi-drivers directory.

    The directory is here: /custom_manifests/oci-ccm-csi-drivers/<version_number>. For example:/custom_manifests/oci-ccm-csi-drivers/v1.25.0.

  4. Apply the new manifests to replace the existing plugin configuration, as shown in the following example.

    oc apply -f custom-manifests/oci-ccm-csi-drivers/v1.xx/01-oci-ccm.yml
oc apply -f custom-manifests/oci-ccm-csi-drivers/v1.xx/01-oci-csi.yml

Verify Plugin Upgrades

To verify the CSI and CCM plugin upgrades on OpenShift clusters, follow these steps:

  1. Verify that the new plugin pods are running.
  2. For CSI, perform storage testing by validating Persistent Volumes (PV):
    1. Ensure that existing and new PVs are accessible.
    2. Attach test persistent volume claims (PVCs) to workloads and confirm proper functionality.
  3. For CCM, perform Cloud Integration Testing:
    1. Check for proper creation and management of load balancers and node IPs.
    2. Monitor the cloud-controller-manager logs for errors or warnings.

Was this article helpful?