vania-janet/multiturn-rag-retrieval-data huggingface dataset:
After you install the operator to your OpenShift project, you can create a subscription that allows you to deploy the blockchain console UI.

Currently, you cannot deploy certificate authorities (CAs), peers, and ordering nodes directly, then, use the console to deploy those nodes instead. This tutorial includes only instructions for installing the console.

To learn more about the Marketplace see the [Red Hat documentation](https://marketplace.redhat.com).





 Limitations 



* IBM Blockchain Platform 2.5.4 is supported on Red Hat OpenShift 4.4+.
* You are responsible for the management of health monitoring, logging, and resource usage of your blockchain components.
* IBM Blockchain Platform is not supported on OpenShift Online.
* Mutual TLS is not supported between your applications and your blockchain nodes.
* You cannot use the extended support release(EMC Symmetrix for R) version of Firefox to log in to the IBM Blockchain Platform console.







 Before you begin 

You must have the cluster administrator role to install the operators from the Red Hat Marketplace.



1. These instructions assume you already have a Kubernetes cluster available in OpenShift Container Platform v4.4+ and that you created a project for your IBM Blockchain deployment. Unsure how to create a project? See [Create a project for your IBM Blockchain Platform deployment](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmdeploy-ocp-rhm-project).
2. Browse to the [Red Hat Marketplace](https://marketplace.redhat.com/en-us) and log in or create a new account.
3. Follow the [instructions](https://marketplace.redhat.com/en-us/documentation/clustersregister-openshift-cluster-with-red-hat-marketplace) to register your OpenShift cluster with the Red Hat Marketplace.
4. When prompted Would you like to go back to the Red Hat Marketplace now? [Y/n], type Y to retrieve the Red Hat Marketplace page in your browser.
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 Red Hat OpenShift on IBM Cloud clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_tutorial)Creating Red Hat OpenShift on IBM Cloud clusters

Create a cluster with worker nodes that come installed with Red Hat OpenShift container orchestration platform.

Red Hat OpenShift on IBM Cloud



* 45 minutes
* 2023-07-13



[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



[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
For more information about how to set up IBM Blockchain in Red Hat OpenShift on IBM Cloud, see [About IBM Blockchain Platform](https://cloud.ibm.com/docs/blockchain?topic=blockchain-get-started-ibp). 
 Other third-party integrations You can install many other integrations into your Red Hat OpenShift cluster, such as through the Red Hat OpenShift catalog, the [Red Hat Marketplace](https://marketplace.redhat.com/en-us/documentation/getting-started), Operators, Helm charts, or do-it-yourself open source software installations. Make sure that these apps are compatible with your Red Hat OpenShift cluster and Kubernetes version. For example, you might need to [update the app](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployopenshift_move_apps_scenarios) for the installation to succeed.
Check if you want to connect none, one or more of the available integrations, like Activity tracking, Logging and Monitoring
13. In the Summary pane on the left, review the order summary and then click Create.



For many more additional information on the fields, see [Creating a classic standard cluster in the console](https://cloud.ibm.com/docs/openshift?topic=openshift-clusters&interface=uiclusters_standard).





 Provisioning your jump host 

The jump host's hardware and software requirements are 4 cores, 16 GB RAM, 20 GB disk space, OS: Red Hat 8.x. You can either use a suitable jump server that is connected to the Red Hat OpenShift on IBM Cloud cluster in IBM Cloud, or you can use the following steps to create an IBM® Virtual Servers instance to serve as your jump host.



1. Log in to [IBM Cloud console](https://cloud.ibm.com/gen1/infrastructure/devices) and click Order +.
2. Select Virtual Servers for Classic.
3. Leave the default value Public for Type of virtual server.
4. Enter a name, for example jump4sdi, for Hostname. Click Information for formatting specifics.
5. Enter a name, for example, ocpsditest.org for Domain. Domain is the identification string that defines administrative control within the internet. Click Information for formatting specifics.
6. Leave the default values 1, hourly and None for Quantity, Billing and Placement group.
7. Select the Location of the same data center (zone) where you set up your Red Hat OpenShift on IBM Cloud cluster.
8. Click View all profiles and select B1.4x16, which is the minimum requirement.
9. Provide your SSH key for SSH Keys or leave the default None. For more information on SSH keys, see [About SSH keys](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-about-ssh-keys).
10.
[Complete the prerequisite steps](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-prereqs).
2. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), click Create.
3. In the Infrastructure section, select Satellite.
4. In the OCP entitlement section, specify an existing OCP entitlement for the worker nodes in this cluster by providing your [Red Hat® account pull secret](https://console.redhat.com/openshift/install/pull-secret) as a file or in raw JSON format. The cluster also uses this pull secret to download Red Hat OpenShift images from your own Red Hat account.
5. In the Location section, select the Satellite location where you want to create the cluster. Make sure that the location that you select is in a Normal state.
6. In the Operating System section, select the operating system of the hosts that you want to use in the default worker pool of your cluster. In locations that are Red Hat CoreOS enabled, you can use either your RHCOS or RHEL hosts. In RHCOS enabled locations, when you want to add worker pools to your cluster, you can use RHCOS or RHEL hosts. Make sure to attach hosts with the operating system that you want to use to your location before assigning them to a worker pool.
7. In the Worker pools section, configure the details for your default worker pool.



1. Select the Satellite zones that Satellite uses to evenly assign hosts across zones that represent zones in your underlying infrastructure provider. Generally, create your worker pool across 3 zones for high availability.
2. Request the vCPU, Memory (GB), and number of Worker nodes per zone that you want to create the worker pool with. Satellite can automatically assign available hosts to the worker pool to fulfill your request. Generally, select at least 1 worker node per zone for a total of 3 worker nodes in your cluster.



8.
<region>.icr.io/<namespace>/<build_name> latest <digest> <namespace> 2 minutes ago 182 MB 33 Issues



Your Red Hat OpenShift build can now pull images from and push images to IBM Cloud Container Registry.





 Using IBM Cloud Container Registry 

By default, your Red Hat OpenShift on IBM Cloud cluster is set up to pull images from the remote, private IBM Cloud Container Registry icr.io domains in the default project. If you want to use images that are stored in IBM Cloud Container Registry for other projects, you can pull the image to the internal registry in an image stream, or create image pull secrets for each global and regional registry in each project.

To import images into the internal registry: See [Importing images from IBM Cloud Container Registry into the internal registry image stream](https://cloud.ibm.com/docs/openshift?topic=openshift-registryimagestream_registry).

To pull images directly from the external IBM Cloud Container Registry: See the following topics.



* [Understanding how to authorize your cluster to pull images from a registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycluster_registry_auth).
* [Copying the all-icr-io secret](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycopy_imagePullSecret) from the default project to the project that you want to pull images from.
* [Creating your own image pull secret](https://cloud.ibm.com/docs/openshift?topic=openshift-registryother_registry_accounts).
* [Adding the image pull secret](https://cloud.ibm.com/docs/openshift?topic=openshift-registryuse_imagePullSecret) to your deployment configuration or to the project service account.







 Understanding how to authorize your cluster to pull images from a private registry 

To pull images from a registry, your Red Hat OpenShift on IBM Cloud cluster uses a special type of Kubernetes secret, an imagePullSecret.
To understand and set up logging for Red Hat OpenShift clusters that run in your Satellite location, see the tutorials in the [IBM Log Analysis documentation](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-tutorial-use-logdna).

You cannot currently use the Red Hat OpenShift on IBM Cloud console or the observability plug-in CLI (ibmcloud ob) to enable logging for Satellite clusters. You must [manually deploy logging agents to your cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-healthenable-clusters-logging) to forward logs to Log Analysis.



 Enabling a logging instance in your cluster 

To enable a logging instance in your Satellite cluster, you must manually install the logging agent in the cluster.



1. [Create a new logging instance](https://cloud.ibm.com/catalog/services/ibm-log-analysis?callback=%2Fobserve%2Flogging%2Fcreate) or locate an existing one that you want to install in your cluster. The logging instance must be in the same region where your cluster's Satellite location is managed from.
2. From the [Logging](https://cloud.ibm.com/observe/logging) page, click on the logging instance.
3. Click on Logging sources and navigate to the Red Hat OpenShift tab.
4. Follow the instructions in the Red Hat OpenShift tab to install the logging agent.
Configure your installation environment 

From the Create tab on the Cloud Pak for Multicloud Management installation page, specify where you want to install the IBM Cloud Pak for Multicloud Management:

1. Select the Red Hat OpenShift cluster where you want to deploy the IBM Cloud Pak for Multicloud Management.
2. Enter or select the project where you want to deploy IBM Cloud Pak for Multicloud Management.





 Step 2. Configure your workspace 

Specify how to track and manage your installation from your IBM Cloud Schematics workspace:

1. In the _Configure your workspace_ section, update the name and tag of the installation workspace.
2. Specify any tags that you want to use for the installation. Specify multiple tags as a comma-separated list.





 Step 3. Complete the pre-installation check 

A Red Hat OpenShift cluster administrator must complete this step.



* 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 pre-installation check. Confirm that the script completes successfully.
* For any certificate signing requests (CSRs) that are generated on your cluster nodes, approve all of the CSRs on your nodes before you install. Run the following commands on each of your cluster nodes to approve your CSRs:



1. Find all CSRs for your cluster nodes:

oc get csr
2. Approve the CSRs for the cluster nodes:

oc adm certificate approve <CSR name>



For more information, see the [Approving the CSRs for your machines](https://docs.openshift.com/container-platform/4.2/machine_management/more-rhel-compute.htmlinstallation-approve-csrs_more-rhel-compute) topic in the OpenShift documentation.







 Step 4. Set the deployment values 

Override the default values by configuring the required deployment values for the OpenShift cluster that you have installed:



Table 1. Deployment values

 Parameter Description Default
* Make sure that you have the correct [permissions](https://cloud.ibm.com/docs/containers?topic=containers-clusters&interface=ui) to create Red Hat OpenShift on IBM Cloud clusters.
* [Create or use an existing cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clusters).
* If you want to use non-SDS worker nodes in a classic cluster [add a block storage device to your worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesmanual_block).
* Choose if you want to [use the internal Portworx key-value database (KVDB)](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_kv_store) or [create a Databases for etcd service instance](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_kv_store) to store the Portworx configuration and metadata.
* Decide whether you want to encrypt your Portworx volumes. To encrypt your volumes, you must [set up an IBM Key Protect or a Hyper Protect Crypto Services instance and store your service information in a Kubernetes secret](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_encryption).
* Make sure that you [copied the image pull secrets from the default to the kube-system project](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycopy_imagePullSecret) so that you can pull images from Container Registry. Make sure that you [add the image pull secrets to the Kubernetes service account](https://cloud.ibm.com/docs/openshift?topic=openshift-registrystore_imagePullSecret) of the kube-system project.
* Decide if you want to include your cluster in a Portworx disaster recovery configuration.
Deploying your OpenShift cluster and jump host 

This topic takes you through the steps for creating the Red Hat® OpenShift® on IBM Cloud® cluster and the associated jump host.



 Before you begin 

When you create the Red Hat OpenShift on IBM Cloud cluster, it is important that the flavor meets SAP's sizing recommendations and your expected workload characteristics, as well as the expected data volumes. The following implementation scenario is based on [Minimum Sizing for SAP Data Intelligence](https://help.sap.com/viewer/835f1e8d0dde4954ba0f451a9d4b5f10/latest/en-US/d771891d749d425ba92603ec9b0084a8.html) and therefore is appropriate for a very basic test environment, only. When planning to setup and deploy a production cluster you must carefully consult the [Sizing Guide for SAP Data Intelligence](https://help.sap.com/viewer/835f1e8d0dde4954ba0f451a9d4b5f10/latest/en-US/633d429ff69441ae81fe57d912397903.html) and adapt the flavors that will meet your specific needs. Before creating your cluster, please refer to the most recent SAP documentation, like [Installation](https://help.sap.com/viewer/a8d90a56d61a49718ebcb5f65014bbe7/latest/en-US/9f866d8ef9a94c30947f12e73eaf0dd9.html) and [Administration Guide](https://help.sap.com/viewer/b13b5722c8ff4bf9bb097251310031d0/latest/en-US/884ffcd587784ed2a311b2c19feb8410.html). You may find more related information in [SAP's Community page](https://community.sap.com/topics/data-intelligence).

Please check that your IBM Cloud account is eligible to create clusters.
8. Click View all profiles and select B1.4x16, which is the minimum requirement.
9. Provide your SSH key for SSH Keys or leave the default None. For more information on SSH keys, see [About SSH keys](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-about-ssh-keys).
10. Check your Operating System - Select Red Hat for Vendor and 8.x - Minimal (64 bit) - HVM for Version.
11. Leave the default values for all the other entry fields.
12. In the Summary pane on the left, check the Third-Party Service Agreements and click Create.



Your Red Hat OpenShift on IBM Cloud cluster and your virtual server should be available in about 15 minutes.





 Preparing the jump host 

Before setting up the Red Hat® OpenShift® on IBM Cloud® cluster on which SAP Data Intelligence will be deployed, you need to prepare your jump host.

If you have created the jump server following the steps listed above, you first should update the operating system to the latest level, and then restart the virtual server instance.



1. upade the OS

sudo dnf update press 'y' when prompted
2. reboot

sudo reboot





 Before you begin 

It's recommended you become familiar with the [Managing your IBM Cloud accounts](https://cloud.ibm.com/docs/account?topic=account-accounts). Your IBM Cloud user ID must at least have the cluster Administrator role.





 Install and verify the Command Line Interfaces (CLIs) for both, IBM Cloud and Red Hat OpenShift on IBM Cloud 

Use the following commands to download and install the CLIs you use to configure the connection between your Red Hat OpenShift on IBM Cloud cluster and your jump host.



1. Login to the jump host and install the IBM Cloud CLI ibmcloud.

curl -fsSL https://clis.cloud.ibm.com/install/linux | sudo sh
Onboarding your Operator bundle 

This tutorial walks you through how to onboard a Certified Operator bundle from a Red Hat registry. By completing this tutorial, you learn how to import the Red Hat OpenShift on IBM Cloud Operator bundle, configure the deployment, license, and other details, and validate that the Operator bundle can be installed on a cluster.

This tutorial is one of four in a series that demonstrates how to onboard and publish a sample Operator bundle from the Red Hat OpenShift on IBM Cloud Certified registry. It uses a fictitious company called Example Corp. As you complete the tutorial, adapt each step to fit your product's needs.



 Before you begin 



1. Go to Red Hat OperatorHub to confirm that your Operator bundle exists in the Red Hat Certified registry.
2. [Create your Red Hat OpenShift on IBM Cloud cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-getting-started).
3. [Upload your Operator bundle and application images to IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started).
4. Verify that you're assigned the correct roles. For more information, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services) and [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).



* Administrator on all account management services and all IAM services
* 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 !
* Destination IP addresses and hostnames: [IBM Cloud Log Analysis endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api_public)
* Protocol and ports: HTTPS 443



: If you plan to use IBM Cloud Log Analysis in your Red Hat OpenShift on IBM Cloud Satellite clusters, then include these network options.

Optional: Allow hosts to communicate with IBM Cloud Monitoring.
: 

* Destination IP addresses and hostnames: [Monitoring endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpoints)
* Protocol and ports: HTTPS 443 and 6443



: If you plan to use Monitoring in your Red Hat OpenShift on IBM Cloud Satellite clusters, then include these network options.
* [Deploying Cloud Paks, licensed software, and other integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_appopenshift_app_cloud_paks)
* [Accessing the Red Hat OpenShift web console](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_appopenshift_console)



* [Red Hat OpenShift console overview](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_appopenshift_console4_overview)





[Testing access to apps with NodePorts](https://cloud.ibm.com/docs/openshift?topic=openshift-nodeportnodeport)



* [About NodePorts](https://cloud.ibm.com/docs/openshift?topic=openshift-nodeportnodeport_planning)
* [Enabling access to an app by using a NodePort service](https://cloud.ibm.com/docs/openshift?topic=openshift-nodeportnodeport_config)



[Managing the app lifecycle](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appupdate_app)



* [Update strategies](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appupdating_apps)
* [Scaling apps](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appapp_scaling)
* [Managing rolling deployments to update your apps](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appapp_rolling)
* [Setting up continuous integration and delivery](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appapp_cicd)
For a list of available operating sysems by cluster version, see [Available Red Hat OpenShift versions](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versionsopenshift_versions_available). Note that to use your RHCOS hosts in your clusters, you must create a Red Hat CoreOS-enabled location and a cluster that runs version 4.9 or later. If no option is specified, the default [operating system that corresponds to the cluster version](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versionsopenshift_versions_available) is used.

--size-per-zone WORKERS_PER_ZONE
: Required. The number of worker nodes to request in each zone. Ensure that you [attach enough hosts to your location](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) to be used as worker nodes. For example, if you enter 2 and then [add 2 more zones](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_zone_add_sat) to this worker pool after you create it, ensure that at least 6 unassigned hosts are attached to your location so that they can be assigned as 2 worker nodes in each of the 3 zones in your worker pool.

--zone ZONE
: Required. The name of the zone where you want hosts to be assigned as worker nodes. To see the zone names for your location, run ibmcloud sat location get --location <location_name_or_ID> and look for the Host Zones field. Note that after you create this worker pool, you can [add more zones](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_zone_add_sat) for high availability.

-l, --label KEY1=VALUE1
: Optional. Apply key-value labels to each worker node in the worker pool.