Validated storage options

This topic details the storage options that are validated for each of the cloud environment providers that are supported by Guardium® Insights.

Table 1. Validated storage options
Platform	Block storage	File storage
IBM Cloud® (Classic)	`ibmc-file-gold-gid`	`ibmc-file-gold-gid`
IBM Cloud (VPC Gen 2)	`ibmc-vpc-block-10ipos-tier` `ocs-storagecluster-ceph-rbd`	`ocs-storagecluster-cephfs`
Amazon Web Services (AWS) (IaaS)	`gp2` `ocs-storagecluster-ceph-rbd`	`efs-sc` `ocs-storagecluster-cephfs`
Red Hat OpenShift service on Amazon Web Services (ROSA)	`gp3-csi`	`efs-sc`
Microsoft Azure (IaaS)	`managed-premium` `ocs-storagecluster-ceph-rbd`	`ocs-storagecluster-cephfs`
Microsoft Azure ARO (managed)	`managed-premium` `ocs-storagecluster-ceph-rbd`	`ocs-storagecluster-cephfs`
Google Cloud	`standard` `ocs-storagecluster-ceph-rbd`	`ocs-storagecluster-cephfs`
Portworx	`portworx-rwo-sc`	`portworx-rwx-sc`
Portworx	For more information, see Portworx under Storage option notes.
VMware	`thin` `ocs-storagecluster-ceph-rbd`	`ocs-storagecluster-cephfs`
Bare Metal	`ocs-storagecluster-ceph-rbd`	`ocs-storagecluster-cephfs`
IBM Spectrum Fusion Version 2.2.1 or later on OpenShift® Container Platform (OCP)	`ibm-spectrum-scale-sc`	`ibm-spectrum-scale-sc`
IBM Spectrum Scale Container Native (with IBM Spectrum Scale Container Storage Interface) Version 5.1.3.x or later and CSI Version 2.5.x or later	`ibm-spectrum-scale-sc`	`ibm-spectrum-scale-sc`
NetApp Trident Version 22.4.0 or later fixes Note: Applies to both self-managed and managed NetApp Trident.	`basic-csi`	`basic-csi`

Storage option notes

IBM Spectrum Fusion: To learn more about the IBM Spectrum Fusion storage class, see https://www.ibm.com/docs/SSG4YK_2.3/sfandcloudpaks.html.

ocs-storagecluster (OpenShift)_

For ocs-storagecluster-ceph-rbd and ocs-storagecluster-cephfs, storage is provided by Openshift Data Foundation (previously OpenShift Container Storage). For this, there are additional hardware requirements, as outlined in these topics:

Important: Dynamic provisioning is required.

Portworx

Portworx storage class names can be any lower case alphanumeric name and include hyphens. To differentiate between block and file storage, you might want to establish a naming convention that includes the storage type (portworx), the access type (rwo for block storage and rwx for file storage), the object (sc for storage class) and other information. For example, portworx-rwo-sc and portworx-rwx-sc or portworx-db2-rwo-sc and portworx-db2-rwx-sc.

Use the following examples to set up the storage classes for Portworx. Replace the metadata name with your own name:

allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: portworx-rwo-sc
parameters:
  allow_others: "true"
  block_size: 4096b
  io_profile: db
  priority_io: high
  repl: "2"
  sharedv4: "false"
provisioner: kubernetes.io/portworx-volume
reclaimPolicy: Retain
volumeBindingMode: Immediate

allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: portworx-rwx-sc
parameters:
  allow_others: "true"
  block_size: 4096b
  repl: "2"
  sharedv4: "true"
provisioner: kubernetes.io/portworx-volume
reclaimPolicy: Retain
volumeBindingMode: Immediate