vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Your IBM Cloud Object Storage service instance remains and is not deleted. If you choose to set this option to true, then you must set ibm.io/auto-create-bucket: true and ibm.io/bucket: "" so that your bucket is automatically created with a name with the format tmp-s3fs-xxxx.
: false: When you delete the PVC, the PV is deleted automatically, but your data and the bucket in your IBM Cloud Object Storage service instance remain. To access your data, you must create a new PVC with the name of your existing bucket.

ibm.io/bucket
: Choose between the following options.
: If ibm.io/auto-create-bucket is set to true: Enter the name of the bucket that you want to create in IBM Cloud Object Storage. If in addition ibm.io/auto-delete-bucket is set to true, you must leave this field blank to automatically assign your bucket a name with the format tmp-s3fs-xxxx. The name must be unique in IBM Cloud Object Storage.
: If ibm.io/auto-create-bucket is set to false: Enter the name of the existing bucket that you want to access in the cluster.

ibm.io/object-path
: Optional: Enter the name of the existing subdirectory in your bucket that you want to mount. Use this option if you want to mount a subdirectory only and not the entire bucket. To mount a subdirectory, you must set ibm.io/auto-create-bucket: "false" and provide the name of the bucket in ibm.io/bucket.

ibm.io/quota-limit
: To use this annotation, you must specify the --set quotaLimit=true option during installation. If you want to use this annotation, but didn't specify --set quotaLimit=true during installation, [re-install the helm chart](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install).
* [Changing the size and IOPS of your existing storage device](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_change_storage_configuration)
* [Backing up and restoring data](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_backup_restore)



* [Setting up periodic snapshots](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock-snaps)
* [Replicating snapshots to another zone](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock-replicate)
* [Duplicating storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock-dupe)
* [Backing up data to IBM Cloud® Object Storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock-cos-backup)
* [Copying data to and from pods and containers](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock-cp)



* [Storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_storageclass_reference)



* [Bronze](https://cloud.ibm.com/docs/containers?topic=containers-block_storagebronze-block)
* [Silver](https://cloud.ibm.com/docs/containers?topic=containers-block_storagesilver-block)
* [Gold](https://cloud.ibm.com/docs/containers?topic=containers-block_storagegold-block)
* [Custom](https://cloud.ibm.com/docs/containers?topic=containers-block_storagecustom-block)



* [Sample customized storage classes](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_custom_storageclass)
Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>



7. List your PVCs and note the name of the PVC that you want to remove.

oc get pvc
8. Remove any pods that currently mount the PVC.



1. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you do not have any pods that currently use your PVC.

oc get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"

Example output

app sat-local-file-gold
2. Remove the pod that uses the PVC. If the pod is part of a deployment, remove the deployment.

oc delete pod <pod_name>

oc delete deployment <deployment-name>
3. Verify that the pod or the deployment is removed.

oc get pods

oc get deployments



9. Delete the PVC. Because all IBM-provided local file storage classes are specified with a Retain reclaim policy, the PV and PVC are not automatically deleted when you delete your app or deployment.

oc delete pvc <pvc-name>
10. Verify that your PVC is removed.

oc get pvc
11. List your PVs and note the name of the PVs that you want to remove.

oc get pv
12. Delete the PVs. Deleting your PVs will make your disks available for other workloads.

oc delete pv <pv-name>
13. Verify that your PV is removed.

oc get pv









 Parameter reference 



 4.8 parameter reference 



Table 1. 4.8 parameter reference
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 IOPS limit ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 Deduplication and compression ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) 
 RAID-5/6 erasure coding ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/checkmark-icon.svg) !
* [ibmcloud ks storage attachment get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_storage_att_get)
* [ibmcloud ks storage attachment ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_storage_att_ls)
* [ibmcloud ks storage attachment rm](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_storage_att_rm)



* storage volume: View a list of storage volumes.



* [ibmcloud ks storage volume get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_storage_att_ls_c)
* [ibmcloud ks storage volume ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_storage_att_ls_2)
Managing portable storage 

Portable storage volumes (PSVs) are an auxiliary storage solution exclusively for Virtual Servers. Within the IBM Cloud® console, you can access portable storage volumes and display all PSVs. You can also attach, detach, swap, and edit volumes. Portable Storage Volumes (PSV) on virtual server instances are encrypted at rest.

You can't attach or swap portable storage volumes to a virtual server instance that is provisioned from an encrypted image template because these PSVs are encrypted at rest.



  Before you begin 

First, go to the storage or devices menu and make sure that you have the correct account permissions to complete the tasks.



*  Go to your console's storage or device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices).
*  Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





  Attaching portable storage 



1.  From the Storage menu, select Block Storage.
2.  In the Portable storage section, select the attach option for the portable storage you want to use.
3.  On the next screen, choose the device that needs the storage, and select Attach.







  Managing portable storage that is attached to a server 

Portable storage attached to a server is listed on the server's Device Details page.



1.  From the Devices menu, select Device List.
2.  From the Device List, select a virtual server instance to view its details.
3.  Click the Storage tab to view the portable storage that is attached to the instance.
4.  In the Actions menu, you select either Swap or Detach the storage.
* [Verifying the encryption of your Block Storage for Classic volumes](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_encrypt)



* [Adding block storage to apps](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block)
* [Using existing block storage in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting_block)



* [Retrieving the information of your existing block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting-block-1)
* [Creating a persistent volume (PV) and a matching persistent volume claim (PVC)](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting-block-2)



* [Using block storage in a stateful set](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_statefulset)



* [Creating the PVC by using dynamic provisioning when you create a stateful set](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_dynamic_statefulset)
* [Static provisioning by using existing PVCs with a stateful set](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_static_statefulset)



* [Changing the size and IOPS of your existing storage device](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_change_storage_configuration)
* [Backing up and restoring data](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_backup_restore)



* [Setting up periodic snapshots](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock-snaps)
[Reset or sync security group settings](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisecurity_group)



* [ibmcloud oc security-group reset](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisecurity_group_reset)
* [ibmcloud oc security-group sync](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisecurity_group_sync)







 ibmcloud oc storage 

Beta[View and modify storage resources](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage).



* storage attachment: View and modify storage volume attachments of worker nodes in your cluster.



* [ibmcloud oc storage attachment create](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_cr)
* [ibmcloud oc storage attachment get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_get)
* [ibmcloud oc storage attachment ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_ls)
* [ibmcloud oc storage attachment rm](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage_att_rm)



* storage volume: View a list of storage volumes.
Removing the Block Storage for VPC storage configuration using the console 



1. From the Satellite storage dashboard, select the storage configuration you want to delete.
2. Select Actions > Delete
3. Enter the name of your storage configuration.
4. Select Delete.







 Removing the Block Storage for VPC storage configuration using the cli 



1. List your storage assignments and find the one that you used for your cluster.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)
2. Remove the assignment. After the assignment is removed, the driver pods and storage classes are removed from all clusters that were part of the storage assignment.

ibmcloud sat storage assignment rm --assignment <assignment_ID>
3. Verify that the driver is removed from your cluster.



1. List of the storage classes in your cluster and verify that the storage classes are removed.

oc get sc
2. List the pods in the kube-system namespace and verify that the storage driver pods are removed.

oc get pods -n kube-system | grep vpc



4. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>











 Parameter reference 



 5.0 parameter reference 



Table 1. 5.0 parameter reference

 Display name CLI option Type Description Required? Default value 

 IAM endpoint g2_token_exchange_endpoint_url Config The IAM endpoint. For example https://iam.cloud.ibm.com. true N/A 
 VPC IaaS endpoint g2_riaas_endpoint_url Config The VPC regional endpoint of your VPC cluster in the format https://region.iaas.cloud.ibm.com.
Cleaning up your Portworx volumes and cluster 

Remove a [Portworx volume](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_removingremove_pvc_apps_volumes), a [storage node](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_removingremove_storage_node_cluster-px), or the [entire Portworx cluster](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_removingremove_storage_node_cluster-px) if you don't need it anymore.



 Removing Portworx volumes from apps 

When you added storage from your Portworx cluster to your app, you have three main components: the Kubernetes persistent volume claim (PVC) that requested the storage, the Kubernetes persistent volume (PV) that is mounted to your pod and described in the PVC, and the Portworx volume that blocks space on the physical disks of your Portworx cluster. To remove storage from your app, you must remove all components.



1. List the PVCs in your cluster and note the NAME of the PVC, and the name of the PV that is bound to the PVC and shown as VOLUME.

kubectl get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
px-pvc Bound pvc-06886b77-102b-11e8-968a-f6612bb731fb 20Gi RWO px-high 78d
2. Review the ReclaimPolicy for the storage class.

kubectl describe storageclass <storageclass_name>

If the reclaim policy says Delete, your PV and the data on your physical storage in your Portworx cluster are removed when you remove the PVC. If the reclaim policy says Retain, or if you provisioned your storage without a storage class, then your PV and your data are not removed when you remove the PVC. You must remove the PVC, PV, and the data separately.
3.
[Expandable storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacity) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon.]
Do not show the message of the day or update reminders.





 Example 

ibmcloud sat storage config upgrade --config ocs-config







 ibmcloud sat storage config sc add 

Add a custom storage class to a Satellite storage configuration.

ibmcloud sat storage config sc add --config-name CONFIG --name NAME [--param PARAM ...] [-q]



 Minimum required permissions 

IBM Cloud IAM Operator platform role for the Configuration resource type in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--config CONFIG
: Required. The name of the storage configuration that you want to add a storage class to. To list Satellite storage configurations, run ibmcloud sat storage config ls.

--name
: Required. The name of the custom storage class that you want to add to your configuration.

--param
: Optional. The custom parameters to provide to the storage class. Parameters are passed as KEY=VALUE pairs. You can pass multiple parameters by specifying the --param option multiple times.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat storage config sc add --config ocs-config --name my-sc --param key=value --param key=value







 ibmcloud sat storage config sc get 

Get the details of a custom storage class in a Satellite storage configuration.

ibmcloud sat storage config sc get --config CONFIG --sc SC [--output OUTPUT] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Configuration resource in Satellite.
daemonset.apps/local-disk-local-provisioner 3 3 3 3 3 <none> 29h

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/local-storage-operator 1/1 1 1 29h

NAME DESIRED CURRENT READY AGE
replicaset.apps/local-storage-operator-df4994656 1 1 1 29h
2. List your storage assignments and find the one that you used for your cluster.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)
3. Remove the assignment. After the assignment is removed, the local storage driver pods and storage classes are removed from all clusters that were part of the storage assignment.

ibmcloud sat storage assignment rm --assignment <assignment_ID>
4. List the resources in the local-storage namespace and verify that the local storage driver pods are removed.

oc get all -n local-storage

Example output

No resources found in local-storage namespace.
5. List of the storage classes in your cluster and verify that the local storage classes are removed.

oc get sc
6. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>



7. List your PVCs and note the name of the PVC that you want to remove.

oc get pvc
8. Remove any pods that currently mount the PVC.



1. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you do not have any pods that currently use your PVC.
Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>











 Parameter reference 



 1.3.1 parameter reference 



Table 1. 1.3.1 parameter reference

 Display name CLI option Type Description Required? Default value 

 AWS Access Key ID aws-access-key Secret AWS Access Key ID. true N/A 
 AWS Secret Access Key aws-secret-access-key Secret AWS Secret Access key. true N/A 







 1.3.7 parameter reference 



Table 2. 1.3.7 parameter reference

 Display name CLI option Type Description Required? Default value 

 AWS Access Key ID aws-access-key Secret AWS Access Key ID. true N/A 
 AWS Secret Access Key aws-secret-access-key Secret AWS Secret Access key. true N/A 







 1.4.2 parameter reference 



Table 3. 1.4.2 parameter reference

 Display name CLI option Type Description Required? Default value 

 AWS Access Key ID aws-access-key Secret AWS Access Key ID. true N/A 
 AWS Secret Access Key aws-secret-access-key Secret AWS Secret Access key. true N/A 









 Getting help and support for AWS EFS 

When you use AWS EFS Storage, try the following resources before you open a support case.



1. Review the FAQs in the [AWS Knowledge Center](https://repost.aws/knowledge-center).
2. Review the [troubleshooting documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-must-gather) to troubleshoot and resolve common issues.
3. Check the status of the IBM Cloud platform and resources by going to the [Status page](https://cloud.ibm.com/status).
4.
Get the name of your OcsCluster custom resource.

oc get ocscluster
2. Save your OcsCluster custom resource YAML file to your local machine as ocscluster.yaml.

oc get ocscluster ocscluster-vpc -o yaml
3. Increase the numOfOsd parameter and reapply the ocscluster CRD to your cluster.

oc apply -f ocscluster.yaml
4. Verify that the additional OSDs are created.

oc get pv







 Expanding ODF by adding worker nodes to your VPC cluster 

To increase the storage capacity in your storage cluster, add compatible worker nodes to your cluster.



1. Expand the worker pool of the cluster that is used for OCS by [adding worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workers). Ensure that your worker nodes meet the [requirements for ODF](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-storage-prep). If you deployed ODF on all the worker nodes in your cluster, the ODF drivers are installed on the new worker nodes when they are added to your cluster.
2. If you deployed ODF on a subset of worker nodes in your cluster by specifying the private <workerNodes> parameters in your OcsCluster custom resource, you can add the node name of the new worker nodes to your ODF deployment by editing the custom resource definition.

oc edit ocscluster ocscluster-vpc
3. Save the OcsCluster custom resource file to reapply it to your cluster.









 Limitations 

Review the following limitations for deploying ODF.

Kubernetes resource ID character limit: Kubernetes PVC names must be fewer than 63 characters.
ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)







 Creating a storage assignment in the API 



1. Copy one of the following example requests.

Example request to assign a [configuration to a cluster](https://containers.cloud.ibm.com/global/swagger-global-api//satellite/createAssignmentByCluster).

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignmentByCluster" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "CLUSTER-ID", "controller": "LOCATION-ID", "name": "ASSIGNMENT-NAME"}"

Example request to [assign configuration to a cluster group](https://containers.cloud.ibm.com/global/swagger-global-api//satellite/createAssignment).

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "string", "groups": [ "CLUSTER-GROUP" ], "name": "ASSIGNMENT-NAME"}"
2. Replace the variables with your details and run the request.
3. Verify the assignment was created by listing your assignments.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"







 Removing Compute Engine storage from your apps 

If you no longer need your Google Compute Engine configuration, you can remove your apps, PVCs, PVs, and assignment from your clusters.



1.