vania-janet/multiturn-rag-retrieval-data huggingface dataset:
2. Under Attached Block Storage for VPC volumes, select a volume.
3. On the next page, click Auto Delete to enable.
4. Confirm your selection.



Alternatively, select a data volume from the list of Block Storage for VPC(Storage > Block storage volumes). On the volume details page, under Attached instances, click the Auto delete toggle to enable or disable automatic deletion.

You can also enable Auto Delete on a new data volume when you create an instance. For more information, see [Create and attach a Block Storage for VPC volume when you create a new instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi).





 Deleting a Block Storage for VPC volume from the CLI 

Use the volume-delete command and specify the volume ID to delete a Block Storage for VPC volume.

You cannot delete an active Block Storage for VPC volume. You must first [detach it from the virtual server](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uidetach-vol-attachment-cli).

ibmcloud is volume-delete (VOLUME_NAME | VOLUME_ID) [-f, --force]

See the following example.

$ ibmcloud is volume-delete demovolume1
This will delete volume demovolume1 and cannot be undone. Continue [y/N] ?> y
Deleting volume demovolume1 under account Test Account as user test.user@ibm.com...
OK
Volume demovolume1 is deleted.





 Deleting a Block Storage for VPC volume with the API 

Make a DELETE /volumes/{id} call.

curl -X DELETE "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token"
* UI
* API
* Terraform







 Deleting your DevOps Insights data 

IBM Cloud® DevOps Insights hosts your data in a highly available and secure environment. Client and system credentials are stored on encrypted disks. Access to data is limited to only those users that require the data to support and maintain DevOps Insights. Data that is stored in DevOps Insights is indexed by a toolchain ID. When you delete a toolchain, all of the data that is related to repos that was collected as part of the toolchain is deleted.

You can delete data in the following ways:



* Delete build, test, and deploy records
* Delete DevOps Insights data for a repo by disabling
* Delete integration between Toolchain and DevOps Insights
* Delete a repo from your toolchain



For more information about toolchains, see [Creating a toolchain from an app](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-toolchains_getting_startedcreating_a_toolchain_from_an_app).

IBM doesn't manage data in DevOps Insights. If you stop using DevOps Insights, you must delete your own data. To delete your data, delete the DevOps Insights tool integration from your toolchain. If the DevOps Insights tool integration is not added again to the toolchain within seven days, the data is deleted.



 Deleting DevOps Insights data sets 

With the Manage data dashboard, you can delete DevOps Insights data for a toolchain, an environment, an application, or a branch. All DevOps Insights data for builds, test results, and deployment records are deleted. This data includes predefined and custom data, but not repo data.

Data can’t be recovered after it is deleted.

To see your manage data dashboard, complete the following steps:



1. From the IBM Cloud console, click the menu icon !
+---------------------------+-----+--------------------+--------------------+------------+--------------------+

Show more
<-- </section "id="section-big-data-log-analytics-5" "> --><-- <section "id="section-big-data-log-analytics-expand" "> --> Expand the tutorial Congratulations, you have built a log analysis pipeline with IBM Cloud. Below are additional suggestions to enhance your solution.<-- <ul> --> * Follow the Build a data lake using Object Storage]] tutorial to add a dashboard to log data. * Integrate additional systems with Event Streams using IBM® App Connect]IBM_ App Connect] ! ! ! ! .<-- </ul> --><-- </section "id="section-big-data-log-analytics-expand" "> --><-- <section "id="section-big-data-log-analytics-removal" "> --> Step 5: Remove services <-- <ol> -->1. From the Resource List]Resource List 1] !! , use the Delete or Delete service menu item in the overflow menu to remove the following service instances.
<-- <ul> -->

* log-analysis-es
* log-analysis-sql
* log-analysis-cos
* log-analysis-iae

<-- </ul> -->

2. Before deleting the log-analysis-kp service, delete the root key.3. Navigate to Manage > Access (IAM) > Service IDs]Manage _gt_ Access _IAM_ _gt_ Service IDs] !
"href": "$vpc_api_endpoint/v1/vpcs8c95b3c1-fe3c-45c-97a6-e43d14088287",
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}





 Update a file share profile in the API 

Make a PATCH /shares/{share_ID} call and specify the profile name in the profile property. The following example changes the profile to a dp2 profile.

curl -X PATCH "$rias_endpoint/v1/shares/432f1a4d-4aac-4ba1-922c-76fdbcbeb1e3?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: $iam_token" -d '{
"profile": {
"name": "dp2"
}
}'





 Delete file shares and mount targets with the API 

Before you can delete a file share, make sure that all mount targets that belong to the file share are [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-mount-target-api). The file share must be in a stable or failed state (that is, when provisioning fails).

If the file share is configured for replication, you myust take extra steps. 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.
2. Under Attached Block Storage for VPC volumes, select a volume.
3. On the next page, click Auto Delete to enable.
4. Confirm your selection.



Alternatively, select a data volume from the list of Block Storage for VPC(Storage > Block storage volumes). On the volume details page, under Attached instances, click the Auto delete toggle to enable or disable automatic deletion.

You can also enable Auto Delete on a new data volume when you create an instance. For more information, see [Create and attach a Block Storage for VPC volume when you create a new instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi).





 Deleting a Block Storage for VPC volume from the CLI 

Use the volume-delete command and specify the volume ID to delete a Block Storage for VPC volume.

You cannot delete an active Block Storage for VPC volume. You must first [detach it from the virtual server](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagedetach-vol-attachment-cli).

ibmcloud is volume-delete (VOLUME_NAME | VOLUME_ID) [-f, --force]

See the following example.

$ ibmcloud is volume-delete demovolume1
This will delete volume demovolume1 and cannot be undone. Continue [y/N] ?> y
Deleting volume demovolume1 under account Test Account as user test.user@ibm.com...
OK
Volume demovolume1 is deleted.





 Deleting a Block Storage for VPC volume with the API 

Make a DELETE /volumes/{id} call.

curl -X DELETE "$vpc_api_endpoint/v1/volumes/$volume_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token"

To verify that the volume is deleted, list the volumes by making a GET /volumes call.
Troubleshooting for creating apps 

General problems with creating applications might include apps that can't be updated, or double-byte characters that aren't displayed. In many cases, you can recover from these problems by following a few easy steps.

Have a casual question? Come chat with the development team on [IBM Cloud Dev Tools Slack](https://ic-devops-slack-invite.us-south.devops.cloud.ibm.com/). After you request your invitation, sign in and join the ask-your-question channel.



 Errors when applying Terraform plan using Schematics 

Error when creating resource instance: This plan requires a paid account. You can upgrade by adding a credit card to your account or you can select the free plan if it's available.

22: resource "ibm_resource_instance" "cos_instance"

The IBM Cloud Infrastructure credentials could not be validated.

62: resource "ibm_container_cluster" "cluster"





 Exceeded your storage quota for Kubernetes clusters 

If the build or deploy jobs fail, and you see the following message, you can delete images from your Kubernetes clusters by using CLI commands. Status: unauthorized: You have exceeded your storage quota. Delete one or more images, or review your storage quota and pricing plan.



* Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) if you don't already have it.
* Log in to IBM Cloud by using ibmcloud login, and point it to the space that you're in.
* List your images by using ibmcloud cr images.
* Delete any unused images by using ibmcloud cr image-rm <respository>:<tag>.
* Rerun the build or deploy job that failed.



For more information, see [Freeing up used storage and changing service plans or quota limits to stay within given quota limits](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_freeup).





 Accessing Kubernetes logs
Deleting webhooks from a cluster 

Some troubleshooting and debugging steps might require you to temporarily remove certain webhooks from your cluster. Follow these steps to remove webhooks, then reapply them after you have resolved your issue.



1.  List the mutating webhooks in your cluster.

oc get mutatingwebhookconfigurations
2.  For each mutating webhook, copy the component YAML file and delete the webhook.



1.  Run the command to copy the YAML file. Save the YAML file so you can reapply it later.

oc get mutatingwebhookconfigurations <WEBHOOK-NAME> -o yaml > <WEBHOOK-NAME>.yml
2.  Delete the mutating webhook.

oc delete mutatingwebhookconfigurations <WEBHOOK-NAME>



3.  List the validating webhooks in your cluster.

oc get validatingwebhookconfigurations
4.  Identify any validating webhooks that are not included in the following list.



*  alertmanagerconfigs.openshift.io
*  managed-storage-validation-webhooks
*  multus.openshift.io
*  performance-addon-operator
*  prometheusrules.openshift.io
*  snapshot.storage.k8s.io



Any validating webhook that is included in this list should not be deleted in the following steps.
5.  For each validating webhook that is not included in the previous list, copy the component YAML file and delete the webhook.



1.  Run the command to copy the YAML file. Save the YAML file so you can reapply it later.

oc get validatingwebhookconfigurations <WEBHOOK-NAME> -o yaml > <WEBHOOK-NAME>.yml
2.  Delete the validating webhook.

oc delete validatingwebhookconfigurations <WEBHOOK-NAME>



6.  When you are done troubleshooting your worker node issue, reapply the webhook YAML files.

oc apply -f <webhook-yaml-file>
Adding and deleting Veeam Backup and Replication 

You can add the Veeam® Backup and Replication service to your instance if you did not include it in your instance order. You can delete the Veeam service from your instance if you no longer need the backup service.

Before you delete the Veeam Backup and Replication service from your instance, review the following considerations.



* Block storage backups are permanently deleted.
* IBM Cloud Object Storage offload storage backups are maintained for seven days after the service removal, and then is permanently deleted.
* You have seven days after the Veeam service is deleted to open a support ticket to restore backups. For more information, see [Contacting IBM Support](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-support).
* The Veeam base, hosts, and license charges continue until the end of month.
* Storage charges stop as the storage areas are permanently deleted.





 Procedure to add Veeam Backup and Replication to VMware as a Service instances 



1. In the VMware Solutions console, click Resources > VMware as a Service from the left navigation pane.
2. In the VMware as a Service table, click the Cloud director sites tab, then click an instance name.
3. Click the Add-on services tab.
4. Click Available services.
5. On the Add-on services window, toggle the Veeam Backup and Replication on.
6. Review the new cost, select the confirmation checkboxes, and click Add.







 Procedure to delete Veeam Backup and Replication to VMware as a Service instances 



1. In the VMware Solutions console, click Resources > VMware as a Service from the left navigation pane.
2. In the VMware as a Service table, click the Cloud director sites tab, then click an instance name.
3. Click the Add-on services tab.
4. Click the vertical overflow menu in the Veeam Backup and Replication panel and click Delete.
5.
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}

The mount target is deleted in the background. Confirm the deletion by trying to view the mount target information. If you get _404 Not Found_ error, the mount target is successfully deleted.





 Delete a file share in the API 

Before you delete a file share, make sure that it is [unmounted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-mount-unmount-vsi) from all virtual server instances and that all mount targets that belong to the file share are [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uidelete-mount-target-api). Also, if the file share has a replica file share, you must remove the replication relationship. For more information, see [Remove the replication relationship with the API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-remove-replication-api).

Make a DELETE /shares/$share_id call to delete a file share. The file share must be in a stable state or failed state (that is, when provisioning fails).

Example:

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

A successful response confirms acceptance for deletion and shows file share information. The status of file share is updated to pending_deletion.

Example:

{
"access_control_mode": "vpc",
"created_at": "2023-05-30T23:31:59Z",
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}
Show more

The mount target is deleted in the background. Confirm the deletion by trying to view the mount target information. If you get _404 Not Found_ error, the mount target is successfully deleted.





 Delete a file share in the API 

Before you delete a file share, make sure that it is [unmounted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-mount-unmount-vsi) from all virtual server instances and that all mount targets that belong to the file share are [deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apidelete-mount-target-api). Also, if the file share has a replica file share, you must remove the replication relationship. For more information, see [Remove the replication relationship with the API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-remove-replication-api).

Make a DELETE /shares/$share_id call to delete a file share. The file share must be in a stable state or failed state (that is, when provisioning fails).

Example:

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

A successful response confirms acceptance for deletion and shows file share information. The status of file share is updated to pending_deletion.

Example:

{
"access_control_mode": "vpc",
If you added IAM policies to an existing service ID, such as to restrict access to a regional registry, the service ID, IAM policies, and API key for the image pull secret are reset by this command.

ibmcloud oc cluster pull-secret apply --cluster CLUSTER

Minimum required permissions:



* Operator or Administrator platform access role for the cluster in IBM Cloud Kubernetes Service
* Administrator platform access role in IBM Cloud Container Registry across all regions and resource groups. The policy can't be scoped to a particular region or resource group.



Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.





 ibmcloud oc cluster rm 

Virtual Private Cloud

Classic infrastructure

Delete a cluster. All worker nodes, apps, and containers are permanently deleted. This action can't be undone.

ibmcloud oc cluster rm --cluster CLUSTER [--force-delete-storage] [--skip-advance-permissions-check] [-f] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--force-delete-storage
: Optional: Deletes the cluster and any persistent storage that the cluster uses. Attention: If you include this option, the data that is stored in the cluster or its associated storage instances can't be recovered.

--skip-advance-permissions-check
: Optional: Skip [the check for infrastructure permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliinfra_permissions_get) before deleting the cluster. Note that if you don't have the correct infrastructure permissions, the cluster deletion might only partially succeed, such as the IBM-managed master being removed but the worker nodes unable to be removed from your infrastructure account.
If you want to fully remove ODF and all your data, you can [remove your storage cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-manage-deploymentocs-rm-crd).



1. List your PVCs and note the name of the PVC and the corresponding PV that you want to remove.

oc get pvc
2. Remove any pods that mount the PVC.



1. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you don't 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 ocs-storagecluster-cephfs
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



3. Optional Delete the PVC. Deleting the PVC deletes your app data from the storage volume.

oc delete pvc <pvc_name>







 Removing your ODF custom resource 

Complete the following steps to remove the ODF resources from your cluster.

The following steps result in data loss. Back up the data on your local volumes before you remove your ODF deployment.

When you delete the OcsCluster custom resource from your cluster, the following resources are deleted. Additionally, any apps that require access to the data on your local volumes might experience downtime. - ODF driver pods. - The MON and OSD PVCs.
* UI
* CLI
* API







 Managing Block Storage for VPC volumes 

You can manage your IBM® Cloud Block Storage for Virtual Private Cloud in the UI, from the CLI, or with the API. You can detach a volume from a virtual server instance or transfer a volume from one instance to another. You can attach a previously attached volume or rename a volume. You can set automatic volume deletion or manually delete a volume. You can assign access to a volume, and you can access volume read/write metrics for monitoring performance. Apply user tags that are associated with a backup policy to a volume to create automated backups.



 Managing Block Storage for VPC in the UI 

Use the console to manage your Block Storage for VPC volumes. In the console, you can complete the following actions.



* Detach a volume from a virtual server instance.
* Transfer a volume from one instance to another.
* Attach a previously attached Block Storage for VPC data volume.
* Rename a Block Storage for VPC volume.
* Delete a Block Storage for VPC data volume.





 Detaching a Block Storage for VPC volume from a virtual server instance 

You can detach a Block Storage for VPC volume that is attached to a virtual server instance. Detaching frees the volume for use by another instance.

To detach a volume, complete the following steps.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Locate the volume and then, click the overflow icon (...) to open a list of options.
3. From the options menu, click Detach from instance.
4. Confirm by clicking Detach instance in the open window.
: Required: The name or ID of the cluster.





 ibmcloud ks cluster rm 

Virtual Private Cloud

Classic infrastructure

Delete a cluster. All worker nodes, apps, and containers are permanently deleted. This action can't be undone.

ibmcloud ks cluster rm --cluster CLUSTER [--force-delete-storage] [--skip-advance-permissions-check] [-f] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--force-delete-storage
: Optional: Deletes the cluster and any persistent storage that the cluster uses. Attention: If you include this option, the data that is stored in the cluster or its associated storage instances can't be recovered.

--skip-advance-permissions-check
: Optional: Skip [the check for infrastructure permissions](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliinfra_permissions_get) before deleting the cluster. Note that if you don't have the correct infrastructure permissions, the cluster deletion might only partially succeed, such as the IBM-managed master being removed but the worker nodes unable to be removed from your infrastructure account. You might skip the permissions check if you want to continue an otherwise blocked operation, such as when you use multiple infrastructure accounts and can handle the infrastructure resources separately from the master, if needed later.

-f
: Optional: Force the command to run with no user prompts.

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



 Example cluster rm command 

ibmcloud ks cluster rm --cluster my_cluster







 ibmcloud ks cluster service bind 

Virtual Private Cloud

Classic infrastructure

Add an IBM Cloud service to a cluster by binding the service instance to a Kubernetes namespace. This command creates service credentials of an IBM Cloud service and stores these credentials in a Kubernetes secret in your cluster.