vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* --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. Important: You can't update host labels on the worker pool later, so make sure to configure the labels properly. You can change the labels on Satellite hosts, if needed.
* --operating-system: Optional: Specify the operating system of the hosts that you want to use to create your worker pool such as REDHAT_7_64, REDHAT_8_64, or RHCOS. Note that you must create a Red Hat CoreOS enabled location to use your RHCOS hosts in your clusters. For clusters created in default locations without Red Hat CoreOS enabled, specify a [version that corresponds to your cluster version](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versionsopenshift_versions_available). If no option is specified, the default version that corresponds to the cluster version is used.



Example worker-pool create command

ibmcloud oc worker-pool create satellite --cluster <cluster_name_or_ID> --name <pool_name> --size-per-zone <number> --zone <satellite_zone> --host-label <cpu=number> --host-label <memory=number> [--host-label <key=value>] [--operating-system (REDHAT_7_64|REDHAT_8_64|RHCOS)]

Example worker-pool create command for creating a worker pool that uses Red Hat CoreOS hosts.
"excluded": []
}





 Creating network zones from the CLI 



1. To create network zones from the CLI, [install the CBR CLI plug-in](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugininstall-cbr-plugin).
2. You can use the cbr-zone-create command to add resources to network zones. For more information, see the CBR [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-zones-cli). Note that the service_name for IBM Cloud Kubernetes Service is containers-kubernetes.

To find a list of available service refs, run the ibmcloud cbr service-ref-targets[command](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-cli-service-ref-targets-command).

Example command to add the containers-kubernetes service to a network zone.

ibmcloud cbr zone-create --name example-zone-1 --description "Example zone 1" --service-ref service_name=containers-kubernetes

The following example creates a network zone to allow a single public IP address to access. You can also use this example in conjunction with the [one IP example rule](https://cloud.ibm.com/docs/containers?topic=containers-cbr&interface=uione-ip). For more information about this scenario, see [Setting up context-based restrictions](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorial).

ibmcloud cbr zone-create --addresses 129.41.86.7 --description "Allow only client IP" --name allow-client-ip







 Creating network zones from the console 



1. Determine the resources that you want add to your allowlist.
2.
Verify that the cluster that you want to use meets the [minimum hardware requirements for Portworx](https://docs.portworx.com/start-here-installation/).
2. If you want to use a virtual machine cluster, make sure that you [added raw, unformatted, and unmounted block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesmanual_block) to your cluster so that Portworx can include the disks into the Portworx storage layer.
3. Verify that your cluster is set up with public network connectivity. For more information, see [Understanding network basics of classic clusters](https://cloud.ibm.com/docs/containers?topic=containers-plan_clusters).







 Step 3: Reach out to Portworx and IBM 

Contact Portworx support by using one of the following methods.



* Sending an e-mail to support@purestorage.com.
* Calling +1 (866) 244-7121 or +1 (650) 729-4088 in the United States or one of the [International numbers](https://support.purestorage.com/Pure_Storage_Technical_Services/Technical_Services_Information/Contact_Us).
* Opening an issue in the [Portworx Service Portal](https://support.purestorage.com/Pure_Storage_Technical_Services/Technical_Services_Information/Contact_Us). If you don't have an account, see [Request access](https://purestorage.force.com/customers/CustomerAccessRequest).
The toolchain in this tutorial supports a Satellite cluster group that contains only one type of cluster: a Kubernetes cluster or a Satellite cluster.
* An instance of the [Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started) service.
* Optional. Secrets that are stored in a secrets management vault and managed centrally from a single location. For more information about choosing from the various secrets management and data protection offerings, see [Managing IBM Cloud secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-manage-secrets-ibm-cloud). If you don't already have an instance of the secrets management vault provider of your choice, create one.
* Optional. A namespace that is created by using the container registry command line. To create a namespace, type the following command from the command line:

ibmcloud cr namespace-add <my namespace>

Alternatively, you can create a namespace on the [Container Registry](https://cloud.ibm.com/registry/namespaces) page. For more information about creating a namespace in this location, see [IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgetting-started) service.





 Related content 



* [Getting started with Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started)
* [Getting started with clusters](https://cloud.ibm.com/docs/containers?topic=containers-getting-started)
* [Getting started with toolchains](https://cloud.ibm.com/devops/getting-started)









 Step 1: Create the toolchain 

In this step, you create a Develop and Deploy application to Kubernetes using deployment strategies toolchain. The target Kubernetes cluster is configured during the toolchain setup by using your IBM Cloud API key and your Kubernetes cluster name. You can change these settings later by updating the Delivery Pipeline configuration.
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. Make sure to set the cluster namespace to default and click Create.



In a new browser tab open the [Kubernetes clusters](https://cloud.ibm.com/kubernetes/clusters):



* Click on your cluster.
* Locate the Ingress subdomain field and click the copy button. The ingress subdomain will be used in the next section.



The toolchain will build your application and deploy it to the cluster.



1. Once the pipeline is created, click the pipeline under Delivery Pipelines.
2. Wait for the DEPLOY stage to complete. The Check health job will fail for VPC clusters.
3. Click on the settings cog in the DEPLOY stage and click Configure stage.



* Click the Environment properties tab at the top.
* Click Add property, click Text property.
* Enter Name: HELM_UPGRADE_EXTRA_ARGS.
* Enter Value: --set ingress.enabled=true,ingress.hosts={dev.INGRESS_SUBDOMAIN} something like: --set ingress.enabled=true,ingress.hosts={dev.vpc-e7f2ca73139645ddf61a8702003a483a-0000.us-south.containers.appdomain.cloud}.



4. Click Save.
5. Click the play button on DEPLOY stage.
6. In a browser tab paste the dev.INGRESS_SUBDOMAIN of the cluster.
Verify that the cluster that you want to use meets the [minimum hardware requirements for Portworx](https://docs.portworx.com/start-here-installation/).
2. If you want to use a virtual machine cluster, make sure that you [added raw, unformatted, and unmounted block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesmanual_block) to your cluster so that Portworx can include the disks into the Portworx storage layer.
3. Verify that your cluster is set up with public network connectivity. For more information, see [Understanding network basics of classic clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_clusters).







 Step 3: Reach out to Portworx and IBM 

Contact Portworx support by using one of the following methods.



* Sending an e-mail to support@purestorage.com.
* Calling +1 (866) 244-7121 or +1 (650) 729-4088 in the United States or one of the [International numbers](https://support.purestorage.com/Pure_Storage_Technical_Services/Technical_Services_Information/Contact_Us).
* Opening an issue in the [Portworx Service Portal](https://support.purestorage.com/Pure_Storage_Technical_Services/Technical_Services_Information/Contact_Us). If you don't have an account, see [Request access](https://purestorage.force.com/customers/CustomerAccessRequest).
* UI
* CLI
* Terraform







 Creating classic clusters 

Classic infrastructure

Use the IBM Cloud CLI or the IBM Cloud console to create a fully customizable standard cluster with your choice of hardware isolation and access to features like multiple worker nodes for a highly available environment.

Red Hat OpenShift on IBM Cloud clusters are created with a public only or both a public and private service endpoint. Public service endpoints can't be disabled, and therefore, you can't convert a public Red Hat OpenShift cluster to a private one. If you want your cluster to remain private, see [Planning your cluster network setup](https://cloud.ibm.com/docs/containers?topic=containers-plan_vpc_basicsvpc-pgw).



 Creating a classic cluster in the console 

Create your single zone or multizone classic Red Hat OpenShift cluster by using the IBM Cloud console. Follow the console instructions to make the following cluster configurations. To begin creating your cluster, navigate to the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift) and click Create cluster.

Location details
: When you create a cluster, its resources remain in the location that you deploy the cluster to.
: 

* 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. To create clusters in a resource group other than the default, you must have at least the [Viewer role](https://cloud.ibm.com/docs/openshift?topic=openshift-userschecking-perms) for the resource group.



: 

* Geography: Select an area to create the cluster in, such as North America. The geography helps filter the Availability and Metro values that you can select in the console.



: 

* Availability: A cluster can be created with a Single zone or Multizone configuration. A multizone cluster provides high availability, with the Red Hat OpenShift master deployed in a multizone-capable zone and three replicas of the master spread across different zones.



* For multizone clusters, choose a Metro location.
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.

ibmcloud oc dedicated host ls --pool a1a1a1a1a

Example output.

ID Zone Flavor State
aaaaa-aa-a1aaa1111aaa1aaa1a11-aaaaaaa1-a1aaaa1a us-south bx2d.host.16x64 created
6. Gather the details required to create a cluster.



1. List available subnets and note which one you want to use for the cluster.

ibmcloud is subnets

Example output.

ID Name Status Subnet CIDR Addresses ACL Public Gateway VPC Zone Resource group
1111-a11aaaa1-1a11-1111-1a1a-aaaaa1111111 a1a1a1a1 available xx.xxx.x.x/xx xxx/xxx xxxx-xxxx-xxxx-xxxx pgw-a1a1a1a1a1a1a my_vpc us-east-1 default
2. List available VPCs and note which one you want to use to create the cluster.

ibmcloud oc vpcs

Example output.

Name ID Provider
my_vpc a111-11a111a1-11a1-1a11-11a1-a1a1111a11a1 vpc-gen2
3. List available zones and note which one you want to create the cluster in.

ibmcloud oc zones --provider vpc-gen2

Example output.

ID Name Metro Flavors
us-east-1 us-east-1 Washington D.C. -
us-east-2 us-east-2 Washington D.C. -
us-east-3 us-east-3 Washington D.C. -
ibmcloud ks cluster create classic --zone dal10 --private-vlan my_private_VLAN_ID --flavor b3c.4x16 --name my_cluster --hardware shared --workers 2 --operating-system UBUNTU_20_64

Create subsequent standard clusters: If you already created a standard cluster in this zone or created a public VLAN in IBM Cloud infrastructure before, specify that public VLAN with the --public-vlan option. To find out whether you already have a public VLAN for a specific zone or to find the name of an existing public VLAN, run ibmcloud ks vlan ls --zone <zone>.

ibmcloud ks cluster create classic --zone dal10 --public-vlan my_public_VLAN_ID --private-vlan my_private_VLAN_ID --flavor b3c.4x16 --name my_cluster --hardware shared --workers 2 --operating-system UBUNTU_20_64







 ibmcloud ks cluster create vpc-gen2 

Virtual Private Cloud

Create a Virtual Private Cloud (VPC) cluster with worker nodes on Generation 2 infrastructure. When you log in to your IBM Cloud account, target the IBM Cloud region and resource group where you want to create your VPC cluster. For supported regions, see [Creating a VPC in a different region](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region). The cluster's resource group can differ from the VPC resource group.

VPC Gen 2 cluster flavors with instance storage are available for allowlisted accounts. To get added to the allowlist, [open a case](https://cloud.ibm.com/unifiedsupport/cases/form) with support.

Free clusters are not available in VPC.
"excluded": []
}





 Creating network zones from the CLI 



1. To create network zones from the CLI, [install the CBR CLI plug-in](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugininstall-cbr-plugin).
2. You can use the cbr-zone-create command to add resources to network zones. For more information, see the CBR [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-zones-cli). Note that the service_name for IBM Cloud Kubernetes Service is containers-kubernetes.

To find a list of available service refs, run the ibmcloud cbr service-ref-targets[command](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-cli-service-ref-targets-command).

Example command to add the containers-kubernetes service to a network zone.

ibmcloud cbr zone-create --name example-zone-1 --description "Example zone 1" --service-ref service_name=containers-kubernetes

The following example creates a network zone to allow a single public IP address to access. You can also use this example in conjunction with the [one IP example rule](https://cloud.ibm.com/docs/containers?topic=containers-cbrone-ip). For more information about this scenario, see [Setting up context-based restrictions](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorial).

ibmcloud cbr zone-create --addresses 129.41.86.7 --description "Allow only client IP" --name allow-client-ip







 Creating network zones from the console 



1. Determine the resources that you want add to your allowlist.
2.
As the cluster user, follow the steps in [Adding Block Storage for VPC to your apps](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-block-add) to create a PVC from your customized storage class.









 Setting up volume expansion 

To provision volumes that support expansion, you must use storage class that has allowVolumeExpansion set to true.

You can only expand volumes that are mounted by an app pod.

[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)



1. If you are not using version 4.2 or later of the add-on, [update the Block Storage for VPC add-on in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-addon-update).
2. [Create a PVC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc_block_qs) that uses a storage class that supports volume expansion.
3. [Deploy an app](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc_block_qs) that uses your PVC. When you create your app, make a note of the mountPath that you specify.
4. After your PVC is mounted by an app pod, you can expand your volume by editing the value of the spec.resources.requests.storage field in your PVC. To expand your volume, edit your PVC and increase the value in the spec.resources.requests.storage field.

kubectl edit pvc <pvc-name>

Example

spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
5. Save and close the PVC.
6. Optional: Verify that your volume is expanded.
Continue with your Portworx setup by [Setting up a key-value store for Portworx metadata](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_kv_store).







 Satellite clusters 

Satellite



1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
2. Create VMs in your cloud provider or set up on-premises hosts that have at least 16 vCPU and 64 GB and enough storage to be attached to your location plus additional storage volumes for app data, the Portworx journal, and KVDB. For highly available data storage, Portworx requires at least 3 worker nodes with raw and unformatted block storage.
3. If you want to use [journal devices](https://docs.portworx.com/install-with-other/operate-and-maintain/performance-and-tuning/tuning/), choose from the following options. Journal devices allow Portworx to write logs directly to a local disk on your worker node.



* Attach an additional 3 GB disk to at least 3 worker nodes in your cluster and find the device path. To find the device path after you attach the disk, log in to your worker node with oc debug <node> and run lsblk to list the devices on that node.
* Select a device on a worker node where you want Portworx to create the journal.



4. If you want to use a specific device for the internal Portworx KVDB, choose from the following options.



* Attach an additional disk to at least 3 worker nodes use for the KVDB, add a 3 GB block storage device to at least 3 worker nodes in your cluster and find the device path. To find the device path after attaching the disk, log in to your worker node with oc debug <node> and run lsblk to list the devices on that node.
* Select one of the block storage devices that you added earlier to use for the KVDB and find the device path.
Complete the [prerequisite steps](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkms_prereqs) to create a KMS instance and root key. If you want to use cross account KMS encryption, make sure to create the KMS and root key in the account whose KMS instance you want to use.
2. Get the ID of the KMS instance that you previously created.

ibmcloud ks kms instance ls
3. Get the ID of the root key that you previously created.

ibmcloud ks kms crk ls --instance-id <KMS_instance_ID>
4. Enable the KMS provider to encrypt secrets in your cluster. Fill in the options with the information that you previously retrieved. The KMS provider's private cloud service endpoint is used by default to download the encryption keys. To use the public cloud service endpoint instead, include the --public-endpoint option. The enablement process can take some time to complete.

ibmcloud ks kms enable -c <cluster_name_or_ID> --instance-id <kms_instance_ID> --crk <root_key_ID> [--public-endpoint]

During the enablement, you might not be able to access the Kubernetes master such as to update YAML configurations for deployments.
5. Verify that the KMS enablement process is finished. The process is finished when that the Master Status is Ready and Key management service is enabled.

ibmcloud ks cluster get -c <cluster_name_or_ID>

Example output when the enablement is in progress

NAME: <cluster_name>
ID: <cluster_ID>
...
Master Status: Key management service feature enablement in progress.

Example output when the master is ready

NAME: <cluster_name>
ID: <cluster_ID>
...
Master Status: Ready (1 min ago)
...
Key Management Service: enabled
Adding clusters to vCenter Server multizone instances 

New deployments of VMware vCenter Server® multizone instances are no longer supported. You can still add and delete clusters, add and remove ESXi servers, and add and delete storage for existing multizone instances.

You can add workload or gateway clusters to vCenter Server multizone instances. When no longer needed, delete the clusters from your instance.



 Procedure to add workload clusters to vCenter Server multizone 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 multizone instance that you want to add the workload cluster to.
3. Click the Infrastructure tab and click Create on the upper right of the Workload clusters table.
4. On the Create cluster page, enter the cluster name.
5. Select the CPU model, the amount of RAM, and the Number of bare metal servers.
6. Specify the vSAN storage settings. Specify the disk types for the capacity and cache disks and the number of disks. Optionally, select the Enable vSAN deduplication and compression checkbox. For more information, see [Enable vSAN deduplication and compression](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclustersvc_addingclusters-vsan-storage-enable-comp).
7. On the Summary pane, review the cluster settings and the estimated price.



* To save the settings as a new configuration template without placing an order, click Save configuration, enter a name for the configuration, and click Continue.
* To save the updates to a saved configuration, click Save configuration, select Modify current configuration, and click Continue.
* To save the updates to a new saved configuration, click Save configuration, select Create new configuration, enter a new name for the configuration, and click Continue.



8. To place the order, ensure that the account to be charged is correct, review and accept the terms, and click Create.







 Procedure to add gateway clusters to vCenter Server multizone instances