vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Install the Red Hat OpenShift on IBM Cloud observability CLI plug-in (ibmcloud ob)](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).
* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).





To set up a monitoring configuration for your cluster:



1. Create an [IBM Cloud Monitoring service instance](https://cloud.ibm.com/docs/monitoring?topic=monitoring-provision) and note the name of the instance. The service instance must belong to the same IBM Cloud account where you created your cluster, but can be in a different resource group and IBM Cloud region than your cluster.
2. Set up a monitoring configuration for your cluster. When you create the monitoring configuration, an Red Hat OpenShift project ibm-observe is created and a Monitoring agent is deployed as a Kubernetes daemon set to all worker nodes in your cluster. This agent collects cluster and pod metrics, such as the worker node CPU and memory usage, or the amount incoming and outgoing network traffic to your pods.

In the console.



1. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), select the cluster for which you want to create a Monitoring configuration.
2. On the cluster Overview page, click Connect.
3. Select the region and the IBM Cloud Monitoring service instance that you created earlier, and click Connect.



In the CLI.



1. Create the Monitoring configuration. When you create the Monitoring configuration, the access key that was last added is retrieved automatically. If you want to use a different access key, add the --sysdig-access-key <access_key> option to the command.
: You can create or [update](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) your cluster to Red Hat OpenShift version 4.6, which includes Kubernetes 1.19. With Red Hat OpenShift 4.6, you get the latest stable enhancements from the community. For more information, see the [blog announcement](https://www.ibm.com/cloud/blog/announcements/openshift-version-46-now-available-in-red-hat-openshift-on-ibm-cloud).

Deprecated Red Hat OpenShift 4.4
: With the release of Red Hat OpenShift 4.6, clusters that run version 4.4 are deprecated, with an unsupported date of 31 May 2021. Update your cluster to at least [version 4.5](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive) as soon as possible.





 15 February 2021 

New! Osaka multizone region
: You can now create classic or VPC clusters in the Osaka, Japan (jp-osa) [location](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zones).

Worker node versions
You can also review the [service architecture](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architecture) for an overview of how Red Hat OpenShift components are set up in the cluster master and worker nodes, or the [global settings](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsglobal-settings) that you can or can't configure.



Comparison between clusters that run in IBM Cloud and standard OCP

 Characteristics Standard OCP Red Hat OpenShift on IBM Cloud 

 Cluster master (control plane) You set up control plane components like the API server and etcd on machines that get the master role. You can modify the control plane components, but keep in mind that you are responsible for backing up, restoring, and making control plane data highly available. IBM sets up the master, manages the control plane components, and automatically applies master patch updates for you. The masters are highly available and backed up automatically. 
 Compute machines (worker nodes) You create your own compatible compute machines, set up compatible network connectivity, SSH into the machines, install OCP, and register the machines as worker nodes in the cluster. Your machines might be installer-provisioned infrastructure (IPI) for a guided setup, or user-provisioned infrastructure (UPI) for more control and subsequent administration on your end. You are responsible for maintaining and updating the worker nodes. You can install updates from the Red Hat OpenShift web console. You select the flavor of worker nodes that you want to add to your cluster, and IBM automatically connects the worker nodes to the cluster and installs OCP. In this sense, the installation is similar to IPI for you because you don't have to manage all the infrastructure and network settings. IBM also provides patch updates that you can choose to apply to your worker nodes, from the IBM Cloud interface (not the Red Hat OpenShift web console). SSH is disabled for added security. 
 OCP versions and patch updates You are responsible for updating the underlying infrastructure for the master and worker nodes. You can use the Red Hat OpenShift web console to update OCP versions.
The custom models now load much faster, greatly reducing latency when they are used for recognition.





 15 July 2020 (Version 1.1.4) 

Red Hat OpenShift version 4.3 is going out of service
: IBM Cloud Pak for Data 3.0.1 is deprecating support for Red Hat OpenShift 4.3 on 1 September 2020. Red Hat OpenShift 4.3 is going out of service on 22 October 2020. IBM Cloud Pak for Data is introducing support for Red Hat OpenShift 4.5. IBM Cloud Pak for Data is recommending that clients upgrade to Red Hat OpenShift 4.5 before 22 October 2020. IBM Support will work with any customers who already installed IBM Cloud Pak for Data 3.0.1 on Red Hat OpenShift 4.3. New customers who want to install on Red Hat OpenShift 4.x are instructed to install Red Hat OpenShift 4.5.





 19 June 2020 (Version 1.1.4) 

Version 1.1.4 is available
: Speech to Text for IBM Cloud Pak for Data version 1.1.4 is now available. Installation and administration of the service include many changes. This version supports IBM Cloud Pak for Data versions 2.5 and 3.0.1, and Red Hat OpenShift versions 3.11 and 4.3. For more information about installing and managing the service, see [Installing Watson Speech to Text version 1.1.4](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-speech-install).

New parameters to control the level of speech activity detection
: The service now offers two new optional parameters for controlling the level of speech activity detection. The parameters can help ensure that only relevant audio is processed for speech recognition.



* The speech_detector_sensitivity parameter adjusts the sensitivity of speech activity detection. You can use the parameter to suppress word insertions from music, coughing, and other non-speech events.
* The background_audio_suppression parameter suppresses background audio based on its volume to prevent it from being transcribed or otherwise interfering with speech recognition. You can use the parameter to suppress side conversations or background noise.



You can use the parameters individually or together.
Cluster version <br><br> * Provide a suite of tools to automate cluster management, such as the Red Hat OpenShift on IBM Cloud [API](https://containers.cloud.ibm.com/global/swagger-global-api//), [CLI plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cli), and [console](https://cloud.ibm.com/kubernetes/clusters).<br> * Automatically apply Red Hat OpenShift master patch OS, version, and security updates.<br> * Make major and minor updates for master nodes available for you to apply.<br> * Provide worker node major, minor, and patch OS, version, and security updates.<br> * Fulfill automation requests to update cluster master and worker nodes.<br><br><br> <br><br> * Use the API, CLI, or console tools to [apply](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) the provided major and minor Red Hat OpenShift master updates and major, minor, and patch worker node updates.<br><br><br> 







 Identity and access management 

You and IBM share responsibilities for controlling access to your Red Hat OpenShift on IBM Cloud instances. For IBM Cloud® Identity and Access Management responsibilities, consult that product's documentation. You are responsible for identity and access management to your application data.



Table 4. Responsibilities for identity and access management

 Resource IBM responsibilities Your responsibilities 

 Observability <br><br> * Provide the ability to integrate IBM Cloud Activity Tracker with your cluster to audit the actions that users take in the cluster.<br><br><br> <br><br> * Set up IBM Cloud Activity Tracker or other capabilities to track user activity in the cluster.<br><br><br> 







 Security and regulation compliance 

IBM is responsible for the security and compliance of Red Hat OpenShift on IBM Cloud. Compliance to industry standards varies depending on the infrastructure provider that you use for the cluster, such as classic or VPC.
* One subnet that can be used for this tutorial, take note of the subnet's zone and name
* Public gateway is attached to the subnet



* Select an existing Cloud Object Storage service or create one if required



5. Under Location



* For Red Hat OpenShift on VPC infrastructure



* Select a Resource group
* Uncheck the inapplicable zones
* In the desired zone verify the desired subnet name and if not present click the edit pencil to select the desired subnet name



* For Red Hat OpenShift on Classic infrastructure follow the [Creating a standard classic cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersclusters_standard) instructions.



* Select a Resource group
* Select a Geography
* Select Single zone as Availability
* Choose a Datacenter





6. Under Worker pool,



* Select 4 vCPUs 16GB Memory as the flavor
* Select 2 Worker nodes per data center for this tutorial (classic only: Leave Encrypt local disk)



7. Under Integrations, enable and configure Logging and Monitoring.
8. Under Resource details,Set Cluster name to <your-initials>-myopenshiftcluster by replacing <your-initials> with your own initials.
9. Click Create to provision a Red Hat OpenShift on IBM Cloud cluster.



Take a note of the resource group selected above. This same resource group will be used for all resources in this lab.



 Initialize a Cloud Shell 

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.
Component Previous Current Description 

 RHEL 8 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. 4.11.17 4.11.18 For more information, see the [change log](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-18). 







 Change log for master fix pack 4.11.17_1535_openshift, released 14 December 2022 

The following table shows the changes that are in the master fix pack 4.11.17_1535_openshift. Master patch updates are applied automatically.



Changes since version 4.11.12_1532_openshift

 Component Previous Current Description 

 Cluster health image v1.3.13 v1.3.14 Updated Go dependencies. Exclude ingress status from cluster status aggregation. 
 etcd v3.5.5 v3.5.6 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.5.6). 
 IBM Calico extension 1213 1257 Updated universal base image (UBI) to resolve: [CVE-2022-1304](https://nvd.nist.gov/vuln/detail/cve-2022-1304), [CVE-2016-3709](https://nvd.nist.gov/vuln/detail/CVE-2016-3709), [CVE-2022-42898](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42898). 
 IBM Cloud Block Storage driver and plug-in v2.3.3 v2.3.4 Update Go to version 1.18.8 and updated universal base image (UBI) to resolve CVEs. 
 IBM Cloud Controller Manager v1.24.7-10 v1.24.8-3 Updated to support the Kubernetes 1.23.14 release.
: Red Hat OpenShift [3.11.170_1543_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311170_1543_worker).







 February 2020 



 19 February 2020 

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

Troubleshooting Ingress
: Added a [debugging guide](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-debug-roks4) and [troubleshooting topic](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_subnet_limit_43) for Ingress in version 4.3 clusters.

Developing and deploying apps
: You can now find expanded information on how to develop and deploy an app to your cluster in the following pages.



* [Planning app deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploy)
* [Building containers from images](https://cloud.ibm.com/docs/openshift?topic=openshift-images)
* [Developing Kubernetes-native apps](https://cloud.ibm.com/docs/containers?topic=containers-app)
* [Deploying Kubernetes-native apps in clusters](https://cloud.ibm.com/docs/containers?topic=containers-deploy_app)
* [Managing the app life cycle](https://cloud.ibm.com/docs/openshift?topic=openshift-update_app)



Learning paths
1.2.33 Red Hat OpenShift on IBM Cloud can optionally [enable a Kubernetes Key Management Service (KMS) provider](https://cloud.ibm.com/docs/openshift?topic=openshift-encryptionkms). 
 1.2.34 Red Hat OpenShift on IBM Cloud can optionally [enable a Kubernetes Key Management Service (KMS) provider](https://cloud.ibm.com/docs/openshift?topic=openshift-encryptionkms). 
 3.2.1 Red Hat OpenShift on IBM Cloud can optionally [enable Kubernetes API server auditing](https://cloud.ibm.com/docs/openshift?topic=openshift-health-audit). 
 3.2.2 Red Hat OpenShift on IBM Cloud can optionally [enable Kubernetes API server auditing](https://cloud.ibm.com/docs/openshift?topic=openshift-health-audit). 
 4.2.6 Red Hat OpenShift on IBM Cloud does not protect kernel defaults to allow customers to tune kernel parameters. 
 4.2.8 Red Hat OpenShift on IBM Cloud ensures that the hostname matches the name issued by the infrastructure. 
 5.1.2 Red Hat OpenShift on IBM Cloud deploys some system components that could have their Kubernetes secret access further restricted. 
 5.1.3 Red Hat OpenShift on IBM Cloud deploys some system components that could have their Kubernetes resource access further restricted. 
 5.1.5 Red Hat OpenShift on IBM Cloud does not set [automountServiceAccountToken: false](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/use-the-default-service-account-to-access-the-api-server) for each default service account.
Built-in container image streams, builds, and tooling ([read more](https://blog.cloudowski.com/articles/why-managing-container-images-on-openshift-is-better-than-on-kubernetes/)) Yes 
 Integrated CI/CD with Jenkins Yes 
 Stricter app security context set up by default Yes 
 Simplified Kubernetes developer experience, with an app console that is suited for beginners Yes 
 Supported operating system Ubuntu 18.04 x86_64, 16.04 x86_64 (deprecated) <br><br> * For versions 4.10 and later: Red Hat Enterprise Linux 8<br> <br> <br> <br> <br> * For versions 4.9 and earlier:Red Hat Enterprise Linux 7<br> * For a complete list, see [Available Red Hat OpenShift versions](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versionsopenshift_versions_available).<br> <br> <br> <br> <br><br><br> 
 Preferred external traffic networking Ingress Router 
 Secured routes encrypted with Hyper Protect Crypto Services Yes 







 Comparison between clusters that run in IBM Cloud and standard OCP 

Because Red Hat OpenShift on IBM Cloud is a managed service, many of the Red Hat® OpenShift® on IBM Cloud® components and global settings that you manually set up in OpenShift Container Platform are set up for you by default in Red Hat OpenShift on IBM Cloud. Review the following differences between Red Hat OpenShift on IBM Cloud clusters and a standard installation of OpenShift Container Platform on your own infrastructure. You can also review the [service architecture](https://cloud.ibm.com/docs/openshift?topic=openshift-service-architecture) for an overview of how Red Hat OpenShift components are set up in the cluster master and worker nodes, or the [global settings](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsglobal-settings) that you can or can't configure.
RHEL 8 Packages 4.18.0-372.19.1 4.18.0-372.26.1 N/A 
 Red Hat OpenShift on IBM Cloud. 4.8.48 4.8.50 For more information, see the [change log](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-50). 







 Change log for worker node fix pack 4.8.48_1572_openshift, released 12 September 2022 

The following table shows the changes that are in the worker node fix pack 4.8.48_1572_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.8.47_1570_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. 4.8.47 4.8.48 For more information, see the [change log](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-48). 







 Change log for master fix pack 4.8.47_1571_openshift, released 1 September 2022 

The following table shows the changes that are in the master fix pack 4.8.47_1571_openshift. Master patch updates are applied automatically.



Changes since version 4.8.46_1566_openshift

 Component Previous Current Description 

 Calico v3.21.5 v3.21.6 See the [Calico release notes](https://docs.tigera.io/archive/v3.21/release-notes/.v3216). Updated the Calico custom resource definitions to include preserveUnknownFields: false.
About virtual network functions over VPC 

Network Function Virtualization (NFV) is the network infrastructure behind virtualizing network services (such as routers, firewalls, and load balancers) that were traditionally run on proprietary hardware. These services, called Virtual Network Functions (VNFs), are packaged as virtual machines (VMs) on commodity hardware, which allows service providers to run their networks on standard servers instead of proprietary ones. This third-party software interacts with the IBM Software-Defined Networking (SDN) controller to offer easy configuration, centralized management, and lower operational costs.

Working along with IBM Cloud® Schematics (Infrastructure as Code) and the IBM Content catalog, customers are able to instantiate best-in-network solutions to manage their workload.

Benefits include:



*  Instantiating virtual network services and modifying configurations without the need to deploy new network hardware.
*  Rapid service delivery with the agility to scale well above physical hardware.
*  Centralized policy control.
*  Using the same routers, firewalls, load balancers, and VPNs in IBM Cloud that were used in physical hardware or other cloud providers.
NIST supplemental guidance 

Information systems can provide a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from single information system components, but doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per device (e.g., email servers or web servers, but not both). Organizations review functions and services provided by information systems or individual components of information systems, to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing). Organizations consider disabling unused or unnecessary physical and logical ports/protocols (e.g., Universal Serial Bus, File Transfer Protocol, and Hyper Text Transfer Protocol) on information systems to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services.
For VMware vSphere Network NSX (NSX-V), review the following more well-known NSX-T objects with similar function to their NSX-V counterparts. Limitations and differences within a vSphere environment are also be discussed.

The following table shows the typically corresponding functions between NSX-T and NSX-V.



Table 1. NSX-V and NSX-T corresponding functions

 NSX-V or vSphere native NSX-T 

 NSX Transport zone Transport zone (overlay or VLAN-backed) 
 Port groups (VDS) Segments or Logical Switch 
 VXLAN (L2 encapsulation) GENEVE (L2 encapsulation) 
 Edge Gateway Tier-0 (T0) Gateway<br><br>[1] 
 Distributed Logical Router Tier-1 (T1) Gateway<br><br>[2] 
 ESXi Server Transport Node (ESXi, KVM, bare metal T0 Gateway) 



With NSX-T, you have Tier-0 (T0) Gateways and Tier-1 (T1) Gateways. While in the previous section they're shown as being equivalent to an NSX-V edge services gateway (ESG) and a Distributed Logical Router (DLR), that's not entirely accurate.

For NSX-T, two new concepts are introduced: Distributed Router (DR) and Service Router (SR).



Table 2. NSX-T Distributer and Service Routers

 Router Type Capabilities 

 Distributed Router Provides basic packet forwarding and distributed east-west routing functions <br>Spans all transport nodes <br>On ESXi runs as kernel module 
 Service Router Provides gateway services<br><br><br><br> * NAT<br> * Load Balancer<br> * Gateway firewall<br> * North-south routing<br> * VPN<br> * DNS Forwarding<br> * DHCP<br><br><br> 



Some key NSX-T concepts do not correspond to NSX-V functions. You need to review the following concepts so you can understand the NSX-T design implementation.