vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Add a Compute Manager](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-D225CAFC-04D4-44A7-9A09-7C365AAFCA0E.htmlGUID-D225CAFC-04D4-44A7-9A09-7C365AAFCA0E).
4. Deploy additional NSX Manager nodes (2 and 3) to form a cluster. Use the IP addresses provisioned in the [previous tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-nsx-t-hostsvpc-bm-vmware-nsx-t-vlannics). For more information, see [Deploy NSX Manager Nodes to Form a Cluster from the UI](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-B89F5831-62E4-4841-BFE2-3F06542D5BF5.htmlGUID-B89F5831-62E4-4841-BFE2-3F06542D5BF5).
5. Configure a Virtual IP Address for a Cluster.
ibmcloud oc 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/openshift?topic=openshift-add_workersvpc_add_pool) or the [CLI reference documentation](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicli_worker_pool_create_vpc_gen2).



* UI: After selecting your cluster from the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), 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.

ibmcloud oc worker-pool create vpc-gen2 --name <worker_pool_name> --cluster <cluster_name_or_ID> --flavor <flavor> --size-per-zone <number_of_workers_per_zone> --vpc-id <VPC ID> --kms-account-id <kms_account_ID> --kms-instance-id <kms_instance_ID> --crk <kms_root_key_ID>





4.
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. The following example configuration creates a classic cluster with a single zone and three worker nodes. For more information and cluster configuration options, see the [Terraform ibm_container_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs) documentation.

Example Terraform configuration file.

resource "ibm_container_cluster" "testacc_cluster" {
name = "test-classic"
datacenter = "dal10"
machine_type = "b3c.4x16"
hardware = "shared"
public_vlan_id = "<vlan_id>"
private_vlan_id = "<vlan_id"
subnet_id = ["<subnet_id>"]

default_pool_size = 3
}

name
: The name of the cluster.

datacenter
: The zone to create the cluster in. To see available zones, run ibmcloud oc zones --provider classic.

machine_type
: The worker node flavor. The flavor determines the amount of memory, CPU, and disk space that is available to your worker nodes. For a list of available worker node flavors, run ibmcloud oc flavors --zone <zone> --provider classic, or see [Classic flavors](https://cloud.ibm.com/docs/containers?topic=containers-classic-flavors&interface=ui).

hardware
: The level of hardware isolation for your worker nodes. Use dedicated to have available physical resources dedicated to you only, or shared to allow physical resources to be shared with other IBM customers. This option is available for virtual machine worker nodes flavors only.
* Before you can use KMS encryption, you must create a KMS instance and set up the required service authorization in IAM. For more information, see [Managing encryption for the worker nodes in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-encryptionworker-encryption).
* By default, your cluster is provisioned with a VPC security group and a cluster-level security group. If you want to attach additional security groups or change which default security groups are applied when you create the cluster, you must [create your VPC cluster in the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2&interface=uicluster_vpcg2_cli).
* If you create a VPC cluster with both a public and a private cloud service endpoint, note that the public service endpoints can't be disabled at a later time. Therefore, you can't convert a public cluster to a private cluster.







 Creating a VPC cluster in the console 



1. Make sure that you complete the prerequisites to [prepare your account](https://cloud.ibm.com/docs/containers?topic=containers-clusters&interface=ui) and decide on your cluster setup.
2. [Navigate to the console](https://cloud.ibm.com/kubernetes/catalog/create?platformType=openshift).
3. In the Infrastructure section, select VPC.
4. In the Virtual private cloud section, choose from the following options.



* Select an existing VPC.
* Click Create VPC.



5. Optional: If you selected Create VPC, complete the following steps.



1. Select a Geography and Region. To review the available regions, see [VPC multizone regions](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-vpc)
2. Enter a name for your VPC.
3.
For more information, see [Creating clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-clusters)
* An Object Storage instance in the same region as your cluster. For more information, see [Provision an instance of Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-provision).







 Step 1: Creating a set of service credentials 



1. Follow the steps to create a set of HMAC [service credentials for your Object Storage instance](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storagegs-bucket-policy). Note that the credentials you create must have the Manager role to create buckets.
2. After you create a set of HMAC service credentials, review the details of your credentials and make a note of the apikey, access_key_id, and secret_access_key. Save these values for the next step.







 Step 2: Creating a secret to store your credentials 



1. Create a secret by using the apikey, access_key_id, and secret_access_key from your service credentials.

oc create secret generic my-cos-secret --type=ibm/ibmc-s3fs --from-literal=access-key=ACCESS-KEY --from-literal=secret-key=SECRET-KEY --from-literal=res-conf-apikey=API-KEY

Example output.

secret/my-cos-secret created
2. Verify the secret was created.

oc get secrets | grep my-cos

Example output.

my-cos-secret ibm/ibmc-s3fs 3 11m







 Step 3: Installing the plug-in 

When you install the plug-in in your cluster, make sure to specify the --set quotaLimit=true option. Specifying this option means any buckets you create with PVCs have a quota limit equal to the storage size in the PVC.



1.
3. Launch IBM Blockchain Platform in the [IBM Cloud Catalog](https://cloud.ibm.com/catalog/services/blockchain-platform).
4. Under Select a pricing plan, ensure that the Standard plan is selected and then click Create.
5. On the Welcome and pre-requisites panel that opens, click I have a Cluster (Skip to Link a cluster).
6. In the Select an IBM Kubernetes Service cluster drop-down list, select your free cluster. Note: If your free cluster is not listed, ensure sure you are not using the ESR version of Firefox. If you are, switch to another browser such as Chrome and retry.
7. Click Deploy to cluster.
8. When the platform is ready, you can click Launch the IBM Blockchain Platform to open the blockchain console UI and get started. Watch the [video](http://ibm.biz/BlockchainPlatformSeries2) to learn how to Deploy a peer on the IBM Blockchain Platform, or try out the getting started tutorial [Build a network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network).



After 30 days, your Kubernetes cluster is deleted along with all of your blockchain nodes and data.







 Key elements of cost 

Because your blockchain network consists of an Kubernetes cluster on IBM Cloud that contains IBM Blockchain Platform components and uses storage of your choice, each of the following elements forms your total cost.

Zoom

![Elements of pricing](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/elements-of-pricing.svg)

Figure 1. Elements of pricing



* IBM Blockchain Platform: Based on a flat rate of $0.29 USD/VPC-hour.
The tool is useful if you want to estimate the price of the selected IBM Cloud for VMware Solutions resources together with other IBM Cloud resources that you might consider purchasing.







 Procedure to add clusters to vCenter Server with Hybridity Bundle 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 the instance to view the clusters in it.

Ensure that the instance status is Available. Otherwise, you can't add clusters to the instance.
3. Click the Infrastructure tab and click Create at the upper right of the Clusters table.
4. On the Create cluster page, enter the cluster name.
5. You can host the cluster in a different IBM Cloud data center than the one that the instance is hosted in. To do so, under Bare metal server, toggle the Select a different location switch on and choose the IBM Cloud data center to host the cluster.
6. Select the CPU model, the amount of RAM, and the Number of bare metal servers for the bare metal configuration.
7. Select vSAN storage and specify the disk types for the capacity and cache disks and the number of disks. If you want more storage, select the High performance with Intel Optane checkbox.
8. Select the license edition for VMware vSAN for the license configuration.
9. Select the network setting of either Public and private network or Private network only.
10. 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 Download icon 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 with Hybridity Bundle instances 



1.
Create a worker pool in your Satellite cluster with host labels. Then, Satellite can automatically assign available hosts to the worker pool. For more information, see [Using host autoassignment](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-autoassign-ov).

Before you begin



* Make sure that you have the Operator platform access role to Kubernetes Service for the cluster in IBM Cloud IAM.
* Optional: [Attach](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) or [list available](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencehost-ls) hosts to your Satellite location with host labels that match your worker pool. Then, after you create your worker pool, these available hosts can be automatically assigned to the worker pool.



To create a worker pool in a Satellite cluster



1. List the Satellite clusters in your account.

ibmcloud oc cluster ls --provider satellite
2. Get the details of the cluster that you want to create the worker pool in. Note the Worker Zones.

ibmcloud oc cluster get --cluster <cluster_name_or_ID>
3. Create the worker pool in your Satellite cluster, with the following parameters.



* --cluster: Enter the name or ID of your cluster.
* --name: Give a name for your worker pool.
* --size-per-zone: Specify the number of worker nodes that you want to have in each zone that the worker pool spans. You can change this value later by resizing the worker pool.
* --zone: Select the initial zone in your Satellite location to create the worker pool in, that you retrieved from your cluster details. You can add more zones later.
* --host-label: Add labels to match the requested capacity of the worker pool with the available hosts in the Satellite location. You can use just the cpu=number host label because Satellite hosts automatically get this host label. You can also add a custom host label like env=prod.
ibmcloud ks cluster create classic --name my_cluster --zone dal10 --flavor mb2c.4x32 --hardware dedicated --workers 3 --public-vlan <public_VLAN_ID> --private-vlan <private_VLAN_ID>

Create a classic cluster that uses private VLANs and the private cloud service endpoint only.

ibmcloud ks cluster create classic --name my_cluster --zone dal10 --flavor b3c.4x16 --hardware shared --workers 3 --private-vlan <private_VLAN_ID> --private-only --private-service-endpoint

For a classic multizone cluster, after you created the cluster in a [multizone metro](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-mz), [add zones](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd_zone):

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 VPC clusters in the CLI 

Review the sample commands for creating classic clusters in the CLI. For more detailed steps and information about creating clusters, see [Creating VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=clicluster_create_vpc). For information about planning your cluster set up, see [Preparing to create clusters](https://cloud.ibm.com/docs/containers?topic=containers-clusters&interface=cli).

Create a VPC cluster with three worker nodes.
After your cluster is created, you can [begin working with your cluster by configuring your CLI session](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



Your cluster is ready for your workloads! You might also want to [add a tag to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workerscluster_tags), such as the team or billing department that uses the cluster, to help manage IBM Cloud resources. For more ideas of what to do with your cluster, review the [Next steps](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersnext_steps).





 Example commands to create classic clusters 

Classic cluster, shared virtual machine

ibmcloud oc cluster create classic --name my_cluster --version 4.11_openshift --zone dal10 --flavor b3c.4x16 --hardware shared --workers 3 --public-vlan <public_VLAN_ID> --private-vlan <private_VLAN_ID>

Classic cluster, bare metal

ibmcloud oc cluster create classic --name my_cluster --version 4.11_openshift --zone dal10 --flavor mb2c.4x32 --hardware dedicated --workers 3 --public-vlan <public_VLAN_ID> --private-vlan <private_VLAN_ID>

Classic cluster with an IBM Cloud Pak entitlement for a default worker pool of 3 worker nodes with 4 cores and 16 memory each.

ibmcloud oc cluster create classic --name cloud_pak_cluster --version 4.11_openshift --zone dal10 --flavor b3c.4x16 --hardware dedicated --workers 3 --entitlement cloud_pak --public-vlan <public_VLAN_ID> --private-vlan <private_VLAN_ID> [--operating-system (REDHAT_7_64|REDHAT_8_64)]
* If worker nodes must access public endpoints, [attach a public gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cliattach-public-gateway-cli) to each subnet.
* Important: Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.
* For more information, see [Overview of VPC networking in IBM Cloud Kubernetes Service: Subnets](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_subnets).



4. Create the cluster in your VPC. You can use the ibmcloud ks cluster create vpc-gen2 command to create a single zone cluster in your VPC with worker nodes that are connected to one VPC subnet only. 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_workersvpc_add_zone) to your cluster after the cluster is created. The cluster takes a few minutes to provision.
Select Workspaces in the navigation bar and press Create to open the Create workspace menu.
2. Enter the Workspace name and select a Resource group according to the intended assignment of the cluster resources.
3. Select the Region where you want the resources to deploy.
4. Add any User tags and Access management tags according to your policies.
5. Click Create to initiate the workspace.







 Creating subnets 

The virtual server instance is connected to the network and gets an IP address from the assigned IP range.

It is recommended that you connect the cluster nodes to a private network, not to a public network.

An extra bastion node can access both public and private networks and can be used to tunnel SSH connections to the cluster nodes.

Private subnets are created in context of the Power Systems Virtual Server workspace. When you connect different networks, you can use GRE Tunneling if a subnet range conflicts with existing classical infrastructure.

You need at least one private subnet in the workspace.

Use the following steps to create a subnet.



1. Go to [Subnets in Power Systems Virtual Server](https://cloud.ibm.com/power/subnets).
2. Select the workspace that you created.
3. Click Create subnet and enter the following information for the new subnet.



* Name for the new subnet.
* Classless Inter-Domain Routing (CIDR) in form of an address prefix.
* Number of bits reserved for the netmask separated by a slash.



By entering a specific IP range, you can restrict the IP address range to a subset of the full CIDR range. Restricting the IP address range prevents IP addresses from being automatically assigned to another virtual server instance during a provisioning request.
4. Click Create subnet.







 Reserving virtual IP addresses 

A high availability cluster typically needs virtual IP addresses that must move with the application in a failover scenario.

Currently, Power Systems Virtual Server does not support reserving a floating IP address. Follow this procedure to avoid that virtual IP addresses are erroneously used during other virtual server deployments in the same workspace:
2. Initialize the Terraform on IBM Cloud CLI.

terraform init
3. Create an Terraform on IBM Cloud execution plan. When you execute this command, Terraform on IBM Cloud validates the syntax of your configuration file and resource definitions against the specifications of the IBM Cloud Provider plug-in.

terraform plan

Example output:

Refreshing Terraform on IBM Cloud state in-memory prior to plan...

 ibm_container_cluster.tfcluster will be created
+ resource "ibm_container_cluster" "tfcluster" {
+ albs = (known after apply)
+ crn = (known after apply)
+ datacenter = "dal10"
+ default_pool_size = 3
+ disk_encryption = true
+ gateway_enabled = false
....

Plan: 1 to add, 0 to change, 0 to destroy.
4. Review the Terraform on IBM Cloud execution plan to verify that your cluster set up is correct.
5. Create your single zone cluster. Note that the creation of your cluster takes a few minutes to complete.

terraform apply

Example output:

...
ibm_container_cluster.tfcluster: Creating...
ibm_container_cluster.tfcluster: Still creating... [10s elapsed]
...
ibm_container_cluster.tfcluster: Creation complete after 20m27s [id=bpugrqtd0ejuoqvinshg]

Apply complete! Resources: 1 added, 0 changed, 1 destroyed.
6. Optional: Review your cluster from the command-line.

Example for IBM Cloud Kubernetes Service

ibmcloud ks cluster get --cluster tfcluster

Example for Red Hat OpenShift on IBM Cloud

ibmcloud oc cluster get --cluster tfcluster



You have now completed the tutorial! You created your single zone IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud cluster.





 Step 3: Convert your single zone cluster into a multizone cluster
* 1 IBM Cloud Object Storage instance and bucket to back up certain [cluster data](https://cloud.ibm.com/docs/containers?topic=containers-service-archibm-data). You can optionally select your own instance.







 Creating a secure cluster by using a template from the UI 

With the secure cluster template, you can create a cluster from the UI with IBM Cloud Schematics that already includes certain security integrations such as encryption, logging, and monitoring enabled by default.



1. Log in to the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift) and click Create cluster +.
2. From the Create tab in the Select your template section, click Secure.
3. Review the pre-configured details for the secure template, including the following sections. To change these values, click Edit. When you are finished, click Done editing to apply your changes.



* Location: Review the resource group and IBM Cloud multizone location where the cluster is created.
* Orchestration service: Review the container platform, version, and entitlement details.

For the OCP entitlement, you can select an entitlement for a worker pool, if you have one. Usually, leave the value set to Purchase additional licenses for this worker pool. If you have an IBM Cloud Pak with a Red Hat OpenShift entitlement that you want to use, you can select Apply my Cloud Pak OCP entitlement to this worker pool. Later, when you configure the worker pool, make sure to select only the flavor and number of worker nodes that your entitlement permits.
* VPC: Review the subnet IP range for your location.
* Resource details: Review the resource prefix that is automatically added to each IBM Cloud resource that is created. You can also optionally provide your own IBM Cloud IAM API key if you don't need a new API key generated for you.
* Integrations: A new instance of each of the following IBM Cloud services is created for you by default. You can edit the template to select an existing instance.



4. In the Summary pane, click Create.
[Create a Kubernetes cluster](https://cloud.ibm.com/docs/containers?topic=containers-clusters).
2. [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 create an image pull secret:



1. Create the Kubernetes secret to store your private registry credentials.

kubectl --namespace <namespace> create secret docker-registry <secret_name> --docker-server=<registry_URL> --docker-username=<docker_username> --docker-password=<docker_password> --docker-email=<docker_email>

--namespace <namespace>
: Required. The Kubernetes namespace of your cluster where you want to use the secret and deploy containers to. To list available namespaces in your cluster, run kubectl get namespaces.

<secret_name>
: Required. The name that you want to use for your image pull secret.

--docker-server <registry_URL>
: Required. The URL to the registry where your private images are stored.

--docker-username <docker_username>
: Required. The username to log in to your private registry.

--docker-password <token_value>
: Required. The password to log in to your private registry, such as a token value.

--docker-email <docker-email>
: Required. If you have one, enter your Docker email address. If you don't have one, enter a fictional email address, such as a@b.c. This email is required to create a Kubernetes secret, but is not used after creation.
2. Verify that the secret was created successfully. Replace <namespace> with the name of the namespace where you created the image pull secret.