vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud oc zone add classic --zone <zone> --cluster <cluster_name_or_ID> --worker-pool <pool_name> --private-vlan <private_VLAN_ID> --public-vlan <public_VLAN_ID>





 Creating 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/openshift?topic=openshift-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/openshift?topic=openshift-clusters&interface=cli).

Create a VPC cluster with three worker nodes.

ibmcloud oc cluster create vpc-gen2 --name my_cluster --version 4.11_openshift --zone us-east-1 --vpc-id <VPC_ID> --subnet-id <VPC_SUBNET_ID> --cos-instance <COS_CRN>--flavor bx2.4x16 --workers 3

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

ibmcloud oc zone add vpc-gen2 --zone <zone> --cluster <cluster_name_or_ID> --worker-pool <pool_name> --subnet-id <VPC_SUBNET_ID>





 Deploying an app with the Red Hat OpenShift service catalog 

From the Red Hat OpenShift console, you can deploy one of the built-in service catalog apps and expose the app with a route.
* [28 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july2820)



* Ingress ALB versions
* UI for creating clusters



* [24 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july2420)



* Minimum cluster size
* Versions
* Worker node replacement



* [21 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july2120)



* New! Red Hat OpenShift version 4.4 clusters



* [20 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july2020)



* Master versions
* Worker node versions



* [16 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july1620)



* Ingress ALB change log
* Pod and service subnets



* [7 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july0720)



* CLI change log



* [6 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july0620)



* Version change logs



* [2 July 2020](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-july0220)



* Comparison between IBM Cloud and OCP clusters
* Global settings
* Private-only VPC clusters
* VPC load balancer
Reader service role to the IBM Cloud Object Storage instance that backs up the location control plane data. 
 App developers Viewer platform role for the Satellite location. Writer or Deployer service access role for the configuration resources. Editor platform role and Writer service role to Red Hat OpenShift clusters or particular projects in a cluster. 
 Billing Viewer platform role for all the Satellite locations in the account. 
 Location administrator Administrator platform role for the location and link resources. Administrator platform role to Red Hat OpenShift clusters. Manager service role to the IBM Cloud Object Storage instance that backs up the location control plane data. 
 DevOps operator Editor platform role for the location and link resources. Deployer service role for the configurations. Operator platform role to Red Hat OpenShift clusters. 
 Operator or site reliability engineer Administrator platform role for the location and link resources. Manager service role for the configuration resources. Administrator platform role and Manager service role to Red Hat OpenShift clusters.
: Added a [debugging guide for the cluster autoscaler](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_cluster_autoscaler).

Expanded troubleshooting
: You can now find troubleshooting steps for Red Hat OpenShift clusters in the following pages.



* [Clusters and masters](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters)
* [Worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters)
* [Cluster networking](https://cloud.ibm.com/docs/openshift?topic=openshift-roks_ts_subdomain)
* [Apps and integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_apps)
* [Load balancers](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_loadbalancer_fails)
* [Ingress](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4)



Tags
: Added how to [add IBM Cloud tags to existing clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workerscluster_tags).

VPC security groups
: [Modify the security group rules](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-security-group)for VPC Gen 2 clusters to allow traffic requests that are routed to node ports on your worker nodes.





 3 February 2020 

Version change log
You can add or reduce the number of worker nodes in your cluster by resizing an existing worker pool, regardless of whether the worker pool is in one zone or spread across multiple zones. For more information, see [Adding worker nodes and zones to clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workers).





 Step 8: Update clusters, worker nodes, and cluster components 

You can install updates to keep your Red Hat OpenShift on IBM Cloud cluster up to date. For more information, see [Updating clusters, worker nodes, and cluster components](https://cloud.ibm.com/docs/openshift?topic=openshift-update).
Review the prerequisites for the [Metro DR](https://docs.portworx.com/portworx-install-with-kubernetes/disaster-recovery/px-metro/1-install-px/prerequisites) and [Asynchronous DR](https://docs.portworx.com/portworx-install-with-kubernetes/disaster-recovery/async-dr/pre-requisites) configuration.
3. Configure disaster recovery for your cluster. Metro DR:



1. Choose at least two Kubernetes clusters that are located in the same metro location. If you have one cluster only, you can still configure this cluster for metro disaster recovery, but Portworx can't do a proper failover until a second cluster is configured.
2. Make sure that all your clusters have sufficient [raw and unformatted block storage](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesmanual_block) so that you can build your Portworx storage layer.
3. Set up a [Databases for etcd service instance](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_kv_store) for your Portworx key-value store. Because both Kubernetes clusters must share the key-value store, you can't use the internal Portworx KVDB.
4. Optional: Decide if you want to set up [encryption for your Portworx volumes](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_encryption).
5. Follow the instructions to [install Portworx](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_deploy) with the disaster recovery plan in both of your clusters. If you installed Portworx without the disaster recovery plan in one of your clusters already, you must re-install Portworx in that cluster with the disaster recovery plan.
Next, your developers can [configure their application pods to exchange the identity token for an IAM token to authenticate requests to IBM Cloud services](https://cloud.ibm.com/docs/openshift?topic=openshift-pod-iam-identityiam-identity-pod).





 Creating an IAM trusted profile for your cluster in the UI 

As an account administrator, create a trusted profile in IBM Cloud Identity and Access Management. For more information, see the [IAM documentation](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile&interface=ui).

Before you begin: Verify that you meet the [prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-pod-iam-identityiam-identity-prereqs).



1. Log in to the [IBM Cloud IAM Trusted profiles console](https://cloud.ibm.com/iam/trusted-profiles).
2. Click Create.
3. Give your trusted profile a name and click Continue.
4. For trust entity type, select Compute resources.
5. For compute service, select Kubernetes.
6. For compute resources, choose among the following options to determine which clusters or resources in the cluster can establish trust.



* All service resources: Any existing and future clusters. To link the trusted profile only to clusters under certain conditions, you can Add new condition +. For example, you might add conditions such as only clusters in a resource group, only clusters with a prod Kubernetes namespace, or only clusters with a trusted-profile Kubernetes service account.
* Specific resources: A particular cluster. Click Add another resource + to select a cluster and fill out conditions such as the Kubernetes namespace or Kubernetes service account that can establish trust.
* Click Continue.



The Kubernetes namespace and service account names that you enter don't have to exist already. Any future namespaces or service accounts with these names can establish trust.
Next, your developers can [configure their application pods to exchange the identity token for an IAM token to authenticate requests to IBM Cloud services](https://cloud.ibm.com/docs/containers?topic=containers-pod-iam-identityiam-identity-pod).





 Creating an IAM trusted profile for your cluster in the UI 

As an account administrator, create a trusted profile in IBM Cloud Identity and Access Management. For more information, see the [IAM documentation](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile&interface=ui).

Before you begin: Verify that you meet the [prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-pod-iam-identityiam-identity-prereqs).



1. Log in to the [IBM Cloud IAM Trusted profiles console](https://cloud.ibm.com/iam/trusted-profiles).
2. Click Create.
3. Give your trusted profile a name and click Continue.
4. For trust entity type, select Compute resources.
5. For compute service, select Kubernetes.
6. For compute resources, choose among the following options to determine which clusters or resources in the cluster can establish trust.



* All service resources: Any existing and future clusters. To link the trusted profile only to clusters under certain conditions, you can Add new condition +. For example, you might add conditions such as only clusters in a resource group, only clusters with a prod Kubernetes namespace, or only clusters with a trusted-profile Kubernetes service account.
* Specific resources: A particular cluster. Click Add another resource + to select a cluster and fill out conditions such as the Kubernetes namespace or Kubernetes service account that can establish trust.
* Click Continue.



The Kubernetes namespace and service account names that you enter don't have to exist already. Any future namespaces or service accounts with these names can establish trust.
* [Multiple public clusters connected with a global load balancer](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmultiple-clusters-glb)



* [Why do I need 3 clusters in three zones?](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmulticluster-three-zones)
* [What if I want to set up multiple clusters across regions?](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmultiple-regions-setup)
* [What options do I have to load balance workloads across multiple clusters?](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmultiple-cluster-lb-options)
* [Setting up a CIS global load balancer](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clusterscis-global-lb-setup)
* [Setting up your own global load balancer](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersbyo-global-lb-setup)
* [What if I want to load balance workloads on the private network?](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersglb-private)





[Planning your worker node setup](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes)



* [Available hardware for worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesshared_dedicated_node)



* [What flavors are available to me?]
Next, your developers can [configure their application pods to exchange the identity token for an IAM token to authenticate requests to IBM Cloud services](https://cloud.ibm.com/docs/containers?topic=containers-pod-iam-identity&interface=uiiam-identity-pod).





 Creating an IAM trusted profile for your cluster in the UI 

As an account administrator, create a trusted profile in IBM Cloud Identity and Access Management. For more information, see the [IAM documentation](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile&interface=ui).

Before you begin: Verify that you meet the [prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-pod-iam-identity&interface=uiiam-identity-prereqs).



1. Log in to the [IBM Cloud IAM Trusted profiles console](https://cloud.ibm.com/iam/trusted-profiles).
2. Click Create.
3. Give your trusted profile a name and click Continue.
4. For trust entity type, select Compute resources.
5. For compute service, select Kubernetes.
6. For compute resources, choose among the following options to determine which clusters or resources in the cluster can establish trust.



* All service resources: Any existing and future clusters. To link the trusted profile only to clusters under certain conditions, you can Add new condition +. For example, you might add conditions such as only clusters in a resource group, only clusters with a prod Kubernetes namespace, or only clusters with a trusted-profile Kubernetes service account.
* Specific resources: A particular cluster. Click Add another resource + to select a cluster and fill out conditions such as the Kubernetes namespace or Kubernetes service account that can establish trust.
* Click Continue.



The Kubernetes namespace and service account names that you enter don't have to exist already. Any future namespaces or service accounts with these names can establish trust.
If your single zone cluster is created in one of the [multizone metro locations](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-mz), you can change your single zone cluster to a [multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmz-clusters). In a multizone cluster, your workloads are distributed across worker nodes in different zones. If one zone is not available, your workloads continue to run in the remaining zones. If you prefer single zone clusters for simplified management, or if your cluster must reside in a specific [single zone city](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-sz) that does not support multizone capabilities, you can create [multiple clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmultiple-clusters-glb) and connect them with a global load balancer.







 Multizone cluster 

Create a multizone cluster to distribute your workloads across multiple worker nodes and zones, and protect against zone failures with hosts, networks, or apps. If resources in one zone go down, your cluster workloads continue to run in the other zones.

Zoom

![High availability for multizone clusters.](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/ha-cluster-multizone.svg)

Figure 1. High availability for multizone clusters

In a multizone cluster, the worker nodes in your worker pools are replicated across multiple zones within one region. Multizone clusters are designed to evenly schedule pods across worker nodes and zones to assure availability and failure recovery.
: Added a [troubleshooting topic](https://cloud.ibm.com/docs/containers?topic=containers-alb-pod-affinity) for when ALB pods don't deploy correctly to worker nodes.







 April 2020 



 30 April 2020 

Cluster and worker node quotas
: Now, each region in your IBM Cloud account has quotas for Kubernetes Service clusters and workers. You can have 100 clusters and 500 worker nodes across clusters per region and per [infrastructure provider](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providers). With quotas in place, your account is better protected from accidental requests or billing surprises. Need more clusters? No problem, just [contact IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the support case, include the new cluster or worker node quota limit for the region and infrastructure provider that you want. For more information, see the [Service limitations](https://cloud.ibm.com/docs/containers?topic=containers-limitations).





 29 April 2020 

ALB pod scaling
: Added steps for scaling up your ALB processing capabilities by [increasing the number of ALB pods replicas](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-managealb_replicas).

VPC cluster architecture
: Refreshed [networking diagrams for VPC scenarios](https://cloud.ibm.com/docs/containers?topic=containers-service-archarchitecture_vpc).

VPC cluster master access
: Updated [accessing the master via a private cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_clustervpc_private_se) for VPC clusters.





 27 April 2020 

Ingress ALB change log
(https://cloud.ibm.com/docs/containers?topic=containers-ts-addon-istio-webhooksts-addon-istio-webhooks)

[Why does my custom gateway Istio operator have a reconcile loop error?](https://cloud.ibm.com/docs/containers?topic=containers-istio_control_planeistio_control_plane)

[How do I delete Operator Lifecycle Manager components?](https://cloud.ibm.com/docs/containers?topic=containers-ts-delete-olmts-delete-olm)





 Load balancers 

[Why can't my app connect via a network load balancer (NLB) service?](https://cloud.ibm.com/docs/containers?topic=containers-cs_loadbalancer_failscs_loadbalancer_fails)

[Classic clusters: Why can't I deploy a load balancer?](https://cloud.ibm.com/docs/containers?topic=containers-cs_subnet_limit_lbcs_subnet_limit_lb)

[Classic clusters: Why does source IP preservation fail when using tainted nodes?](https://cloud.ibm.com/docs/containers?topic=containers-cs_source_ip_fails_lbcs_source_ip_fails_lb)

[VPC clusters: Why can't my app connect via load balancer?](https://cloud.ibm.com/docs/containers?topic=containers-vpc_ts_lbvpc_ts_lb)

[VPC clusters: Why does a Kubernetes LoadBalancer service fail with no IPs?](https://cloud.ibm.com/docs/containers?topic=containers-vpc_no_lbvpc_no_lb)

[Why do I see SyncLoadBalancerFailed errors when creating a VPC cluster?](https://cloud.ibm.com/docs/containers?topic=containers-ts-loadbalancer-sync-failedts-loadbalancer-sync-failed)
* Disable Distributed Power Management (DPM) if it is enabled for any of the selected clusters - VUM does not remediate clusters with active DPM. DPM monitors the resource use of the running VMs in the cluster. If sufficient excess capacity exists, DPM recommends moving VMs to other hosts in the cluster and placing the original host into standby mode to conserve power. Putting hosts into standby mode might interrupt remediation.
* Disable High Availability admission control if it is enabled for any of the selected clusters - VUM does not remediate clusters with active HA admission control. Admission control is a policy that is used by VMware HA to ensure failover capacity within a cluster. If HA admission control is enabled during remediation, the VMs within a cluster might not migrate with vMotion.
* Disable Fault Tolerance (FT) if it is enabled - This setting affects all fault tolerant VMs in the selected clusters. If FT is turned on for any of the VMs on a host, VUM does not remediate that host. For FT to be enabled, the hosts on which the primary and secondary VMs run must be of the same version and must have the same patches installed. If you apply different patches to these hosts, FT cannot be reenabled.
* Enable parallel remediation for the hosts in the selected clusters - Remediate hosts in clusters in a parallel manner. If the setting is not selected, VUM remediates the hosts in a cluster sequentially. You can select one of the following options for parallel remediation:



* You can let VUM continuously evaluate the maximum number of hosts it can remediate concurrently without disrupting DRS settings.
* You can specify a limit of the number of concurrently remediated hosts in each cluster you remediate. Note, VUM remediates concurrently only the hosts on which VMs are powered off or suspended. You can choose to power off or suspend VMs from the VM Power State menu in the Maintenance Mode Options pane on the Host Remediation Options page. By design only one host from a vSAN cluster can be in a maintenance mode at any time.
NAME READY UP-TO-DATE AVAILABLE AGE
router-default 2/2 2 2 26m
2. Check whether the Ingress controller's load balancer service exists and is assigned a public external IP address (classic clusters) or a hostname (VPC clusters).



* If a service that is named router-default is listed and is assigned an IP address (classic clusters) or a hostname (VPC clusters), continue to the next step.
* If no router-default service is created after several minutes, [review ways to get help](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).



oc get svc -n openshift-ingress

Example output

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
router-default LoadBalancer 172.21.47.119 169.XX.XX.XX 80:31182/TCP,443:31154/TCP 27m
router-internal-default ClusterIP 172.21.51.30 <none> 80/TCP,443/TCP,1936/TCP 26m



5. Check again whether the Ingress subdomain and secret are created. If they are not available, but you verified that all the components in steps 1 - 3 exist, [review ways to get help](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).

ibmcloud oc cluster get -c <cluster_name_or_ID>
* [Installing with a script](https://cloud.ibm.com/docs/containers?topic=containers-add_workersintel-sgx-script)



* [Adding tags to existing clusters](https://cloud.ibm.com/docs/containers?topic=containers-add_workerscluster_tags)



* [Adding tags to clusters with the console](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd-tags-console)
* [Adding tags to clusters with the CLI](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd-tags-cli)



* [Adding labels to existing worker pools](https://cloud.ibm.com/docs/containers?topic=containers-add_workersworker_pool_labels)
* [Automatically resolving issues for your worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-add_workersplanning_autorecovery)



[Creating and managing dedicated hosts on VPC Gen 2 infrastructure](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsdedicated-hosts)



* [Setting up dedicated hosts in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostssetup-dedicated-host-cli)
* [Removing worker nodes from a dedicated host in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsremove-worker-nodes-cli)
* [Removing dedicated hosts in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsremove-dedicated-hosts-cli)
* [Removing dedicated hosts pools in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostsremove-dedicated-host-pool-cli)





 Autoscaling clusters