vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The cluster name must start with a letter, can contain letters, numbers, and hyphen (-), and must be 35 characters or fewer.
9. Click Create. When you create the cluster, the cluster master is automatically created in your Satellite location control plane, and your worker pool is automatically assigned available hosts that match your worker node request.
10. Wait for the cluster to reach a Normal state.

If you don't have any available and matching hosts in your Satellite location, the cluster is still created but enters a Warning state. [Attach hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) to your Satellite location so that hosts can be assigned as worker nodes to the worker pool. If the hosts are not automatically assigned, you can also manually [assign Satellite hosts to your cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-assign-manual). Ensure that hosts are assigned as worker nodes in each zone of your default worker pool.
11. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), verify that your cluster reaches a Normal state.
12. [Access your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_cluster_sat) to access the Red Hat OpenShift web console or to run oc and kubectl commands from the CLI. If you enabled Satellite Config access, you must complete this step to synchronize the permissions.

If your location hosts have private network connectivity only, or if you use Amazon Web Services, Google Cloud Platform, or Microsoft Azure hosts, you must be connected to your hosts' private network, such as through VPN access, to connect to your cluster and access the Red Hat OpenShift web console.
For more information, see [Creating clusters](https://cloud.ibm.com/docs/containers?topic=containers-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.

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

kubectl 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.
Creating clusters on dedicated hosts for VPC 

Virtual Private Cloud

Follow the steps to create a dedicated host in a dedicated host pool. Then, provision a cluster on your dedicated host infrastructure.



1. List available dedicated host flavors. Note the flavor and flavor class that you want to use to create a dedicated host.

ibmcloud ks flavors --provider vpc-gen2 --zone us-south-1

Example output.

OK
For more information about these flavors, see 'https://ibm.biz/flavors'
Name Cores Memory Network Speed OS Server Type Storage Secondary Storage Flavor Class Provider
bx2d.16x64 16 64GB 16Gbps UBUNTU_18_64 virtual 100GB 600GB bx2d vpc-gen2
bx2d.32x128.600gb 32 128GB 16Gbps UBUNTU_18_64 virtual 100GB 600GB bx2d vpc-gen2
bx2d.48x192.900gb 48 192GB 16Gbps UBUNTU_18_64 virtual 100GB 900GB bx2d vpc-gen2
...
2. Create a dedicated host pool. Specify the flavor class and metro that you want to use.

ibmcloud ks dedicated pool create --name my_host_pool --flavor-class bx2d --metro dal
3. Verify that the dedicated host pool was created.

ibmcloud ks dedicated pools

Example output.

ID Name Metro Flavor Class Hosts State
dh_a1aaa1111aaa1aaa1a11 my_host_pool dal bx2d 0 created
4. Create the dedicated host. Specify the zone, dedicated host pool, and flavor.

ibmcloud ks dedicated host create --zone us-south --pool a1a1a1a1a --flavor bx2d.host.16x64
5. Verify that the dedicated host was created. If the dedicated host is in the create_pending state, wait a few minutes for it to reach the created state.

ibmcloud ks dedicated host ls --pool a1a1a1a1a
Open the [Satellite console](https://cloud.ibm.com/satellite/locations) in your browser.
2. Select the location where you created your storage configuration.
3. Click the Locations tab, then click Storage.
4. Click the storage configuration that you want to assign to a cluster group.
5. On the Configuration details page, click Create storage assignment.
6. In the Create an assignment pane, enter a name for your assignment.
7. From the Version drop-down list, select the storage configuration version that you want to assign.
8. From the Cluster group drop-down list, select the cluster group that you want to assign to the storage configuration. Note that the clusters in your cluster group where you want to assign storage must all be in the same Satellite location.
9. Click Create to create the assignment.
10. Verify that your storage configuration is deployed to your cluster.



1. From the [Satellite console](https://cloud.ibm.com/satellite/locations), navigate to your Location and select Storage
2. Click the storage configuration that you created and review the Assignments tab.
3. Click the Assignment that you created and review the Rollout status for your configuration.









 Creating an assignment in the CLI 



1. List your storage configurations and make a note of the storage configuration that you want to assign to your clusters.

ibmcloud sat storage config ls
2. Get the ID of the cluster, cluster group, or service that you want to assign storage to.

To make sure that your cluster is registered with Satellite Config or to create groups, see [Setting up clusters to use with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).

Example command to list cluster groups.

ibmcloud sat group ls

Example command to list clusters.

ibmcloud oc cluster ls --provider satellite

Example command to list Satellite services.

ibmcloud sat service ls --location <location>
3.
On the Create cluster page, select the cluster type.
5. For workload clusters, enter the cluster name and complete the following configuration.



1. Complete the licensing settings.



* For Business Partner users, the vSphere license (Enterprise Plus edition) is included and purchased on your behalf.
* For users who are not Business Partners, select Include with purchase for the new vSphere license to be purchased on your behalf.
* Bring Your Own License (BYOL) is no longer supported except for migrations or upgrades of existing BYOL clusters. Select I will provide or Use existing license and enter your own license key only if you are performing an upgrade or migration of an existing BYOL cluster.
* The Use existing license option is available only if you are using a BYOL vSphere or vSAN license for your instance. When the option is enabled, you can select the existing license only if the instance has enough capacity for the additional hosts.



2. Complete the bare metal server configuration.



* If you want to host the cluster in a different IBM Cloud data center than the one that the instance is hosted in, toggle the Select a different location switch on and choose the IBM Cloud data center to host the cluster.
* For Cascade Lake or SAP-certified Cascade Lake, select one of the preset configurations. For Cascade Lake, also specify the RAM size.



3. Complete the storage configuration.



* If you select NFS storage and want to add and configure the same settings to all file shares, specify the Number of shares, Size (GB), and Performance.
* If you select NFS storage and want to add and configure file shares individually, toggle the Configure shares individually switch on, then click Add shared storage and select the Size (GB) and Performance for each file share. You must select at least one file share.
* If you select vSAN storage, specify the following values:



* Size for the vSAN capacity disks
* Number of vSAN capacity disks
* Size for vSAN cache disks
* Number of vSAN cache disks
* vSAN license edition





If you want more storage, check the High performance with Intel Optane box.
Before creating your cluster, please refer to the most recent SAP documentation, like [Installation](https://help.sap.com/viewer/a8d90a56d61a49718ebcb5f65014bbe7/latest/en-US/9f866d8ef9a94c30947f12e73eaf0dd9.html) and [Administration Guide](https://help.sap.com/viewer/b13b5722c8ff4bf9bb097251310031d0/latest/en-US/884ffcd587784ed2a311b2c19feb8410.html). You may find more related information in [SAP's Community page](https://community.sap.com/topics/data-intelligence).

Please check that your IBM Cloud account is eligible to create clusters. For more information and the steps to set up your account, see [Prepare to create clusters at the account level](https://cloud.ibm.com/docs/openshift?topic=openshift-clusterscluster_prepare).





 Provisioning your OpenShift cluster 

Use the following steps to create your Red Hat OpenShift on IBM Cloud cluster. Again, the values used in this scenario are suggestions for a test environment. Please, select additional optional values that will fit your specific needs.

Currently, IBM Cloud offers several Red Hat OpenShift on IBM Cloud versions, starting from 4.6.x up to 4.10.x.

Please consider that SAP only supports Red Hat OpenShift on IBM Cloud version 4.8.x for SAP Data Intelligence 3.2

The Information button provides field-specific information on how to use a field.



1. Log in to [IBM Cloud console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift) and click Create cluster +.
2. Select your setup - Leave the value set to Manual Setup.
3. Select Classic for Infrastructure.
4. Leave the value Default for Resource group.
5.
From the Cloud Object Storage drop-down menu, select a standard IBM Cloud Object Storage instance to use for the internal Red Hat OpenShift container registry, or [create a standard IBM Cloud Object Storage instance](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-provisionprovision-instance) to use.



4. Configure the Location details for your cluster.



1. Select the Resource group that you want to create your cluster in. You can't change the resource group later. If you don't select a resource group, your cluster is created in the default resource group.
2. Select the zones to create your cluster in. The zones are filtered based on the VPC that you selected, and include the subnets that you previously created.



5. Configure your Worker pool setup.



1. If you want a larger size for your worker nodes, click Change flavor. Otherwise, leave the default 4 vCPUs / 16 GB flavor selected.
2. Set how many worker nodes to create per zone, such as the minimum value of 2. For more information, see [What is the smallest size cluster that I can make?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqssmallest_cluster).



6. Complete the Resource details to customize the cluster name and any tags that you want to use to organize your IBM Cloud resources.
7. In the Summary pane, review the order summary and then click Create. Your cluster creation might take some time to complete. After the cluster state shows Normal, the cluster network and load balancing components take about 10 more minutes to deploy and update the cluster domain that you use for the Red Hat OpenShift web console and other routes. Before you continue, wait until the cluster is ready by checking that the Ingress Subdomain follows a pattern of <cluster_name>.<globally_unique_account_HASH>-0001.<region>.containers.appdomain.cloud.
[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 ks cluster get --cluster <cluster_name_or_ID>.
2. Create a new worker pool in your cluster.

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

kubectl describe svc <kubernetes_lb_service_name>
Creating clusters on dedicated hosts for VPC 

Virtual Private Cloud

Follow the steps to create a dedicated host in a dedicated host pool. Then, provision a cluster on your dedicated host infrastructure.



1. List available dedicated host flavors. Note the flavor and flavor class that you want to use to create a dedicated host.

ibmcloud oc flavors --provider vpc-gen2 --zone us-south-1

Example output.

OK
For more information about these flavors, see 'https://ibm.biz/flavors'
Name Cores Memory Network Speed OS Server Type Storage Secondary Storage Flavor Class Provider
bx2d.16x64 16 64GB 16Gbps UBUNTU_18_64 virtual 100GB 600GB bx2d vpc-gen2
bx2d.32x128.600gb 32 128GB 16Gbps UBUNTU_18_64 virtual 100GB 600GB bx2d vpc-gen2
bx2d.48x192.900gb 48 192GB 16Gbps UBUNTU_18_64 virtual 100GB 900GB bx2d vpc-gen2
...
2. Create a dedicated host pool. Specify the flavor class and metro that you want to use.

ibmcloud oc dedicated pool create --name my_host_pool --flavor-class bx2d --metro dal
3. Verify that the dedicated host pool was created.

ibmcloud oc dedicated pools

Example output.

ID Name Metro Flavor Class Hosts State
dh_a1aaa1111aaa1aaa1a11 my_host_pool dal bx2d 0 created
4. Create the dedicated host. Specify the zone, dedicated host pool, and flavor.

ibmcloud oc dedicated host create --zone us-south --pool a1a1a1a1a --flavor bx2d.host.16x64
5. Verify that the dedicated host was created. If the dedicated host is in the create_pending state, wait a few minutes for it to reach the created state.
* Click the browser back button to return to the VPC details page.
* Repeat the previous three steps to attach a public gateway to each subnet.





* 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 name.
* Click Create.







 Step 1: Deploy a dynamic web application to be accelerated 

Let's consider a simple dynamic web application for collaboration for a team geographically distributed. With this application, team members can create and manage team's to-do items together.

This [sample application](https://github.com/IBM-Cloud/cdn-with-cda-todolist) is based on [Beego](https://beego.vip/), a RESTful HTTP framework for the rapid development of Go applications including APIs, web apps and backend services.



 Build the application 



1. Clone the application

git clone https://github.com/IBM-Cloud/cdn-with-cda-todolist.git
2. Change to the application directory

cd cdn-with-cda-todolist
3. Identify the cluster. ibmcloud ks cluster ls will return cluster names.

ibmcloud ks cluster ls

Set the variable accordingly:

MYCLUSTER=<cluster_name>
4. Identify the Container Registry and set a namespace. ibmcloud cr info will return the name of the container registry.

ibmcloud cr info

Set the variable accordingly:

MYCONTAINERREGISTRY=<us.icr.io_like_value_returned_from_ibmcloud_cr_info>

Set the variable to a name you want to used as a new namespace:

MYNAMESPACE=<my_container_registry_namespace>
5.
* Click Create.



* Attach a Public Gateway to each of the subnets that you create:



* Navigate to the [Virtual private clouds](https://cloud.ibm.com/vpc-ext/network/vpcs).
* Click the previously created VPC used for the cluster.
* Scroll down to subnets section and click a subnet.
* In the Public Gateway section, click Detached to change the state to Attached.
* Click the browser back button to return to the VPC details page.
* Repeat the previous three steps to attach a public gateway to each subnet.





* 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 name.
* Click Create.



Note: Do not proceed until your workers are ready.





 Step 2: Create a sample application 



1. From the [IBM Cloud console](https://cloud.ibm.com/), use the left side menu option and select [DevOps](https://cloud.ibm.com/devops).
2. Click Create toolchain.
3. In the search box type kubernetes as a filter.
4. Click on the Develop a Kubernetes app with Helm tile.
5. Enter a unique Toolchain Name for the toolchain such as <your-initials>-mynodestarter-toolchain and select a resource group.
6. Enter a unique Repository Name for the repository such as <your-initials>-mynodestarter-repository.
7. Click on the Delivery Pipeline tab.
8. Provide an IBM Cloud API Key. If you don't have one, create by clicking on New.
9. Select a region and your cluster from the list.
10.
[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

If you can't remember which zone the VLAN is in for the --zone option, you can check whether the VLAN is in a certain zone by running ibmcloud ks vlan ls --zone <zone>.
3. Verify that the cluster was created. It can take up to 15 minutes for the worker node machines to be ordered and for the cluster to be set up and provisioned in your account.

ibmcloud ks cluster ls

When your cluster is fully provisioned, the State changes to deployed.

NAME ID State Created Workers Zone Version Resource Group Name Provider
mycluster aaf97a8843a29941b49a598f516da72101 deployed 20170201162433 3 dal10 1.26 Default classic
4. Check the status of the worker nodes.

ibmcloud ks worker ls --cluster <cluster_name_or_ID>

Before continuing to the next step, the worker nodes must be ready. The State changes to normal and the Status is Ready.

ID Public IP Private IP Machine Type State Status Zone Version
prod-dal10-pa8dfcc5223804439c87489886dbbc9c07-w1 169.xx.xxx.xxx 10.xxx.xx.xxx free normal Ready dal10 1.26
5. Add the subnet to your cluster by specifying the subnet ID.
(https://cloud.ibm.com/docs/openshift?topic=openshift-faqssmallest_cluster).



8. Complete the Resource details to customize the cluster name and any tags that you want to use to organize your IBM Cloud resources.
9. In the Summary pane, review the order summary and then click Create. Your cluster creation might take some time to complete. After the cluster state shows Normal, the cluster network and load balancing components take about 10 more minutes to deploy and update the cluster domain that you use for the Red Hat OpenShift web console and other routes. Before you continue, wait until the cluster is ready by checking that the Ingress Subdomain follows a pattern of <cluster_name>.<globally_unique_account_HASH>-0001.<region>.containers.appdomain.cloud.
10. Verify that your cluster setup is finished before you continue to the next step by checking that the worker nodes on the Worker Nodes tab have a Status of normal.



Now that your cluster is ready, [deploying your first app](https://cloud.ibm.com/docs/openshift?topic=openshift-getting-started&interface=uideploy-app)!





 Creating a VPC cluster in the console 

Create a VPC cluster by using the IBM Cloud console. VPC Red Hat OpenShift clusters run version 4.11, which includes Kubernetes version 1.25. The operating system is Red Hat Enterprise Linux 7.

Want to learn more about customizing your cluster setup with the CLI? Check out [Creating a VPC cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2).



1. Create a Virtual Private Cloud (VPC) on generation 2 compute.



1. Navigate to the [VPC create console](https://cloud.ibm.com/vpc/provision/vpc).
2. Give the VPC a name and select a resource group to deploy the VPC into.
3.
* 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 name.
* Click Create.







 Step 1: Deploy a dynamic web application to be accelerated 

Let's consider a simple dynamic web application for collaboration for a team geographically distributed. With this application, team members can create and manage team's to-do items together.

This [sample application](https://github.com/IBM-Cloud/cdn-with-cda-todolist) is based on [Beego](https://github.com/beego/beego), a RESTful HTTP framework for the rapid development of Go applications including APIs, web apps and backend services.



 Build the application 



1. Clone the application

git clone https://github.com/IBM-Cloud/cdn-with-cda-todolist.git
2. Change to the application directory

cd cdn-with-cda-todolist
3. Identify the cluster. ibmcloud ks cluster ls will return cluster names.

ibmcloud ks cluster ls

Set the variable accordingly:

MYCLUSTER=<cluster_name>
4. Identify the Container Registry and set a namespace. ibmcloud cr info will return the name of the container registry.

ibmcloud cr info

Set the variable accordingly:

MYCONTAINERREGISTRY=<us.icr.io_like_value_returned_from_ibmcloud_cr_info>

Set the variable to a name you want to used as a new namespace:

MYNAMESPACE=<my_container_registry_namespace>
5. Create a namespace to store the container image. Feel free to skip this step and use an existing namespace.