Enabling support for Native Cloud Object Storage

Edit your Db2uInstance custom resource (CR) to enable Native Cloud Object Storage support.

1. The new advanced option enableCos must be set to "true" in order to enable the functionality at deployment time:
   An example file of the required edits for the enableCos parameter:

   spec:
     version: s11.5.9.0
     nodes: 2
     addOns:
       opendataformats:
         enabled: true
     advOpts:
       enableCos: "true"
       

2. The cloud object storage provider can be optionally configured through the advanced option cosProvider field:
   • aws: For Cloud Object Storage providers such as AWS S3 and IBM Cloud Object Storage, the cosProvider is set to "aws". This is the default value and can be omitted.
   • self-hosted: For other Cloud Object Storage providers such as Ceph Object Storage using RADOS, ODF MCG, and MinIO, either when configured using SSL but not using CA signed certificate, and when not configured to use SSL, cosProvider field must be set to "self-hosted".

     spec:
       version: s11.5.9.0
       nodes: 2
       addOns:
         opendataformats:
           enabled: true
       advOpts:
         enableCos: "true"
         cosProvider: "self-hosted"

3. The local disk for the caching tier must be configured as part of the storage configuration under the new "cachingtier" storage section. The "cachingtier" provides both the size and the storage class that manages the local NVMe drives on the target nodes. The name and configuration of the storage class is specific to the deployment environment.

   The following example output shows the caching tier configured with a storage size of 100Gi and using a sample storage class name local-device:

     storage:
       - name: cachingtier
         spec:
           accessModes:
             - ReadWriteMany
           resources:
             requests:
               storage: 100Gi
           storageClassName: local-device
         type: template