vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* For Kubernetes on Classic infrastructure see reference documentation [Creating classic cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-classic&interface=ui).
* Choose a resource group.
* Uncheck all zones except one.
* Scale down to 1 Worker nodes per zone.
* Choose the smallest Worker Pool flavor.
* Enter a Cluster namemycluster-tpcr.
* Click Create.



When the cluster is provisioned, leave the browser (cluster overview) tab open and available for later. You can move on to the next steps nonetheless.





 Step 3: Create a trusted profile 



1. In a new browser tab (IAM trusted profile), use the top navigation Manage > Access (IAM), then Trusted profiles on the left to get to the [trusted profiles](https://cloud.ibm.com/iam/trusted-profiles/create) overview. Then Create a new trusted profile.
2. Use TPwithCR as Name and type in a short Description, e.g., Test trusted profile with compute resource. Thereafter, click Continue.
3. In the second form tab under Select trusted entity type pick Compute resources and a dialog Create trust relationship appears. There, choose Kubernetes as Compute service type.
4. Next, you can decide between either all or specific service resources.



* Click on Specific resources and the next form field appears.
* In Enter or select an instance, click Add resource. Then, in the field Allow access to select the Kubernetes cluster mycluster-tpcr.
* Then, enter tptest as value for Namespace. Leave the field for Service account as is to go with the default.
* Finish by clicking Continue.



5. Next, click on Access policy. In the list of services, select All Identity and Access enabled services and click Next. Go with All resources, click Next again, then select Viewer, and again click on Next. In the section Roles and actions, select Reader for Service access and Viewer for Platform access. When done, click Next and finally Add.
Create three Kubernetes clusters in IBM Cloud in the regions you prefer. These clusters can be located in any region you want, although for high performance they should be relatively close together. For example, the regions, East Coast US, and West Coast US, and Canada are better than the regions, West Coast US, London, and Tokyo.
2. Deploy a new IBM Blockchain Platform instance on the cluster in one of the regions. If you are using a Kubernetes cluster on IBM Cloud, you need to link the service instance to the cluster. Repeat these steps in the second and third regions. When you are finished, you have three separate IBM Blockchain Platform instances linked to three separate clusters, each in a different region, and three separate consoles.



This tutorial assumes that an ordering service exists with a channel defined that the peers can join.



 Step one: Create the peer organization's CA and metadata in cluster one 



1. Deploy a CA in the first cluster by following the instructions in the Build a network tutorial for [Creating your peer organization's CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-create-CA-org1CA). Make note of the values of the CA enroll ID and secret because you need to provide those values when you import the CA into other clusters.
2. After the CA tile status indicator is green, Running, follow the instructions to [Register identities with your CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-use-CA-org1). In those instructions, you create two identities, one for the peer and another for the peer's organization admin identity.
3. [Create the peer's organization MSP definition](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-create-peers-org1) for the peer's organization in the first cluster.
4.
: No longer do you have to manually specify the networking and worker node details to create a cluster, or enable security integrations such as logging and monitoring after creation. Instead, you can try out the technical preview to create a multizone cluster with nine worker nodes and encryption, logging, and monitoring already enabled. For more information, see [Creating a cluster by using an IBM Cloud Schematics template](https://cloud.ibm.com/docs/openshift?topic=openshift-templates&interface=ui).

IBM Cloud Object Storage plug-in
: Version 2.1.3 is [released](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog). Master fix pack update change log documentation
: Master fix pack update change log documentation is available for version [1.21.4_ 1528](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1211214_1528), [1.20.10_1550](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12012010_1550), [1.19.14_1557](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911914_1557), and [1.18.20_1562](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1562).





 23 August 2021 

Registry token update
: Registry tokens are no longer accepted for authentication in IBM Cloud Container Registry. Update your clusters to use IBM Cloud IAM authentication. For more information, see [Accessing IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_access). For more information about Registry token deprecation, see [IBM Cloud Container Registry Deprecates Registry Tokens for Authentication](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-container-registry-deprecates-registry-tokens-for-authentication).
[Create a new VPC subnet](https://cloud.ibm.com/vpc/provision/network) in the same VPC and in one or more zones where your cluster has worker nodes. Make sure that you create a subnet that can support both the number of worker nodes and services that you plan to create in your cluster. The default CIDR size of each VPC subnet is /24, which can support up to 253 worker nodes and services. To check your cluster's VPC and zones, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.
2. Create a new worker pool in your cluster.

ibmcloud oc worker-pool create vpc-gen2 --name <name> --cluster <cluster_name_or_ID> --flavor <flavor> --size-per-zone <number_of_worker_nodes> --label <key>=<value>
3. Using the ID for the larger subnets that you created in step 1, add the zones to the worker pool. Repeat the following command for each zone and subnet.

ibmcloud oc zone add vpc-gen2 --zone <zone> --subnet-id <subnet_id> --cluster <cluster_name_or_ID> --worker-pool <worker_pool_name>
4. After a few minutes, verify that your LoadBalancer service is successfully provisioned onto one of the new subnets. If the service is provisioned successfully, no Warning or Error events are displayed.

oc describe svc <kubernetes_lb_service_name>
ibmcloud ks zone add classic --zone <zone> --cluster <cluster_name_or_ID> --worker-pool <pool_name> --private-vlan <private_VLAN_ID> --public-vlan <public_VLAN_ID>





 Creating a single-zone classic cluster with Terraform 

Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud platform infrastructure and resources, including classic clusters. To create a classic cluster with Terraform, you first create a Terraform configuration file that declares the type of cluster resource you want to create. Then, you apply the Terraform configuration file. For more information on Terraform, see [About Terraform on IBM Cloud](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-about).

Before you begin:



* [Install the Terraform CLI and the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_clitf_installation).
* Make sure you have an IBM Cloud [API key](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uicreate_user_key).





1. Create a Terraform provider file. Save the file in your Terraform directory. For more information, see the [Terraform IBM Cloud Provider documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs).

Example Terraform provider file.

terraform {
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
version = "1.53.0"
}
}
}

provider "ibm" {
region = "us-south"
ibmcloud_api_key = "<api-key>"
}
2. Create a Terraform configuration file for a classic cluster. Save the file in your Terraform directory.
[Set up Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).
3. [Create a Satellite cluster](https://cloud.ibm.com/docs/satellite?topic=openshift-satellite-clusters) that runs on compute hosts in Amazon Web Services (AWS). Make sure that you select the Enable cluster admin access for Satellite Config option when you create the cluster. If you don't enable Administrator (admin) access for Satellite Config when creating your cluster, you must re-create your cluster and enable admin access before you can deploy storage. For more information about how to add hosts from AWS to your Satellite location so that you can assign them to a cluster, see [Adding AWS hosts to Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-awsaws-host-attach).
4. Manually provision an [AWS EFS file system](https://docs.aws.amazon.com/efs/latest/ug/gs-step-two-create-efs-resources.html) in your AWS account. Make sure that the EFS device is in the same VPC and subnet that you used for your AWS hosts, and that your hosts and EFS device use the same security group.



Before you begin, review the [parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-efs-csi-driveraws-efs-csi-driver-parameter-reference) for the template version that you want to use.





 Creating and assigning a configuration in the console 



1. [From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6.
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) and select the geography, data center, and pod to host the cluster.
2. Specify the cluster name.
3. Select the CPU model, RAM size, and the number of bare metal servers.



7. For network interface settings, enter the hostname prefix, and then select the uplink speed and network type.
8. On the Summary pane, verify the cluster configuration before you add the cluster.



1. Review the settings for the cluster.
2. Review the estimated price of the cluster. Click Pricing details to generate a PDF summary. To save or print your order summary, click the Print or the Download icon ![Download icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/download.svg) on the upper right of the PDF window.
3. Click the link or links of the terms that apply to your order, and confirm that you agree with these terms before you add the cluster.
4. Click Create.









 Results after you add clusters to vCenter Server instances 



1. The deployment of the cluster starts automatically and the status of the cluster is changed to Initializing. You can check the status of the deployment by viewing the deployment history on the instance details page.
2. When the cluster is ready to use, its status changes to Available. The newly added cluster is enabled with vSphere High Availability (HA) and vSphere Distributed Resource Scheduler (DRS).



You cannot change the cluster name. Changing the cluster name might cause the add or delete ESXi servers operations in the cluster to fail.





 Related links
ibmcloud oc zone add classic --zone <zone> --cluster <cluster_name_or_ID> --worker-pool <pool_name> --private-vlan <private_VLAN_ID> --public-vlan <public_VLAN_ID>





 Creating a single-zone classic cluster with Terraform 

Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud platform infrastructure and resources, including classic clusters. To create a classic cluster with Terraform, you first create a Terraform configuration file that declares the type of cluster resource you want to create. Then, you apply the Terraform configuration file. For more information on Terraform, see [About Terraform on IBM Cloud](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-about).

Before you begin:



* [Install the Terraform CLI and the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_clitf_installation).
* Make sure you have an IBM Cloud [API key](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uicreate_user_key).





1. Create a Terraform provider file. Save the file in your Terraform directory. For more information, see the [Terraform IBM Cloud Provider documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs).

Example Terraform provider file.

terraform {
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
version = "1.53.0"
}
}
}

provider "ibm" {
region = "us-south"
ibmcloud_api_key = "<api-key>"
}
2. Create a Terraform configuration file for a classic cluster. Save the file in your Terraform directory.
After you create a [classic](https://cloud.ibm.com/docs/containers?topic=containers-getting-startedclusters_gs) or a [VPC](https://cloud.ibm.com/docs/containers?topic=containers-getting-startedvpc-gen2-gs) cluster with a public gateway, deploy your first app. You can use a sample websphere-liberty Java application server that IBM provides and deploy the app to your cluster by using the Kubernetes dashboard.

The [Kubernetes dashboard](https://github.com/kubernetes/dashboard) is a web console component that is provided by the open source community and installed in your cluster by default. Use the Kubernetes dashboard to manage Kubernetes resources that are within your cluster, such as pods, services, and namespaces. Not sure what all these Kubernetes resources mean? Check out the overview for [container](https://cloud.ibm.com/docs/containers?topic=containers-overview) and [Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-overview) concepts.



 Deploying an app to a standard cluster and exposing with a load balancer 

Follow the steps to deploy an example websphere-liberty to your standard cluster.



1. Select your cluster from the [cluster list](https://cloud.ibm.com/kubernetes/clusters) to open the details for your cluster.
2. Click Kubernetes dashboard.
3. From the menu bar, click the Create new resource icon (+).
4. Select the Create from form tab.



1. Enter a name for your app, such as liberty.
2. Enter websphere-liberty for your container image. Remember that your cluster's VPC subnet must have a public gateway so that the cluster can pull an image from DockerHub.
3. Enter the number of pods for your app deployment, such as 1.
4.
All subnets that were automatically ordered during cluster creation are immediately marked for deletion after you delete a cluster, and you can't reuse the subnets to create a new cluster.

Before you begin



* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
* To reuse user-managed private subnets from a cluster that you no longer need, delete the unneeded cluster.

ibmcloud ks cluster rm --cluster <cluster_name_or_ID>
* The 172.16.0.0/16, 172.18.0.0/16, 172.19.0.0/16, and 172.20.0.0/16 subnet ranges are prohibited.



To create a cluster by using existing subnets:



1. Get the subnet ID and the ID of the VLAN that the subnet is on.

ibmcloud ks subnets --provider classic

In this example output, the subnet ID is 1602829 and the VLAN ID is 2234945:

GETting subnet list...
OK
ID Network Gateway VLAN ID Type Bound Cluster
1550165 10.xxx.xx.xxx/26 10.xxx.xx.xxx 2234947 private
1602829 169.xx.xxx.xxx/28 169.xx.xxx.xxx 2234945 public
2. [Create a cluster from the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-classic) by using the VLAN ID that you identified. Include the --no-subnet option to prevent a new portable public IP subnet and a new portable private IP subnet from being created automatically.

ibmcloud ks cluster create classic --zone dal10 --flavor b3c.4x16 --no-subnet --public-vlan 2234945 --private-vlan 2234947 --workers 3 --name my_cluster
After the account administrator makes these preparations, you might not need to change them each time that you create a cluster. However, each time that you create a cluster, you still want to verify that the current account-level state is what you need it to be.



1. [Create or upgrade your account to a billable account (IBM Cloud Pay-As-You-Go or Subscription)](https://cloud.ibm.com/registration).
2. [Set up an API key for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-access-creds) in the region and resource groups where you want to create clusters. Assign the API key with the [required service and infrastructure permissions to create clusters](https://cloud.ibm.com/docs/containers?topic=containers-access_referencecluster_create_permissions). Are you the account owner? You already have the necessary permissions! When you create a cluster, the API key for that region and resource group is set with your credentials.
3. Verify that you as a user (not just the API key) have the required permissions to create clusters.



1. From the [IBM Cloud console](https://cloud.ibm.com/) menu bar, click Manage > Access (IAM).
2. Click the Users page, and then from the table, select yourself.
3. From the Access policies tab, confirm that you [have the required permissions to create clusters](https://cloud.ibm.com/docs/containers?topic=containers-access_referencecluster_create_permissions). Make sure that your account administrator does not assign you the Administrator platform access role at the same time as scoping the access policy to a namespace.



4. If your account uses multiple resource groups, figure out your account's strategy for [managing resource groups](https://cloud.ibm.com/docs/containers?topic=containers-access-overviewresource_groups).



* The cluster is created in the resource group that you target when you log in to IBM Cloud.
Create the worker pool in your cluster and spread worker nodes across the zones that you defined. Note that the creation of worker nodes might take a few minutes to complete.

terraform apply

Example output

...
ibm_container_worker_pool.workerpool: Creating...
ibm_container_worker_pool.workerpool: Creation complete after 6s [id=aaaaaaaaa1eaaaaaaaaa/aaaaaaaaa1eaaaaaaa-aa1aa11]
ibm_container_worker_pool_zone_attachment.test-dal10: Creating...
ibm_container_worker_pool_zone_attachment.test-dal10: Still creating... [10s elapsed]
ibm_container_worker_pool_zone_attachment.test-dal10: Still creating... [20s elapsed]
...
Apply complete! Resources: 4 added, 0 changed, 0 destroyed.
4. Optional: Review the worker nodes in your cluster from the command-line.

Example for IBM Cloud Kubernetes Service

ibmcloud ks workers --cluster tfcluster --show-pools

Example for Red Hat OpenShift on IBM Cloud

ibmcloud oc workers --cluster tfcluster --show-pools







 Step 5: Remove the default worker pool from your cluster 

You can remove the default worker pool from your cluster.

The default worker pool is automatically created when the cluster is created. Because you do not explicitly specify the default worker pool in your configuration file, you cannot remove this worker pool by removing the ibm_container_worker_pool resource from your file. Instead, you use the local-exec Terraform on IBM Cloud provisioner to run an IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud command against your cluster to remove the default worker pool.



1. Open your Terraform on IBM Cloud configuration and add the following content.
To include your application-specific binary files, see [Planning for custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create a custom image and use that image to build the IBM Symphony cluster through this offering. string hpcc-symphony732-rhel86-smc-v1 
 smc_host_instance_type Specify the virtual server instance profile type name to be used to create the Symphony Multi Cluster host. For more information, see [VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). string bx2-4x16 









 Step 3: Generate a plan 

After you create your Schematics workspace and updated the configuration parameters, you need to generate a plan to validate all of the configuration properties.



1. Click Generate plan. When you click Generate plan, a new log is generated that can be viewed in the Jobs tab by clicking Jobs.
2. Review the log file for any errors, fix the properties, and regenerate the plan by clicking Generate plan again.







 Step 4: Apply a plan 

When you apply a plan, the IBM Cloud® SMC resources are deployed on your IBM Cloud account with your specific choice of configuration properties.



1. After you generate a plan in the IBM Cloud console, click Apply plan. This action generates a new log that can be viewed in the Jobs tab.
2. Review the log file for any errors, fix the errors, and then click Apply plan again.
3. After you successfully apply a plan, you can review all of the resources that are deployed under this workspace by clicking the Resources tab.



One of the last things shown in the log file after the Apply plan is an SSH key string:


2023/03/29 12:20:02 Terraform refresh | secondary_host_domain_name = "hpc-smc-secondary.smc.ibmhpc.com"
2023/03/29 12:20:02 Terraform refresh | smc_web_console = "https://localhost:8443/platform"
* You must configure permissions on the default export policy or create your own custom export policy.
* You must have one or more dataLIFs for the SVM.
* You must have NFS services enabled on the SVM.
* You must set up a snapshot policy on the SVM.





1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
2. [Set up Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).
3. [Create a Satellite cluster](https://cloud.ibm.com/docs/satellite?topic=openshift-satellite-clusters).



* Make sure that you select the Enable cluster admin access for Satellite Config option when you create the cluster. If you don't enable Administrator (admin) access for Satellite Config when creating your cluster, you must re-create your cluster and enable admin access before you can deploy storage.
* Your cluster must meet the requirements for ONTAP-NAS. For more information, see the [NetApp documentation](https://netapp-trident.readthedocs.io/en/stable-v21.04/support/requirements.html).
* Your hosts must meet the [Satellite host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs) in addition to the requirements for ONTAP-NAS.



4. [Add your Satellite to a cluster group](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig-groups).



Before you begin, review the [parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-ontap-nas-parameter-reference) for the template version that you want to use.





 Creating and assigning a configuration in the console 



1.