vania-janet/multiturn-rag-retrieval-data huggingface dataset:
2.21 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.21 sha256:4ce661dc331005bc3cb828a677c760b2dda3c2951415141a91aeb0c0b9a351da 
 2.20 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.20 sha256:655330f36771d274082b6c16a60620350597a9d6f2489a6246b9d2833d021211 
 2.19 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.19 sha256:482d28e51d5acc65471b366bbdcabc97f69e49da933337a7c42f45907cd63173 
 2.18 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.18 sha256:56cc0a6562e786f1b87b490e6a34ed655fa2c376ae3c8622690912dce7d9a608 
 2.17 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.17 sha256:c1e9d5a9674a093635c386f96d35781aea7cad6cc1da86991ee1a85c854216f8 
 2.16 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.16 sha256:3a3b5a981caed4238ef7297bb54b4a32b974b0499b12744347bc661d3f323916
* To get the offering_crn for the offering and the offering_version_crn for each version in the offering, run the following command.

ibmcloud is catalog-image-offering $catalog_id $offering_id



When you provision an instance, you can either provision the instance from the private catalog-managed image in the latest version in a catalog product offering by using the offering_crn value or from the specific version in the catalog product offering by using the offering_version_crn value.

Save the offering_crn and offering_version_crnin variables, which are used later to provision an instance.

offering_crn="crn:v1:staging:public:globalcatalog-collection:global:a/efe5afc483594adaa8325e2b4d1290df:0b322820-dafd-4b5e-b694-6465da6f008a:offering:136559f6-4588-4af2-8585-f3c625eee09d"
offering_version_crn="crn:v1:staging:public:globalcatalog-collection:global:a/efe5afc483594adaa8325e2b4d1290df:0b322820-dafd-4b5e-b694-6465da6f008a:version:136559f6-4588-4af2-8585-f3c625eee09d/8ae92879-e253-4a7c-b09f-8d30af12e518"



7. List the available boot volumes for creating your instance. If you are creating an instance from an image, skip this step. To create an instance from an existing volume, you must use a volume compatible with the instance options chosen previously. A compatible volume is in the same zone as the instance that is being provisioned, in an unattached state, and has an OS compatible with the profile that is selected in step 5. Use the volumes subcommand to see the compatible volumes.
[BI.S4.H2.3000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1109&presetId=1103) 56 112 3072 GB 135,127 OLAP/OLTP (**) 
 [BI.S4.H4.3000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1117&presetId=1117) 112 224 3072 GB 285,970 OLAP/OLTP (**) 
 [BI.S4.H4.6000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1117&presetId=1113) 112 224 6144 GB 285,970 OLAP/OLTP (**) 
 [BI.S4.H8.6000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1119&presetId=1121) 224 448 6144 GB 550,670 OLAP/OLTP (**) 
 [BI.S4.H8.12000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1119&presetId=1129) 224 448 12288 GB 550,670 OLAP/OLTP (**) 



(*): RHEL 7.4 for SAP Solutions, RHEL 7.6 for SAP Solutions, RHEL 7.9 for SAP Solutions, RHEL 8.2 for SAP Solutions -- SLES 12 SP2, SLES 12 SP4, SLES 12 SP5, SLES 15, SLES 15 SP1, SLES 15 SP2, SLES 15 SP3
Example command to create a version 4.11 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-remote --template-version 4.11 --param "osd-size=OSD-SIZE" --param "osd-storage-class=OSD-STORAGE-CLASS" --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP" --param "kms-encryption=KMS-ENCRYPTION" [--param "kms-instance-name=KMS-INSTANCE-NAME"] [--param "kms-instance-id=KMS-INSTANCE-ID"] [--param "kms-base-url=KMS-BASE-URL"] [--param "kms-token-url=KMS-TOKEN-URL"] [--param "kms-root-key=KMS-ROOT-KEY"] [--param "kms-api-key=KMS-API-KEY"] --param "ignore-noobaa=IGNORE-NOOBAA"

Example command to create a version 4.12 configuration.
660198a6-52c6-21cd-7b57-e37917cef586 debian-8.x-amd64 Debian GNU/Linux (8.x jessie/Stable - Minimal Install) 2018-10-30T06:12:06.624+00:00 available public
e15b69f1-c701-f621-e752-70eda3df5695 debian-9.x-amd64 Debian GNU/Linux (9.x Stretch/Stable - Minimal Install) 2018-10-30T06:12:06.705+00:00 available public
2d7acb16-3d4b-d0e5-d623-e43783a9b126 red-7.x-amd64 Red Hat Enterprise Linux (7.x - Minimal Install) 2019-03-11T02:30:57.249+00:00 available public
7eb4e35b-4257-56f8-d7da-326d85452591 ubuntu-16.04-amd64 Ubuntu Linux (16.04 LTS Xenial Xerus Minimal Install) 2018-10-30T06:12:06.537+00:00 available public
cfdaf1a0-5350-4350-fcbc-97173b510843 ubuntu-18.04-amd64 Ubuntu Linux (18.04 LTS Bionic Beaver Minimal Install) 2018-10-30T06:12:06.51+00:00 available public
b45450d3-1a17-2226-c518-a8ad0a75f5f8 windows-2012-amd64 Windows Server (2012 Standard Edition) 2018-10-30T06:12:06.678+00:00 available public
81485856-df27-93b8-a838-fa28a29b3b04 windows-2012-r2-amd64 Windows Server (2012 R2 Standard Edition) 2018-10-30T06:12:06.564+00:00 available public
The file is similar to the following example:

locals {
mask = "${element(split("/", var.machine_cidr), 1)}"
gw = "${cidrhost(var.machine_cidr,1)}"

ignition_encoded = "data:text/plain;charset=utf-8;base64,${base64encode(var.ignition)}"
}

data "ignition_file" "hostname" {
count = "${var.instance_count}"

filesystem = "root"
path = "/etc/hostname"
mode = "420"

content {
content = "${var.name}-${count.index}"
}
}

data "ignition_file" "static_ip" {
count = "${var.instance_count}"

filesystem = "root"
path = "/etc/sysconfig/network-scripts/ifcfg-ens192"
mode = "420"

content {
content = <<EOF
TYPE=Ethernet
BOOTPROTO=none
NAME=ens192
DEVICE=ens192
ONBOOT=yes
IPADDR=${local.ip_addresses[count.index]}
PREFIX=${local.mask}
GATEWAY=${local.gw}
DOMAIN=${var.cluster_domain}
DNS1=10.187.214.66
EOF
}
}

data "ignition_systemd_unit" "restart" {
count = "${var.instance_count}"

name = "restart.service"

content = <<EOF
[Unit]
ConditionFirstBoot=yes
[Service]
Type=idle
ExecStart=/sbin/reboot
[Install]
WantedBy=multi-user.target
EOF
}

data "ignition_config" "ign" {
count = "${var.instance_count}"
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driveribm-vpc-block-csi-driver-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driveribm-vpc-block-csi-driver-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driveribm-vpc-block-csi-driver-config-create-api)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driverstorage-ibm-vpc-block-csi-driver-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driverstorage-ibm-vpc-block-csi-driver-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driverstorage-ibm-vpc-block-csi-driver-include-assignment-create-api)
* [Deploying an app that uses Block Storage for VPC](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driversat-storage-vpc-deploy-app)
* [Removing Block Storage for VPC storage from your apps](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-drivervpc-csi-rm-apps)
Example request to create a version 4.11 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "local-volume-file", "storage-template-version": "4.11", "update-assignments": true, "user-config-parameters": { "entry.name": "AUTO-DISCOVER-DEVICES", { "entry.name": "LABEL-KEY", { "entry.name": "LABEL-VALUE", { "entry.name": "DEVICEPATH", { "entry.name": "FSTYPE","user-secret-parameters": }

Example request to create a version 4.12 configuration.
Different lockers require different parameters to be provided.

Options:

--backend (Required) Specifies the types of lockers we upload the artifact ('cos', 'git')
--pipeline-run-id The ID of the PipelineRun running the CLI command
--namespace Specifies the pipeline the evidence is collected from
--upload-path If present, this overrides the artifact name with the specified value
--is-summary If present, this uploads the artifact to the location where evidence summary is usually stored

Options for Git:

--git-token-path (Optional) Github Token's path
--git-api-url (Optional) Github API url

Required Environment Variables:

PIPELINE_RUN_ID= Can be used instead of '--pipeline-run-id' option
NAMESPACE= Can be used instead of '--namespace' option

Required Environment Variables, if you are using 'git' provider:

EVIDENCE_REPO_ORG= The Git repo org (Required if you are using 'git' backend)
EVIDENCE_REPO_NAME= The Git repo name (Required if you are using 'git' backend)

Required Environment Variables, if you are using GitHub:

GHE_TOKEN= Github Enterprise API Token (Optional if you are using --git-token-path)

Required Environment Variables, if you are using Cloud Object Storage:

COS_API_KEY= Cloud Object Storage API Key (Required if you are using 'cos' backend)
COS_BUCKET_NAME= Bucket Name where the artifact will be uploaded in the COS Instance (Required if you are using 'cos' backend)
COS_ENDPOINT= The COS API Endpoint matching the region where the bucket is located (Required if you are using 'cos' backend)

If you are using github, use --git-token-path field to set your GitHub Token and --git-api-url field to set the # GitHub Enterprise API URL instead of GHE_TOKEN and GH_URL environment variables.
* [(Optional) Getting the device details for your ODF configuration](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localsat-storage-odf-local-devices)
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localodf-local-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localodf-local-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localodf-local-config-create-api)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localstorage-odf-local-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localstorage-odf-local-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localstorage-odf-local-include-assignment-create-api)
* [Deploying an app that uses OpenShift Data Foundation](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localsat-storage-odf-local-deploy)
* [Scaling your ODF configuration by attaching raw disks](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localsat-storage-scale-odf-local-disk)
2.5 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.5 sha256:90bdb361ba94b75dfd7feb7c6a2577ece9f91e0392f20a5b4e9808120041b3e2 
 2.4 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.4.1 sha256:ade4209bbc6923c02a3315c7e6dcc4376afc355db2765b792205be9b33f4243d 
 2.3 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.3 sha256:1451dab959183c6378a804ce0744913028623e10c401e5ebc1a1f88c82443ba4 
 2.2 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.2 sha256:2073c470e83418abf2c11ec92554c139aadd18f0c63fffb92c2c3f5e90c46ba6 
 2.1 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.1 sha256:b5be69c4ae42a7af28a9d7ad25df548c77959b006507367507c9ff0f992306f2 
 2.0 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.0 sha256:cc13eadecb8e99a7fe56a071427c2caa34149c31d1ad84f4f03c96f111dd0154 



The following available image versions are listed in descending order, starting with the current version.
Review the repository URLs, and then continue to the next steps.



 Application-related repositories 

If you want to set up your CD toolchain from scratch, configure these repositories during CI toolchain creation, and then use or link to them here.

To fetch the respective URL, go to the CI Pipeline, select the respective tool card. Right-click the tool card, and select Copy link address.



* Inventory: The inventory repository records details of artifacts that are built by the CI and CD pipelines. For example, https://<region>.git.cloud.ibm.com/myorg/my-compliance-ci-inventory
* Issues: The issues repository records issues that are found while the CI pipeline is running. For example, https://<region>.git.cloud.ibm.com/myorg/my-compliance-ci-issues.
* Evidence: All raw compliance evidence that belongs to the application is collected here. For example, https://<region>.git.cloud.ibm.com/myorg/my-compliance-ci-evidence.



The toolchain currently supports linking only to existing IBM-hosted Git Repos and Issue Tracking repositories.





 Inventory 

Repository URL: URL of the inventory repository that is configured in your CI toolchain as captured in the previous step.





 Issues 

Repository URL: URL of the issues repository that is configured in your CI toolchain as captured in the previous step.





 Pipeline Configuration 

The pipeline configuration repository contains YAML files and scripts that are needed for deployment, testing, and other custom tasks.

For this tutorial, the pipeline configuration repository is the same as the one defined for the DevSecOps CI for Infrastructure as Code (IaC). Select Use existing deployment configuration repository and select the repository that is used for the pipeline configuration of the CI Toolchain.

For more information about Git repos, see [Configuring your Git Repos and Issue Tracking](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-config-github).
Example command to create a version 4.10 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-remote --template-version 4.10 --param "osd-size=OSD-SIZE" --param "osd-storage-class=OSD-STORAGE-CLASS" --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP" --param "kms-encryption=KMS-ENCRYPTION" [--param "kms-instance-name=KMS-INSTANCE-NAME"] [--param "kms-instance-id=KMS-INSTANCE-ID"] [--param "kms-base-url=KMS-BASE-URL"] [--param "kms-token-url=KMS-TOKEN-URL"] [--param "kms-root-key=KMS-ROOT-KEY"] [--param "kms-api-key=KMS-API-KEY"] --param "ignore-noobaa=IGNORE-NOOBAA"

Example command to create a version 4.11 configuration.
3m 3m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibm.io/ibmc-file", expecting that a volume for the claim is provisioned either manually or via external software
1m 1m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal ProvisioningSucceeded Successfully provisioned volume pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2



You successfully created a PV and bound it to a PVC. Cluster users can now [mount the PVC](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_app_volume_mount) to their deployments and start reading from and writing to the PV object.







 Using File Storage for Classic in a stateful set 

If you have a stateful app such as a database, you can create stateful sets that use File Storage for Classic to store your app's data. Alternatively, you can use an IBM Cloud database-as-a-service and store your data in the cloud.

What do I need to be aware of when adding File Storage for Classic to a stateful set?
: To add storage to a stateful set, you specify your storage configuration in the volumeClaimTemplates section of your stateful set YAML. The volumeClaimTemplates is the basis for your PVC and can include the storage class and the size or IOPS of your File Storage for Classic that you want to provision. However, if you want to include labels in your volumeClaimTemplates, Kubernetes does not include these labels when creating the PVC. Instead, you must add the labels directly to your stateful set.

You can't deploy two stateful sets at the same time.
mountPath: /usr/share/nginx/html
- name: myvol2
mountPath: /tmp1
volumeClaimTemplates:
- metadata:
name: myvol1
spec:
accessModes:
- ReadWriteOnce access mode
resources:
requests:
storage: 20Gi
storageClassName: ibmc-block-bronze-delayed
- metadata:
name: myvol2
spec:
accessModes:
- ReadWriteOnce access mode
resources:
requests:
storage: 20Gi
storageClassName: ibmc-block-bronze-delayed
Show more

name
: Enter a name for your stateful set. The name that you enter is used to create the name for your PVC in the format: <volume_name>-<statefulset_name>-<replica_number>.

serviceName
: Enter the name of the service that you want to use to expose your stateful set.

replicas
: Enter the number of replicas for your stateful set.

podManagementPolicy
: Enter the pod management policy that you want to use for your stateful set.



* OrderedReady: With this option, stateful set replicas are deployed one after another. For example, if you specified three replicas, then Kubernetes creates the PVC for your first replica, waits until the PVC is bound, deploys the stateful set replica, and mounts the PVC to the replica. After the deployment is finished, the second replica is deployed. For more information about this option, see [OrderedReady Pod Management](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/orderedready-pod-management)
* Parallel: With this option, the deployment of all stateful set replicas is started at the same time. If your app supports parallel deployment of replicas, then use this option to save deployment time for your PVCs and stateful set replicas.



matchLabels
2.25 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.25 sha256:31f01a325fcb53651742fbb4af1d9a3ec425fc9b2662e1894c01389ff37426bf 
 2.24 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.24 sha256:a97c10d27cdf8ee543cad4b29980ccdd5a697164f40ade7f399a0b7a3619f2ea 
 2.23 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.23 sha256:8582554fda2c36c0750d734c78b692b96ac0f983d4d2e11a186e224ec2fa554f 
 2.22 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.22 sha256:0653ba3abbdadf347fde238667b510757ecd9625dd7f7d53c512d7a5a2762612 
 2.21 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.21 sha256:4ce661dc331005bc3cb828a677c760b2dda3c2951415141a91aeb0c0b9a351da 
 2.20 icr.io/continuous-delivery/pipeline/pipeline-base-image:2.20 sha256:655330f36771d274082b6c16a60620350597a9d6f2489a6246b9d2833d021211
* [Prerequisites for using AWS EBS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-prereq)
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-config-create-api)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driverstorage-aws-ebs-csi-driver-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driverstorage-aws-ebs-csi-driver-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driverstorage-aws-ebs-csi-driver-include-assignment-create-api)
* [Deploying an app that uses AWS EBS storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driversat-storage-ebs-deploy)
3m 3m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibm.io/ibmc-file", expecting that a volume for the claim is provisioned either manually or via external software
1m 1m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal ProvisioningSucceeded Successfully provisioned volume pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2



You successfully created a PV and bound it to a PVC. Cluster users can now [mount the PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_app_volume_mount) to their deployments and start reading from and writing to the PV object.







 Using File Storage for Classic in a stateful set 

If you have a stateful app such as a database, you can create stateful sets that use File Storage for Classic to store your app's data. Alternatively, you can use an IBM Cloud database-as-a-service and store your data in the cloud.

What do I need to be aware of when adding File Storage for Classic to a stateful set?
: To add storage to a stateful set, you specify your storage configuration in the volumeClaimTemplates section of your stateful set YAML. The volumeClaimTemplates is the basis for your PVC and can include the storage class and the size or IOPS of your File Storage for Classic that you want to provision. However, if you want to include labels in your volumeClaimTemplates, Kubernetes does not include these labels when creating the PVC. Instead, you must add the labels directly to your stateful set.

You can't deploy two stateful sets at the same time.