vania-janet/multiturn-rag-retrieval-data huggingface dataset:
In this sense, the installation is similar to IPI for you because you don't have to manage all the infrastructure and network settings. IBM also provides patch updates that you can choose to apply to your worker nodes, from the IBM Cloud interface (not the Red Hat OpenShift web console). SSH is disabled for added security. 
 OCP versions and patch updates You are responsible for updating the underlying infrastructure for the master and worker nodes. You can use the Red Hat OpenShift web console to update OCP versions. IBM automatically applies updates to the master, and provides version updates and security patch updates for the worker nodes. You choose when to apply these updates to your worker nodes, from the IBM Cloud interface (not the Red Hat OpenShift web console). Supported versions might vary from standard OpenShift Container Platform. 
 Autoscaling compute machines You can set up a ClusterAutoscaler resource. You can set up the [cluster autoscaler plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-classic-vpc). 
 Worker node operating system CoreOS or RHEL For a list of supported operating systems by cluster version, see [Red Hat OpenShift on IBM Cloud version information](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions). 
 Support Provided per the terms of your Red Hat subscription or cloud provider. You can use the oc adm must-gather tool to help gather information. Provided by [IBM Cloud Support](https://www.ibm.com/cloud/support). You can use the oc adm must-gather tool, or the [Diagnostics and Debug Tool](https://cloud.ibm.com/docs/openshift?topic=openshift-debug-tool) to help gather information. 
 Red Hat OpenShift web console You set up and can configure or disable the Red Hat OpenShift web console. The Red Hat OpenShift web console is set up for you. You can't configure or disable the web console.
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.

Instead of manually installing Red Hat® OpenShift Container Platform on IBM Cloud classic infrastructure, check out [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial). This offering lets you create an IBM Cloud Kubernetes Service cluster with worker nodes that come installed with the OpenShift Container Platform software. You get all the advantages of managed IBM Cloud Kubernetes Service for your cluster infrastructure environment, while the OpenShift tooling and catalog that runs on Red Hat Enterprise Linux for your app deployments.

[Red Hat® OpenShift Container Platform ![External link icon](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/icons/launch-glyph.svg)](https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform) is built around a core of containers, with orchestration and management provided by Kubernetes, on a foundation of Atomic Host and Red Hat® Enterprise Linux. OpenShift Origin is the community distribution of Kubernetes that is optimized for continuous app development and multi-tenant deployment. The community project provides developer and operations-centric tools that are based on Kubernetes to enable rapid app development, deployment, scaling, and long-term app lifecycle maintenance.

This tutorial shows how you can set up OpenShift Container Platform 3.11 on IBM Cloud classic infrastructure with Terraform on IBM Cloud to try out the high availability capabilities of native Kubernetes and IBM Cloud. Review the following image to find an architectural overview of the classic infrastructure components that are needed for the Red Hat OpenShift Container Platform to work properly.

!
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



[Updating VPC worker nodes that use OpenShift Data Foundation](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpc)Updating VPC worker nodes that use OpenShift Data Foundation

For VPC clusters with a storage solution such as OpenShift Data Foundation you must cordon, drain, and replace each worker node sequentially. If you deployed OpenShift Data Foundation to a subset of worker nodes in your cluster, then after you replace the worker node, you must then edit the ocscluster resource to include the new worker node.

Red Hat OpenShift on IBM Cloud Virtual Private Cloud (VPC)



* 60 minutes
* 2023-07-11



[Installing OpenShift Data Foundation on a private cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-private)Installing OpenShift Data Foundation on a private cluster

OpenShift Data Foundation is a highly available storage solution that you can use to manage persistent storage for your containerized workloads in Red Hat® OpenShift® on IBM Cloud® clusters.

Red Hat OpenShift on IBM Cloud Virtual Private Cloud (VPC)



* 2 hours
* 2023-05-09



[Creating a Red Hat OpenShift cluster in your Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_rh_tutorial)Creating a Red Hat OpenShift cluster in your Virtual Private Cloud (VPC)

Create an Red Hat® OpenShift® on IBM Cloud® cluster in your Virtual Private Cloud (VPC).

Red Hat OpenShift on IBM Cloud Virtual Private Cloud (VPC)



* 45 minutes
* 2023-07-07
: Add extra capabilities to your app through the integration of IBM Cloud services, such as Watson APIs, Blockchain, data services, or Internet of Things.





 Comparison between Red Hat OpenShift and community Kubernetes clusters 

Both Red Hat OpenShift on IBM Cloud and IBM Cloud Kubernetes Service clusters are production-ready container platforms that are tailored for enterprise workloads. The following table compares and contrasts some common characteristics that can help you choose which container platform is best for your use case.



Characteristics of community Kubernetes and Red Hat OpenShift clusters

 Characteristics Community Kubernetes clusters Red Hat OpenShift clusters 

 Complete cluster management experience through the IBM Cloud Kubernetes Service automation tools (API, CLI, console) Yes Yes 
 Worldwide availability in single and multizones Yes Yes 
 Consistent container orchestration across hybrid cloud providers Yes Yes 
 Access to IBM Cloud services such as AI Yes Yes 
 Software-defined storage Portworx solution available for multizone data use cases Yes Yes 
 Create a cluster in an IBM Virtual Private Cloud (VPC) Yes Yes 
 Latest community Kubernetes distribution Yes 
 Scope IBM Cloud IAM access policies to access groups for service access roles that sync to cluster RBAC Yes 
 Classic infrastructure cluster on only the private network Yes 
 GPU bare metal worker nodes Yes Yes 
 Integrated IBM Cloud Paks and middleware Yes 
 Built-in container image streams, builds, and tooling ([read more](https://blog.cloudowski.com/articles/why-managing-container-images-on-openshift-is-better-than-on-kubernetes/)) Yes 
 Integrated CI/CD with Jenkins Yes 
 Stricter app security context set up by default Yes 
 Simplified Kubernetes developer experience, with an app console that is suited for beginners Yes
Developers started by deploying their apps in containers with Red Hat OpenShift on IBM Cloud. They created clusters for a shared Dev environment that allow worldwide Developers to collaboratively deploy app improvements quickly. Containers allow each development team to use the language of their choice.

Security first: The IT Execs chose bare metal clusters. With bare metal for Red Hat OpenShift on IBM Cloud, the sensitive customs workloads now have familiar isolation but within the flexibility of public cloud.

Because the shipping company also wants to work with other ports, app security is crucial. Shipping manifests and customs information are highly confidential. From that secure core, Vulnerability Advisor provides these scans:



* Image vulnerability scans
* Policy scans that are based on ISO 27k



At the same time, IBM Cloud® Identity and Access Management helps to control who has which level of access to the resources.

Developers focus on domain problems, by using existing tools: Instead of Developers that write unique logging and monitoring code, they snap it into apps, by binding IBM Cloud services to clusters. Developers are also freed up from infrastructure management tasks because IBM takes care of Kubernetes and infrastructure upgrades, security, and more.

Compute, storage, and apps run in the public cloud with secure access to shipping data across the globe, as needed. Compute in clusters is tamper-proof and isolated to bare metal.

Technical solution:



* Red Hat OpenShift on IBM Cloud
* IBM Cloud® Functions
* IBM Cloudant
* IBM Secure Gateway





 Step 1: Containerize apps, by using microservices 



* Create a Node.js app or deploy an example.
* Structure apps into a set of cooperative microservices that run within Red Hat OpenShift on IBM Cloud based on functional areas of the app and its dependencies.
* Deploy the manifest and shipment apps to container that run in Red Hat OpenShift on IBM Cloud.
* Provide standardized DevOps dashboards through Kubernetes.
* Use IBM Secure Gateway to maintain secure connections to existing on-premises databases.







 Step 2: Ensure global availability 



* After Developers deploy the apps in their Dev and Test clusters, they use the IBM Cloud® Continuous Delivery toolchains and Helm to deploy country-specific apps into clusters across the globe.
2. Enter or select the Red Hat OpenShift on IBM Cloud project where you want to deploy IBM Cloud Pak for Data.







 Step 3. Configure your workspace 

Specify how you will track and manage your installation:



1. Enter or select a name for the installation.
2. Consider changing the default resource group.
3. Specify any tags that you want to use for the installation. Specify multiple tags as a comma-separated list.







 Step 4. Complete the preinstallation task 

A Red Hat OpenShift on IBM Cloud cluster administrator must complete this step. Specifically, the administrator must have an [access](https://cloud.ibm.com/docs/openshift?topic=openshift-users) policy in IBM Cloud Identity and Access Management that has an Operator role or higher.



* If you are not an administrator, use the Share link to share the script with your cluster administrator.
* If you are a cluster administrator, click Run script to run the preinstallation set up on your cluster.



The preinstallation script makes the following changes to your Red Hat OpenShift on IBM Cloud cluster:



* Increases the size of the Docker registry to 200 GB. This change increases the cost of your Red Hat OpenShift on IBM Cloud cluster.
* Creates the security context constraints that are required for IBM Cloud Pak® for Data.
* Grants access to the security context constraints to the service accounts that are required for IBM Cloud Pak® for Data.



Confirm that the script completes successfully before you proceed.

If the cluster administrator is not allowed to modify the storage, or the infrastructure account is not the same as the current account, a storage administrator can manually execute the script that is provided in [Complete the preinstallation section](https://cloud.ibm.com/catalog/content/ibm-cp-datacore-6825cc5d-dbf8-4ba2-ad98-690e6f221701-global).





 Step 5. Set the deployment values 

Choose a storage class:



* EnduranceFileStorage - This option uses the storage class ibmc-file-gold-gid to install Cloud Pak for Data.
You can [set up the entitled Helm chart repository](https://cloud.ibm.com/docs/openshift?topic=openshift-helm), where Helm charts that incorporate entitled software are stored. If you already have Helm installed in your cluster, run helm repo add entitled https://raw.githubusercontent.com/IBM/charts/master/repo/entitled.





 Adding a private registry to the global pull secret 

With OpenShift Container Platform, you can set up a global image pull secret that each worker node in the cluster can use to pull images from a private registry.

By default, your Red Hat OpenShift on IBM Cloud cluster has a global image pull secret for the following registries, so that default Red Hat OpenShift components can be deployed.



* cloud.openshift.com
* quay.io
* registry.connect.redhat.com
* registry.redhat.io



Do not replace the global pull secret with a pull secret that does not have credentials to the default Red Hat registries. If you do, the default Red Hat OpenShift components that are installed in your cluster, such as the OperatorHub, might fail because they can't pull images from these registries.

Before you begin:



* [Download the jq JSON processor command line package](https://stedolan.github.io/jq/download/). You use jq to combine the JSON value of the default global pull secret with the private registry pull secret that you want to add.
* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



To add private registries, edit the global pull-secret in the openshift-config project.



1. Create a secret value that holds the credentials to access your private registry and store the decoded secret value in a JSON file. When you create the secret value, the credentials are automatically encoded to base64. By using the --dry-run option, the secret value is created only and no secret object is created in your cluster.
* 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:



* vSAN - vSphere® provider and storage class configured in Red Hat OpenShift environment that allows ReadWriteOnce persistent volumes to be stored as virtual machine disks. The IBM Cloud Red Hat OpenShift environment allows ReadWriteMany persistent volumes.
* Block - IBM Cloud provider and storage class configured in Red Hat OpenShift environment that allows ReadWriteOnce persistent volumes.



* Public internet - Provide access to the VMware and Red Hat OpenShift environment to communicate with the public internet.
* IBM Cloud private network - Provide access to the VMware and Red Hat OpenShift environment to communicate with the IBM Cloud private network and services.







 Related links 



* [VMware vCenter Server and Red Hat OpenShift architecture overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-intro)
* [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)
* Deploy the manifest and shipment apps to container that run in Red Hat OpenShift on IBM Cloud.
* Provide standardized DevOps dashboards through Kubernetes.
* Use IBM Secure Gateway to maintain secure connections to existing on-premises databases.







 Step 2: Ensure global availability 



* After Developers deploy the apps in their Dev and Test clusters, they use the IBM Cloud® Continuous Delivery toolchains and Helm to deploy country-specific apps into clusters across the globe.
* Workloads and data can then meet regional regulations.
* Built-in HA tools in Red Hat OpenShift on IBM Cloud balance the workload within each geographic region, including self-healing and load balancing.







 Step 3: Data sharing 



* IBM Cloudant is a modern NoSQL database suitable a range of data-driven use cases from key-value to complex document-oriented data storage and query.
* To minimize queries to the regional databases, IBM Cloudant is used to cache the user's session data across apps.
* This configuration improves the front-end app usability and performance across apps on Kubernetes Service.
* While worker apps in Red Hat OpenShift on IBM Cloud analyze on-premises data and store results in IBM Cloudant, IBM Cloud® Functions reacts to changes and automatically sanitizes data on the incoming feeds of data.
* Similarly, notifications of shipments in one region can be triggered through data uploads so that all down-stream consumers can access new data.









 Results 



* Microservices greatly reduce time to delivery for patches, bug fixes, and new features. Initial development is fast, and updates are frequently 10 times per week.
* Shipping customers and government officials have access to manifest data and can share customs data, while they comply with local regulations.
* The shipping company benefits from improved logistics management in the supply chain: reduced costs and faster clearance times.
* 99% are digital declarations, and 90% of imports processed without human intervention.
[Benefits and service offerings](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovcs_ov)



* [Benefits of using the service](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovbenefits)
* [Comparison between Red Hat OpenShift and community Kubernetes clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovopenshift_kubernetes)
* [Comparison between clusters that run in IBM Cloud and standard OCP](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovcompare_ocp)



[Supported infrastructure providers](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providersinfrastructure_providers)



* [Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providersvpc-gen2-infra-overview)
* [Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providerssatellite-infra-overview)
* [Classic](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providersclassic-infra-overview)
* [Troubleshooting and support](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providersinfra-troubleshoot)



[Your responsibilities with using Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-responsibilities_iksresponsibilities_iks)



* [Overview of shared responsibilities](https://cloud.ibm.com/docs/openshift?topic=openshift-responsibilities_iksoverview-by-resource)
* Shorten time-to-deploy solutions and implement standard DevOps and monitoring processes to address bugs that affected reporting accuracy



Technical solution:



* Red Hat OpenShift on IBM Cloud
* IBM Cloud Object Storage
* IBM Cloud Data Engine (Spark)
* IBM Cloudant
* Secure Gateway



Red Hat OpenShift on IBM Cloud provides scalable compute resources and the associated DevOps dashboards to create, scale, and tear down apps and services as needed. Using industry-standard containers, apps can initially be re-hosted on Red Hat OpenShift on IBM Cloud quickly without major architectural changes.

This solution provides the immediate benefit of scalability. By using Kubernetes's rich set of deployment and runtime objects, the mortgage company monitors and manages the upgrades to apps reliably. They're also able to replicate and scale the apps that use defined rules and the automated Kubernetes orchestrator.

Secure Gateway is used to create a secure pipeline to on-premises databases and documents for apps that are re-hosted to run in Red Hat OpenShift on IBM Cloud.

IBM Cloud Object Storage is for all raw document and data storage as they go forward. For Monte Carlo simulations, a workflow pipeline is put in place where simulation data is in structured files that are stored in IBM Cloud Object Storage. A trigger to start the simulation scales compute services in Red Hat OpenShift on IBM Cloud to split the data of the files into N event buckets for simulation processing. Red Hat OpenShift on IBM Cloud automatically scales to N associated service executions and writes intermediate results to IBM Cloud Object Storage. Those results are processed by another set of the Red Hat OpenShift on IBM Cloud compute services to produce the final results.

IBM Cloudant is a modern NoSQL database that is useful for many data-driven use cases: from key-value to complex document-oriented data storage and query. To manage the growing set of regulatory and management report rules, the mortgage company uses IBM Cloudant to store documents that are associated with raw regulatory data the come into the firm. Compute processes on Red Hat OpenShift on IBM Cloud are triggered to compile, process, and publish the data in various reporting formats.
Red Hat OpenShift security bulletins that affect Red Hat OpenShift on IBM Cloud users or the IBM Cloud platform are published in the [IBM Cloud security bulletin](https://cloud.ibm.com/status?component=containers-kubernetes&selected=security).

Some CVEs require the latest patch update for a version that you can install as part of the regular [cluster update process](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) in Red Hat OpenShift on IBM Cloud. Make sure to apply security patches in time to protect your cluster from malicious attacks. For more information about what is included in a security patch, refer to the [version change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions_available).





 Does the service offer support for bare metal and GPU? 

Certain VPC worker node flavors offer GPU support. For more information, see the [VPC flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavors).

Yes, you can provision your worker node as a single-tenant physical bare metal server. Bare metal servers come with high-performance benefits for workloads such as data, GPU, and AI. Additionally, all the hardware resources are dedicated to your workloads, so you don't have to worry about "noisy neighbors".

For more information about available bare metal flavors and how bare metal is different from virtual machines, see [Physical machines (bare metal)](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesbm).





 What is the smallest size cluster that I can make? 

Your cluster must have at least 2 worker nodes to run default Kubernetes and OpenShift Container Platform components. You can't have a cluster with 0 worker nodes, and you can't power off or suspend billing for your worker nodes. Additionally, the type of cluster and the number of worker pools that you have can impact the size of your cluster.