vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Planning your deployment 

SAP Data Hub is available for Red Hat OpenShift Container Platform 3.11. IBM Cloud manages the platform for you; you chose the size and number of worker nodes and the geographic location of the data center.

When Planning your deployment, you set the flavor of your worker nodes within your Red Hat OpenShift on IBM Cloud cluster. Flavor describes the compute resources, such as CPU or vCPU, memory, and disk capacity that you order when you provision your worker node. Worker nodes of the same flavor are grouped in worker node pools. The total number of worker nodes in a cluster determines the compute capacity that is available to your apps in the cluster. For more information, see [Planning your worker node setup](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodes).



 Red Hat OpenShift Cluster Network Connectivity 

SAP Data Hub allows you to connect a wide range of systems and components, as long as the required network connectivity is in place.

To be sure the connections between systems and components meet requirements, we recommend that you combine planning the SAP Data Hub network layout with planning the systems you want to connect. Planning everything together helps ensure that network communication is possible for the required protocols (such as firewall rules, DMZ setups, and so on).

For security, we recommend using:



* Properly encrypted communication for all channels, in particular, leveraging transport layer security (TLS).
* A common certificate authority (CA) that can be imported as a trusted source in the various components.



For more information, see the [Administration Guide for SAP Data Hub](https://help.sap.com/doc/70ce58a2ed23404fac27ae36c8f76900/2.7.latest/en-US/loio70ce58a2ed23404fac27ae36c8f76900.pdf).

For productive setups, we recommend preparing the required SSL certificates using the preferred tools. For non-productive setups, note that the SAP Data Hub installer can generate self-signed certificates.





 Red Hat OpenShift Cluster Storage
: For classic clusters in Dallas, updated the required IP addresses and ports that you must open in a [public gateway firewall device](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_outbound), [private gateway device firewall](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_private), or [Calico network isolation policies](https://github.com/IBM-Cloud/kube-samples/tree/master/calico-policies).

Object Storage
: Added steps to help you [decide on the object storage configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_installconfigure_cos) and added troubleshooting steps for when [app pods fail because of an Operation not permitted error](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_operation_not_permitted).





 13 October 2020 

New! Certified Red Hat OpenShift version 4.5
: You can now create clusters that run Red Hat OpenShift version 4.5. To update an existing cluster, see the [Version 4.5 preparation actions](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive). The Red Hat OpenShift 4.5 release is also certified for Kubernetes 1.18.

Deprecated: Red Hat OpenShift version 4.3
: With the release of version 4.5, clusters that run version 4.3 are deprecated. Update your clusters to at least [version 4.4](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) today.

Version change logs
: Change log documentation is available for [4.5.13_1515](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4513_1515).
OpenShift Container Platform licenses can be supplied by an [existing IBM Cloud Pak entitlement](https://cloud.ibm.com/docs/openshift?topic=openshift-costslicenses-cloud-pak) or [by Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-costslicenses-on-demand).



 OCP licenses from Red Hat OpenShift on IBM Cloud 

When you create worker nodes by adding a worker pool or cluster, Red Hat OpenShift on IBM Cloud helps you include the purchase of OpenShift Container Platform licenses for the worker nodes. The way that these OpenShift Container Platform licenses are billed varies by the type of OpenShift Container Platform licenses that the worker nodes have.



* [New OCP licenses](https://cloud.ibm.com/docs/openshift?topic=openshift-costslicenses-on-demand-new) with reduced pricing, available 9 November 2020. Create a cluster or worker pool with the latest flavors to use the new OCP licenses.
* Deprecated: [Old OCP licenses](https://cloud.ibm.com/docs/openshift?topic=openshift-costslicenses-on-demand-old) for existing worker nodes before 9 November 2020 or deprecated bare metal flavors. [Migrate](https://cloud.ibm.com/docs/openshift?topic=openshift-costslicenses-on-demand-migrate) your existing worker nodes to take advantage of the new OCP licenses.





 New OCP licenses with reduced pricing, available 9 November 2020 

New OCP licenses include reduced pricing from Red Hat. a Red Hat OpenShift license is billed for every two virtual cores (or one physical cores) of the worker node flavor. Charges vary by the type of worker node that you have, for as long as you have the worker node.
If no logging configurations for syslog exist in your cluster, the Fluentd component is removed automatically. If you don't forward logs to syslog and want to ensure that the Fluentd component is removed from your cluster, [automatic updates to Fluentd must be enabled](https://cloud.ibm.com/docs/containers?topic=containers-updatelogging-up).





 15 November 2019 

New! Single zone location for Red Hat OpenShift clusters
: You can create single zone Red Hat OpenShift on IBM Cloud clusters in São Paulo, Brazil (sao01).





 11 November 2019 

Exposing apps that are external to your cluster by using Ingress
: Added information for how to use the proxy-external-service Ingress annotation to include an app that is external to your cluster in Ingress application load balancing.

Red Hat OpenShift overview
: Added an [Red Hat OpenShift overview page](https://cloud.ibm.com/docs/openshift?topic=openshift-overview).

Setting pod priority
: Added a [pod priority page](https://cloud.ibm.com/docs/openshift?topic=openshift-pod_priority).

Using IBM Cloud Container Registry
: Added the following topics about using IBM Cloud Container Registry:



* [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 default-region-icr-io secrets](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).
Updating Satellite location control plane hosts 

IBM provides version updates for your hosts that are assigned to the Satellite location control plane. The version updates include OpenShift Container Platform, the operating system, and security patches. You choose when to apply the host version updates by detaching the hosts from your location, reloading the host machine in the infrastructure provider, and reattaching and reassigning the host to the Satellite location control plane.



 Considerations before you update control plane hosts 

Review the following considerations before you update your Satellite location control plane hosts.

How can I tell if a version update is available?
: Version updates for hosts become available as the Red Hat OpenShift on IBM Cloud team packages new versions for worker nodes. Typically, worker node version updates are released every two weeks.
: You might check for a version update to meet your required security cadence, such as updates on a monthly or bi-monthly basis. To review available version updates, see the [Version change log for Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).

Does updating the hosts impact the cluster masters that run in the Satellite location control plane?
: Yes. Because the cluster masters run in your Satellite location control plane, make sure that you have enough extra hosts in your control plane before you update any hosts. To attach extra hosts, see [Attaching capacity to your Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts).

Do the hosts in my Satellite-enabled IBM Cloud services have to run the same version as my Satellite location control plane?
: No, the hosts that are assigned to the Satellite location control plane do not have to run the same version as the hosts that are assigned to Satellite-enabled IBM Cloud services that run in the location. However, all hosts in the location must run a supported version.
The SSH key should be configured in the same account that is being used against the API key.
* Update the region value where the cluster is deployed. The selected region should match the region where the SSH key is configured.
* Update the cluster_prefix value to the specific cluster prefix for your Red Hat OpenShift cluster.
* Update the worker_nodes_per_zone value according to your requirement.





Review the following table for more information about cluster deployment parameters:



Table 1. Cluster deployment parameters

 Parameter Description 

 api_key This is the API key for the IBM Cloud account in which the Red Hat OpenShift cluster needs to be deployed. For more information on how to create an API key, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey). 
 ssh_key_name Comma-separated list of names of the SSH key configured in your IBM Cloud account that is used to establish a connection to the Red Hat OpenShift login node. Ensure that the SSH key is present in the same resource group and region where the cluster is being provisioned. If you do not have an [SSH key](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys) in your IBM Cloud account, create one by using the SSH keys instructions. 
 region Enter a region from the following list in which the cluster will be deployed: us-south, us-east, eu-gb, eu-de, jp-tok, au-syd, jp-osa, br-sao, ca-tor. For more information, see [Region and data center location for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations). 
 cluster_prefix Prefix that is used to name the IBM Cloud resources that are provisioned to build the Red Hat OpenShift cluster. You cannot create more than one instance of the Red Hat OpenShift cluster with the same name. Make sure that the name is unique. Enter a prefix name, for example, 'my-openshift'. The length of the prefix should be fewer than 13 characters.
Previously, when you removed a nonmanagement cluster, for example, an edge services cluster, any services installed on that cluster were not removed. You had to first delete the services from the cluster and then delete the cluster itself.

This change affects the Juniper vSRX and Red Hat OpenShift for VMware services.

REST APIs
: APIs are now available for the Red Hat OpenShift for VMware service.

New and updated documentation
: A new topic, Resource requirements for add-on services, is now available.

The topic describes how capacity checking works for various services and what resources are required to install certain services, such as Caveonix RiskForesight, Juniper vSRX, and Veeam. The information replaces the documentation that was provided in the overviews of the individual services.

User interface updates and enhancements
: A checklist is added at the beginning of the ordering pages to help you prepare your environment when you place an order for the first time. This feature does not apply to the following instances and services.



* Single-node Trial for Migration and App Modernization instances
* Single-node Trial for Data Protection and Disaster Recovery instances
* KMIP for VMware instances
* On-premises VMware HCX instances
* Caveonix RiskForesight licenses
* Veeam licenses
If you include this option, you must also include the --provider option.

-q
: Optional. Do not show the message of the day or update reminders.
3. Verify that your location is created and wait for the location Status to change to action required. When you create the location, a location control plane master is deployed to the region that you selected during location creation. During this process, the Status of the location shows deploying. While the master deploys, you can now attach compute capacity to your location to complete the setup of the Satellite location control plane.

ibmcloud sat location ls

Example output

Name ID Status Ready Created Hosts (used/total) Managed From
mylocation brhtfum2015a6mgqj16g action required no 1 minute ago 0 / 3 Washington DC
4. To finish the setup of your location.



1. [Attach compute hosts to your location](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts).
2. Assign these hosts as worker nodes to the [Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane).





Want to verify if your location is enabled for Red Hat CoreOS? See [Is my location enabled for Red Hat CoreOS?](https://cloud.ibm.com/docs/satellite?topic=satellite-locationsverify-coreos-location).





 Is my location enabled for Red Hat CoreOS? 

You can verify that your location is enabled for Red Hat CoreOS by running the location get command. Look for the Ignition Server Port: field to populate. Wait to check until after your location is provisioned.

Red Hat CoreOS is available in all supported Satellite locations and for Red Hat OpenShift version 4.9 and later. Red Hat CoreOS hosts don't support all services. For more information, see [Supported Satellite-enabled IBM Cloud services](https://cloud.ibm.com/docs/satellite?topic=satellite-managed-services).

ibmcloud sat location get --location LOCATION
IBM Cloud RBAC Operator 86de2b7 3dd6bbc Updated image for [CVE-2020-28851](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28851). 
 Red Hat OpenShift 4.5.31 4.5.35 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.htmlocp-4-5-35). 
 Red Hat OpenShift Control Plane Operator v4.5.0-20210112 v4.5.0-20210301 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.5.0+20210301). 
 OpenVPN Operator image v1.1.2 v1.2.0 Fixed a bug that could prevent worker node VPN updates. 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.5.0-20210112 v4.5.0-20210301 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.5.0+20210301). 
 Red Hat OpenShift on IBM Cloud toolkit 4.5.0+20210112 4.5.0+20210301 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.5.0+20210301). 







 Change log for worker node fix pack 4.5.35_1534_openshift, released 29 March 2021 

The following table shows the changes that are in the worker node fix pack 4.5.35_1534_openshift.
Thus, the annual rollout of benefits is a key aspect of fostering an employee-centered culture.

They need a solution that helps the Developers and their users.



* FRONT-END TO EXISTING BENEFITS: insurance, educational offerings, wellness, and more
* REGION-SPECIFIC FEATURES: each country has unique HR policies so that the overall site might look similar but show region-specific benefits
* DEVELOPER-FRIENDLY TOOLS that accelerate rollout of features and bug fixes
* CHATBOT to provide authentic conversations about benefits and resolve users requests and questions efficiently.



Technical solution:



* Red Hat OpenShift on IBM Cloud
* IBM Cloud® Continuous Delivery
* IBM Logging and Monitoring
* IBM® Secure Gateway for IBM Cloud®
* IBM Cloud App ID



Accelerated development is a key win for the HR Exec. The team gets started by containerizing their apps and putting them in the cloud. With the use of modern containers, Developers can experiment easily with Node.js SDK and push changes to Development and Test systems, which are scaled out on separate clusters. Those pushes were automated with open toolchains and IBM Cloud® Continuous Delivery. No longer were updates to the HR site languishing in slow, error-prone build processes. They can deliver incremental updates to their site, daily or even more frequently. Moreover, logging and monitoring for the HR site is rapidly integrated, especially for how the site pulls personalized data from back-end benefit systems. Developers don’t waste time building complex logging systems, just to be able to troubleshoot live systems. Developers don't need to become experts in cloud security, they can enforce policy driven authentication easily by using IBM Cloud App ID.

With Red Hat OpenShift on IBM Cloud, they went from over-built hardware in a private data center to customizable compute that reduces IT operations, maintenance, and energy. To host the HR site, they could easily design Kubernetes clusters to fit their CPU, RAM, and storage needs. Another factor for less personnel costs is that IBM manages Kubernetes, so the Developers can focus on delivering better employee experience for benefits enrollment.
If you are interested in learning more about how to use IBM Blockchain Platform on Red Hat OpenShift Container Platform, Red Hat Open Kubernetes Distribution (OKD), or Kubernetes, see [Getting started with IBM Blockchain Platform 2.5.4](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-get-started-console-ocp).

If you are an experienced Hyperledger Fabric customer and are interested in learning more about how to use the IBM Blockchain peer, CA, orderer, and smart contract containers images, see [Using the IBM Blockchain images ](https://cloud.ibm.com/docs/blockchain-sw-254?topic=blockchain-sw-254-blockchain-images).

After you link your IBM Blockchain Platform to your Kubernetes cluster on IBM Cloud, you can launch the console to create and manage your blockchain components and experience the following important benefits:



* Control: You control and manage your blockchain components and certificates from one central console. Deploy only the components needed for your business and add more as your need grow.
* Flexible Kubernetes based deployment: You can take advantage of the compute (CPU, memory, storage) options for your Kubernetes cluster and leverage built-in HA and DR options.





 What is the Blockchain Service? 

The following diagram illustrates the three elements of the IBM Blockchain Platform:

Zoom

![IBM Blockchain Platform](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/IBP-Diagram.svg)

Figure 1. The IBM Blockchain Platform components



* IBM Blockchain Platform Console (UI): This is the console that allows you to create and manage your blockchain components. After you provision a service instance in IBM Cloud, you can deploy an instance of the IBM Blockchain console and link it to your Kubernetes cluster on IBM Cloud.
Access policies determine the level of access that users in your IBM Cloud account have to resources across the IBM Cloud platform. A policy assigns a user one or more roles that define the scope of access to a single service or to a set of services and resources that are organized together in a resource group. Each service in IBM Cloud might require its own set of access policies.



 Pick the correct access policy and role for your users 

You must define access policies for every user that works with Red Hat OpenShift on IBM Cloud. The scope of an access policy is based on a user's defined role or roles, which determine the actions that the user can perform. Some policies are pre-defined but others can be customized. The same policy is enforced whether the user makes the request from the IBM Cloud API, CLI, or UI.

The following image shows the different types of permissions and roles, the actions a role can perform, and how the roles relate to each other.

Zoom

![In IBM Cloud, you can assign IAM platform, IAM service, Cloud Foundry, and infrastructure roles.](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/user_access.png)

Figure 1. Assign IAM platform, IAM service, Cloud Foundry, and infrastructure roles

To see the specific Red Hat OpenShift on IBM Cloud permissions that can be performed with each role, check out the [User access permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-access_reference) reference topic.



 Overview of IBM Cloud IAM platform access roles 

Use platform access roles in IBM Cloud Identity and Access Management (IAM) to grant users access to manage cluster resources in Red Hat OpenShift on IBM Cloud. When you configure permissions for Red Hat OpenShift on IBM Cloud in IAM, use the name containers-kubernetes for the API or CLI, and Kubernetes Service for the console.

What types of actions do platform access roles permit?
Worker node management fee Per vCPU hour of the hosts that are assigned to the cluster as worker nodes. Per vCPU hour of the hosts that are assigned to the cluster as worker nodes. The benefits of IBM Cloud Satellite, such as to create the cluster on any compatible infrastructure that you want; tooling to consistently deploy apps, storage drivers, and endpoints across the location; integration with IBM Cloud platform tooling such as IAM; continuous monitoring by IBM Site Reliability Engineers; access to IBM Cloud support; and more. 
 OCP licensing fee Per vCPU hour. You can either purchase a license during cluster creation or [bring your own](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clustersbyo-ocp-satellite). Per vCPU hour. You can either purchase a license during cluster creation or [bring your own](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clustersbyo-ocp-satellite). 







 Bringing your own OCP license 

All user clusters in your Satellite location are installed with OpenShift Container Platform, which incurs a licensing fee from Red Hat. However, you can bring your own OpenShift Container Platform license for clusters created with your on-premises infrastructure or for clusters created on-premises by using IBM Cloud Paks.

When you create the cluster, make sure to include your Red Hat pull secret to entitle the cluster to run OCP, either by uploading the pull secret in the console or by including the --pull-secret option in the ibmcloud oc cluster create satellite[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicli_cluster-create-satellite).

Service clusters, which are the underlying platform for all IBM Cloud services are created by services such as Key Protect or IBM Cloud Object Storage and do not require a license.