vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* If you installed Istio manually or used the Istio community Helm chart, see the [Istio uninstall documentation](https://istio.io/latest/docs/setup/getting-started/uninstall).
* If you previously installed BookInfo in the cluster, clean up those resources.



1. Change the directory to the Istio file location.

cd <filepath>/istio-1.18.0
2. Delete all BookInfo services, pods, and deployments in the cluster.

samples/bookinfo/platform/kube/cleanup.sh
3. The uninstallation process can take up to 10 minutes. Before you install the Istio managed add-on in the cluster, run kubectl get namespaces and verify that the istio-system namespace is removed.











 Troubleshooting 

To resolve some common issues that you might encounter when you use the managed Istio add-on, see [Troubleshooting managed add-ons](https://cloud.ibm.com/docs/containers?topic=containers-debug_addons).
In a production-ready environment, of course, you need to size the servers and the volumes according to the number of concurrent users and the expected amount of data and further parameters. Find more in the topic [!Sizing process for SAP Systems](/docs/sap?topic=sap-sizing).
{: important}

Depending on the database vendor you should consult their specific documentation, recommendations and best practises how to setup the file systems. You may start here.
* [IBM Db2](/docs/sap?topic=sap-anydb-ibm-db2)
* [SAP MaxDB](/docs/sap?topic=sap-anydb-ibm-maxdb)
* [SAP ASE](/docs/sap?topic=sap-anydb-ase)

We let sapinst, the SAP installation programm, care about the user management, the disk partitioning as well as folder and subfolder creations that are required for the SAP application and the RDBMS.

 Logging in to your Windows VSI

You can access the newly created VSI with Windows Remote Desktop. Enter the Floating IP and the Administrator password that you retrieved during the steps that are described previously.

 Initializing the block storage for Windows disk usage

1. Start the Windows Server Disk Management
(../icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.Figure 1. Windows Server Disk Manager]
1. Find the block storage - usually it is Disk 2 and shows the ordered size and the status offline
1. Right-click the Disk tile and select online from the menu
1. Again right-click the Disk tile and select Initialize Disk from the menu, check to make sure that the correct disk is selected, select GPT as the default partition style - see footnote (+) below - and click Ok
1. Now right-click the related tile to the right that shows Unallocated and select New Simple Volume...
1. Click Next twice, which retains the default value for the disk size and then specify your preferred drive letter, or leave the default and click Next
1.
Asia Pacific Japan Osaka jp-osa jp-osa-1, jp-osa-2, jp-osa-3 
 Asia Pacific Japan Tokyo jp-tok jp-tok-1, jp-tok-2, jp-tok-3 
 Europe Germany Frankfurt eu-de eu-de-1, eu-de-2, eu-de-3 
 Europe United Kingdom London eu-gb eu-gb-1, eu-gb-2, eu-gb-3 
 North America Canada † Toronto ca-tor ca-tor-1, ca-tor-2, ca-tor-3 
 North America United States Dallas us-south us-south-1, us-south-2, us-south-3 
 North America United States Washington DC us-east us-east-1, us-east-2, us-east-3 
 South America Brazil † São Paulo br-sao br-sao-1, br-sao-2, br-sao-3 



†Toronto and São Paulo multizone regions: Toronto and São Paulo are available as multizone regions for clusters on VPC infrastructure only.





 Resources in a single zone cluster 

In a single zone cluster, your cluster's resources remain in the data center (zone) in which the cluster is deployed, but management operations might be routed through a regional endpoint.

Your cluster's resources, including the master and worker nodes, are in the same zone that you deployed the cluster to. When you initiate local container orchestration actions, such as oc commands, the information is exchanged between your master and worker nodes within the same zone.

If you set up other cluster resources, such as storage, networking, compute, or apps running in pods, the resources and their data remain in the zone that you deployed your cluster to.

When you initiate cluster management actions, such as running ibmcloud oc commands, basic information about the cluster such as name, ID, user, the command is routed through a regional endpoint and the global endpoint.





 Resources in a multizone cluster 

In a multizone cluster, your cluster's resources are spread across multiple zones for higher availability.

Worker nodes are spread across multiple zones in the metro location to provide more availability for your cluster. The Kubernetes master replicas are also spread across zones.
Asia Pacific Japan Osaka jp-osa jp-osa-1, jp-osa-2, jp-osa-3 
 Asia Pacific Japan Tokyo jp-tok jp-tok-1, jp-tok-2, jp-tok-3 
 Europe Germany Frankfurt eu-de eu-de-1, eu-de-2, eu-de-3 
 Europe United Kingdom London eu-gb eu-gb-1, eu-gb-2, eu-gb-3 
 North America Canada † Toronto ca-tor ca-tor-1, ca-tor-2, ca-tor-3 
 North America United States Dallas us-south us-south-1, us-south-2, us-south-3 
 North America United States Washington DC us-east us-east-1, us-east-2, us-east-3 
 South America Brazil † São Paulo br-sao br-sao-1, br-sao-2, br-sao-3 



†Toronto and São Paulo multizone regions: Toronto and São Paulo are available as multizone regions for clusters on VPC infrastructure only.





 Resources in a single zone cluster 

In a single zone cluster, your cluster's resources remain in the data center (zone) in which the cluster is deployed, but management operations might be routed through a regional endpoint.

Your cluster's resources, including the master and worker nodes, are in the same zone that you deployed the cluster to. When you initiate local container orchestration actions, such as kubectl commands, the information is exchanged between your master and worker nodes within the same zone.

If you set up other cluster resources, such as storage, networking, compute, or apps running in pods, the resources and their data remain in the zone that you deployed your cluster to.

When you initiate cluster management actions, such as running ibmcloud ks commands, basic information about the cluster such as name, ID, user, the command is routed through a regional endpoint and the global endpoint.





 Resources in a multizone cluster 

In a multizone cluster, your cluster's resources are spread across multiple zones for higher availability.

Worker nodes are spread across multiple zones in the metro location to provide more availability for your cluster. The Kubernetes master replicas are also spread across zones.
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 

Add zones to the default worker pool in your cluster that you created in step 1. By adding zones, the same number of worker nodes that you created in step 2 are spread across these zones converting your single zone cluster into a multizone cluster.



1. Open your Terraform on IBM Cloud configuration file and add the following content to your configuration. For each zone that you want to add, you must add a separate ibm_container_worker_pool_zone_attachment resource.

resource "ibm_container_worker_pool_zone_attachment" "dal12" {
cluster = ibm_container_cluster.tfcluster.id
worker_pool = ibm_container_cluster.tfcluster.worker_pools.0.id
zone = "dal12"
private_vlan_id = "<private_vlan_ID_dal12>"
public_vlan_id = "<public_vlan_ID_dal12>"
resource_group_id = data.ibm_resource_group.resource_group.id
}

resource "ibm_container_worker_pool_zone_attachment" "dal13" {
cluster = ibm_container_cluster.tfcluster.id
worker_pool = ibm_container_cluster.tfcluster.worker_pools.0.id
zone = "dal13"
private_vlan_id = "<private_vlan_ID_dal13>"
public_vlan_id = "<public_vlan_ID_dal13>"
resource_group_id = data.ibm_resource_group.resource_group.id
}
Show more
* [ibmcloud oc cluster config](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_config)
* cluster create: Create a classic or VPC cluster.



* [ibmcloud oc cluster create classic](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_create)
* [ibmcloud oc cluster create vpc-gen2](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicli_cluster-create-vpc-gen2)



* [ibmcloud oc cluster get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_get)
* cluster image-security: Manage image security enforcement in your cluster.



* [ibmcloud oc cluster image-security disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics-image-security-disable)
* [ibmcloud oc cluster image-security enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics-image-security-enable)



* [ibmcloud oc cluster ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_clusters)
* cluster master: View and modify the master for a cluster.



* cluster master audit-webhook: View and modify the audit webhook configuration for a cluster's Kubernetes API server.
* [ibmcloud oc cluster config](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_config)
* [ibmcloud oc cluster create classic](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_create)
* [ibmcloud oc cluster create vpc-gen2](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicli_cluster-create-vpc-gen2)
* [ibmcloud oc cluster get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_get)
* [ibmcloud oc cluster image-security disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics-image-security-disable)
* [ibmcloud oc cluster image-security enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics-image-security-enable)
* [ibmcloud oc cluster ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_clusters)
* [ibmcloud oc cluster master pod-security get](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicluster-master-pod-security-get)
* [ibmcloud oc cluster master pod-security policy disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicluster-master-pod-security-policy-disable)
Because Satellite Config works across Satellite locations, you can [add your new clusters to existing cluster groups](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig-groups) that are already [subscribed to the configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-upload) that you want to deploy.
9. Similar to Satellite Config, if you used Satellite storage configurations, you can assign these configurations to your new clusters to install the storage drivers.



When you are done and your new location is healthy, you can [remove the previous location](https://cloud.ibm.com/docs/satellite?topic=satellite-host-removelocation-remove-console).
Created: 2018-09-28T15:43:15+0000
Location: dal10
Pod Subnet: 172.30.0.0/16
Service Subnet: 172.21.0.0/16
Master URL: https://c3.<region>.containers.cloud.ibm.com:30426
Public Service Endpoint URL: https://c3.<region>.containers.cloud.ibm.com:30426
Private Service Endpoint URL: https://c3-private.<region>.containers.cloud.ibm.com:31140
Master Location: Dallas
Master Status: Ready (21 hours ago)
Ingress Subdomain: mycluster-<hash>-0000.us-south.containers.appdomain.cloud
Ingress Secret: mycluster-<hash>-0000
Workers: 6
Worker Zones: dal10, dal12
Version: 1.26_1524
Owner: owner@email.com
Resource Group ID: a8a12accd63b437bbd6d58fb6a462ca7
Resource Group Name: Default









 Managing Satellite worker pools 

Review the following differences from classic Red Hat OpenShift on IBM Cloud clusters when you manage the worker pool life cycle of clusters that are in a Satellite location.



 Creating Satellite worker pools with host labels for autoassignment 

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.
To determine whether a location has a multizone region, your can run ibmcloud oc locations and look for the value in the Multizone Metro column.



Available multizone metro locations for classic clusters in Red Hat OpenShift on IBM Cloud.

 Geography Country Metro Region Zones 

 Asia Pacific Australia Sydney au-syd syd01, syd04, syd05 
 Asia Pacific Japan Osaka jp-osa osa21, osa22, osa23 
 Asia Pacific Japan Tokyo jp-tok tok02, tok04, tok05 
 Europe Germany Frankfurt de-fra fra02, fra04, fra05 
 Europe United Kingdom London uk-lon lon02, lon04, lon05, lon06 
 North America United States Dallas us-dal dal10, dal12, dal13 
 North America United States Washington DC us-wdc wdc04, wdc06, wdc07 







 Classic single zone regions 

If you create a classic cluster in a single zone region, you can create multiple worker nodes but you can't spread them across data centers (zones). The highly available master includes three replicas on separate hosts, but is not spread across zones.

Classic single zone clusters are managed from the regional endpoint located in the nearest region that supports classic multizone, such as mon01 to us-east or sao01 to us-south.



Available single zone data center locations for classic clusters in Red Hat OpenShift on IBM Cloud.

 Geography Country Metro Region Zone Managed from region 

 Asia Pacific India Chennai in-che che01 AP North (ap-north, jp-tok) 
 Asia Pacific Singapore Singapore sng-mtr sng01 AP North (ap-north, jp-tok) 
 Europe Italy Milan it-mil mil01 EU Central (eu-central, eu-de) 
 Europe Netherlands Amsterdam nl-ams ams03 EU Central (eu-central, eu-de) 
 North America Canada Montreal ca-mon mon01 US East (us-east) 
 North America Canada Toronto ca-tor tor01 US East (us-east)
"10.XXX.XXX.XXX",
"10.XXX.XXX.XXX",
"10.XXX.XXX.XXX",
"10.XXX.XXX.XXX",
"10.XXX.XXX.XXX"
],
"is_public": false,
"is_byoip": false,
"cidr": "10.XXX.XXX.X/29"
}
],
"zone": "dal10",
"region": "us-south"
},
{
"id": "2234945",
"subnets":
{
"id": "2219170",
"ips":
"169.XX.XXX.XX",
"169.XX.XXX.XX",
"169.XX.XXX.XX",
"169.XX.XXX.XX",
"169.XX.XXX.XX"
],
"is_public": true,
"is_byoip": false,
"cidr": "169.XX.XXX.X/29"
}
],
"zone": "dal10",
"region": "us-south"
}
],
"vlan_errors": [],
"reserved_ips": []
}
cluster_id:
----
bmnj1b1d09lpvv3oof0g
reserved_private_ip:
----

reserved_private_vlan_id:
----

reserved_public_ip:
----

Events: <none>



* VPC clusters: Verify that the VPC load balancer for your ALBs exists. In the output, look for the VPC load balancer Name that starts with kube-<cluster_ID>.
To view your events, make sure that you have an Activity Tracker instance in the location that matches your cluster location. Note that clusters in the Montreal, Toronto, and Washington, D.C. locations forward all events to the Dallas Activity Tracker location.



Corresponding Activity Tracker instance and Red Hat OpenShift on IBM Cloud cluster locations.

 Red Hat OpenShift on IBM Cloud classic location Activity Tracker event location 

 Dallas (dal10, dal12, dal13) Dallas 
 Montreal (mon01) Washington, D.C. 
 San Jose (sjc03, sjc04) Dallas 
 São Paulo (sao01) Dallas 
 Toronto (tor01) Toronto 
 Washington, D.C. (wdc04, wdc06, wdc07) Washington, D.C. 
 Amsterdam (ams03) Frankfurt 
 Frankfurt (fra02, fra04, fra05) Frankfurt 
 Milan (mil01) Frankfurt 
 Paris (par01) Frankfurt 
 London (lon02, lon04, lon05, lon06) London 
 Sydney (syd01, syd04, syd05) Sydney 
 Chennai (che01) Chennai 
 Seoul (seo01) Seoul 
 Osaka (osa21, osa22, osa23) Osaka 
 Singapore (sng01) Tokyo 
 Tokyo (tok02, tok04, tok05) Tokyo 





Corresponding Activity Tracker instance and Red Hat OpenShift on IBM Cloud cluster locations.

 Red Hat OpenShift on IBM Cloud VPC location Activity Tracker event location 

 Dallas (us-south-1, us-south-2, us-south-3) Dallas 
 São Paulo (br-sao-1, br-sao-2, br-sao-3) Dallas 
 Washington, D.C. (us-east-1, us-east-2, us-east-3) Washington, D.C. 
 Toronto (ca-tor-1, ca-tor-2, ca-tor-3) Toronto 
 Frankfurt (eu-de-1, eu-de-2, eu-de-3) Frankfurt
Creating single and multizone Kubernetes and OpenShift clusters 

Use this tutorial to create single and multizone clusters with [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-iks-overview) or [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-roks-overview), and deploy your own set of compute hosts in the public cloud where you can run and manage highly available containerized apps.

In this tutorial, you create a standard classic IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud cluster with the following configuration:



* The cluster is created in the us-south region.
* The cluster is created with the default worker pool.
* All worker nodes are connected to a private and public VLAN. These public and private VLANs assign public and private IP addresses to the worker nodes.
* All worker nodes are created with a virtual worker node flavor on shared hardware. If you want to use a different worker node flavor, see the [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes) or [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodes) documentation.
* To allow access to your cluster from the internet and run public-facing app workloads in your cluster, the cluster is set up with both a public and a private service endpoint. For more information, about how network traffic flows when a public and a private service endpoint is enabled, see Worker-to-master and user-to-master communication: Service endpoints in [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-plan_clusters) and [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_clustersworkeruser-master).



Keep in mind that creating a cluster incurs costs.
The cluster can run in your Satellite location or in IBM Cloud. To add a cluster that runs in IBM Cloud, you must first [register the cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-register) with the Satellite Config component.

ibmcloud sat group attach --cluster CLUSTER [--cluster CLUSTER] --group GROUP [-q]



 Minimum required permissions 

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





 Command options 

--cluster, -c CLUSTER
: Required. The cluster that you want to add to the cluster group. To list registered clusters, run ibmcloud sat cluster ls.

--group, -g GROUP
: Required. The name or ID of the cluster group where you want to add the cluster. To list available cluster groups, run ibmcloud sat group ls.

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





 Example 

ibmcloud sat group attach --cluster mycluster --group mygroup







 ibmcloud sat group create 

Create a cluster group. After you created the cluster group, you can subscribe the cluster group to a Satellite configuration.

ibmcloud sat group create --name NAME [--cluster CLUSTER] [-q]



 Minimum required permissions 

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





 Command options 

--name NAME
: Required. The name for the cluster group.

--cluster, -c CLUSTER
: Optional. The name or ID of a cluster that you want to add to the cluster group.
GET/v2/getCACert Get the cluster's CA certificate. containers-kubernetes.cluster.view cluster-ca-certificate.get 
 POST/v2/rotateCACert Rotate the cluster's CA certificate. containers-kubernetes.cluster.create cluster-ca-certificate.rotate 
 POST/v2/createCA Create a CA certificate. cluster-ca-certificate.create containers-kubernetes.cluster.create 







 Cluster 

Review the following cluster API methods, their corresponding actions in IBM Cloud IAM, and the events that are sent to IBM Cloud Activity Tracker for Red Hat OpenShift on IBM Cloud.



Cluster API methods, IAM actions, and Activity Tracker events.

 API Method Description IAM action for the API Activity Tracker event 

 DELETE/v1/clusters/{idOrName} Delete a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.delete 
 DELETE/v1/clusters/{idOrName}/apiserverconfigs/auditwebhook Delete an audit webhook configuration. containers-kubernetes.cluster.operate containers-kubernetes.cluster.delete 
 DELETE/v1/clusters/{idOrName}/services/{namespace}/{serviceInstanceId} Unbind an IBM Cloud service from a cluster. containers-kubernetes.cluster.operate containers-kubernetes.service.delete 
 DELETE/v1/clusters/{idOrName}/usersubnets/{subnetId}/vlans/{vlanId} Remove a user-managed subnet from a cluster. containers-kubernetes.cluster.operate containers-kubernetes.vlan.delete 
 GET/v1/clusters List the clusters that you have access to. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName} View details for a cluster. containers-kubernetes.cluster.read N/A
* [Step 8: Check the OpenVPN](https://cloud.ibm.com/docs/openshift?topic=openshift-ocp-debugoc-debug-openvpn)
* [Step 9: Refresh the cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-ocp-debugoc-debug-refresh-master)
* [Step 10: Retry](https://cloud.ibm.com/docs/openshift?topic=openshift-ocp-debugoc-debug-retry)



[Cluster states](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-states-reference)



* [Aborted](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-aborted)
* [Critical](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-critical)
* [Create failed](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-create-failed)
* [Delete failed](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-delete-failed)
* [Deleted](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-deleted)
* [Deleting](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-deleting)