vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The [Red Hat OpenShift Container Platform CLI](https://docs.openshift.com/container-platform/4.12/cli_reference/openshift_cli/getting-started-cli.html) exposes commands for managing your applications, as well as lower level tools to interact with each component of your system. The CLI is available using the oc command.

To avoid installing the command line tools, the recommended approach is to use the IBM Cloud Shell.

IBM Cloud Shell is a cloud-based shell workspace that you can access through your browser. It's preconfigured with the full IBM Cloud CLI and many plug-ins and tools that you can use to manage apps, resources, and infrastructure.

In this step, you'll use the IBM Cloud shell and configure oc to point to the cluster assigned to you.



1. When the cluster is ready, click the button (next to your account) in the upper right corner to launch a [Cloud shell](https://cloud.ibm.com/shell). Make sure you don't close this window/tab.
2. Check the version of the OpenShift CLI:

oc version

> The version needs to be at minimum 4.12.x, otherwise install the latest version by following [these instructions](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorialsgetting-started-common_shell).
3. Validate your cluster is shown when listing all clusters:

ibmcloud oc clusters
4. Initialize the oc command environment by replacing the placeholder <your-cluster-name>:

ibmcloud oc cluster config -c <your-cluster-name> --admin
5. Verify the oc command is working:

oc get projects









 Step 2: Deploying an application 

In this section, you'll deploy a Node.js Express application named patient-health-frontend, a user interface for a patient health records system to demonstrate Red Hat OpenShift features.
* IBM Cloud Satellite clusters: Continue with [Accessing clusters on Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_cluster_sat).



6. If any users in your account use multifactor authentication (MFA) like TOTP, make sure that you [enable it for all users at the account level](https://cloud.ibm.com/docs/account?topic=account-enablemfa). To use MFA, it must be enabled at the account level to avoid authentication errors.







 Accessing clusters through the public cloud service endpoint 

For Red Hat OpenShift clusters with a public cloud service endpoint, you can log in to your cluster from the console or CLI.



 Connecting to the cluster from the console 

You can quickly access your Red Hat OpenShift on IBM Cloud cluster from the console.



1. In the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), click the cluster that you want to access.
2. Click Red Hat OpenShift web console.
3. To continue working in the command line, click your profile name, such as IAMname@email.com, and then click Copy Login Command. Depending on your cluster version, log in to your cluster from the command line as follows.



* Version 3.11: Paste the copied oc login command into your command line.
* Version 4: Click Display Token, copy the oc login command, and paste the command into your command line.





For security reasons, first log out of the IBM Cloud console and then log out of the Red Hat OpenShift web console before you close your browser. You must complete both steps in the specified order to successfully log out of the Red Hat OpenShift web console.

What's next?
: Try [Deploying apps through the console](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_appdeploy_apps_ui).





 Connecting to the cluster from the CLI
* Administrator on all account management services and all IAM services
* Editor on the software instance service
* Editor on the IBM Cloud Container Registry service
* Administrator on the Red Hat OpenShift on IBM Cloud cluster



Make sure that you use the same account to access IBM Cloud Container Registry and to create the Red Hat OpenShift on IBM Cloud cluster.





 Step 1: Import your Operator 



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select the product that you're onboarding.
3. From the Software tab, click Import a version.
4. Choose Operator from GitHub repository as your deployment method.
5. Confirm that Public repository is set as the repository type.
6. Enter https://github.com/IBM-Cloud/operator-bundle-sample/archive/refs/tags/v0.0.3.tar.gz as your source URL.
7. Enter the software version in the format of major version, minor version, and revision, for example, 1.0.0.

Enter the version of your software and not the version of your Operator. For example, you might be using Operator version 1.3.0 to install software version 3.1.1.
8. Click Add version.







 Step 2: Review your version details 

From the Configure version tab, you can review your version details. After you review your version details, click Next.





 Step 3: Set an image pull secret 

When you create your Red Hat® OpenShift® on IBM Cloud® cluster, the cluster includes an IAM service ID that is given reader access to IBM Cloud Container Registry. The service ID credentials are authenticated in a nonexpiring service ID API key that is stored in image pull secrets in your cluster.
Installing the CLI 

You can use the following tools to manage your Red Hat OpenShift on IBM Cloud clusters. While you can install a subset of the tools, all of the following tools are recommended.

Virtual Private Cloud

Classic infrastructure

Satellite



 Understanding the CLI tools 



Table 1: CLI tools

 CLI Description 

 ibmcloud You can use the ibmcloud CLI to login to your account, add users, manage your catalogs and more. 
 ks plug-in After installing the ibmcloud CLI, you can use the ks plug-in to create and manage Red Hat OpenShift on IBM Cloud clusters as well as Satellite hosts and Locations. 
 oc You can use the oc CLI to manage resources within your clusters like pods, deployments, and more. 







 Step 1: Run the installation command 

The latest version of the IBM Cloud CLI is installed when you run the command. As the CLI installs, keep an eye on the command line to authenticate as needed.



* For MacOS, run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/osx | sh
* For Linux™, run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/linux | sh
* For Windows™, run the following command in PowerShell as an administrator:

iex (New-Object Net.WebClient).DownloadString('https://clis.cloud.ibm.com/install/powershell')

To open PowerShell, right-click the Windows™ PowerShell icon, and select Run as administrator.
* For WSL2 on Windows™, run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/linux | sh



For more information about installing the Mac OS X M1/ARM or Linux 64-bit ARM versions of the CLI, see the IBM Cloud CLI [release notes](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/). These versions are provided as-is and are not fully supported.
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



[Setting capacity quotas for apps that use IBM Cloud Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-tutorial-quota)Setting capacity quotas for apps that use IBM Cloud Object Storage

With IBM Cloud Object Storage, you can dynamically provision buckets for apps running in your Red Hat OpenShift on IBM Cloud clusters. You can also dynamically set capacity quotas on those buckets during provisioning. Quotas can help you manage the resources your workloads use while also avoiding unnecessary charges.

Red Hat OpenShift on IBM Cloud Object Storage



* 45 minutes
* 2023-02-16



[Evaluate the compliance of your Red Hat OpenShift on IBM Cloud clusters ](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-osco-scan)Evaluate the compliance of your Red Hat OpenShift on IBM Cloud clusters

By using the OpenShift Compliance Operator (OSCO) through Security and Compliance Center, you can run scans to validate your level of compliance to a grouping of controls, also known as a profile. In this scenario, you configure your cluster to be able to run the OSCO scan.

Security and Compliance Center Red Hat OpenShift on IBM Cloud



* 20 minutes
* 2023-06-28



Databases[Getting started with IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant)Getting started with IBM Cloudant

The IBM® Cloudant® for IBM Cloud® Getting started tutorial demonstrates how to use the IBM Cloud® dashboard to create an IBM Cloudant service instance and obtain service credentials to connect to it. Finally, it guides you through the creation of a simple, locally hosted web application that uses your IBM Cloudant database.

Cloudant



* 20 minutes
* 2023-04-03
* Editor on the catalog management service
* Editor on the IBM Cloud Container Registry service
* Administrator on the Red Hat OpenShift on IBM Cloud cluster
* Editor on the software instance service





Make sure that you use the same account to access IBM Cloud Container Registry and to create the Red Hat OpenShift on IBM Cloud cluster.





 Step 1: Import your Operator bundle 



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select the product that you're onboarding.
3. From the Software tab, click Import a version.
4. Select Operator from Red Hat registry as your deployment method.
5. Select Certified as your Red Hat repository.
6. Select your Operator bundle. For example, for the purposes of this tutorial, you can select Akka Cluster Operator as your Operator.
7. Select the Operator bundle version that you want to import.
8. Enter the software version that the Operator bundle installs in the format of major version, minor version, and revision. For example, you can use Operator version 1.1.0 to install software version 3.1.1.
9. Review the summary of your Operator bundle.
10. Click Add version.







 Step 2: Review your version details 

From the Configure version tab, you can review your version details. After you review your version details, click Next.





 Step 3: Set the license requirements 

If users are required to accept any license agreements beyond the IBM Cloud Services Agreement, provide the URL to each agreement.



1. From the Add license agreements tab, click Add license.
2. Enter the name and URL, and click Add license.
3. Enter all additional license agreements, and click Next.







 Step 4: Review your readme file
Adding services by using Helm charts 

You can add complex Red Hat OpenShift apps to your cluster by using Helm charts.

In Red Hat OpenShift clusters that run version 4, use [Operators](https://cloud.ibm.com/docs/openshift?topic=openshift-operators) instead of Helm charts. If you have custom Helm charts, you can create a [Helm-based Operator](https://docs.openshift.com/container-platform/4.7/operators/operator_sdk/) instead.



 About Helm in Red Hat OpenShift on IBM Cloud 



 What is Helm and how do I use it? 

[Helm](https://helm.sh) is a Kubernetes package manager that uses Helm charts to define, install, and upgrade complex Kubernetes apps in your cluster. Helm charts package the specifications to generate YAML files for Kubernetes resources that build your app. These Kubernetes resources are automatically applied in your cluster and assigned a version by Helm. You can also use Helm to specify and package your own app and let Helm generate the YAML files for your Kubernetes resources.





 What Helm charts are supported in Red Hat OpenShift on IBM Cloud? 

For an overview of available Helm charts, see the [Helm charts catalog](https://cloud.ibm.com/kubernetes/helm). The Helm charts that are listed in this catalog are grouped as follows:



* iks-charts: Helm charts that are approved for Red Hat OpenShift on IBM Cloud. The name of this repo was changed from ibm to iks-charts.
* ibm-charts: Helm charts that are approved for Red Hat OpenShift on IBM Cloud and IBM Cloud Private clusters.
* ibm-community: Helm charts that originated outside IBM, such as from [Red Hat OpenShift on IBM Cloud partners](https://cloud.ibm.com/docs/openshift?topic=openshift-service-partners). These charts are supported and maintained by the community partners.
* kubernetes: Helm charts that are provided by the Kubernetes community and considered stable by the community governance.
Setting up the IBM Cloud Schematics CLI 

Before you begin using the IBM Cloud® Schematics CLI to deploy Red Hat® OpenShift® for HPC, review and complete the following prerequisites:



1. Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2. Log in to the IBM Cloud CLI with your IBMid. If you have multiple accounts, you are prompted to select which account to use. If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login

If your credentials are rejected, you might be using a federated ID. To log in with a federated ID, use the --sso flag. For more information, see [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id).
3. Install and set up the [IBM Cloud Schematics CLI plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin).
4. Make sure to generate your IBM Cloud API key. For more information, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey).
5. Create the config.json file that represents the configuration parameters that you would like to use to build the Red Hat OpenShift cluster. To learn more about all the properties, see [Deployment values](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-deployment-values). You can view a sample configuration file [here](https://github.com/IBM-Cloud/hpc-cluster-lsf/blob/main/sample/configs/hpc_workspace_config.json).
Update your cluster to [version 4.4](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions), and then to a supported version such as [4.5](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive) as soon as possible.





 5 March 2021 

Trusted images
: You can now [set up trusted content for container images](https://cloud.ibm.com/docs/openshift?topic=openshift-imagestrusted_images) that are signed and stored in IBM Cloud Container Registry.





 1 March 2021 

CLI change log
: Updated the Red Hat OpenShift on IBM Cloud CLI plug-in change log page for the [release of version 1.0.233](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10).

New! General availability of IBM Cloud Satellite®
: With IBM Cloud Satellite, you can bring your own compute infrastructure that is in your on-premises data center, at other cloud providers, or in edge networks as a Satellite Location to IBM Cloud. Then, you use the capabilities of Satellite to run IBM Cloud services on this infrastructure, and consistently deploy, manage, and control your app workloads. To get started, [create a location](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-started). Then, [create a Red Hat OpenShift on IBM Cloud cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusters) on your own infrastructure, and assign your additional hosts as worker nodes in the cluster.

Exposing apps in Satellite clusters
: Added an overview of the [options for exposing apps in Satellite clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-sat-expose-apps) and steps for setting up each option.

Worker node versions
How can I migrate it to Red Hat OpenShift on IBM Cloud? 

You can take some general steps to containerize your app as follows.



1. Use the [Twelve-Factor App](https://12factor.net/) as a guide for isolating dependencies, separating processes into separate services, and reducing the statefulness of your app as much as possible.
2. Find an appropriate base image to use. You can use publicly available images from [Docker Hub](https://hub.docker.com/), [public IBM images](https://cloud.ibm.com/docs/Registry?topic=Registry-public_imagespublic_images), or build and manage your own in your private IBM Cloud Container Registry.
3. Add to your Docker image only what is necessary to run the app.
4. Review the [common app modification scenarios](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployopenshift_move_apps_scenarios).
5. Instead of relying on local storage, plan to use persistent storage or cloud database-as-a-service solutions to back up your app's data.
6. Over time, refactor your app processes into microservices.



For more, see the following tutorials.



* [Moving a VM-based app to Kubernetes](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vm-to-containers-and-kubernetes).









 Common app modification scenarios 

Red Hat OpenShift has different default settings than community Kubernetes, such as stricter security context constraints. Review the following common scenarios where you might need to modify your apps so that you can deploy them on Red Hat OpenShift clusters.



Common scenarios that require app modifications

 Scenario Steps you can take 

 Your app runs as root. You might see the pods fail with a CrashLoopBackOff status The pod requires privileged access.
To run IBM Cloud Paks on Red Hat OpenShift on IBM Cloud, see [Adding Cloud Paks](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_cloud_paks). For more information about setting up your IBM Cloud Kubernetes Service cluster to pull entitled software, see [Setting up a cluster to pull entitled software](https://cloud.ibm.com/docs/containers?topic=containers-registrysecret_entitled_software).





 18 February 2021 

Increase the performance of the ibmcloud cr image-list and ibmcloud cr image-digests commands by using the --no-va option
: If you don't need the security status (Vulnerability Advisor) results as part of the output of the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) or [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) commands, you can use the --no-va option to increase performance.





 15 February 2021 

New region in Japan
: A new region in Japan is available. The new region is jp-osa and the domain name is jp2.icr.io. For more information, see [Local regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local).





 19 November 2020 

You can use Portieris to enforce container image security
: With effect from 19 November 2020, Container Image Security Enforcement is deprecated. To enforce container image security, you can use [Portieris](https://github.com/IBM/portieris). You can use Portieris to control where images are deployed from, enforce Vulnerability Advisor policies, and ensure that [content trust](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontent) is properly applied to the image.
To create and run these apps, you must be familiar with the concept of microservices, the [12-factor app](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploy12factor) guidelines, [Docker and containerization principles](https://www.docker.com/), and available [Red Hat OpenShift deployment options](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploy).

Red Hat OpenShift and Red Hat OpenShift on IBM Cloud provide multiple options for how to [expose an app and keep an app private](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planning), [add persistent storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan), [integrate other services](https://cloud.ibm.com/docs/openshift?topic=openshift-ibm-3rd-party-integrations), and how you can [secure your workloads and protect sensitive data](https://cloud.ibm.com/docs/openshift?topic=openshift-securitycontainer). Before you move your app to a cluster in Red Hat OpenShift on IBM Cloud, verify that you can run your app as a containerized app on the supported RHEL 7 or RHEL 8 operating system and that Red Hat OpenShift and Red Hat OpenShift on IBM Cloud provide the capabilities that your workload needs.

Do cluster administrators and developers interact with each other?
: Yes. Cluster administrators and developers must interact frequently so that cluster administrators understand workload requirements to provide this capability in the cluster, and so that developers know about available limitations, integrations, and security principles that they must consider in their app development process.







 Sizing your Red Hat OpenShift cluster to support your workload 

Figuring out how many worker nodes you need in your cluster to support your workload is not an exact science. You might need to test different configurations and adapt.
Step 1: Create a Red Hat OpenShift on IBM Cloud cluster 



1. Log in to your account and resource group. If you have a federated account, include the --sso option.

ibmcloud login [-g RESOURCE GROUP] [--sso]
2. Run the following command to create a version 4.11 cluster in Washington, DC with 2 worker nodes that have 4 cores and 16 GB memory.

ibmcloud oc cluster create classic --name my-tutorial-cluster --location wdc04 --version 4.11_openshift --flavor b3c.4x16 --workers 2 --public-service-endpoint
3. Your cluster creation might take some time to complete. After the cluster state shows Normal, the cluster network and Ingress components take about 10 more minutes to deploy and update the cluster domain that you use for the Red Hat OpenShift web console and other routes.
4. List your cluster details. Review the cluster State, check the Ingress Subdomain, and note the Master URL.

ibmcloud oc cluster get --cluster <cluster_name_or_ID>
5. Download and add the kubeconfig configuration file for your cluster.

ibmcloud oc cluster config --cluster <cluster_name_or_ID>
6. In your browser, navigate to the address of your Master URL and append /console. For example, https://c0.containers.cloud.ibm.com:23652/console.
7. From the Red Hat OpenShift web console menu bar, click your profile IAM#user.name@email.com > Copy Login Command. Display and copy the oc login token command into your command line to authenticate via the CLI.
8. Verify that the oc commands run properly with your cluster by checking the version.

oc version

Example output

Client Version: v4.11.0
Kubernetes Version: v1.26.6.2