vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Logging To set up an [OpenShift Container Platform Elasticsearch, Fluentd, and Kibana (EFK) stack](https://docs.openshift.com/container-platform/4.11/logging/cluster-logging.html), see [installing the cluster logging operator](https://cloud.ibm.com/docs/openshift?topic=openshift-healthoc_logging_operator). 
 Service catalog The service catalog is not supported. Use [Operators](https://cloud.ibm.com/docs/openshift?topic=openshift-operatorsoperators_4) instead. Do not use the OperatorHub to install the service catalog. 
 Service mesh The Istio managed add-on is not supported. Instead, use the [Red Hat service mesh operator](https://docs.openshift.com/container-platform/4.11/service_mesh/v1x/servicemesh-release-notes.html). Note: The default IBM Cloud configuration of the routers enables host networking, which is not compatible with the service mesh network policy. For the service mesh ingress to work, [apply a network policy](https://gist.githubusercontent.com/kitch/39c504a2ed9e381c2aadea436d5b52e4/raw/d8efa69f41d41425b16bb363a881a98d40d3708c/mesh-policy.yaml). 









 Classic cluster limitations 

Classic infrastructure clusters in Red Hat OpenShift on IBM Cloud are released with the following limitations.



 Compute 

Keep in mind that the [service](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) limitations also apply.



Classic cluster compute limitations

 Category Description 

 Reserved instances [Reserved capacity and reserved instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-provisioning-reserved-capacity-and-instances) are not supported.
Learning path for developers 

Following a curated learning path to deploy highly available containerized apps in Red Hat OpenShift clusters and use the powerful tools of Red Hat OpenShift on IBM Cloud to automate, isolate, secure, manage, and monitor your app workloads across zones or regions.



 Access the cluster 

Begin working with your cluster by setting up the CLI and accessing the cluster.



1. CLI setup: [Set up the CLIs](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-install) that are necessary to create and work with clusters. As you work with your cluster, refer to the [command reference](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli) and keep track of CLI version updates with the [CLI change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog).
2. User permissions: Ensure that your cluster administrator gives you the proper [IBM Cloud IAM role](https://cloud.ibm.com/docs/openshift?topic=openshift-learning-path-adminadmin_secure) to access the cluster.
3. Cluster access: [Access your cluster through the public or private cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster).



Need help? Check out [Troubleshooting clusters and masters](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters) and [Troubleshooting worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_worker_nodes).





 Plan your deployment 

Before you deploy an app, decide how you want to set up your app so that your app can be accessed properly and be integrated with other services.



1.
For virtual machines, it can take a few minutes for the worker node machines to be ordered, and for the cluster to be set up and provisioned in your account. Bare metal physical machines are provisioned by manual interaction with IBM Cloud infrastructure, and can take more than one business day to complete.

ibmcloud oc cluster ls

When the provisioning of your Red Hat OpenShift master is completed, the State of your cluster changes to normal. After your Red Hat OpenShift master is ready, the provisioning of your worker nodes is initiated.

NAME ID State Created Workers Zone Version Resource Group Name Provider
mycluster blrs3b1d0p0p2f7haq0g normal 20170201162433 3 dal10 4.11.42_1544_openshift Default classic

Is your cluster not in a normal state? Check out the [Debugging clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters) guide for help. For example, if your cluster is provisioned in an account that is protected by a firewall gateway appliance, you must [configure your firewall settings to allow outgoing traffic to the appropriate ports and IP addresses](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_outbound).
9. Check the status of the worker nodes.

ibmcloud oc worker ls --cluster <cluster_name_or_ID>

When the worker nodes are ready, the worker node state changes to normal and the status changes to Ready. When the node status is Ready, you can then access the cluster. Note that even if the cluster is ready, some parts of the cluster that are used by other services, such as Ingress secrets or registry image pull secrets, might still be in process. Note that if you created your cluster with a private VLAN only, no Public IP addresses are assigned to your worker nodes.

ID Public IP Private IP Flavor State Status Zone Version
[Develop and deploy an app on Virtual Private Cloud by using deployment strategies](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-vpc)Develop and deploy an app on Virtual Private Cloud by using deployment strategies

In this tutorial, you learn how to create an open toolchain by using different deployment strategies. You also learn how toolchains are implemented in the IBM Cloud® Continuous Delivery service and how to develop and deploy a simple web application (app) by using toolchains.

Creating apps Red Hat OpenShift on IBM Cloud

+2

Kubernetes service,Continuous Delivery



* 30 minutes
* 2022-10-06



[Develop and deploy an application to a Virtual Machine](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-vsi)Develop and deploy an application to a Virtual Machine

This tutorial demonstrates how to set up a Continuous Delivery toolchain and deliver a simple application (app) to a Virtual Machine. You can set up source control, and then build, test, and deploy the code to different deployment stages.

Continuous Delivery



* 40 minutes
* 2022-10-06



[Deploy a Java Liberty app by using IBM Cloud Schematics](https://cloud.ibm.com/docs/apps?topic=apps-tutorial-liberty-webapp)Deploy a Java Liberty app by using IBM Cloud Schematics

In this tutorial, you learn how to create and deploy a scalable Java Liberty application. This scalable web app offers a one-click option to create an IBM Cloud® Schematics workspace with your choice of preconfigured Terraform templates. The Terraform templates deploy your app to IBM Cloud with options for the deployment target (Kubernetes or Red Hat® OpenShift®) and the DevOps toolchain pipeline structure.

Schematics Red Hat OpenShift on IBM Cloud

+4

Red Hat OpenShift on IBM Cloud,Kubernetes service,Continuous Delivery,Creating apps



* 45 minutes
* 2023-03-09
[Working with Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-containers-openshiftshared-containers-openshift)



* [Deploying Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-containers-openshiftdeployment)
* [Related resources](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-containers-openshiftrelated-resources)
* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-containers-openshiftrelated-controls)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-containers-openshiftnext-steps)







 Storage 

[Storage for VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storagevpc-architecture-storage)



* [IBM® Cloud Block Storage for Virtual Private Cloud](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storageblock)
* [IBM Cloud® Object Storage](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storagestorage-cos)
* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storagerelated-controls)
For secured routes, you can decide where you want to implement the TLS termination, such as at the router or at the pod. For more information, see [Exposing apps with routes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routes).





 Securely expose apps with LoadBalancer and Ingress services 

You can use network load balancer (NLB) and Ingress application load balancer (ALB) networking services to connect your apps to the public internet or to external private networks. Review the following optional settings for NLBs and ALBs that you can use to meet back-end app security requirements or encrypt traffic as it moves through your cluster.





 Can I use security groups to manage my cluster's network traffic? 

Classic clusters: IBM Cloud [security groups](https://cloud.ibm.com/docs/security-groups?topic=security-groups-about-ibm-security-groupsabout-ibm-security-groups) are applied to the network interface of a single virtual server to filter traffic at the hypervisor level. If you want to manage traffic for each worker node, you can use security groups. When you create a security group, you must allow the VRRP protocol, which Red Hat OpenShift on IBM Cloud uses to manage NLB IP addresses. To uniformly manage traffic for your cluster across all your worker nodes, use [Calico and Kubernetes policies](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policies).

VPC clusters: VPC security groups are applied to the network interface of a single virtual server to filter traffic at the hypervisor level. You can add inbound and outbound rules to the default security group for your cluster to manage inbound and outbound traffic to a VPC cluster. For more information about the security groups, including the default settings, see [Controlling traffic with VPC security groups](https://cloud.ibm.com/docs/containers?topic=containers-vpc-security-group&interface=ui).
* IBM Cloud® Direct Link: [IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-dl-about) allows you to create a direct, private connection between your remote network environments and Red Hat OpenShift on IBM Cloud without routing over the public internet. The IBM Cloud Direct Link offerings are useful when you must implement hybrid workloads, cross-provider workloads, large or frequent data transfers, or private workloads. To choose an IBM Cloud Direct Link offering and set up an IBM Cloud Direct Link connection, see [Get Started with IBM Cloud IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl) in the IBM Cloud Direct Link documentation.
* Virtual Router Appliance (VRA) or Fortigate Security Appliance (FSA): You might choose to set up a [VRA (Vyatta)](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-about-the-vra) or [FSA](https://cloud.ibm.com/docs/vmwaresolutions/services?topic=vmwaresolutions-fsa_considerations) to configure an IPSec VPN endpoint. This option is useful when you have a larger cluster, want to access multiple clusters over a single VPN, or need a route-based VPN. To configure a VRA, see [Setting up VPN connectivity with VRA](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvyatta).



If you plan to connect your cluster to on-premises networks, check out the following helpful features.



* You might have subnet conflicts with the IBM-provided default 172.30.0.0/16 range for pods and 172.21.0.0/16 range for services.
You can reuse the same public and private VLANs that were created for you because multiple clusters can share VLANs.

For more information about VLANs, subnets, and IP addresses, see [Overview of networking in Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-subnetsbasics).

Need to create your cluster by using custom subnets? Check out [Using existing subnets to create a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-subnetssubnets_custom).





 Worker node communication across subnets and VLANs 

In several situations, components in your cluster must be permitted to communicate across multiple private VLANs. For example, if you want to create a multizone cluster, if you have multiple VLANs for a cluster, or if you have multiple subnets on the same VLAN, the worker nodes on different subnets in the same VLAN or in different VLANs can't automatically communicate with each other. You must enable either Virtual Routing and Forwarding (VRF) or VLAN spanning for your IBM Cloud infrastructure account.



* [Virtual Routing and Forwarding (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf): VRF enables all the private VLANs and subnets in your infrastructure account to communicate with each other. Additionally, VRF is required to allow your workers and master to communicate over the private cloud service endpoint, and to communicate with other IBM Cloud instances that support private cloud service endpoints. To check whether a VRF is already enabled, use the ibmcloud account show command. To enable VRF, run ibmcloud account update --service-endpoint-enable true. This command output prompts you to open a support case to enable your account to use VRF and service endpoints. VRF eliminates the VLAN spanning option for your account because all VLANs are able to communicate. When VRF is enabled, any system that is connected to any of the private VLANs in the same IBM Cloud account can communicate with the cluster worker nodes.
Creating and managing dedicated hosts on VPC Gen 2 infrastructure 

Virtual Private Cloud

Dedicated hosts are single-tenant managed hypervisors that can only be used to deploy Red Hat OpenShift on IBM Cloud clusters.

Dedicated hosts, including those with instance storage, are available in Beta for allowlisted accounts only. [Contact support](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help) for information about how to get added to the allowlist. Additionally, if you want to use dedicated hosts with instance storage, include this in your support case.



 Setting up dedicated hosts in the CLI 

To order dedicated hosts, you must first create a host pool. Then, you can create hosts in the pool.

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service.



1. Review the available dedicated host flavors and make a note of the flavor class that you want to create your host pool with, for example bx2. Dedicated host flavors that include instance storage are indicated with the letter d in the fourth position of the name, for example bx2d-2x8. For more information about using instance storage, see [Instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).

ibmcloud oc dedicated flavors --zone ZONE --provider PROVIDER
2. Create a dedicated host pool.

ibmcloud oc dedicated pool create --flavor-class CLASS --metro METRO --name NAME

--flavor-class CLASS
: The flavor-class of the dedicated host pool. To see available options, run the ibmcloud oc dedicated flavors command. Example: bx2.

--metro METRO
: The metro to create the dedicated host pool in, such as dal or wdc.

--name NAME
: The name of the dedicated host pool.
3. Create at least one dedicated host in each zone where your workers reside.

To improve redundancy, create more than one dedicated host in each zone where your workers reside.
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.
5. Click My software > Visit the Marketplace.
6. In the search bar, type blockchain to load the blockchain tile.
7. Click Purchase to get started. From the Purchase complete page, click Install now. This installs the IBM Blockchain Platform operator into your cluster. Note that during the installation process you are required to select which OpenShift project to deploy the operator to from the Namespace scope drop-down. After the operator is installed, your cluster connects back to Red Hat Marketplace and then becomes a target cluster for installing and managing the operator from Red Hat Marketplace. You can deploy the operator multiple times across different clusters as long as they have registered with the Red Hat Marketplace. When selecting a namespace for operator installation, All namespaces on the cluster is selected by default—you must change this default selection to a specific namespace in the cluster to make operator and Fabric components run in a dedicated namespace.

Zoom

![Install the operator in the openshift-operators namespace](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/allnamespace-install-operator.png)

Figure 1. Install the operator in the openshift-operators namespace
8. The Console and Fabric components can be installed in any namespace.

Zoom

!
[Supply Chain](https://www.ibm.com/products/supply-chain-business-network?lnk=STW_US_STESCH&lnk2=demo_SupplyChnBus&pexp=def&psrc=none&mhsrc=ibmsearch_a&mhq=supply%20chain) Supply chain resiliency starts with a business network that handles peak events with ease and detects potential issues before they occur. 
 [Data Fabric](https://www.ibm.com/topics/data-fabric?mhsrc=ibmsearch_a&mhq=data%20fabric) Data fabric is an architecture that facilitates the end-to-end integration of various data pipelines and cloud environments through the use of intelligent and automated systems. 
 [Business Automation](https://www.ibm.com/cloud/cloud-pak-for-business-automation?lnk=STW_US_STESCH&lnk2=learn_CloudPakAtm&pexp=DEF&psrc=NONE&mhsrc=ibmsearch_a&mhq=Business%20Automation) IBM Cloud Pak for Business Automation is a modular set of integrated software components, built for any hybrid cloud, designed to automate work and accelerate business growth. 
 [Security](https://www.ibm.com/products/cloud-pak-for-security?lnk=STW_US_STESCH&lnk2=learn_CloudPakSec&pexp=DEF&psrc=NONE&mhsrc=ibmsearch_a&mhq=cloud%20pak%20for%20security) IBM Cloud Pak for Security can help you gain deeper insights, mitigate risks and accelerate response. 
 [IBM Cloud](https://ibm.com/cloud) IBM Cloud provides solutions that enable higher levels of compliance, security, and management, with proven architecture patterns and methods for rapid delivery for running mission-critical workloads. 







 Learn how our customers are finding success 

The following use cases are examples of CSMs collaborating with IBM customers.

NCHC uses AIOps to improve public network services and proactively prevent outages.
Direct Link docs 

The IBM Cloud Direct Link solution is designed to seamlessly connect your on-premises resources to your cloud resources. Leverage the docs, CLI, and API reference to plan for, provision, and manage your direct links.

 Developer tools 

[API & SDK reference](https://cloud.ibm.com/apidocs/direct_link)[CLI reference](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)[Terraform reference](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/dl_gateway)

 Recommended content 

[Ordering Direct Link Dedicated Terminate a single-tenant, fiber-based, cross connect into your own IBM Cloud private network connection. Also used by colocation facilities adjacent to IBM Cloud PoPs and data centers.](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-dedicated)[!Ordering Direct Link Connect Fast setup Leverage a service provider to quickly establish and deliver connectivity to IBM Cloud locations. Ideal for multi-cloud environments with your service provider's network.](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-connect)

 Video library 

[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/dl//images/thumbnail.png)<br><br>IBM Cloud Direct Link for hybrid cloud](https://cloud.ibm.com/docs/dl?topic=dl-offering-video)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>!
The Direct Link Dedicated Hosting on Classic solution 

The Direct Link Dedicated Hosting on Classic solution provides connectivity similar to Dedicated on Classic, but the connection point is next to an IBM Cloud data center, which improves latency for higher performance use cases. IBM Cloud offers various customizable colocation services with this solution, with simple pricing.

Common use cases: Best for working with non-standard compute technologies, for dedicated storage requirements, or for using existing IT investments.

Zoom

![Direct Link Dedicated Hosting on Classic](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-Link-Dedicated-Hosting.png)

Figure 4. Direct Link Dedicated Hosting on Classic

Termination location: IBM Cloud Data Center (DC).

Typical deployment time: 30 - 60 days after all requirements are finalized and contracts are executed.

Cross-connect details: IBM Cloud provides 1G or 10G fiber connections from the IBM Cloud cross-connect router (XCR) infrastructure to the customer's colocation environment as part of the deployment. If colocation services are not requested (if existing environments are connected already), IBM Cloud provides a Letter of Authorization (LOA) that a customer uses to order fiber ethernet (single-mode fiber only, either 1Gig-LX or 10Gig-LR optics) that runs from a customer cage to the IBM Cloud CFA termination point, which will be tied down to the cross-connect router (XCR) infrastructure. The media must be a 1310 nm wavelength optic.

Port speed options: Select 1 Gbps, 2 Gbps, 5 Gbps, or 10 Gbps.

Approximate latency: Latency is approximately 0.5 ms within the local data center.

IBM colocation services: Yes.

Redundancy: IBM Cloud provides connections to two diverse cross-connect routers (XCRs) as part of the product. To establish redundant connectivity, customers must configure BGP on each Direct Link on Classic connection as they prefer.