vania-janet/multiturn-rag-retrieval-data huggingface dataset:
GET/v1/clusters/{idOrName}/subnets List subnets from your IBM Cloud infrastructure account that are bound to a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/usersubnets List user-managed subnets that are bound to a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/webhooks List all webhooks for a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/workerpools List the worker pools in a cluster. containers-kubernetes.cluster.read N/A 
 GET/v2/classic/getCluster Get detailed cluster information. containers-kubernetes.cluster.read N/A 
 GET/v2/classic/getClusters List the classic clusters that you have access to. containers-kubernetes.cluster.read N/A 
 GET/v2/classic/getVLANs List available classic infrastructure VLANs for a zone. containers-kubernetes.cluster.read N/A 
 GET/v2/getCluster View details for a cluster. containers-kubernetes.cluster.read N/A 
 GET/v2/getClusterAddons View details of the add-ons that are enabled in a cluster. containers-kubernetes.cluster.read N/A 
 GET/v2/getCRKs List the root keys for a key management service (KMS) instance. containers-kubernetes.cluster.read N/A 
 GET/v2/getFlavors List available flavors types for a VPC zone (data center). N/A N/A 
 GET/v2/getKMSInstances Get key management service (KMS) instances tied to an account containers-kubernetes.cluster.read N/A 
 GET/v2/getKubeconfig Get the cluster's kubeconfig file. Optionally include the network configuration file.
If you are logging in with a federated ID, use ibmcloud login --sso.

ibmcloud login [--sso]
2. If you have multiple IBM Cloud accounts, select the account where you want to create your cluster.
3. To create clusters in a resource group other than default, target that resource group. A cluster can be created in only one resource group, and after the cluster is created, you can't change its resource group. You must have at least the [Viewer role](https://cloud.ibm.com/docs/containers?topic=containers-userschecking-perms) for the resource group to target it.

ibmcloud target -g <resource_group_name>
4. Review the zones where you can create your cluster. In the output of the following command, zones have a Location Type of dc. To span your cluster across zones, you must create the cluster in a [multizone-capable zone](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-mz). Multizone-capable zones have a metro value in the Multizone Metro column. If you want to create a multizone cluster, you can use the IBM Cloud console, or [add more zones](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd_zone) to your cluster after the cluster is created.

ibmcloud ks locations

When you select a zone that is located outside your country, keep in mind that you might require legal authorization before data can be physically stored in a foreign country.
5. Review the worker node flavors that are available in that zone. The flavor determines the amount of virtual CPU, memory, and disk space that is set up in each worker node and made available to your apps. Worker nodes in classic clusters can be created as virtual machines on shared or dedicated infrastructure, or as bare metal machines that are dedicated to you. For more information, see [Planning your worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes).
- If the cluster name is 26 characters or fewer and the cluster name is unique in this region, the entire cluster name is included and is not modified: myclustername.<br><br><br><br> * If the cluster name is 26 characters or fewer and there is an existing cluster of the same name in this region, the entire cluster name is included and a dash with six random characters is added: myclustername-ABC123.<br> * If the cluster name is 26 characters or greater and the cluster name is unique in this region, only the first 24 characters of the cluster name are used: myveryverylongclusternam.<br> * If the cluster name is 26 characters or greater and there is an existing cluster of the same name in this region, only the first 17 characters of the cluster name are used and a dash with six random characters is added: myveryverylongclu-ABC123.<br><br><br> 
 <globally_unique_account_HASH> A globally unique HASH is created for your IBM Cloud account. All subdomains that you create for NLBs in clusters in your account use this globally unique HASH. 
 0001 The first and second characters indicate a public or a private (internal) subdomain. - 00 indicates a subdomain that has a public DNS entry.<br><br><br><br> * i0 indicates a subdomain that has a private DNS entry.<br> * The first and second characters, 00, indicate a public subdomain.<br> * The third and fourth characters, such as 01 or another number, act as a counter for each subdomain that you create.<br><br><br> 
 <region> The region that the cluster is created in. 
 containers.appdomain.cloud The subdomain for Red Hat OpenShift on IBM Cloud subdomains. 







 Enable health checks on a subdomain by creating a health monitor 

Enable health checks on the NLB IP addresses behind a single subdomain to determine whether they are available or not.
Click Infrastructure on the left navigation pane. In the Clusters table, locate the cluster that you want to delete and click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) next to the Status column.
4. In the Delete cluster window, confirm that you completed the migration of VMs to other clusters, if needed, and that you want to delete the cluster. Click Delete.







 Related links 



* [Viewing services for Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_viewingservices)
* [Expanding and contracting capacity for Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingservers)
* [Creating a VPC cluster in the console](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2clusters_vpcg2_ui)
* [Creating VPC clusters from the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2cluster_vpcg2_cli)
* [Example commands to create VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2cluster_create_vpc)
* [Creating a VPC cluster with Terraform](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2cluster_vpcg2_tf)



[Creating clusters on dedicated hosts for VPC](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-dedicated-hostscluster-create-dedicated-hosts)





 Accessing clusters 

[Accessing clusters](https://cloud.ibm.com/docs/containers?topic=containers-access_clusteraccess_cluster)



* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-access_clusterprereqs)
* [Accessing clusters through the public cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_clusteraccess_public_se)
* [Accessing clusters through the private cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_clusteraccess_private_se)



* [Accessing VPC clusters through the private cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_clustervpc_private_se)
addGroup [cluster-group create](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-create) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 View cluster groups that are attached to Satellite Config. groups [cluster-group ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-ls) <br>[cluster-group get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-get) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 Remove a cluster group. removeGroup [cluster-group rm](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-rm) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 







 Resource platform access roles 



Actions that you can take with platform access roles.

 Action API CLI None Viewer Editor Operator Administrator 

 View Kubernetes resources that are managed by Satellite Config. resources calls resource ls ![Feature available.]
* UI: From the [cluster creation page](https://cloud.ibm.com/kubernetes/catalog/create), make sure to include the KMS instance, Root key and optionally, if the KMS instance resides in a different account, the KMS account fields.
* CLI: Make sure to include the --kms-instance-id, --crk fields and also the optional--kms-account-id field if the KMS instance resides in an account different from the clusters account, such as in the following VPC example.

ibmcloud ks cluster create vpc-gen2 --name <cluster_name> --zone <vpc_zone> --vpc-id <vpc_ID> --subnet-id <vpc_subnet> --flavor <flavor> --workers <number_of_workers_per_zone> --kms-account-id <kms_account_ID> --kms-instance-id <kms_instance_ID> --crk <kms_root_key_ID>



* Creating a worker pool: For more information, see [Creating VPC worker pools](https://cloud.ibm.com/docs/containers?topic=containers-add_workersvpc_add_pool) or the [CLI reference documentation](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicli_worker_pool_create_vpc_gen2).



* UI: After selecting your cluster from the [Kubernetes clusters console](https://cloud.ibm.com/kubernetes/clusters), click Worker pools > Add. Then, make sure to include the KMS instance, Root key and optionally, if the KMS instance resides in a different account, the KMS account fields.
* CLI: Make sure to include the --kms-instance-id, --crk fields and also the optional--kms-account-id field if the KMS instance resides in an account different from the clusters account, such as in the following VPC example.
: The zone where you want to create the cluster. This value is required for standard clusters.
: Review available [classic](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-mz) or [VPC](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc) zones. When you select a zone that is located outside your country, keep in mind that you might require legal authorization before data can be physically stored in a foreign country.

--flavor FLAVOR
: Choose a flavor, or machine type, for your worker nodes. You can deploy your worker nodes as virtual machines on shared or dedicated hardware, or as physical machines on bare metal. Available physical and virtual flavors vary by the zone in which you deploy the cluster. For more information, see the documentation for the ibmcloud ks flavors (machine-types)[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_machine_types).

--name NAME
: Required: The name for the cluster. The name must start with a letter, can contain letters, numbers, periods (.), and hyphen (-), and must be 35 characters or fewer. Use a name that is unique across regions. The cluster name and the region in which the cluster is deployed form the fully qualified domain name for the Ingress subdomain. To ensure that the Ingress subdomain is unique within a region, the cluster name might be truncated and appended with a random value within the Ingress domain name.

--operating-system SYSTEM
: Optional. The operating system of the worker nodes you want to provision in your cluster. For a list of available operating systems by cluster version, see [IBM Cloud Kubernetes Service version information](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).

--version MAJOR.MINOR.PATCH
: Optional: The Kubernetes version for the cluster master node.
* [R0024, R0025: Cluster issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0024)
* [R0026: Host disk space](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0026)
* [R0033, R0034, R0035: Control plane capacity issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0033)
* [R0036: Location subdomain traffic routing](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0036)
* [R0038, R0101: Location has cluster operations in progress](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0038)
* [R0043: Layer 3 connectivity](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0043)
* [R0044: DNS issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0044)
* [R0045: Host read-only file system issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0045)
* [R0046: NTP issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0046)
* [R0047: Location health checking](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0047)
* [R0048: etcd backup failure](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0048)
satcluster2 brkiku2202thnmhb1sp0 assigned Ready satcluster sat-satc-69f2410d3ecfea9127aeec07f01475f241728a16 169.62.196.22
satcluster3 brkiltb20m0oqr29mo2g assigned Ready satcluster sat-satc-9985014f499827ddde3ce3e5bedad26af5a73263 169.62.196.29
controlplane01 brjrgp920bg4u254brr0 assigned Ready infrastructure sat-virtualser-4d7fa07cd3446b1f9d8131420f7011e60d372ca2 169.62.196.30
controlplane02 brjrdmd20dfjgaai4vc0 assigned Ready infrastructure sat-virtualser-9826f0927254b12b4018a95327bd0b45d0513f59 169.62.196.23
controlplane03 brjs18u20ohqh54svnog assigned Ready infrastructure sat-virtualser-948b454ea091bd9aeb8f0542c2e8c19b82c5bf7a 169.62.196.20
* [Context](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_mortgage_context)
* [Solution](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_mortgage_solution)
* [Results](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_mortgage_results)



* [Payment tech company streamlines developer productivity, deploying AI-enabled tools to their partners 4 times faster](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_payment_tech)



* [Context](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_payment_tech_context)
* [Solution](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_payment_tech_solution)
* [Results](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_financeuc_payment_tech_results)





[Healthcare use cases for IBM Cloud](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthcs_uc_health)



* [Healthcare provider migrates workloads from inefficient VMs to Ops-friendly containers for reporting and patient systems](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate)



* [Context](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate_context)
* [Solution](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate_solution_model)
* [Results](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate_results)
A string to filter results by, such as the name of a pod, namespace, or other string.

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





 Example 

ibmcloud sat resource ls









 Service commands 

Use these commands to view the Satellite-enabled IBM Cloud service clusters that are deployed to your Satellite location.



 ibmcloud sat service ls 

List all Satellite-enabled IBM Cloud service clusters in your location to review details such as requested host resources. For more information about how Satellite-enabled IBM Cloud service clusters request resources, see [Using host auto assignment](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-autoassign-ov).

ibmcloud sat service ls --location LOCATION [--output OUTPUT] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Cluster resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--location LOCATION
: Required. Enter the ID or name of the location where the Satellite-enabled IBM Cloud service clusters exist. To retrieve the location ID or name, run ibmcloud sat location ls.

--output JSON
: Optional. Displays the command output in JSON format.

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





 Example 

ibmcloud sat service ls --location mylocation









 Storage commands 

Use these commands to view the storage resources that run in clusters that are registered with [Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).

The ibmcloud sat storage assignment group of commands are available in beta.

Before working with your Satellite storage assignments and configurations, be sure to target the Managed from region of your Satellite by running ibmcloud sat location ls then ibmcloud target -r <region>.
Viewing clusters for vCenter Server instances 

View the summary and detailed information of the clusters that are provisioned in a VMware vCenter Server® instance.



 Procedure to view clusters for vCenter Server instances 



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 an instance to view the clusters in it.
3. Click the Infrastructure tab. In the Clusters table, view the summary about the clusters:



* Cluster name: The name and type of the cluster.
* Cluster type: The type of cluster. Types include witness, consolidated, workload, and edge gateway.
* ESXi servers: The number of VMware ESXi™ servers in the cluster.
* Storage: The type of storage that the cluster uses.
* Data center location: The IBM Cloud data center where the cluster is hosted.
* Pod: The pod where the cluster is deployed.
* Networking: Whether Public and private network or Private network only.
* Uplink speed: Whether 10 Gb or 25 Gb.
* Status: The status of the cluster. The status can have one of the following values:



* Initializing: The cluster is being created and configured.
* Modifying: The cluster is being modified.
* Available: The cluster is ready to use.
* Deleting: The cluster is being deleted.
* Deleted: The cluster is deleted.



* Actions: Click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) to delete the cluster.



4. Click a cluster name to view the ESXi server, storage, and network interface details.



ESXi server details

Additional ESXi server details

Storage details



Table 1. ESXi server details

 Item Description
[Cloud Foundry roles](https://cloud.ibm.com/docs/containers?topic=containers-cloud-foundry-rolescloud-foundry-roles)





 Locations 

[Locations](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesregions-and-zones)



* [IBM Cloud Kubernetes Service locations](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneslocations)



* [How locations are organized](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesexample_locations_org)
* [Classic multizone regions](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-mz)
* [Classic single zone regions](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-sz)
* [VPC multizone regions](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc)
* [Resources in a single zone cluster](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesregions_single_zone)
* [Resources in a multizone cluster](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesregions_multizone)



* [Accessing the global endpoint](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesendpoint)



* [Logging in to IBM Cloud](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneslogin-ic)
* [Logging in to IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneslogin-iks)
You can create context-based restrictions (CBR) for IBM Cloud Kubernetes Service resources or for specific APIs. With Context-based restrictions, you can protect the following resources.

Protect IBM Cloud Kubernetes Service resources
: [Restrict access to clusters, resource groups, or regions](https://cloud.ibm.com/docs/containers?topic=containers-cbrresources-types-cbr).

Protect specific APIs
: Restrict accessing to provisioning and managing clusters and workers. Or, restrict access to Kubernetes APIs such as viewing pods and nodes. For more information, see [Protecting specific APIs](https://cloud.ibm.com/docs/containers?topic=containers-cbrprotect-api-types-cbr).

Applications running on IBM Cloud Kubernetes Service clusters, for example web servers exposed by a Kubernetes LoadBalancer are not restricted by CBR rules.



 Protecting IBM Cloud Kubernetes Service resources 

You can create CBR rules to protect specific regions, and clusters.

Cluster
: Protects a specific IBM Cloud Kubernetes Service cluster. If you select a cluster in your CBR rule, only traffic from resources in the network zones that you associate with the rule can interact with that cluster.
: If you use the CLI, you can specify the --service-instance CLUSTER-ID option to protect a specific cluster.
: If you use the API, you can specify "name": "serviceInstance","value": "CLUSTER-ID" in the resource attributes.

Region
: Protects IBM Cloud Kubernetes Service resources in a specific region. If you select a region in your CBR rule, then only traffic from resources in the network zones that you associate with the rule can interact with resources in that region.
: If you use the CLI, you can specify the --region REGION option to protect resources in a specific region.
: If you use the API, you can specify "name": "region","value": "REGION" field in the resource attributes.

Resource group
: Protects IBM Cloud Kubernetes Service resources in a specific resource group.
* [Allowing IBM Cloud Kubernetes Service to access other IBM Cloud resources by using CBR](https://cloud.ibm.com/docs/containers?topic=containers-cbrcbr-integrations)



* [Creating network zones](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-cbr-network-zone-containers)



* [Creating network zones from the API](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-network-zone-api)
* [Creating network zones from the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-network-zone-cli)
* [Creating network zones from the console](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-network-zone-console)



* [Creating rules](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-cbr-rule-containers)



* [Creating rules by using the API](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-cbr-rule-api)
* [Creating rules from the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-cbr-rule-cli)
* [Creating rules from the console](https://cloud.ibm.com/docs/containers?topic=containers-cbrcreate-cbr-rule-console)



* [Limitations](https://cloud.ibm.com/docs/containers?topic=containers-cbrcbr-limitations)



[Example context-based restrictions scenarios](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial)



* [Understanding the scenario](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-scenario)