vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you remove the PVC, the PV that is bound to the PVC is released. Depending on how you provisioned your storage, your PV goes into a Deleting state if the PV is deleted automatically, or into a Released state, if you must manually delete the PV. Note: For PVs that are automatically deleted, the status might briefly say Released before it is deleted. Rerun the command after a few minutes to see whether the PV is removed.

kubectl get pv <pv_name>
8. If your PV is not deleted, manually remove the PV.

kubectl delete pv <pv_name>
9. Verify that the PV is removed.

kubectl get pv
10. List the physical storage instance that your PV pointed to and note the id of the physical storage instance.

ibmcloud sl file volume-list --columns id --columns notes | grep <pv_name>

Example output for File Storage for Classic.

id notes
12345678 {"plugin":"ibm-file-plugin-5b55b7b77b-55bb7","region":"us-south","cluster":"aa1a11a1a11b2b2bb22b22222c3c3333","type":"Endurance","ns":"default","pvc":"mypvc","pv":"pvc-d979977d-d79d-77d9-9d7d-d7d97ddd99d7","storageclass":"ibmc-file-gold"}

"plugin":"ibm-file-plugin-5b55b7b77b-55bb7"
: The storage plug-in that the cluster uses.

"region":"us-south"
: The region that your cluster is in.

"cluster":"aa1a11a1a11b2b2bb22b22222c3c3333"
: The cluster ID that is associated with the storage instance.
For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete mount target of a file share with the API 

Make a DELETE /shares/{share_ID}/mount_targets/{target_id} call to delete a mount target of a file share. The file share must be in a stable state.

See the following example.

curl -X DELETE "$vpc_api_endpoint/v1/shares/$share_id/mount_targets/$target_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer ${API_TOKEN}"

A successful response has a confirmation of acceptance for deletion and response that contains the target information. Status of mount target shows deleting while the deletion is underway.

The following example deletes a mount target where access_control_mode is security_group. The response shows the security group and subnet. You can also see the specifics of the reserved IP address that was used for the virtual network interface of the mount target in the primary_ip section. By default the virtual network interface is deleted along with the mount target when the mount target is deleted.

{
"access_control_mode": "security_group",
"created_at": "2023-05-30T01:59:46.000Z",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8/mount_targets/9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"id": "9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"lifecycle_reasons": [],
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. Remove any pods that mount the PVC.



1. List the pods that mount the PVC.

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

Example output

blockdepl-12345-prz7b: claim1-block-bronze

If no pod is returned in your CLI output, you don't have a pod that uses the PVC.
2. Remove the pod that uses the PVC.

If the pod is part of a deployment, remove the deployment.

kubectl delete pod <pod_name>
3. Verify that the pod is removed.

kubectl get pods



4. Remove the PVC.

kubectl delete pvc <pvc_name>
5. Review the status of your PV. Use the name of the PV that you retrieved earlier as VOLUME.

kubectl get pv <pv_name>

When you remove the PVC, the PV that is bound to the PVC is released. Depending on how you provisioned your storage, your PV goes into a Deleting state if the PV is deleted automatically, or into a Released state, if you must manually delete the PV. Note: For PVs that are automatically deleted, the status might briefly say Released before it is deleted. Rerun the command after a few minutes to see whether the PV is removed.
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/openshift?topic=openshift-storage_cos_install).
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-file-share-api).
* [Manage file share user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-add-tags-api).



To see information about the File Storage for VPC API methods, see the following section in the [API reference](https://cloud.ibm.com/apidocs/vpc-betalist-share-profiles).

File Storage for VPC regional API is available for customers with special approval to preview this feature.



 Rename a file share in the API 

Make a PATCH /shares/$share_id call to rename a specific file share. See the following example.

curl -X PATCH "$vpc_api_endpoint/v1/shares/$share_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer ${API_TOKEN}" -d '{
"name": "share-renamed1"
}'

A successful response looks like the following example.

{
"access_control_mode": "vpc",
"created_at": "2023-03-30T23:31:59Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"id": "0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"iops": 3000,
"lifecycle_state": "stable",
"name": "share-renamed1",
"profile": {
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uidelete-file-share-api).
* [Manage file share user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-add-tags-api).



To see information about the File Storage for VPC API methods, see the following section in the [API reference](https://cloud.ibm.com/apidocs/vpc-betalist-share-profiles).

File Storage for VPC regional API is available for customers with special approval to preview this feature.



 Rename a file share in the API 

Make a PATCH /shares/$share_id call to rename a specific file share. See the following example.

curl -X PATCH "$vpc_api_endpoint/v1/shares/$share_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer ${API_TOKEN}" -d '{
"name": "share-renamed1"
}'

A successful response looks like the following example.

{
"access_control_mode": "vpc",
"created_at": "2023-03-30T23:31:59Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"id": "0995b8c6-c323-4e59-9ea9-fa14dd66bba8",
"iops": 3000,
"lifecycle_state": "stable",
"name": "share-renamed1",
"profile": {
For add-on values, see [Cluster autoscaler add-on parameter reference](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-install-addonca_addon_ref)

api_route
: Set the IBM Cloud Kubernetes Service API [endpoint](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cli_api) for the region that your cluster is in. No default; uses the targeted region that your cluster is in.

resources.limits.cpu
: Set the maximum amount of worker node CPU that the ibm-iks-cluster-autoscaler pod can consume. The default value is 300m.

resources.limits.memory
: Set the maximum amount of worker node memory that the ibm-iks-cluster-autoscaler pod can consume. The default value is 300Mi.

resources.requests.cpu
: Set the minimum amount of worker node CPU that the ibm-iks-cluster-autoscaler pod starts with.| The default value is 100m.

resources.requests.memory
: Set the minimum amount of worker node memory that the ibm-iks-cluster-autoscaler pod starts with. The default value is 100Mi.

maxNodeProvisionTime
: Set the maximum amount of time in minutes that a worker node can take to begin provisioning before the cluster autoscaler cancels the scale-up request. The default value is 120m.

scaleDownUnneededTime
: Set the amount of time in minutes that a worker node must be unnecessary before it can be scaled down. The default value is 10m.

scaleDownDelayAfterAdd
: Set the amount of time after scale up that scale down evaluation resumes. The default value for scaleDownDelayAfterAdd is 10 minutes. The default value is 10m.

scaleDownDelayAfterDelete
: Set the amount of time after node deletion that scale down evaluation resumes. The default value for scaleDownDelayAfterDelete is the same as the scan-interval which is 1m.
Deleting a subscription with the CLI 

You can delete an IBM Cloud Object Storage subscription by running the [ibmcloud ce subscription cos delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-delete) command.

For example, use the following command to delete an IBM Cloud Object Storage subscription that is called mycosevent,

ibmcloud ce subscription cos delete --name mycosevent

If you delete an app or a job that is associated with the subscription, the subscription is not deleted. Instead, it moves to ready state of false because the subscription depends on the availability of the app or job. If you re-create the application or job (or another app or job with the same name), your subscription reconnects and the Ready state is true.
Release notes for watsonx.data 

Use these release notes to learn about the latest updates to IBM® watsonx.data that are grouped by date.



  7 July 2023 

watsonx.data is a new open architecture that combines the elements of the data warehouse and data lake models. The best-in-class features and optimizations available on the watsonx.data make it an optimal choice for next generation data analytics and automation. In the first release (watsonx.data 1.0.0), the following features are supported:



*  Creating, scaling, pausing, resuming, and deleting the Presto query engine
*  Associating and dissociating a catalog with an engine
*  Exploring catalog objects
*  Adding and deleting a database-catalog pair
*  Updating database credentials
*  Adding and deleting bucket-catalog pair
*  Exploring bucket objects
*  Loading data
*  Exploring data
*  Querying data
*  Query history
You can use IBM Planning Analytics® as a Service to invite additional users to access your service instance. You must first invite users into your IBM Cloud account using Identity Access Management (IAM) and then add the same users to Planning Analytics Workspace.

Planning Analytics



* 2023-01-31



[Known issues and limitations](https://cloud.ibm.com/docs/planning-analytics?topic=planning-analytics-Known)Known issues and limitations

Known issues and limitations includes a list of known issues and a list of functionality that is not available for this release.

Planning Analytics



* 15 minutes
* 2023-01-31



[Provisioning your Planning Analytics as a Service account](https://cloud.ibm.com/docs/planning-analytics?topic=planning-analytics-provisioning_account)Provisioning your Planning Analytics as a Service account

IBM Planning Analytics® as a Service can now be auto-provisioned into your own IBM Cloud account.

Planning Analytics



* 2023-01-31



[Saving and reloading a book](https://cloud.ibm.com/docs/planning-analytics?topic=planning-analytics-Saving)Saving and reloading a book

You can access Save as from the Save menu, and Reload book from the Refresh menu.

Planning Analytics



* 15 minutes
* 2023-01-31



[Assigning user permissions with TM1 security](https://cloud.ibm.com/docs/planning-analytics?topic=planning-analytics-Assigning)Assigning user permissions with TM1 security

After users are added to the TM1 Server, you can assign each user appropriate permissions using TM1 security.

Planning Analytics



* 15 minutes
* 2023-01-31



[Build a data lake using object storage](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-smart-data-lake)Build a data lake using object storage

Definitions of the term data lake vary, but in the context of this tutorial, a data lake is an approach to storing data in its native format for organizational use.
* The cluster name must start and end with an alphanumeric character.
* The maximum length of the cluster name is 30 characters.
* The cluster name must be unique within the vCenter Server with Hybridity Bundle instance.







 Data center location 

The IBM Cloud data center location of the cluster is set to the IBM Cloud data center of the vCenter Server instance by default. You can deploy the cluster to a different IBM Cloud data center than the deployed instance. However, you must ensure that the network latency between the two IBM Cloud data centers is less than 150 ms.

If you deploy the cluster to a different IBM Cloud data center or IBM Cloud infrastructure pod, three more VLANs are ordered for use with the ordered IBM Cloud bare metal servers.







 Bare metal server settings 

You can choose Skylake or Cascade Lake. Options might differ depending on the version that your instance was initially deployed in.



 Skylake 

When you select Skylake, you have options for the CPU model and RAM.



Table 1. Options for Skylake bare metal servers

 CPU model options Cores GHz RAM options 

 Dual Intel® Xeon® Silver 4110 processor 16 2.1 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5120 processor 28 2.2 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6140 processor 36 2.3 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 







 Cascade Lake 

For the Cascade Lake setting, you have options for the CPU model and RAM.

Cascade Lake bare metal servers are available only for VMware vSphere Enterprise Plus 6.7u3 instances.



Table 2. Options for Cascade Lake bare metal servers

 CPU model options Cores GHz RAM options 

 Dual Intel Xeon Silver 4210 processor 20 2.2 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 processor 32 2.3 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB
* If you want to host the cluster in a different IBM Cloud data center than the one that the instance is hosted in, toggle the Select a different location switch on and choose the IBM Cloud data center to host the cluster.
* For Skylake or Cascade Lake CPU generation type, select the CPU model, RAM size, and the Number of bare metal servers.
* For SAP-certified Cascade Lake, select one of the preset configurations.



3. Complete the storage configuration.



* If you select NFS storage and want to add and configure the same settings to all file shares, specify the Number of shares, Size (GB), and Performance.
* If you select NFS storage and want to add and configure file shares individually, toggle the Configure shares individually switch on, then click Add shared storage and select the Size (GB) and Performance for each individual file share. You must select at least one file share.
* If you select vSAN storage, specify the following values:



* Size for the vSAN capacity disks
* Number of vSAN capacity disks
* Size for vSAN cache disks
* Number of vSAN cache disks
* vSAN license edition





If you want more storage, check the High performance with Intel Optane box.

By default, the Enable vSAN deduplication and compression box is selected. If you do not want to enable vSAN deduplication and compression, clear the checkbox.



6. For gateway clusters, complete the following configuration.



1. For data center location, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) and select the geography, data center, and pod to host the cluster.
2. Specify the cluster name.
3. Select the CPU model, RAM size, and the number of bare metal servers.



7. For network interface settings, enter the hostname prefix, and then select the uplink speed and network type.
8.
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) and select the geography, data center, and pod to host the instance.
3. Specify the CPU model: either Cascade Lake or SAP-certified Cascade Lake and choose one of the available configurations. For Cascade Lake, also select the RAM size.
4. Specify [the number of bare metal servers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-consold-clustervc_orderinginstance-bare-metal-number).
5. If you want to use NFS storage, select the corresponding option.



* To add and configure file shares individually, toggle the Configure shares individually switch on. Then, click Add shared storage and select the Size (GB) and Performance for each file share. You must select at least one file share.
* To add and configure the same settings to all file shares, specify the Number of shares, Size (GB), and Performance.



6. If you want to use vSAN™ storage, select the corresponding option.



* Specify the disk type and size for the vSAN capacity disks, the number of vSAN capacity disks, the disk size for vSAN cache disks, and the number of vSAN cache disks.
* By default, the Enable vSAN deduplication and compression checkbox is selected. If you do not want to enable vSAN deduplication and compression, clear the checkbox.
* Specify the vSAN license edition.



7. Specify the networking type.
8. Select the uplink speed. The 25 Gb option is available only for specific pods and data center locations.
9. Select the VLAN settings:



* If you want to order new public and private VLANs, click Order new VLANs.
Select the IBM Cloud® data center settings. For more information, see [Region and data center locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).



 Geography 

Select the region where your consolidated cluster or instance is hosted.





 Data center 

Select the IBM Cloud data center where the consolidated cluster is hosted.





 Pod 

Select the IBM Cloud data center pod where you want to deploy your resources. Keep the default pod selection if you do not have reasons to prefer a different pod.







 Cluster name 

By default, the cluster names are set to instance name-edge.

You can also specify a new name for your clusters. The names must meet the requirements that are listed in [Cluster name](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-consold-clustervc_orderinginstance-consold-cluster-name).





 CPU model 

You can choose the following CPU models:



* Dual Intel® Xeon® Silver 4210 processor (Cascade Lake)
* Dual Intel Xeon Gold 5218 processor (Cascade Lake)







 RAM 

You can select different values between 64 GB and 1.5 TB.





 Number of bare metal servers 

The number of servers is set to two and cannot be changed. Both servers have the same configuration.





 Hostname prefix 

The hostname prefix applies to all clusters in the instance. It must meet the following requirements:



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* The hostname prefix must start with a lowercase alphabetic character.
* The hostname prefix must end with a lowercase alphabetic or numeric character.
* The maximum length of the hostname prefix is 10 characters.







 Configure hostnames individually 

You can customize the hostnames prefix individually by toggling the switch on.

The hostname prefix must meet the following requirements:



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* No consecutive dash characters are allowed.
Dual Intel Xeon Platinum 8260 (Cascade Lake) 48 2.4 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Quad Intel Xeon Gold 6248 (Cascade Lake) 80 2.5 384 GB, 768 GB, 1.5 TB, 3 TB 
 Quad Intel Xeon Platinum 8260 (Cascade Lake) 96 2.4 384 GB, 768 GB, 1.5 TB, 3 TB 







 Number of bare metal servers 

You can order 3 - 30 servers. All servers have the same configuration.





 vSAN configuration 

Specify the following settings for vSAN™ configuration.



 Size for vSAN capacity disks 

Select an option for the capacity disks that you need.





 Number of vSAN capacity disks 

Specify the number of capacity disks that you want to add.







 Estimated resources available per cluster 

Review the estimated resources available per cluster.





 Networking 

Specify the networking type and uplink speed.



 Networking type 

The networking type is set to Private network only.





 Uplink speed 

The uplink speed provides two options:



* 10 Gb, which is selected by default.
* 25 Gb, which is available only for specific pods and data center locations. The following table shows the available locations for the 25 Gb uplink speed.



Asia-Pacific

Europe

NA East



Table 1. Available locations for 25 Gb uplink speed

 Geography Data center Pod 

 Asia-Pacific TOK02 02 
 Asia-Pacific TOK04 01 
 Asia-Pacific TOK05 01 









 Related links 



* [Management cluster (multizone VMware instance only)](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-mgmt-cluster)
* [Procedure to order VMware Regulated Workloads](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-orderinginstance-procedure)