vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Adding ESXi servers to vCenter Server instances 

You can expand the capacity of your VMware® vCenter Server® instance according to your business needs by adding VMware ESXi™ servers.



 Before you add ESXi servers to vCenter Server instances 



* For existing instances with VMware vSphere® 6.5 or 6.7, you cannot add ESXi servers. To add ESXi servers, upgrade your vSphere® software to 7.0. For more information, see [Upgrading VMware vSphere software from vSphere 6.5 or 6.7 to 7.0](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphere_70_upgrade).
* For existing instances with vSphere 7.0u2, you can add only ESXi servers with vSphere 7.0u3.
* For the gateway cluster, you cannot add or delete ESXi servers.
* Whenever possible, add ESXi servers by using the IBM Cloud® for VMware Solutions console because changes that you make on the VMware vSphere® Web Client are not synchronized with the IBM Cloud for VMware Solutions console. Therefore, add ESXi servers to vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the IBM Cloud for VMware Solutions console.
* A vCenter Server instance with NFS storage must have at least three ESXi servers. Each of the nondefault clusters can be expanded to have up to 59 ESXi servers.
* A vCenter Server instance with vSAN™ storage must have at least four ESXi servers.
* If your initial cluster has vSAN storage, adding one or more ESXi servers after deployment can increase the cluster storage capacity.
* If your initial cluster has vSAN storage, SED SSD disks are no longer available. Non-SED SSD disks are ordered.
* You can add 1-20 ESXi servers at a time. For more information about the minimum of ESXi servers, see [Is a two-node vCenter Server instance highly available?]
In the two-node minimum deployment, one node has one NSX Controller, and the other node has two NSX Controllers. If the node with two NSX Controllers goes down, NSX Controller operations are placed in read-only mode, and new VMs (virtual machines) or vMotion VMs might experience networking issues.

When a third node is added to a two-node cluster, vCenter Server automatically rebalances the three NSX Controllers across the three nodes and creates a highly available environment.
* Can I set up VMware vCenter HA configuration?

You can configure vCenter HA, but configuration support is not provided by IBM Cloud for VMware Solutions.
* Can clusters be renamed?

For a new vCenter Server instance, you can set the name of the initial cluster that is created during deployment. When you add a cluster to a vCenter Server instance, you can specify the name that you want on the IBM Cloud for VMware Solutions console.
* How are patches managed?

IBM provides ongoing updates to the IBM code by deploying the IBM CloudDriver virtual server instance (VSI) on demand. Updates and patches for the IBM management components are applied automatically, as needed.

When you review the summary details for each instance, the Properties section displays the Current version. The current version is the IBM code version that is set when the instance is initially ordered. Day 2 operations such as adding or removing hosts, storage, services, or clusters are automatically updated with the current IBM code. Customer upgrade to the current IBM code version is never required. The IBM code version is separate from the VMware and service software versions. When the IBM code version is updated, the VMware software and service versions that are already installed for the instance remain unchanged.

IBM does not provide ongoing updates to add-on services such as Zerto or Veeam®. Obtaining and installing these updates is your responsibility.

Newly deployed VMware ESXi™ servers and clusters are patched with recent, but not necessarily the most recent, VMware ESXi updates.

For all other VMware component updates, you must ensure that newly deployed ESXi servers and clusters have the most recent updates that you require.
* [Using a reservation in a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-use)
* [Reviewing reservation usage](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-review)







 Enhancing security 

[Security for Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-securitysecurity)



* [Overview of security threats for your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-securitythreats)
* [Red Hat OpenShift API server and etcd](https://cloud.ibm.com/docs/openshift?topic=openshift-securityapiserver)



* [How is access to my API server granted?](https://cloud.ibm.com/docs/openshift?topic=openshift-securityapi-server-access)
* [What does Red Hat OpenShift on IBM Cloud do to secure my API server and etcd data store?](https://cloud.ibm.com/docs/openshift?topic=openshift-securitysecure-api-server)
* [What else can I do to secure my API server?](https://cloud.ibm.com/docs/openshift?topic=openshift-securityapi-server-what-else)
* [Rotating CA certificates in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-securitycert-rotate)



* [Worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-securityworkernodes)



* [Who owns the worker node and am I responsible to secure it?](https://cloud.ibm.com/docs/openshift?topic=openshift-securityworker-node-owner)
* [How does my worker node setup look?]
Unsupported: Beta versions of numerous Kubernetes APIs For more information, review [Preparing to upgrade to Red Hat OpenShift Container Platform 4.9](https://access.redhat.com/articles/6329921), [Kubernetes API and Feature Removals In 1.22: Here’s What You Need To Know](https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/) and [Deprecated API Migration Guide](https://kubernetes.io/docs/reference/using-api/deprecation-guide/v1-22). See [Deprecation Warnings](https://kubernetes.io/blog/2020/09/03/warnings/deprecation-warnings) for methods to identify use of deprecated APIs. Warnings for components provided by the Red Hat OpenShift on IBM Cloud cluster install can be ignored since they will be handled during the update. Note that Red Hat OpenShift on IBM Cloud cluster administrators do not need to provide a manual acknowledgment before the cluster can be upgraded, as mentioned in this Red Hat [article](https://access.redhat.com/articles/6329921). 









 Migrating your worker nodes to RHEL 8 

After updating your worker nodes to version 4.9, migrate them to use RHEL 8 by provisioning a new worker pool, then deleting the previous worker pool. See [Migrating to a new Red Hat Enterprise Linux version](https://cloud.ibm.com/docs/openshift?topic=openshift-rhel_migrate).
Why does my build error due to image pull authentication? 

Virtual Private Cloud

Classic infrastructure

 What’s happening 

When a build such as from Operator Hub or the built-in developer content catalog tries to pull an image from a Red Hat registry, the build might fail with an authentication error similar to the following.

error: build error: After retrying 2 times, Pull image still failed due to error: unauthorized: authentication required

 Why it’s happening 

By default, your cluster is set up with image pull secrets to Red Hat registries such as registry.redhat.io, registry.connect.redhat.com, and cloud.openshift.com. Additionally in the default project, your cluster has image pull secrets to access the <region>.icr.io registries for IBM Cloud Container Registry.

However, if an operator or built-in template has a build component that must pull an image from a private registry, the build might fail with an authentication error because the build does not have access to the default image pull secrets in its service account. By default, builds can pull images that are stored only in the internal registry.

 How to fix it 

Set up the build with access to the image, either by pulling the image from the private registry or by importing the image from the private registry into the internal registry.

For more information, see the [Red Hat OpenShift documentation](http://docs.openshift.com/container-platform/4.11/cicd/builds/creating-build-inputs.html).



1. Check the build configuration file to see what registry the build needs pull access to. For example, if your build is part of a Red Hat OpenShift template, the build config spec.strategy.sourceStrategy.from.name value refers to the registry.redhat.io private registry.

oc -n openshift get template react-web-app-example -o yaml

Example output

strategy:
sourceStrategy:
from:
kind: DockerImage
name: registry.redhat.io/rhoar-nodejs-tech-preview/rhoar-nodejs-10-webapp
2.
: After you [change your worker node VLAN connections](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_network_clusterchange-vlans), you can now [move router services across VLANs](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routesmigrate-router-vlan-classic).

Storage utilities
: [IBM Cloud storage utilities](https://cloud.ibm.com/docs/openshift?topic=openshift-utilities) are now available for Red Hat OpenShift clusters.





 20 January 2020 

Helm version 3
: Updated [Adding services by using Helm charts](https://cloud.ibm.com/docs/openshift?topic=openshift-helm) to include steps for installing Helm v3 in your cluster. Migrate to Helm v3 today for several advantages over Helm v2, such as the removal of the Helm server, Tiller.

Ingress ALB change log
: Updated the [nginx-ingress image build to 621](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).

Version change log
: Patch updates are available.
: Red Hat OpenShift [3.11.161_1538_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311161_1538).





 6 January 2020 

Ingress ALB change log
: Updated the [ingress-auth image to build 373](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).





 3 January 2020 

Version change log
: Worker node patch updates are available.
The Red Hat OpenShift web console switches to the Developer perspective, and the menu now offers items such as +Add, Topology, and Builds.
4. Click +Add.
5. In the Add pane menu bar, select the Project that you want to create your app in from the drop-down list.
6. Click the method that you want to use to add your app, and follow the instructions. For example, click From Git.







 Deploying apps through the CLI 

To create an app in your Red Hat OpenShift on IBM Cloud cluster, use the oc new-app[command](https://docs.openshift.com/container-platform/4.11/cli_reference/openshift_cli/developer-cli-commands.htmlnew-app). For example, you might refer to a public GitHub repo, a public GitLab repo with a URL that ends in .git, or another local or remote repo. For more information, [try out the tutorial](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorialopenshift_deploy_app) and review the [Red Hat OpenShift documentation](https://docs.openshift.com/container-platform/4.11/applications/creating_applications/odc-creating-applications-using-developer-perspective.html).

oc new-app --name <app_name> https://github.com/<path_to_app_repo> [--context-dir=<subdirectory>]

What does the new-app command do?
: The new-app command creates a build configuration and app image from the source code, a deployment configuration to deploy the container to pods in your cluster, and a service to expose the app within the cluster.
* [Kubernetes security bulletins](https://cloud.ibm.com/docs/openshift?topic=openshift-securitysecurity_bulletins)



[Architecture and dependencies of the service](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-architecture)



* [Classic Red Hat OpenShift version 4 architecture](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-architecture-4)



* [Red Hat OpenShift version 4 master components](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-architecture-4-master)
* [Red Hat OpenShift version 4 worker node components](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-architecture-4-workers)



* [VPC cluster service architecture](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-architecture_vpc)



* [Cluster with public and private cloud service endpoints](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architecturevpc-service-arch-public-and-private)
* [Cluster with private cloud service endpoint only](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architecturevpc-service-arch-private-only)
* [VPC version 4 master and worker node components](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-arch-vpc-4)



* [Overview of personal and sensitive data storage and removal options](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureibm-data)



* [What information is stored with IBM when using Red Hat OpenShift on IBM Cloud?]
route.route.openshift.io/hello-world
2. Delete the resources.

oc delete all -l app=hello-world -n hello-world







 What's next? 

For more information about working with your apps, see the [Red Hat OpenShift developer activities](https://docs.openshift.com/container-platform/4.11/welcome/index.htmldeveloper-activities) documentation.

Install two popular Red Hat OpenShift on IBM Cloud add-ons: [IBM Log Analysis](https://cloud.ibm.com/docs/openshift?topic=openshift-healthopenshift_logging) and [IBM Cloud Monitoring](https://cloud.ibm.com/docs/openshift?topic=openshift-health-monitor).
Load balancer and load balancer monitor for IBM Cloud Provider Master 169 177 Version 2.0 network load balancers (NLBs) were updated to fix problems with long-lived network connections to endpoints that failed readiness probes. 
 Red Hat OpenShift Master 3.11.170 4.3.12 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.html). 
 Red Hat OpenShift Worker 3.11.170 4.3.10 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.html). 
 Red Hat OpenShift Control Plane Operator Master N/A 3b3ff62 New!: Added a toolkit to enable running Red Hat OpenShift version 4 with a managed control plane. For more information, see the [Red Hat OpenShift HyperShift toolkit repository](https://github.com/openshift/hypershift-toolkit/commit/3b3ff6269b1c71ffa4a0598f7969aad6f7e4eb20). 
 Red Hat OpenShift HyperShift toolkit Master N/A 3b3ff62 New!: Added a toolkit to enable running Red Hat OpenShift version 4 with a managed control plane. For more information, see the [Red Hat OpenShift HyperShift toolkit repository](https://github.com/openshift/hypershift-toolkit/commit/3b3ff6269b1c71ffa4a0598f7969aad6f7e4eb20).
OpenVPN Operator image v1.4.1 v1.4.2 Updated ansible operator base image to version v1.18.0 to resolve CVEs. 
 Red Hat OpenShift 4.7.43 4.7.45 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-45) 
 Red Hat OpenShift Control Plane Operator v4.7.0-20220222 v4.7.0-20220308 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20220308). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.7.0-20220222 v4.7.0-20220308 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20220308). 
 Red Hat OpenShift on IBM Cloud toolkit 4.7.0+20220222 4.7.0+20220308 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20220308). 







 Change log for worker node pack 4.7.45_1557_openshift, released 28 March 2022 



Changes since version 4.7.44_1554_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A
Portieris admission controller v0.12.2 v0.12.3 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.12.3) 
 Red Hat OpenShift 4.8.31 4.8.35 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-35) 
 Red Hat OpenShift Control Plane Operator v4.8.0-20220222 v4.8.0-20220322 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0+20220322). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.8.0-20220222 v4.8.0-20220322 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0+20220322). 
 Red Hat OpenShift on IBM Cloud toolkit 4.8.0+20220222 4.8.0+20220322 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0+20220322). 







 Change log for worker node pack 4.8.35_1550_openshift, released 28 March 2022 



Changes since version 4.8.32_1548_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A
For the global load balancer to detect if one of your clusters is unavailable, consider adding a ping-based health check to every IP address. When you set up this check, your DNS provider regularly pings the IP addresses that you added to your domain. If one IP address becomes unavailable, then traffic is not sent to this IP address anymore. However, Red Hat OpenShift does not automatically restart pods from the unavailable cluster on worker nodes in available clusters. If you want Red Hat OpenShift to automatically restart pods in available clusters, consider setting up a [multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmz-clusters).



 Why do I need 3 clusters in three zones? 

Similar to using [3 zones in multizone clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmz-clusters), you can provide more availability to your app by setting up three clusters across zones. You can also reduce costs by purchasing smaller machines to handle your workload.





 What if I want to set up multiple clusters across regions? 

You can set up multiple clusters in different regions of one geolocation (such as US South and US East) or across geolocations (such as US South and EU Central). Both setups offer the same level of availability for your app, but also add complexity when it comes to data sharing and data replication. For most cases, staying within the same geolocation is sufficient. But if you have users across the world, it might be better to set up a cluster where your users are so that your users don't experience long waiting times when they send a request to your app.





 What options do I have to load balance workloads across multiple clusters?
IBM Cloud File Storage for Classic plug-in and monitor 421 425 Fixes for Fixing [CVE-2022-40303](https://nvd.nist.gov/vuln/detail/CVE-2022-40303) and [CVE-2022-40304](https://nvd.nist.gov/vuln/detail/CVE-2022-40303). 
 Key Management Service provider v2.5.12 v2.5.13 Updated Go dependencies and to Go version 1.19.4. 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.11.0-20221205 v4.11.0-20230123 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.11.0+20230123). 
 Red Hat OpenShift on IBM Cloud. 4.11.17 4.11.22 See the [Red Hat OpenShift on IBM Cloud Release Notes](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-22). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.11.0-20221205 v4.11.0-20230123 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.11.0+20230123). 
 Red Hat OpenShift on IBM Cloud toolkit 4.11.0+20221205 4.11.0+20230123 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.11.0+20230123).
IBM Cloud File Storage for Classic plug-in and monitor 421 425 Fixes for Fixing [CVE-2022-40303](https://nvd.nist.gov/vuln/detail/CVE-2022-40303) and [CVE-2022-40304](https://nvd.nist.gov/vuln/detail/CVE-2022-40303). 
 Key Management Service provider v2.5.12 v2.5.13 Updated Go dependencies and to Go version 1.19.4. 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.10.0-20221205 v4.10.0-20230123 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.10.0+20230123). 
 Red Hat OpenShift on IBM Cloud. 4.10.43 4.10.47 See the [Red Hat OpenShift on IBM Cloud Release Notes](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-47). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.10.0-20221205 v4.10.0-20230123 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.10.0+20230123). 
 Red Hat OpenShift on IBM Cloud toolkit 4.10.0+20221205 4.10.0+20230123 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.10.0+20230123).
Load balancer and load balancer monitor for IBM Cloud Provider 1328 1510 Updated image for [CVE-2020-27780](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27780). 
 Red Hat OpenShift 4.6.38 4.6.42 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-42). 
 Red Hat OpenShift Control Plane Operator v4.6.0-20210630 v4.6.0-20210816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20210816). 
 OpenVPN Operator image v1.3.4 v1.3.6 Updated image for [CVE-2021-33910](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33910). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.6.0-20210630 v4.6.0-20210816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20210816). 
 Red Hat OpenShift on IBM Cloud toolkit 4.6.0+20210630 4.6.0+20210816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20210816). 







 Change log for worker node fix pack 4.6.42_1552_openshift, released 16 August 2021
Load balancer and load balancer monitor for IBM Cloud Provider 1328 1510 Updated image for [CVE-2020-27780](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27780). 
 Red Hat OpenShift 4.7.19 4.7.23 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-23). 
 Red Hat OpenShift Control Plane Operator v4.7.0-20210630 v4.7.0-20210816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210816). 
 OpenVPN Operator image v1.3.4 v1.3.6 Updated image for [CVE-2021-33910](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33910). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.7.0-20210630 v4.7.0-20210816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210816). 
 Red Hat OpenShift on IBM Cloud toolkit 4.7.0+20210630 4.7.0+20210816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210816). 







 Change log for worker node fix pack 4.7.23_1528_openshift, released 16 August 2021