vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Locations 

You can deploy IBM Cloud® Kubernetes Service clusters worldwide. When you create a cluster, its resources remain in the location that you deploy the cluster to. To work with your cluster, you can access the service via a global API endpoint.

Zoom

![IBM Cloud Kubernetes Service locations](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/locations.svg)

Figure 1. IBM Cloud Kubernetes Service locations

This image is an artistic representation and does not reflect actual political or geographic boundaries.



 IBM Cloud Kubernetes Service locations 

IBM Cloud resources are organized into a hierarchy of geographic locations. IBM Cloud Kubernetes Service is available in a subset of these locations, including worldwide multizone regions and single zone regions. Other IBM Cloud services might be available globally or within a specific location.

ibmcloud ks locations



 How locations are organized 

The following image is used as an example to explain how IBM Cloud Kubernetes Service locations are organized. For more information, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).

Zoom

![Organization of IBM Cloud Kubernetes Service locations](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/cs_regions_hierarchy.png)

Figure 1. Organization of IBM Cloud Kubernetes Service locations



Organization of IBM Cloud Kubernetes Service locations.

 Type Example Description 

 Geography North America (na) An organizational grouping that is based on geographic continents. 
 Country Canada (ca) The location's country within the geography. 
 Metro For example, Dallas (dal). The name of a city where 1 or more data centers are located.
ibmcloud oc nlb-dns ls --cluster <cluster_name_or_id>

In this example output, the mycluster-a1b2cdef345678g9hi012j3kl4567890-0002.us-south.containers.appdomain.cloud subdomain has the highest 000<n> value of 0002.

Subdomain Load Balancer Hostname Health Monitor SSL Cert Status SSL Cert Secret Name
mycluster-a1b2cdef345678g9hi012j3kl4567890-0000.us-south.containers.appdomain.cloud ["1234abcd-us-south.lb.appdomain.cloud"] None created mycluster-a1b2cdef345678g9hi012j3kl4567890-0000
mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud ["5678efgh-us-south.lb.appdomain.cloud"] None created mycluster-a1b2cdef345678g9hi012j3kl4567890-0001
mycluster-a1b2cdef345678g9hi012j3kl4567890-0002.us-south.containers.appdomain.cloud ["9012ijkl-us-south.lb.appdomain.cloud"] None created mycluster-a1b2cdef345678g9hi012j3kl4567890-0002
2. In the subdomain that you copied, change the 000<n> value in the subdomain to i00<n+1>.
<-- </section "id="section-create-cis-service-instance-examples" "> --><-- </section "id="section-create-cis-service-instance" "> --><-- <section "id="section-delete-cis-service-instance" "> --> ibmcloud cis instance-delete Delete a CIS service instance. ibmcloud cis instance-delete INSTANCE -f, --force] ! ! ! ! ! !
<-- <section "id="section-delete-cis-service-instance-options" "> --> Command options INSTANCE: The name or ID of a CIS service instance. Required.-f, --force: Delete instance without prompting for confirmation.<-- </section "id="section-delete-cis-service-instance-options" "> --><-- <section "id="section-delete-cis-service-instance-examples" "> --> Examples Delete cis instance cis-demo ibmcloud cis instance-delete cis-demo -f
<-- </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.
The functionality of this plan was split across various tiers and are now available in Enterprise Essential, Enterprise Advanced, and Enterprise Premier plans. See [Transition to Enterprise](https://cloud.ibm.com/docs/cis?topic=cis-transitioning-next-plan).





 How do I delete my CIS instance? 

To delete a CIS instance, you must first delete all global load balancers, pools, and health checks. Then delete the associated domain (zone). Go to the Overview page and click the trash can icon next to the domain name located in the Service Details section to start the deletion process.

If you are moving your domain to a different provider, be sure to migrate your DNS records and other configuration information to the new provider before activating the domain there. Activating the domain before migrating from CIS can cause your domain to changed to a [Moved state](https://cloud.ibm.com/docs/cis?topic=cis-domain-moved-status).





 I added a user to my account and gave that user permission to manage Internet Services instance(s). Why is that user facing authentication issues? 

It's possible that you did not assign "service access roles" to the user. Note that there are two separate sets of roles:



* Platform access
* Service access



You need platform access roles to create and manage service instances, while service access roles perform service-specific operations on service instances. In the console, these settings can be updated by selecting Manage > Security > Identity and Access.





 Why is my domain in Pending state? How do I activate it? 

When you add a domain to CIS, we give you a couple of name servers to configure at your registrar (or at your DNS provider, if you are adding a subdomain). The domain or subdomain remains in pending state until you configure the name servers correctly. Make sure you add both the name servers to your registrar or DNS provider. We periodically scan the public DNS system to check whether the name servers have been configured as instructed. As soon as we are able to verify the name server change (which can take up to 24 hours), we activate your domain.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-command-options-origin-certificate-delete" "> --><-- <section "id="section-command-example-origin-certificate-delete" "> --> Examples Delete origin certificate a5836c2a7ea72d2e225890caea70ae32. ibmcloud cis origin-certificate-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo
<-- </section "id="section-command-example-origin-certificate-delete" "> --><-- </section "id="section-origin-certificate-delete" "> --><-- </section "id="section-origin-certificates-cli-ref" "> --><-- <section "id="section-overview" "> --> Overview View the overview information for a domain.<-- <section "id="section-get-overview" "> --> ibmcloud cis overview Show the overview information for a domain. ibmcloud cis overview DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-get-overview-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.<-- </section "id="section-delete-cert-options" "> --><-- <section "id="section-delete-cert-examples" "> --> Examples Delete custom certificate 5a7805061c76ada191ed06f989cc3dac. ibmcloud cis certificate-delete 31984fea73a15b45779fa0df4ef62f9b 5a7805061c76ada191ed06f989cc3dac -i "cis-demo"
<-- </section "id="section-delete-cert-examples" "> --><-- </section "id="section-delete-cert" "> --><-- </section "id="section-tls" "> --><-- <section "id="section-waf" "> --> Web application firewall (WAF) Manage Web Application Firewalls by using the following waf commands.<-- <section "id="section-show-waf-setting" "> --> ibmcloud cis waf-setting Show WAF setting. ibmcloud cis waf-setting DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-show-waf-setting-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.-i, --instance: Instance name or ID.
<-- </section "id="section-command-example-origin-certificate" "> --><-- </section "id="section-origin-certificate" "> --><-- <section "id="section-origin-certificate-delete" "> --> ibmcloud cis origin-certificate-delete Delete an origin certificate. ibmcloud cis origin-certificate-delete DNS_DOMAIN_ID CERT_ID --instance INSTANCE_NAME] ! ! ! ! ! ! ! !
<-- <section "id="section-command-options-origin-certificate-delete" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.CERT_ID: The ID of Origin Certificate. 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-command-options-origin-certificate-delete" "> --><-- <section "id="section-command-example-origin-certificate-delete" "> --> Examples Delete origin certificate a5836c2a7ea72d2e225890caea70ae32. ibmcloud cis origin-certificate-delete 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i 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. Required.--output: Specify output format, only JSON is supported.<-- </section "id="section-create-cis-service-instance-options" "> --><-- <section "id="section-create-cis-service-instance-examples" "> --> Examples Create a standard plan cis instance cis-demo ibmcloud cis instance-create cis-demo standard
<-- </section "id="section-create-cis-service-instance-examples" "> --><-- </section "id="section-create-cis-service-instance" "> --><-- <section "id="section-delete-cis-service-instance" "> --> ibmcloud cis instance-delete Delete a CIS service instance. ibmcloud cis instance-delete INSTANCE -f, --force] ! ! ! ! ! !
<-- <section "id="section-delete-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-delete-a-firewall-rule-options" "> --><-- <section "id="section-delete-a-firewall-rule-examples" "> --> Examples Delete firewall-rule 372e67954025e0ba6aaa6d586b9e0b60. ibmcloud cis firewall-rule-delete 31984fea73a15b45779fa0df4ef62f9b 372e67954025e0ba6aaa6d586b9e0b60 -i "cis-demo"
<-- </section "id="section-delete-a-firewall-rule-examples" "> --><-- </section "id="section-delete-a-Firewall-rule" "> --><-- <section "id="section-validate-a-firewall-rule-expression" "> --> ibmcloud cis firewall-rule-validate Validate a firewall-rule expression. ibmcloud cis firewall-rule-validate DNS_DOMAIN_ID EXPRESSION -i, --instance INSTANCE] ! ! ! ! ! ! ! !
<-- <section "id="section-validate-a-firewall-rule-expression-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.EXPRESSION: The filter expression. For example, ip.src eq 93.184.216.0. Required.-i, --instance: Instance name or ID.
* What happened to Enterprise Package plans?

Starting on 21 June 2023, you can no longer configure the Enterprise package plan. The functionality of this plan was split across various tiers and are now available in Enterprise Essential, Enterprise Advanced, and Enterprise Premier plans. See [Transition to Enterprise](https://cloud.ibm.com/docs/cis?topic=cis-transitioning-next-plan).
* How do I delete my CIS instance?

To delete a CIS instance, you must first delete all global load balancers, pools, and health checks. Then delete the associated domain (zone). Go to the Overview page and click the trash can icon next to the domain name located in the Service Details section to start the deletion process.

If you are moving your domain to a different provider, be sure to migrate your DNS records and other configuration information to the new provider before activating the domain there. Activating the domain before migrating from CIS can cause your domain to changed to a [Moved state](https://cloud.ibm.com/docs/cis?topic=cis-domain-moved-status).
* I added a user to my account and gave that user permission to manage Internet Services instance(s). Why is that user facing authentication issues?

It's possible that you did not assign "service access roles" to the user. Note that there are two separate sets of roles:



* Platform access
* Service access



You need platform access roles to create and manage service instances, while service access roles perform service-specific operations on service instances. In the console, these settings can be updated by selecting Manage > Security > Identity and Access.
* Why is my domain in Pending state? How do I activate it?

When you add a domain to CIS, we give you a couple of name servers to configure at your registrar (or at your DNS provider, if you are adding a subdomain). The domain or subdomain remains in pending state until you configure the name servers correctly. Make sure you add both the name servers to your registrar or DNS provider.
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)
* [Best practice to secure traffic and internet application via CIS](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cis-for-optimal-securitybest-practice-configure-security-level-selectively)
* [Improving App Availability with Multizone Clusters](https://www.ibm.com/cloud/blog/announcements/improving-app-availability-multizone-clusters)
[Page Rules](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/cis/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)
Delete all services from the secondary vCenter Server instance.
2. Ensure that no NSX objects are expanded into the secondary instance that you want to delete.
3. Delete the secondary vCenter Server from the primary SSO (Single Sign-On) domain. For more information, see [Unregister vCenter Server from Single Sign-On](https://kb.vmware.com/s/article/2106736).
4. Demote the local domain controller VSI (Virtual Service Instance). For more information, see [Demoting domain controllers and domains](https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/demoting-domain-controllers-and-domains--level-200-).
5. Delete the secondary vCenter Server instance from the IBM Cloud for VMware Solutions console.
6. Repeat steps 1 - 5 for all secondary vCenter Server instances in your multisite configuration.
7. After deleting all secondary instances, you can also delete the primary instance from the IBM Cloud for VMware Solutions console.







 Related links 



* [Deleting vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletinginstance)
* [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
* [Managing virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-servers)
Deleting vCenter Server instances 

To release the components that you ordered in a VMware vCenter Server® instance, delete the instance.

When you delete a vCenter Server instance, the following components are released sequentially:



1. All deployed services
2. The Support fee for 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 vCenter Server instances from the Resources page 



1.
Select Let's get started from the welcome page to begin setting up CIS.







 Step 2. Add and configure your domain 

Next, begin protecting and improving the performance of your web service by entering your domain or a subdomain.

Specify DNS zones. You can configure the name servers for these domains or subdomains at the domain's registrar or DNS provider. Do not use CNAMEs.

The Overview screen shows your domain in Pending status and remains Pending until you complete configuring your name servers with the registrar or existing DNS provider, which is covered in Step 4.

You cannot delete the CIS instance after you add a domain. To delete the instance, delete the domain from the instance first.





 Step 3. Set up your DNS records (optional) 

Before transitioning the traffic for your domain to CIS, it is recommended that you import or recreate your DNS records in CIS. You can choose to skip this step, but if your DNS records are not configured properly in CIS, it might leave parts of your website inaccessible.

Import records by uploading your exported records from your current DNS, or manually create your DNS records. To import records, select Import records.

When you are finished, or to skip this step, select Next step.





 Step 4. Configure your name servers with the registrar or existing DNS provider 

To begin receiving the benefits of CIS, you must delegate your domain to CIS. To delegate a domain, create an NS record with the name servers provided by CIS at your domain's registrar or existing DNS provider. If you are unsure of who the registrar is for your domain, you can look it up at [whois.icann.org](https://whois.icann.org/).

If you delegate a subdomain (for instance, subdomain.example.com) from another DNS provider, you must replace the existing name server (NS) records and replace them with a name server record for each of the name servers that are provided by CIS.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.-f, --force: Attempt to delete policy without prompting for confirmation.<-- </section "id="section-delete-alert-policy-options" "> --><-- <section "id="section-delete-alert-policy-examples" "> --> Examples delete an alert policy a2633e68-1a64-2512-a321-b64a17c7db7a. ibmcloud cis alert-policy delete a2633e68-1a64-2512-a321-b64a17c7db7a -f -i "cis-demo"
<-- </section "id="section-delete-alert-policy-examples" "> --><-- </section "id="section-delete-alert-policy" "> --><-- </section "id="section-alert-policy" "> --><-- <section "id="section-alert-webhook" "> --> Alert Webhook <-- <section "id="section-list-alert-webhooks" "> --> ibmcloud cis alert-webhooks List all alert webhooks. ibmcloud cis alert-webhooks -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-opt-list-alert-webhooks" "> --> Command options -i, --instance: Instance name or ID.
Removing an instance 

You can remove an instance of the IBM Cloud Security and Compliance Center Workload Protection service.

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 data to the IBM Cloud Security and Compliance Center Workload Protection 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 Security and Compliance Center Workload Protection 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/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/icons/icon_hamburger.svg) > Resource list.
3. 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