vania-janet/multiturn-rag-retrieval-data huggingface dataset:
<-- </section "id="section-delete-cis-service-instance-examples" "> --><-- </section "id="section-delete-cis-service-instance" "> --><-- <section "id="section-update-cis-service-instance" "> --> ibmcloud cis instance-update Update a CIS service instance. ibmcloud cis instance-update INSTANCE --name NAME] --plan PLAN] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-update-cis-service-instance-options" "> --> Command options INSTANCE: The name or ID of a CIS service instance. Required.NAME: The name of CIS service instance.PLAN: The name or ID of a service plan.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-cis-service-instance-options" "> --><-- <section "id="section-update-cis-service-instance-examples" "> --> Examples Update cis instance cis-demo to enterprise-usage plan. ibmcloud cis instance-update cis-demo --plan enterprise-usage
<-- </section "id="section-update-cis-service-instance-examples" "> --><-- </section "id="section-update-cis-service-instance" "> --><-- <section "id="section-get-cis-service-instance" "> --> ibmcloud cis instance Show details of a CIS service instance. ibmcloud cis instance INSTANCE --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-get-cis-service-instance-options" "> --> Command options INSTANCE: The name or ID of a CIS service instance.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-command-options-page-rule-delete" "> --><-- <section "id="section-command-examples-page-rule-delete" "> --> Examples Delete page rule a5836c2a7ea72d2e225890caea70ae32. ibmcloud cis page-rule-update 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo
<-- </section "id="section-command-examples-page-rule-delete" "> --><-- </section "id="section-page-rule-delete" "> --><-- <section "id="section-page-rules" "> --> ibmcloud cis page-rules List page rules of the DNS domain. ibmcloud cis page-rules DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-page-rules" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-page-rules" "> --><-- <section "id="section-command-examples-page-rules" "> --> Examples List all page rules in domain 31984fea73a15b45779fa0df4ef62f9b.
<-- </section "id="section-list-cis-service-instances-examples" "> --><-- </section "id="section-list-cis-service-instances" "> --><-- <section "id="section-set-context-cis-service-instance" "> --> ibmcloud cis instance-set Set context service instance to operate. ibmcloud cis instance-set INSTANCE_NAME] --unset] ! ! ! ! ! !
<-- <section "id="section-set-service-instances-options" "> --> Command options INSTANCE_NAME: The name of CIS service instance. If it is presented, set the context instance to operate, if not, show the current context instance.--unset: Unset context instance.<-- </section "id="section-set-service-instances-options" "> --><-- <section "id="section-set-context-cis-service-examples" "> --> Examples Set context service instance to cis-demo ibmcloud cis instance-set cis-demo
<-- </section "id="section-set-context-cis-service-examples" "> --><-- </section "id="section-set-context-cis-service-instance" "> --><-- <section "id="section-create-cis-service-instance" "> --> ibmcloud cis instance-create Create a CIS service instance. ibmcloud cis instance-create INSTANCE_NAME PLAN --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-create-cis-service-instance-options" "> --> Command options INSTANCE_NAME: The name of CIS service instance. Required.PLAN: The name or ID of a service plan.
Deleting on-premises HCX instances 

Use this procedure to delete the VMware® HCX™ instances that you ordered for on-premises use.



  Before you begin 

Ensure that you reviewed the considerations in [Considerations before you delete on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_considerations).





  Procedure to delete on-premises HCX instances 



1.  From the IBM Cloud® for VMware Solutions console, click Licenses from the left navigation pane.
2.  Scroll down to the On-premises HCX activation keys table and find the instance to delete.
3.  In the Actions column, click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg).
4.  In the Delete instance window, click OK. The status of the instance is changed to Removing. When the instance deletion is completed, the instance is no longer available in the On-premises HCX activation keys table.







  Related links 



*  [Ordering on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_orderingserviceinstances)
*  [Viewing on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_viewingserviceinstances)
*  [Glossary of HCX terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_glossary)
*  [VMware Hybrid Cloud Extension documentation](https://cloud.vmware.com/vmware-hcx/resources)
Delete your DNS records from CIS. For more information, see [Deleting DNS records](https://cloud.ibm.com/docs/cis?topic=cis-set-up-your-dns-for-cisdeleting-dns-records).
3. Delete each project that you created. When you delete a project, all the components contained in that project are also deleted. For more information, see [Delete a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectdelete-project).



Note that your custom domain is not deleted, but is no longer associated with the application that you created.
<-- </section "id="section-delete-ratelimit-rule-examples" "> --><-- </section "id="section-delete-ratelimit-rule" "> --><-- </section "id="section-ratelimit" "> --><-- <section "id="section-resource-instance" "> --> Resource instance Manipulate CIS Service instances by using the following instance commands.<-- <section "id="section-list-cis-service-instances" "> --> ibmcloud cis instances List all CIS service instances. ibmcloud cis instances --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-list-service-instances-options" "> --> Command options --output: Specify output format, only JSON is supported.<-- </section "id="section-list-service-instances-options" "> --><-- <section "id="section-list-cis-service-instances-examples" "> --> Examples List all CIS instance in current account. ibmcloud cis instances
<-- </section "id="section-list-cis-service-instances-examples" "> --><-- </section "id="section-list-cis-service-instances" "> --><-- <section "id="section-set-context-cis-service-instance" "> --> ibmcloud cis instance-set Set context service instance to operate. ibmcloud cis instance-set INSTANCE_NAME] --unset] ! ! ! ! ! !
<-- <section "id="section-set-service-instances-options" "> --> Command options INSTANCE_NAME: The name of CIS service instance.
After the billing cycle ends, the status of the device changes from ACTIVE to RECLAIM until the reclaim process completes which can take days or weeks into the following month.

After the ESXi server reclaim process completes, the subnets and VLANs are deleted, and the instance deletion is completed.

You can review the next account invoice to confirm that you are no longer billed for this instance. From the IBM Cloud console, click Manage > Billing and usage, then click Invoices.



 Procedure to delete Cyber Recovery instances from the Resources page 



1. From the VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, find the instance to delete.
3. Click the vertical overflow menu next to the Status column, and then click Delete instance. The status of the instance is changed to Deleting. When the instance is deleted successfully, the components of the instance are released, and the status of the instance is changed to Deleted.
4. If you want to delete the instance record from the VMware Solutions console, complete the following steps:



1. Click the vertical overflow menu next to the Status column, and then click Delete from the console.
2. In the Delete instance window, click Delete.









 Procedure to delete Cyber Recovery instances from the instance details page 



1. From the IBM Cloud for VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click the instance to delete.
3. Click Actions next to vCenter console, and then click Delete instance. The status of the instance is changed to Deleting. When the instance is deleted successfully, the components of the instance are released, and the status of the instance is changed to Deleted.
4. If you want to delete the instance record from the VMware Solutions console, complete the following steps:



1. Click Actions again and then click Delete from the console.
2. In the Delete instance window, click Delete.









 Related links
"cis_crn": "crn:v1:bluemix:public:internet-svcs:global:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0::"
},
"name": "my-cis-instance",
"type": "cis"
},
"wrap_info": null,
"warnings": null,
"auth": null
}







 Delete a configuration 

Removes a configuration for a secrets engine that serves as the backend for a specific type of secret. You can delete configurations for the following secret types: public_cert, private_cert



 Example requests 

Delete a public certificate authority configuration.

curl -X DELETE 'https://https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/public_cert/config/certificate_authorities/my-lets-encrypt' -H 'X-Vault-Token: {Vault-Token}'

Delete the DNS provider configuration.

curl -X DELETE 'https://https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/public_cert/config/dns_providers/my-cis-instance' -H 'X-Vault-Token: {Vault-Token}'

Delete a private certificate authority configuration.

curl -X DELETE 'https://https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/private_cert/config/root_certificate_authorities/my-root-ca' -H 'X-Vault-Token: {Vault-Token}'





 Example response 

A successful request returns an HTTP 204 No Content response.
Removing an instance 

You can remove an instance of the IBM Cloud Monitoring service from the IBM Cloud UI or through the command line.

When you remove an instance from the IBM Cloud, consider the following information to tidy up:



1. Write down the list of sources that forward metrics to the IBM Cloud Monitoring instance that you want to remove. You must remove the agent from each source.
2. Remove permissions that are granted to users to work with the instance.

If you use an access group to manage permissions to access the instance, you must remove the access group.

If you use an access group to manage permissions to access different service instances, you must remove the policies that grant permissions to the instance that you want to remove.

If you grant individual policies to users, you must gather the information of each user that has access to the instance. Then, you must remove one by one the policies that relate to the instance that you want to delete.



Then, delete the instance from the IBM Cloud Dashboard.



 Removing an instance through the IBM Cloud UI 

To remove an instance of IBM Cloud Monitoring by using the IBM Cloud UI, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Observability.
3. Select Monitoring. The list of the instances is displayed.
4. Click the Actions icon ![Three dots icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/actions.png) next to the instance you want to delete and click Delete.







 Removing an instance through the CLI 

To remove an instance of IBM Cloud Monitoring through the command line, complete the following steps:



1.
When the instance is deleted successfully, the components of the instance are released, and the status of the instance is changed to Deleted.
4. If you want to delete the instance record from the IBM Cloud for VMware Solutions console, complete the following steps:



1. In the Actions column, click the Delete icon again.
2. In the Delete instance window, click OK.









 Procedure to delete instances from the instance details page 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance to delete.
3. Click the vertical overflow menu icon next to vCenter console and click Delete instance. The status of the instance is changed to Deleting. When the instance is deleted successfully, the components of the instance are released, and the status of the instance is changed to Deleted.
4. If you want to delete the instance record from the IBM Cloud for VMware Solutions console, complete the following steps:



1. Click the vertical overflow menu icon next to vCenter console again and click Delete instance.
2. In the Delete instance window, click OK.









 Related links 



* [Deleting vCenter Server with Hybridity Bundle instances in a multisite configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_deletinginstance_multi)
* [Viewing vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_viewinginstances)
* [Expanding and contracting capacity for vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_addingremovingservers)
* [Managing virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-servers)
[Page Rules](https://cloud.ibm.com/docs-content/v1/content/cbb80bf851fb762a838129cba09d5674f8bfffda/Registry/includes/solution-tutorials/includes/solution-tutorials/images/solution32-multi-region-k8s-cis/cis-pagerules.png)

Page Rules







 Step 5: Remove resources 



 Remove Kubernetes Cluster resources 



1. Remove the Ingress, you can do so by running the following command:

kubectl delete -f glb-ingress.yaml
2. Remove the service, you can do so by running the following command:

kubectl delete service hello-world-service
3. Remove the deployment, you can do so by running the following command:

kubectl delete deployment hello-world-deployment
4. Delete the clusters if you created them specifically for this tutorial.







 Remove CIS resources 



1. Remove the GLB.
2. Remove the origin pools.
3. Remove the health checks.
4. Update the DNS for your custom domain.
5. Delete the CIS instance if you created it specifically for this tutorial.









 Related content 



* [IBM Cloud Internet Services](https://cloud.ibm.com/docs/cis?topic=cis-getting-started)
* [Manage your IBM CIS for optimal security](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cis-for-optimal-securitymanage-your-ibm-cis-for-optimal-security)
* [Kubernetes Service](https://cloud.ibm.com/docs/containers)
* [Building containers from images](https://cloud.ibm.com/docs/containers?topic=containers-images)
Deleting Cyber Recovery instances 

To release the components that you ordered in a Cyber Recovery instance, delete the instance.

When you delete a Cyber Recovery instance, the following components are released sequentially:



1. All deployed services
2. The Support fee for VMware NSX-T™ instances or the Support and Services fee for NSX-V instances
3. VMware® product licenses
4. VMware ESXi™ servers
5. Subnets
6. VLANs



Review the following information before you proceed.



* Any existing VLANs that you own, outside of IBM Cloud® for VMware Solutions, are not deleted.
* Any VLANs that contain your own resources, such as gateways or Veeam® servers are not deleted.
* Any VLANs or subnets without attached gateways or servers are deleted even though you might have IP addresses assigned to it from the subnets to your VMs.



Because of resource dependencies, the components in your instance are not released immediately when you delete the instance. For example, the VLANs and the VLAN primary subnets cannot be deleted until the ESXi servers are fully reclaimed by the IBM Cloud infrastructure, which happens at the end of the IBM Cloud infrastructure billing cycle. At the end of the billing cycle, which is typically 30 days, the subnets and VLANs are deleted and the instance deletion is completed.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted instance.

The instance remains in Deleting status and the monthly ESXi servers are available for the remainder of the account monthly billing cycle. After the billing cycle ends, the status of the device changes from ACTIVE to RECLAIM until the reclaim process completes which can take days or weeks into the following month.

After the ESXi server reclaim process completes, the subnets and VLANs are deleted, and the instance deletion is completed.

You can review the next account invoice to confirm that you are no longer billed for this instance. From the IBM Cloud console, click Manage > Billing and usage, then click Invoices.



 Procedure to delete Cyber Recovery instances from the Resources page 



1.
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/action-menu-icon.svg) to open the service instance actions menu.
4. Click Delete service.







 Deleting instances from the IBM Cloud CLI 

You can delete an instance of Hyper Protect Crypto Services from the IBM Cloud CLI by running the following command:

ibmcloud resource service-instance-delete <instance_name|instance_ID>

Replace instance_name with your instance name and instance_ID with your [service instance ID](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-retrieve-instance-ID). You can use either the instance name or the service instance ID to run the command.
Securing your data in CIS 

To ensure that you can securely manage your data when you use IBM Cloud® Internet Services, it is important to know exactly what data is stored and encrypted and how to delete any stored personal data.



  How your data is stored and encrypted in CIS 

CIS interacts with Cloudflare services using a channel that is fully encrypted end-to-end using Transport Layer Security (TLS) 1.2. CIS does not store any customer data. Configuration data about your specific CIS configuration is encrypted in transit and at rest. CIS configuration data is deleted on your request through the UI, CLI, or API.





  Protecting your sensitive data in CIS 

All data related to CIS configuration is not considered sensitive data. The configuration data is encrypted at rest. No customer-managed keys are managed by the CIS offering. Therefore, neither Key Protect nor Hyper Protect Crypto Services are used.



  Working with customer-managed keys for CIS 

No customer-managed keys are managed by the CIS offering.







  Deleting your data in CIS 

The CIS configuration data is deleted on request through the UI, CLI or API.



  Deleting CIS instances 

The CIS data retention policy describes how long your data is stored after you delete the service. The data retention policy is included in the CIS service description, which you can find in [IBM Cloud Terms](https://cloud.ibm.com/docs/overview?topic=overview-terms). When a CIS instance is deleted by the UI, CLI, or API, the instance data is retained for seven days from deletion.

Before deleting an instance, all the domains in the instance must be removed.

Deleting the CIS instance removes all data.





  Restoring deleted data for CIS 

CIS can currently restore the deleted instance. After you delete an instance of CIS, you can restore the deleted service instance within the data retention period of seven days. After the seven-day period expires, the service instance is permanently deleted.

To view which service instances are available for restoration, use the ibmcloud resource reclamations command. To restore a deleted service instance, use the ibmcloud resource reclamation-restore command.
Find the instance you that want to delete and click the settings button to the right of the instance. Then, click Delete (the name of your instance).

To delete the operator, navigate back to the Installed Operators page and click the settings button to the right of the IBM Blockchain Platform operator. Then, click Uninstall Operator.

Alternatively, you can use the CLI to switch to the OpenShift project that you created for your blockchain network:


oc project <PROJECT_NAME>


And then remove any instances or the IBM Blockchain operator by using the OpenShift CLI. For example, this command would delete the operator:


kubectl delete deployment ibp-operator






 Next steps 

When you access your console, you can use the Nodes tab of your console UI to create CAs, peers, or an ordering service. See the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-ibp-console-build-networkibp-console-build-network) to get started with the console.

To learn how to manage the users that can access the console, view the logs of your console and your blockchain components, see [Administering your console](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-console-icp-manageconsole-icp-manage).





 Support 

Support is provided for the paid version of the Red Hat Marketplace offering and support cases can be opened through the Red Hat Marketplace [support portal](https://marketplace.redhat.com/en-us/support). Customers that use the trial version from Red Hat Marketplace, can refer to [self-help resources](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-blockchain-supportblockchain-support-resources) for assistance.





 Create a project for your IBM Blockchain Platform deployment 

Before you can deploy the operator, you need to create a project for your deployment of IBM Blockchain Platform.
ibmcloud cis access-policy-delete DNS_DOMAIN_ID ACCESS_APPLICATION_ID ACCESS_POLICY_ID [-i, --instance INSTANCE]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

ACCESS_APPLICATION_ID
: The ID of access application. Required.

ACCESS_POLICY_ID
: The ID of access policy. Required.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.





 Examples 

Delete access policy 65fe21071877669cc69544642bc6c4c4.

ibmcloud cis access-policy-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 65fe21071877669cc69544642bc6c4c4 -i cis-demo









 Cache 

Manipulate how the cache performs using the following cache commands:



 ibmcloud cis cache-purge 

Clear cached assets file by file or entirely for a given DNS domain to guarantee served assets are updated.

ibmcloud cis cache-purge DNS_DOMAIN_ID (--all | --file file1 --file file2...｜--tag tag1 --tag tag2...|--host host1 --host host...| --prefix prefix1 --prefix prefix2...) [-f, --force] [-i, --instance INSTANCE_NAME] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

--all
: Purging all cached files. This option is mutually exclusive with --file.

--file
: Granularly remove one or more files by specifying URLs. This option is mutually exclusive with --all.

--tag