vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Red Hat OpenShift NSX Edge configuration 

Review the NSX components that are used to support the Red Hat® OpenShift® 4.7 environment. To use this information, you must understand how to create these components and add the configuration. Review [Add an Edge Services Gateway](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.install.doc/GUID-B9A97F20-4996-4E16-822C-0B98DDE70571.html). PowerNSX commands are provided if you would want to use this method.

Zoom

![Red Hat OpenShift 4.7 networking](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/openshift-networking41.svg)

Figure 1. OpenShift 4.7 networking



 NSX ESG 

The first component that is configured within the IBM Cloud® for VMware Solutions with Red Hat OpenShift is a pair of NSX Edge appliances. The NSX Edge appliances are configured as an Active or Passive pair of X-Large NSX Edge devices.

As part of the configuration process, the NSX Edge is connected to the IBM Cloud Public and Private subnets that are ordered for the Red Hat OpenShift cluster.



Table 1. NSX Edge deployment

 Component Configuration 

 CPU 6 vCPU 
 RAM 8 GB 
 Disk 4.5 GB VMDK resident on shared storage with 4 GB swap 



The NSX Edges are configured as active or passive in either the internal or dedicated deployment. Therefore, the user must create the vSphere Distributed Resource Scheduler (DRS) anti-affinity rules to ensure that NSX Edges do not run on the same host as their respective peer appliance.



Table 2. NSX Edge anti-affinity rules

 Field Value 

 Name OpenShift-ESG 
 Type Separate virtual machines
If your cluster is gateway-enabled cluster, plan to create a new cluster before support ends. If you need similar functionality, consider creating a cluster on VPC infrastructure.

[Extended update support (EUS) updates](https://docs.openshift.com/container-platform/4.10/updating/preparing-eus-eus-upgrade.html) are not available at this time for Red Hat OpenShift on IBM Cloud version 4.10 clusters.

Zoom

![This badge indicates Kubernetes version 1.23 certification for Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/certified-kubernetes-color.svg)

Figure 1. Kubernetes version 1.23 certification badge

Red Hat OpenShift on IBM Cloud is a Certified Kubernetes product for version 1.23 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.



 Release timeline 

The following table includes the expected release timeline for version 4.10. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release history for Red Hat OpenShift on IBM Cloud version 4.10.

 Supported? Red Hat OpenShift / Kubernetes version Release date Unsupported date 

 Deprecated 4.10 / 1.23 27 April 2022 29 November 2023† 







 Preparing to update
* [System context for vCenter Server and Red Hat OpenShift architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-syscontext)
* [Red Hat OpenShift architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-redhat-arch)
* [IBM Cloud® for VMware Solutions SDDC architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-arch)
* [IBM Cloud networking and infrastructure](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-sddc-infra)
* [Storage options on IBM Cloud and Red Hat OpenShift](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-storage)
Red Hat OpenShift on IBM Cloud,Terraform on IBM Cloud



* 2 hours
* 2023-03-07



[Provisioning an IBM Cloud virtual server for VPC](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-sample_vpc_config)Provisioning an IBM Cloud virtual server for VPC

Use IBM Cloud Provider plug-in to provision a VPC, and set up networking for your VPC, and provision a virtual server for VPC in your IBM Cloud account. A VPC allows you to create your own space in IBM Cloud so that you can run an isolated environment in the public cloud with custom network policies.

Virtual Private Cloud (VPC) Terraform on IBM Cloud



* 2 hours
* 2023-04-21



[Creating single and multizone Kubernetes and OpenShift clusters](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-tutorial-tf-clusters)Creating single and multizone Kubernetes and OpenShift clusters

Create a classic IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud cluster by using Terraform on IBM Cloud.

Kubernetes service Red Hat OpenShift on IBM Cloud

+2

Red Hat OpenShift on IBM Cloud,Terraform on IBM Cloud



* 2 hours
* 2023-05-11



[Using Terraform on IBM Cloud to manage your own Red Hat OpenShift Container Platform on IBM Cloud classic infrastructure](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-redhat)Using Terraform on IBM Cloud to manage your own Red Hat OpenShift Container Platform on IBM Cloud classic infrastructure

Use this tutorial to create your own highly available Red Hat® OpenShift Container Platform 3.11 environment on IBM® Cloud classic infrastructure by using Terraform on IBM Cloud.

Red Hat OpenShift on IBM Cloud Terraform on IBM Cloud



* 3 hours
* 2023-03-07
4.6.58 4.6.59 See the [Red Hat OpenShift on IBM Cloud release notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-59). 
 OpenVPN client 2.5.6-r0-IKS-592 2.5.6-r1-IKS-629 Updated Alpine base image to version 3.16 to resolve CVEs. Updated OpenVPN to version 2.5.6-r1. 
 OpenVPN Operator image v1.4.6 v1.4.7 Updated Ansible operator base image to version v1.22.1 to resolve CVEs. 
 OpenVPN server 2.5.6-r0-IKS-591 2.5.6-r1-IKS-628 Updated Alpine base image to version 3.16 to resolve CVEs. Updated OpenVPN to version 2.5.6-r1. 
 Portieris admission controller v0.12.4 v0.12.5 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.12.5). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.6.0-20220614 v4.6.0-20220712 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20220712). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.6.0-20220614 v4.6.0-20220712 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20220712).
Create a [Knative-compliant container image](https://knative.dev/docs/serving/samples/hello-world/helloworld-python/index.html).
3. [Deploy the image](https://developers.redhat.com/blog/2020/04/30/serverless-applications-made-faster-and-simpler-with-openshift-serverless-ga) to your Red Hat OpenShift Serverless processor that runs in your Satellite cluster. You can use the Red Hat OpenShift web console in the developer perspective, or use the kn command line tool for Satellite Serverless.



Now, you have a managed Satellite location that runs on your edge environment and performs on-demand model inferencing for your edge data through your AI-trained model and Red Hat OpenShift Serverless.
: Red Hat OpenShift [4.3.27_1528_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4327_1528) and [3.11.232_1555_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311232_1555).





 2 July 2020 

Comparison between IBM Cloud and OCP clusters
: Added a [table of differences between standard OCP installations and Red Hat OpenShift on IBM Cloud clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovcompare_ocp).

Global settings
: Added information about the [config.openshift.io global settings](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsglobal-settings) that you can or can't configure.

Private-only VPC clusters
: Added diagrams for the [service architecture](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architectureservice-architecture_vpc), [flow of app requests with routers](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routesroute_vpc_private), and [flow of app requests with Ingress](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-about-roks4architecture-vpc_private) in VPC clusters that are created with the private cloud service endpoint only.

VPC load balancer
With IBM Cloud, you can create clusters for your containerized workloads from two different container management platforms: the IBM version of community Kubernetes and Red Hat OpenShift on IBM Cloud. The container platform that you select is installed on your cluster master and worker nodes. Later, you can [update the version](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) but can't roll back to a previous version or switch to a different container platform. If you want to use multiple container platforms, create a separate cluster for each.

For more information, see [Comparison between Red Hat OpenShift and community Kubernetes clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovopenshift_kubernetes).

Kubernetes
: [Kubernetes](https://kubernetes.io/) is a production-grade, open source container orchestration platform that you can use to automate, scale, and manage your containerized apps that run on an Ubuntu operating system. With the [IBM Cloud Kubernetes Service version](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions), you get access to community Kubernetes API features that are considered beta or higher by the community. Kubernetes alpha features, which are subject to change, are generally not enabled by default. With Kubernetes, you can combine various resources such as secrets, deployments, and services to securely create and manage highly available, containerized apps.

Red Hat OpenShift
: Red Hat OpenShift on IBM Cloud is a Kubernetes-based platform that is designed especially to accelerate your containerized app delivery processes that run on a Red Hat Enterprise Linux 7 operating system. You can orchestrate and scale your existing Red Hat OpenShift workloads across on-prem and off-prem clouds for a portable, hybrid solution that works the same in multicloud scenarios.
: To configure Red Hat OpenShift on IBM Cloud, IBM engineers follow relevant cybersecurity practices from the Kubernetes worker node benchmark that is published by the [Center of Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). You can review the compliance of worker nodes against [CIS Kubernetes benchmark](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmarkcis-worker-test) and [Red Hat OpenShift benchmark](https://cloud.ibm.com/docs/openshift?topic=openshift-benchmark-comparison) standards.

Compute isolation
: Worker nodes are dedicated to a cluster and don't host workloads of other clusters. When you create a classic cluster, you can choose to provision your worker nodes as [physical machines (bare metal) or as virtual machines](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes) that run on shared or dedicated physical hardware. Worker nodes in a VPC cluster can be provisioned as virtual machines on shared infrastructure only.

Option to deploy bare metal on classic
: If you create a standard classic cluster, you can choose to provision your worker nodes on bare metal physical servers (instead of virtual server instances). With bare metal machines, you have additional control over the compute host, such as the memory or CPU. This setup eliminates the virtual machine hypervisor that allocates physical resources to virtual machines that run on the host. Instead, all a bare metal machine's resources are dedicated exclusively to the worker, so you don't need to worry about "noisy neighbors" sharing resources or slowing down performance. Bare metal servers are dedicated to you, with all its resources available for cluster usage.

Encrypted disks
: By default, every worker node is provisioned with two local SSD, AES 256-bit encrypted data partitions. The first partition contains the kernel image that is used to boot the worker node and is not encrypted.
With Red Hat OpenShift on IBM Cloud, you can create a standard cluster in a [Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). A VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.

Before you can create a VPC cluster, you must have a VPC and at least one VPC subnet that you provision by using the IBM Cloud console, CLI, or API. You manage these resources in the VPC dashboard directly. When you create your cluster, worker nodes are automatically provisioned as [Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers) instances and you can view and manage these instances in Red Hat OpenShift on IBM Cloud only.

To add persistent storage to your VPC cluster, you can use the [Block Storage for VPC add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block). The add-on sets up pre-defined Kubernetes storage classes, the storage provider, and the storage driver in your cluster so that you can provision Block Storage for VPC by using Kubernetes persistent volume claims (PVCs).

To secure your cluster network traffic, you can modify the default security group for your worker nodes. For more information, see [Security in your IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-security-in-your-vpc).

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.
OpenShift Console access changes on IBM Cloud VPC Previously, Red Hat OpenShift on IBM Cloud VPC clusters that have disabled their public service endpoint, provided Red Hat OpenShift console access via the private service endpoint URL (for example https://cX00.private.us-south.containers.cloud.ibm.com:port) which required the internet browser to reach the IBM Cloud private network with routing to 166.8.0.0/14. Now, the Red Hat OpenShift console for such clusters is accessible via the virtual private endpoint (VPE) gateway URL (for example https://clusterID.vpe.private.us-south.containers.cloud.ibm.com:port). The VPE gateway is created automatically for the cluster and it exists in the same VPC as the cluster. To access the Red Hat OpenShift console, the internet browser must be able to resolve the VPE gateway URL and reach the VPE gateway in the VPC. To enable the access, setup the VPC VPN or other networking solution to be able to access the VPE gateway. For more information, please see [Accessing VPC clusters through the VPE gateway](https://cloud.ibm.com/docs/containers?topic=containers-access_clustervpc_vpe) documentation. It is important to set the IBM Cloud VPC Private DNS server addresses (161.26.0.7 and 161.26.0.8) as DNS resolvers and set routing towards IaaS services (161.26.0.0/16).
[Service Mesh on Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-openshift-service-mesh)Service Mesh on Red Hat OpenShift on IBM Cloud

This tutorial walks you through how to install Red Hat OpenShift Service Mesh alongside microservices for a sample app called BookInfo in a Red Hat OpenShift on IBM Cloud cluster. You will also learn how to configure an Istio ingress-gateway to expose a service outside of the service mesh, perform traffic management to set up important tasks like A/B testing and canary deployments, secure your microservice communication and use of metrics, logging and tracing to observe services.

Red Hat OpenShift on IBM Cloud Kubernetes service



* 2 hours
* 2023-05-05



[Plan, create and update deployment environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-plan-create-update-deployments)Plan, create and update deployment environments

Multiple deployment environments are common when building a solution. They reflect the lifecycle of a project from development to production. This tutorial introduces tools like the IBM Cloud CLI and Terraform to automate the creation and maintenance of these deployment environments.

Kubernetes service Virtual Servers for Classic

+5

Object Storage,Cloudant,,Activity Tracker hosted event search,Monitoring



* 2 hours
* 2023-05-05



[Text analysis with Code Engine](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-text-analysis-code-engine)Text analysis with Code Engine

In this tutorial, you will learn about IBM Cloud® Code Engine by deploying a text analysis with Natural Language Understanding application. You will create a Code Engine project, select the project and deploy Code Engine entities - applications and jobs - to the project. You will learn how to bind IBM Cloud services to your Code Engine entities. You will also understand the auto-scaling capability of Code Engine where instances are scaled up or down (to zero) based on incoming workload.

Code Engine Kubernetes service
Log into your IBM Cloud account and create a Red Hat OpenShift on IBM Cloud cluster from the [Red Hat OpenShift on IBM Cloud cluster create page](https://cloud.ibm.com/kubernetes/catalog/create?platformType=openshift).
2. Set the Orchestration service to 4.12.x version of Red Hat OpenShift on IBM Cloud.
3. Select your OCP entitlement.
4. Under Infrastructure choose Classic or VPC



* For Red Hat OpenShift on IBM Cloud on VPC infrastructure, you are required to create a VPC and one subnet prior to creating the Kubernetes cluster. Create or inspect a desired VPC keeping in mind the following (see instructions provided under the [Creating a standard VPC cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersclusters_vpcg2)):



* One subnet that can be used for this tutorial, take note of the subnet's zone and name
* Public gateway is attached to the subnet



* Select the desired VPC
* Select an existing Cloud Object Storage service or create one if required and then select



5. Under Location



* For Red Hat OpenShift on IBM Cloud on VPC infrastructure



* Select a Resource group
* Uncheck the inapplicable zones
* In the desired zone verify the desired subnet name and if not present click the edit pencil to select the desired subnet name



* For Red Hat OpenShift on IBM Cloud on Classic infrastructure follow the [Creating a standard classic cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersclusters_standard) instructions.



* Select a Resource group
* Select a Geography
* Select Single zone as Availability
* Choose a Datacenter





6. Under Worker pool,



* Select 4 vCPUs 16GB Memory as the flavor
* Select 2 Worker nodes per data center for this tutorial (classic only: Leave Encrypt local disk)



7.
* Before the service is installed in your environment, a check is completed against the available capacity of the target cluster in the environment to ensure that the service components can fit. The storage capacity check applies only to vSAN storage. For NFS clusters, a new NFS datastore, dedicated to Red Hat OpenShift, is added.
* The cluster is associated with the Red Hat account from the pull secret that is provided.
* The Latency Sensitivity setting of the Red Hat OpenShift cluster VMs can affect Kubernetes scheduling performance. By default, the setting is set to Normal, but it can be set to High if you encounter Kubernetes performance issues.







 Considerations when you delete Red Hat OpenShift for VMware 



* Before you delete Red Hat OpenShift for VMware, you must remove any additional VMs that you created in the ocp directory on VMware. The VMware Solutions automation removes only the items that were deployed during the initial installation of Red Hat OpenShift (VMs, storage, and NSX). Any node that is deployed after the installation is not cleaned up.
* The VXLAN, DLR, and the Edge Gateway that were created during the initial deployment of Red Hat OpenShift for VMware is deleted. The VMs that you deployed on VXLAN will lose connectivity after the removal of Red Hat OpenShift for VMware starts.
* If your cluster uses NFS storage, deleting Red Hat OpenShift deletes the NFS datastore that was added during installation.
* If you are using a vSAN datastore, delete any persistent volumes that you no longer need before you uninstall Red Hat OpenShift. Any volumes that are not deleted will remain in the vSAN storage after the Red Hat OpenShift uninstallation.
* Before you delete the service, you must remove any personal VMs that were deployed with this service, from the storage. Red Hat OpenShift only orders personal VMs if it’s not vSAN.







 Related links
* 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. This step is described in [Red Hat OpenShift 4.7 additional configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-config-intro).







 Related links 



* [What is Red Hat OpenShift?](https://www.ibm.com/cloud/blog/what-is-openshift)
* [Red Hat OpenShift 4 Release Update](https://www.youtube.com/watch?v=YJvTu8jC6CU)
* [Installing a cluster on vSphere with user-provisioned infrastructure](https://docs.openshift.com/container-platform/4.7/installing/installing_vsphere/installing-vsphere.html)
* [Getting started with IBM Cloud Virtual Private Networking](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-started)
Unsupported: Although the Kubernetes [SCTP protocol](https://kubernetes.io/docs/concepts/services-networking/service/sctp) and [application protocol](https://kubernetes.io/docs/concepts/services-networking/service/application-protocol) features are generally available in the community release, creating load balancers that use these protocols is not supported in Red Hat OpenShift on IBM Cloud clusters. 
 IBM Cloud File Storage for Classic plug-in and monitor 392 393 Updated universal base image (UBI) to version 8.4 to resolve CVEs. 
 IBM Cloud RBAC Operator 63cd064 cfd8ae9 Update to use Go version 1.16.4. Updated universal base image (UBI) to version 8.4 to resolve CVEs. 
 Red Hat OpenShift 4.6.28 (master) 4.7.12 (master) 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-12). 
 Red Hat OpenShift configuration N/A N/A Updated the [feature gate configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsfeature-gates). 
 Red Hat OpenShift Control Plane Operator v4.6.0-20210512 v4.7.0-20210512 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210512). 
 OpenVPN Operator image v1.3.1 v1.3.2 Updated ansible operator base image to version 1.7.2 to resolve CVEs and updated image to implement additional IBM security controls.