vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Removing ESXi servers from Cyber Recovery instances 

You can contract the capacity of your Cyber Recovery instance according to your business needs by removing VMware ESXi™ servers.



 Before you remove ESXi servers from Cyber Recovery instances 



* For the gateway cluster, you cannot add or remove ESXi servers.
* Whenever possible, remove ESXi servers by using the VMware Solutions console because changes that you make on the VMware vSphere® Web Client are not synchronized with the VMware Solutions console. Therefore, remove ESXi servers from Cyber Recovery only for on-premises ESXi servers or ESXi servers that you don't manage in the VMware Solutions console.
* When you remove ESXi servers, the servers are placed in maintenance mode, and then, all the virtual machines (VMs) running on the servers are migrated before they are removed from Cyber Recovery. For maximum of control over the relocation of VMs, place the ESXi servers to remove in maintenance mode and migrate the VMs running on them manually using the VMware vSphere Web Client. After that, remove the ESXi servers by using the VMware Solutions console.
* If you are using NFS storage, NSX-T™ instances require at least three ESXi servers for a consolidated cluster or at least two servers for any other cluster.
* If you are using vSAN™ storage, at least four ESXi servers are required.







 Procedure to remove ESXi servers from Cyber Recovery instances 



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 for which you want to contract capacity.
3. Click the Infrastructure tab.
4. In the applicable cluster table, click the cluster from which you want to remove ESXi servers.
5. In the ESXi servers section, select the servers that you want to remove and click Remove.
6. Click Delete in the Remove ESXi server window.







 Results after you remove ESXi servers from Cyber Recovery instances 



1. You might experience a slight delay on the console, while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
For more information, see [VMware Hybrid Cloud Extension](https://cloud.vmware.com/vmware-hcx).







 Considerations before you delete on-premises HCX instances 

Review the following considerations before you delete an HCX instance that was ordered for on-premises use:



1. In the VMware vSphere Web Client, go to the HCX user interface and check the following items:



1. Ensure that no HCX migration or disaster recovery operation is running.
2. Ensure that all the extended networks are removed.
3. Ensure that all the interconnect components with paired cloud sites are removed.



You must complete all the previous steps before you proceed to the next step. Otherwise, the activation key for the on-premises HCX instance is canceled. If the activation key is canceled, migrations can't be performed and errors might occur for HCX components.
2. In the IBM Cloud for VMware Solutions console, delete the on-premises HCX instance that was ordered to obtain the activation key for the on-premises HCX Manager. Ensure that the deleted instance is no longer available in the console before you proceed to the next step.

For more information, see [Deleting on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_deletingserviceinstances).
3. In the VMware vSphere Web Client, delete the on-premises HCX Manager.







 Related links 



* [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)
Click the Actions icon ![Three dots icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection/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 Security and Compliance Center Workload Protection through the command line, complete the following steps:



1. [Pre-requisite] [Installion of the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli). If the CLI is installed, continue with the next step.
2. Log in to the region in the IBM Cloud where you want to provision the instance. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)
3. Set the resource group where the instance is provisioned. Run the following command: [ibmcloud target](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_target)

By default, the default resource group is set.
4. Remove the instance. Run the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:

ibmcloud resource service-instance-delete NAME --recursive

Where NAME is the name of the instance

For example, to remove an instance, run the following command:

ibmcloud resource service-instance-delete secure-instance-01 --recursive

The --recursive option is used to delete the service keys that were associated with the instance.
[-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
: Granularly remove one or more files by the associated Cache-Tag (Enterprise plan only). This option is mutually exclusive with --all.

--host
: Granularly remove one or more files by specifying the host (Enterprise plan only). This option is mutually exclusive with --all.

--prefix
: Granularly remove one or more files by a prefix (Enterprise plan only). This option is mutually exclusive with --all.

-f, --force
: Purging all cached files without prompting for confirmation.

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

--output
: Specify output format, only JSON is supported.





 Examples 

Clear all cached assets file for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis cache-purge 31984fea73a15b45779fa0df4ef62f9b --all --force -i "cis-demo"







 ibmcloud cis cache-settings 

Get caching settings for a given DNS domain.

ibmcloud cis cache-settings DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 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 is used.
Delete access application a5836c2a7ea72d2e225890caea70ae32.

ibmcloud cis access-app-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo









 Access certificate 



 ibmcloud cis access-certificate-create 

Create an access certificate for a given DNS domain (Enterprise plan only).

ibmcloud cis access-certificate-create DNS_DOMAIN_ID --name NAME --ca-cert-file CERT_FILE [--associated-hostnames ASSOCIATED_HOSTNAMES] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

--name value
: The name of the Certificate. Required.

--ca-cert-file value
: The Root CA file for your certificates. Required.

--associated-hostnames value
: The hostnames that are prompted for this certificate.

ACCESS_APPLICATION_ID
: The ID of access application.

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





 Examples 

Create an access certificate for domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis access-certificate-create 31984fea73a15b45779fa0df4ef62f9b --name example --ca-cert-file CERT_FILE --associated-hostnames example.com -i cis-demo







 ibmcloud cis access-certificates 

List all access certificates for a given DNS domain (Enterprise plan only).

ibmcloud cis access-certificates DNS_DOMAIN_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
[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. [Pre-requisite] [Installion of the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli). If the CLI is installed, continue with the next step.
2. Log in to the region in the IBM Cloud where you want to provision the instance. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)
3. Set the resource group where the instance is provisioned. Run the following command: [ibmcloud target](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_target)

By default, the default resource group is set.
4. Remove the instance. Run the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:

ibmcloud resource service-instance-delete NAME --recursive

Where NAME is the name of the instance

For example, to remove an instance, run the following command:

ibmcloud resource service-instance-delete monitoring-instance-01 --recursive

The --recursive option is used to delete the service keys that were associated with the monitoring instance.
Deleting VMware as a Service instances 

When you no longer need them, you can delete the IBM Cloud® for VMware as a Service instances that are provisioned in your account.

You cannot delete an instance if it still has virtual data centers (VDCs) in it. Before you delete your instance, ensure that all VDCs in the instance are deleted.



  Procedure to delete 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 the instance that you want to delete.
3.  Click the Actions... menu, and then click Delete instance.

The status of the VMware as a Service instance is changed to Deleting. When the instance is deleted successfully, the instance components are released, and the status is changed to Deleted.







  Related links 



*  [Viewing and deleting virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-view-delete)
*  [VMware as a Service overview](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vmware-aas-overview)
*  [Ordering VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-ordering)
*  [Viewing VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-viewing)
*  [Visualizing your site with IBM Cloud® Monitoring](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-single-tenant-monitoring)
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-get-waf-overrides-options" "> --><-- <section "id="section-get-waf-override-examples" "> --> Examples Get a WAF overide rule under instance cis-demo. ibmcloud cis waf-override 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i "cis-demo"
<-- </section "id="section-get-waf-override-examples" "> --><-- </section "id="section-get-waf-override" "> --><-- <section "id="section-delete-waf-override" "> --> ibmcloud cis cis waf-override-delete Delete a URL based Web Application Firewall (WAF) rule. ibmcloud cis waf-override-delete DNS_DOMAIN_ID OVERRIDE_WAF_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-delete-waf-overrides-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.OVERRIDE_WAF_ID: The ID of override WAF rule. Required.-i, --instance: Instance name or ID.
ibmcloud cis glb-delete 31984fea73a15b45779fa0df4ef62f9b 699d98642c564d2e855e9661899b7252 -i "cis-demo"
<-- </section "id="section-delete-glb-examples" "> --><-- </section "id="section-delete-glb" "> --><-- <section "id="section-list-glb" "> --> ibmcloud cis glbs List all load balancers for the given domain. ibmcloud cis glbs DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-list-glb-options" "> --> 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-list-glb-options" "> --><-- <section "id="section-list-glb-examples" "> --> Examples List load balancers for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis glbs 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"
<-- </section "id="section-list-glb-examples" "> --><-- </section "id="section-list-glb" "> --><-- <section "id="section-list-glb-pools" "> --> ibmcloud cis glb-pools List all GLB pools for a given service instance.
<-- </section "id="section-show-glb-examples" "> --><-- </section "id="section-show-glb" "> --><-- <section "id="section-delete-glb" "> --> ibmcloud cis glb-delete Delete a global load balancer under a given DNS domain. ibmcloud cis glb-delete DNS_DOMAIN_ID GLB_ID -i, --instance INSTANCE] ! ! ! ! ! !
<-- <section "id="section-delete-glb-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.GLB_ID: The ID of global load balancer. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-delete-glb-options" "> --><-- <section "id="section-delete-glb-examples" "> --> Examples Delete global load balancer 699d98642c564d2e855e9661899b7252 in domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis glb-delete 31984fea73a15b45779fa0df4ef62f9b 699d98642c564d2e855e9661899b7252 -i "cis-demo"
<-- </section "id="section-delete-glb-examples" "> --><-- </section "id="section-delete-glb" "> --><-- <section "id="section-list-glb" "> --> ibmcloud cis glbs List all load balancers for the given domain.
Command options 

-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.





 Examples 

List domains for the specified domain cis-demo.

ibmcloud cis domains -i "cis-demo"







 ibmcloud cis domain-activation-check 

Perform activation check on the given domain.

ibmcloud cis domain-activation-check DNS_DOMAIN_ID [-i, --instance INSTANCE]



 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.





 Examples 

Perform activation check on the specified domain.

ibmcloud cis domain-activation-check 31984fea73a15b45779fa0df4ef62f9b -i "cis-demo"









 Domain settings 

Manipulate domain settings using the following domain-settings commands:



 ibmcloud cis domain-settings 

Get details of a feature for given domain.

ibmcloud cis domain-settings DNS_DOMAIN_ID [-g, --group GROUP | -f, --feature FEATURE] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

DNS_DOMAIN_ID
: The ID of DNS domain. Required.

-g, --group
: Display features in a same group. Valid values for group are all, domain, reliability, performance, security. This option is mutually exclusive with -f, --feature.

-f, --feature
: Feature of domain settings to check. This option is mutually exclusive with g, --group. Valid values are as follow:



* always_use_https: Redirect all requests with scheme http to https. This applies to all http requests to the domain.
! ! ! ! ! !
<-- <section "id="section-delete-waf-overrides-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.OVERRIDE_WAF_ID: The ID of override WAF rule. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.-f, --force: Attempt to delete URL based WAF rule without prompting for confirmation.<-- </section "id="section-delete-waf-overrides-options" "> --><-- <section "id="section-delete-waf-override-examples" "> --> Examples Delete a WAF overide rule under instance cis-demo. ibmcloud cis waf-override-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i "cis-demo"
<-- </section "id="section-delete-waf-override-examples" "> --><-- </section "id="section-delete-waf-override" "> --><-- </section "id="section-waf" "> --><-- <section "id="section-authenticated-origin-pull" "> --> Authenticated Origin Pull Manage Authenticated Origin Pull by using the following authenticated-origin-pull commands.<-- <section "id="section-show-authenticated-origin-pull-settings" "> --> ibmcloud cis authenticated-origin-pull-settings Get authenticated origin pull settings for a domain. ibmcloud cis authenticated-origin-pull-settings DNS_DOMAIN_ID --level zone|hostname] --hostname HOSTNAME] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! !
: The ID of DNS record. 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.





 Examples 

Get a dns record details in domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis dns-record 31984fea73a15b45779fa0df4ef62f9b 77335b17ce1853d0d76e08a8379a0376 -i "cis-demo"







 ibmcloud cis dns-record-delete 

Delete a DNS record for a given domain of a service instance.

ibmcloud cis dns-record-delete DNS_DOMAIN_ID DNS_RECORD_ID [-i, --instance INSTANCE]



 Command options 

`DNS_DOMAIN_ID
: The ID of DNS domain. Required.

DNS_RECORD_ID
: The ID of DNS record. Required.

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





 Examples 

Delete a dns record in domain 31984fea73a15b45779fa0df4ef62f9b.

ibmcloud cis dns-record-delete 31984fea73a15b45779fa0df4ef62f9b 77335b17ce1853d0d76e08a8379a0376 -i "cis-demo"







 ibmcloud cis dns-records 

List all DNS records for a given domain of a service instance.
In addition, you can now control what content gets cached by CIS and how long it stays cached. Go to Performance > Caching to define the global caching level and the browser expiration. You can customize the global security and caching rules with Page Rules. Page Rules enable fine-grained configuration using specific domain paths. As example with Page Rules, you could decide to cache all contents under /assets for 3 days:

Zoom

![Page Rules](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/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)
Deleting a webhook using the CLI 

To delete a webhook using the CLI, run the following command.

ibmcloud cis alert-webhook-delete WEBHOOK_ID [-i, --instance INSTANCE] [-f, --force]

Where:



* WEBHOOK_ID is the ID of webhook.
* i, --instance value is the instance name or ID. If not set, the context instance specified by 'cis instance-set INSTANCE' is used.
* -f, --force attempts to delete webhook without prompting for confirmation.









 Configuring webhooks using the API 

To call these methods, you must be assigned one or more IAM access roles.



* internet-svcs.zones.read
* internet-svcs.zones.update



You can check your access by going to Users > name > Access policies.



 Creating a webhook using the API 

Creating a webhook alert is a two step process. First, create the webhook, then use the ID in the response that you receive to create the alert.

To create a webhook by using the API, follow these steps:



1. Set up your API environment with the correct variables.
2. Store your the following variable to be used in the API command:



* crn: the full url-encoded CRN of the service instance.
* name: the name of the webhook.
* url: the URL of the webhook.
* secret: the optional secret or API key needed to use the webhook.



3. When all variables are initiated, create the webhook:



curl -X POST https://api.cis.cloud.ibm.com/v1/:crn/alerting/destinations/webhooks
-H 'content-type: application/json'
-H 'x-auth-user-token: Bearer xxxxxx'
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.-f, --force: Attempt to delete webhook without prompting for confirmation.<-- </section "id="section-delete-alert-webhook-options" "> --><-- <section "id="section-delete-alert-webhook-examples" "> --> Examples delete an alert webhook b2633e68-9a64-4519-b361-a64a67c8db8e. ibmcloud cis alert-webhook-delete b2633e68-9a64-4519-b361-a64a67c8db8e -f -i "cis-demo"
<-- </section "id="section-delete-alert-webhook-examples" "> --><-- </section "id="section-delete-alert-webhook" "> --><-- </section "id="section-alert-webhook" "> --><-- <section "id="section-private-endpoint-support" "> --> Private endpoint support To ensure that you have enhanced control and security over your data when you use the CIS CLI, you have the option of using private routes to CIS endpoints. Private routes are not accessible or reachable over the internet. By using CIS private endpoints, you can protect your data from threats from the public network and logically extend your private network.Regional support is provided for a limited number of CLI commands. The following regions support private endpoints:<-- <ul> --> * us-south * us-east<-- </ul> --><-- <section "id="section-logging-in-cli-private-endpoint" "> --> Logging in to the CLI with a private endpoint Use the following command to log in to a private endpoint by using the CLI: ibmcloud login -a private.cloud.ibm.com