vania-janet/multiturn-rag-retrieval-data huggingface dataset:
System context for vCenter Server and Red Hat OpenShift architecture 

The following diagram shows the system context for this reference architecture. A system context diagram is a high-level diagram that provides an initial view of the system. It defines the key elements of a system, the boundary of the system, and the entities that interact with it, along with the interaction.

Zoom

![VMware Solutions and Red Hat® OpenShift® System Context](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/openshift-systemcontext.svg)

Figure 1. IBM Cloud® for VMware Solutions and Red Hat OpenShift system context



 Actors 

The system context diagram identifies the following actors:



* VMware administrator - The administrator is responsible for the ongoing deployment and maintenance of the VMware® environment.
* Red Hat OpenShift administrator - The administrator is responsible for the ongoing deployment and maintenance of the Red Hat® OpenShift® environment.
* Application user - The users of the applications that are deployed in the VMware and Red Hat OpenShift environment.







 Systems 

The system context diagram identifies the following systems:



* NSX Edge - Virtual appliances that manage north-south traffic into and out of the vCenter Server® instance.
* NSX load balancer - Used by Red Hat OpenShift for access to control plane and worker hosts. Load balancing is a function within the NSX® Edge, providing an L4/7 application load balancer.
* IBM Cloud for VMware Solutions Active Directory - Used for vCenter and NSX Manager authentication and can be extended to be used by Red Hat OpenShift.
* IBM Cloud for VMware Solutions DNS - Used by the VMware and Red Hat OpenShift environment to provide FQDN registration and resolution. DNS is configured to forward lookups to shared IBM DNS servers, allowing the resolution of public endpoints.
* IBM Cloud shared NTP - Used to maintain time synchronization within the environment.
* Persistent volumes:
* Manually extract the required configuration settings that need to be transferred to the NSX-T environment Juniper vSRX appliances.







 Red Hat OpenShift for VMware 

Red Hat OpenShift for VMware for NSX-T is available for vCenter Server with NSX-T instances. The migration approach summary is as follows:



* Provision the vCenter Server with NSX-T instance with Red Hat OpenShift for VMware.
* Configure the new Red Hat OpenShift for VMware cluster as required.
* Create a migration plan, which includes how to handle data from the applications that are being migrated.
* Consider the use of Migration Toolkit for Containers.







 VMware Aria Operations and VMware Aria Operations for Logs 

VMware Aria® Operations™ and VMware Aria Operations™ for Logs is available for vCenter Server with NSX-T instances.

The primary use case for VMware Aria Operations and VMware Aria Operations for Logs is to capture performance, capacity, and logging messages for the vCenter Server instance. A secondary use case is to capture performance, capacity, and logging messages for the workload VMs hosted on the vCenter Server instance.

The migration approach for the primary use case would be to:



* Provision vCenter Server with NSX-T with the VMware Aria Operations and VMware Aria Operations for Logs service.
* No performance, capacity, or log messages for the NSX-V instance components need to be retained as the instance will be deleted.
* When the vCenter Server with NSX-V is deleted, the VMware Aria Operations and VMware Aria Operations for Logs service will also be deleted.
* Migrate the content of the vCenter Server with NSX-V with the VMware Aria Operations and VMware Aria Operations for Logs service to vCenter Server with NSX-T by following the VMware documentation.







 Related links 



* [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
Red Hat OpenShift Container Platform on VPC landing zone 

Red Hat OpenShift Container Platform on VPC landing zone is a deployable architecture solution that is based on the IBM Cloud for Financial Services reference architecture. It creates secure and compliant Red Hat OpenShift Container Platform workload clusters on a Virtual Private Cloud (VPC) network.



 Architecture diagram 

Zoom

![Architecture diagram of the OpenShift Container Platform on VPC deployable architecture](https://cloud.ibm.com/docs-content/v1/content/9610604e9f8dcd5f7b6b138dd22ba445300be7f5/deployable-reference-architectures/terraform-ibm-landing-zone/roks.drawio.svg)

Figure 1. Single region architecture diagram for Red Hat OpenShift Container Platform on VPC on IBM Cloud





 Design requirements 

Zoom

![Design requirements for Secure infrastructure on VPC for regulated industries](https://cloud.ibm.com/docs-content/v1/content/9610604e9f8dcd5f7b6b138dd22ba445300be7f5/deployable-reference-architectures/terraform-ibm-landing-zone/heat-map-deploy-arch-slz-ocp.svg)

Figure 2. Scope of the design requirements





 Components 



 VPC architecture decisions 



Table 1. Architecture decisions

 Requirement Component Reasons for choice Alternative choice 

 Provide access management and tooling for the workload that is deployed in the workload VPC Management VPC service Create a separate VPC service where SSH connectivity from outside is allowed 
 Provide compute, storage, and network services to support hosted applications and operations that deliver services to the consumer Workload VPC service Create a separate VPC service as an isolated environment, without direct public internet connectivity and without direct SSH access
When you provision a Red Hat OpenShift Cluster on Power Systems Virtual Server, it is easier to use the IBM™ provided automation to create the entire cluster of servers and install Red Hat OpenShift rather than individually provisioning Power Systems Virtual Server instances. For instructions to deploy a Red Hat OpenShift Cluster on Power Systems Virtual Server, including preparation of the required Operation System images for the cluster, see [Deploying Red Hat OpenShift Container Platform 4.x on IBM Power Systems Virtual Servers](https://developer.ibm.com/components/ibm-power/series/deploy-ocp-cloud-paks-power-virtual-server/).







 Hardware specifications 

The following IBM Power Systems can host a Power Systems Virtual Server: IBM Power System S922 (9009-22A), IBM Power System S922 (9009-22G), IBM Power System E980 (9080-M9S), IBM Power System E1080 (9080-HEX), and IBM Power System S1022 (9105-22A). For more information about these systems and how they're used inside the Power Systems Virtual Server, see their data sheets and the hardware overview table.

If you'd like to compare your current environment's performance to what's available through the Power Systems Virtual Server, see the [IBM Power Systems performance report](https://www.ibm.com/downloads/cas/K90RQOW8). For a more condensed comparison, see [IBM Power Systems CPW performance data comparison](https://www.itechsol.com/wp-content/uploads/2018/07/IBM-Power-Systems-CPW-Performance-Data-Comparison-P7-vs-P8-vs-P9-rev3-July-2018.pdf).



 Data sheets 



* [IBM Power System S922 (9009-22A)](https://www.ibm.com/downloads/cas/KQ4BOJ3N)
* [IBM Power System E980 (9080-M9S)](https://www.ibm.com/downloads/cas/VX0AM0EP)
Red Hat OpenShift Container Platform on VPC landing zone 

Red Hat OpenShift Container Platform on VPC landing zone is a deployable architecture solution that is based on the IBM Cloud for Financial Services reference architecture. It creates secure and compliant Red Hat OpenShift Container Platform workload clusters on a Virtual Private Cloud (VPC) network.



 Architecture diagram 

Zoom

![Architecture diagram of the OpenShift Container Platform on VPC deployable architecture](https://cloud.ibm.com/docs-content/v1/content/bbc046343d620cb2210cb1c62a46d7601ae08e00/secure-infrastructure-vpc/includes/deployable-reference-architectures/terraform-ibm-landing-zone/includes/deployable-reference-architectures/terraform-ibm-landing-zone/roks.drawio.svg)

Figure 1. Single region architecture diagram for Red Hat OpenShift Container Platform on VPC on IBM Cloud





 Design requirements 

Zoom

![Design requirements for Secure infrastructure on VPC for regulated industries](https://cloud.ibm.com/docs-content/v1/content/bbc046343d620cb2210cb1c62a46d7601ae08e00/secure-infrastructure-vpc/includes/deployable-reference-architectures/terraform-ibm-landing-zone/includes/deployable-reference-architectures/terraform-ibm-landing-zone/heat-map-deploy-arch-slz-ocp.svg)

Figure 2. Scope of the design requirements





 Components 



 VPC architecture decisions 



Table 1. Architecture decisions

 Requirement Component Reasons for choice Alternative choice 

 Provide access management and tooling for the workload that is deployed in the workload VPC Management VPC service Create a separate VPC service where SSH connectivity from outside is allowed 
 Provide compute, storage, and network services to support hosted applications and operations that deliver services to the consumer Workload VPC service Create a separate VPC service as an isolated environment, without direct public internet connectivity and without direct SSH access
: Red Hat OpenShift [4.3.21_1523_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4321_1523) for worker nodes, [4.3.19_1523_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4319_1523) for masters, and [3.11.216_1551_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311216_1551).





 20 May 2020 

New! Virtual Private Cloud Generation 2
: You can now create standard Kubernetes clusters in your [Gen 2 Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.
: For more information, check out the following links.



* [Overview of Classic and VPC infrastructure providers](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers)
* [Supported virtual machine flavors for VPC Gen 2 worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesvm)
* [New VPC Gen 2 commands for the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli)
* [VPC cluster limitations](https://cloud.ibm.com/docs/containers?topic=containers-limitationsks_vpc_gen2_limits)



: Ready to get started? Try out the [Creating a cluster in your VPC on generation 2 compute tutorial](https://cloud.ibm.com/docs/containers?topic=containers-vpc_ks_tutorial).





 18 May 2020
Supported IBM Cloud and third-party integrations 

Learn more about the following IBM®, IBM Cloud®, and third-party integrations for Red Hat OpenShift on IBM Cloud clusters.



IBM Cloud and third-party integrations for Red Hat® OpenShift® on IBM Cloud® clusters

 Service Description 

 IBM Cloud platform services IBM Cloud platform services that support service keys can be integrated by using [service binding](https://cloud.ibm.com/docs/openshift?topic=openshift-service-binding). 
 IBM Cloud classic infrastructure services Your Red Hat OpenShift cluster is based on fully integrated IBM Cloud classic infrastructure services such as Virtual Servers, Bare Metal Servers, or VLANs. You create and work with these services instances by using the IBM Cloud Kubernetes Service API, CLI, or console. To secure your cluster network or connect to an on-prem data center, you can configure one of the following options:<br><br><br><br> * [strongSwan IPSec VPN Service](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvpn-setup)<br> * [IBM Cloud® Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)<br> * [Virtual Router Appliance (VRA)](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvyatta)<br> * [Fortigate Security Appliance (FSA)](https://cloud.ibm.com/docs/vmwaresolutions/services?topic=vmwaresolutions-fsa_considerations)<br><br><br> 
 IBM Cloud storage Supported persistent storage solutions, such as IBM Cloud File Storage for Classic, IBM Cloud Block Storage, or IBM Cloud Object Storage are integrated as Kubernetes flex drivers and can be set up by using Helm charts. The storage documentation for each solution includes instructions to install and manage storage.
Service limitations 

Red Hat® OpenShift® on IBM Cloud® and the Red Hat OpenShift open source project come with default service settings and limitations to ensure security, convenience, and basic functionality. Some limitations you might be able to change where noted.

If you anticipate reaching any of the following Red Hat OpenShift on IBM Cloud limitations, [contact IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar) and provide the cluster ID, the new quota limit, and the region in your support ticket.



 Service and quota limitations 

Red Hat OpenShift on IBM Cloud comes with the following service limitations and quotas that apply to all clusters, independent of what infrastructure provider you plan to use. Keep in mind that the [classic](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationsclassic_limits) and [VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationsks_vpc_gen2_limits) cluster limitations also apply.

To view quota limits on cluster-related resources in your IBM Cloud account, use the ibmcloud oc quota ls command.



Red Hat OpenShift on IBM Cloud limitations

 Category Description 

 API rate limits 200 requests per 10 seconds to the Red Hat OpenShift on IBM Cloud API from each unique source IP address. 
 App deployment The apps that you deploy to and services that you integrate with your cluster must be able to run on the operating system of the worker nodes. 
 Container-native virtualization The Red Hat OpenShift [container-native virtualization add-on](https://docs.openshift.com/container-platform/4.11/virt/about-virt.html) to run VM workloads alongside container workloads is not supported by IBM. If you choose to install the add-on yourself, you must use bare metal machines, not virtual machines. You are responsible for resolving any issues and impact to your workloads from using container-native virtualization.
Single-region IBM Cloud for Financial Services reference architecture for VPC with Red Hat OpenShift on IBM Cloud 

If you want to use containers, you can add [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-roks-overview) to your VPC. Except for the addition of Red Hat OpenShift on IBM Cloud, you use the same architectural patterns and components that were described for the [Single-region IBM Cloud for Financial Services reference architecture for VPC with Virtual Servers for VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsi).

The following diagram shows a more detailed view of both the management and workload VPCs when Red Hat OpenShift on IBM Cloud is introduced.



 Architecture diagram 

Zoom

![Single region IBM Cloud for Financial Services reference architecture for VPC with Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/vpc/images/roks-single-region/roks-single-region-consumer-intranet.svg)

Figure 1. Single region IBM Cloud for Financial Services reference architecture for VPC with Red Hat OpenShift on IBM Cloud

You can choose to use Red Hat OpenShift on IBM Cloud alongside (or instead of) virtual servers in either or both VPCs. Even though it is shown in the diagram as an option, it is not required to put Red Hat OpenShift on IBM Cloud in your management VPC.





 Red Hat OpenShift on IBM Cloud concepts 

Red Hat OpenShift on IBM Cloud is a managed offering to create your own Red Hat OpenShift on IBM Cloud cluster of compute hosts to deploy and manage containerized apps on IBM Cloud. Red Hat OpenShift on IBM Cloud provides intelligent scheduling, self-healing, horizontal scaling, service discovery and load balancing, automated rollouts and rollbacks, and secret and configuration management for your apps.
The NSX DLR virtual machines are configured as an active - passive pair, and vSphere Distributed Resource Scheduler (DRS) anti-affinity rules are created to ensure that the DLR VMs do not run on the same host. This step is described in [Red Hat OpenShift NSX DLR configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-nsxdlr-intro).
* Update DNS - The infrastructure DNS, provisioned with the vCenter Server instance is updated with the names and IP addresses for the Red Hat OpenShift components by using a PowerShell script. This step is described in [VMware Solutions DNS configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-dns-intro).



* Phase 2 - Red Hat OpenShift installation. These steps are described in [Red Hat OpenShift 4.7 user provider infrastructure installation](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-install-intro).



* A Red Hat virtual machine, the bastion node, is provisioned to run the Red Hat OpenShift installer and to host an HTTP Server. It is registered with Red Hat by using your subscription, and the Red Hat OpenShift installer is downloaded.
* On the bastion node, the install-config.yaml file is populated with the required Red Hat OpenShift parameters and Red Hat OpenShift ignition is used to generate a number of files used for the installation of the bootstrap, control plane, and worker machines.
* Terraform, on the bastion node, uses the files that are created by Ignition to create the Red Hat OpenShift VMs.



* Phase 3 - Post deployment activities. Configure a persistent volume for use by the Red Hat OpenShift cluster.
4.12.7 4.12.11 For more information, see the [change log](https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.htmlocp-4-12-11). 
 Red Hat OpenShift on IBM Cloud configuration N/A N/A Set proper topology spread constraints for the default Red Hat OpenShift on IBM Cloud image registry configuration used by classic clusters. 
 OpenVPN Operator image v1.4.22 v1.4.23 Updated base image to resolve CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361). 
 Portieris admission controller v0.13.3 v0.13.4 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.4). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator and Metrics Server 4.12.0-20230314 4.12.0-20230417 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.12.0+20230417).
For more information about installing the Red Hat OpenShift user provider infrastructure, see [Installing a cluster on vSphere with user-provisioned infrastructure](https://docs.openshift.com/container-platform/4.7/installing/installing_vsphere/installing-vsphere.html).



 Creating the Red Hat OpenShift Installer yaml file 

Use the following table to document the parameters you need for your deployment. Examples are shown that match the deployment described in this document.



* The SSH key can be copied after it is displayed by using the command: cat /root/.ssh/id_rsa.pub.
* The pull secret collected from Red Hat®. For more information, see [Red Hat OpenShift infrastructure providers](https://cloud.redhat.com/openshift/install/vsphere/user-provisioned)(requires logging in to your Red Hat account).





Table 1. File parameters for install-config.yaml

 Parameters Example Your deployment 

 Base domain dallas.ibm.local 
 Metadata name ocp 
 vCenter Server IP address 10.208.17.2 
 Username administrator@vsphere.local 
 Password s3cretPassw0rd 
 vCenter Server instance data center datacenter1 
 vCenter Server instance datastore vsanDatastore 
 Pull Secret 
 Public SSH Key 



Using the following install-config.yaml file shown in the figure, update it using your deployment details from the [previous table](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-install-introopenshift-runbook-runbook-install-yaml-table):



1. Update the base domain name.
2. Update the metadata name with the Red Hat OpenShift cluster name.
3. Provide the following vCenter Server information:



* vCenter IP address
* vCenter username and password
* Datacenter name
* Datastore name



4. Paste the Pull Secret.
5.
To connect to a different VPC or to an on-prem data center, use the [VPN for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example) service.







 Kubernetes community and open source integrations 

Because you own the standard clusters that you create in Red Hat OpenShift on IBM Cloud, you can choose to install third-party solutions to add extra capabilities to your cluster.

Some open source technologies, such as Portworx are tested by IBM and provided as managed add-ons, Helm charts, or IBM Cloud services that are operated by the service provider in partnership with IBM. These open source tools are fully integrated into the IBM Cloud billing and support system.

You can install other open source tools in your cluster, but these tools might not be managed, supported, or verified to work in Red Hat OpenShift on IBM Cloud.

Supported integrations depend on the container platform, the infrastructure provider, and the cluster type that you choose. For more information, see [Supported IBM Cloud and third-party integrations](https://cloud.ibm.com/docs/containers?topic=containers-supported_integrations).



 Integrations operated in partnership 

For more information about Red Hat OpenShift on IBM Cloud partners and the benefit of each solution that they provide, see [Red Hat OpenShift on IBM Cloud partners](https://cloud.ibm.com/docs/openshift?topic=openshift-service-partners).





 Managed add-ons 

Red Hat OpenShift on IBM Cloud integrates popular open source integrations by using [managed add-ons](https://cloud.ibm.com/docs/openshift?topic=openshift-managed-addons). Managed add-ons are an easy way to install an open source tool in your cluster that is tested by IBM and approved to be used in Red Hat OpenShift on IBM Cloud.

Managed add-ons are fully integrated into the IBM Cloud support organization. If you have a question or an issue with using the managed add-ons, you can use one of the Red Hat OpenShift on IBM Cloud support channels.