vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Red Hat OpenShift 4.9.23 4.9.25 See [change logs](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-25). 







 Change log for worker node pack 4.9.23_1530_openshift, released 14 March 2022 



Changes since version 4.9.22_1529_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A 
 Red Hat OpenShift 4.9.22 4.9.23 See the [change log](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-23). 







 Change log for master fix pack 4.9.21_1528_openshift, released 3 March 2022 



Changes since version 4.9.17_1525_openshift

 Component Previous Current Description 

 Cluster health image v1.3.0 v1.3.3 Updated golang.org/x/crypto to v0.0.0-20220214200702-86341886e292. Adds fix for [CVE-2021-43565](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-43565). Adds Golang dependency updates. 
 Gateway-enabled cluster controller 1586 1653 Updated to use Go version 1.17.7 and updated Go modules to fix CVEs. 
 IBM Calico extension 923 929 Updated universal base image (UBI) to the 8.5-230 version to resolve CVEs. Updated to use Go version 1.16.13. 
 IBM Cloud Block Storage for Classic driver and plug-in v2.1.6 v2.1.7 Fix for [CVE-2021-3538](https://nvd.nist.gov/vuln/detail/CVE-2021-3538).
Red Hat OpenShift Control Plane Operator v4.9.0-20220412 v4.10.0-20220420 See the [Red Hat OpenShift toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.10.0+20220420). 
 Red Hat OpenShift configuration N/A N/A Updated the [feature gate configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsfeature-gates). 
 Red Hat OpenShift Metrics Server v4.9.0-20220412 v4.10.0-20220420 See the [Red Hat OpenShift toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.10.0+20220420). 
 Red Hat OpenShift toolkit 4.9.0+20220412 4.10.0+20220420 See the [Red Hat OpenShift toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.10.0+20220420).
Portieris admission controller v0.13.3 v0.13.4 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.4). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator and Metrics Server 4.12.0-20230314 4.12.0-20230417 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.12.0+20230417). 
 Red Hat OpenShift on IBM Cloud toolkit 4.12.0+20230314 4.12.0+20230417 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.12.0+20230417). 







 Change log for worker node fix pack 4.12.15_1542_openshift, released 24 April 2023 

The following table shows the changes that are in the worker node fix pack 4.12.15_1542_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.12.13_1539_openshift

 Component Previous Current Description 

 RHEL 8 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. 4.12.13 4.12.15 See [change logs](https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.htmlocp-4-12-15). 
 Haproxy N/A N/A N/A 







 Change log for worker node fix pack 4.12.13_1539_openshift, released 24 April 2023
Step 2: Create the Red Hat OpenShift cluster, attach the workers, and fix the DNS 



1. Inside your clone of the repository, copy the file .envrc-template to .envrc.
2. Complete each of the templated environment variables. Follow the instructions that are included within the file.
3. If you are not using direnv, type source .envrc to load .envrc into your terminal's environment.
4. Run make all (or gmake all on MacOS). This command creates the Red Hat OpenShift cluster, attaches the worker node VMs, and configures networking so that the cluster is publicly accessible.
5. Scroll past any messages, even if they are error messages.



The entire process takes approximately one hour. If the process takes significantly longer, or if you see any repeated persistent errors, [submit an issue on this repository](https://github.com/ibm-garage/try-sat-aws).





 Next steps 

For more information about how to access your cluster, see [Accessing OpenShift clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_cluster_sat). The process in this tutorial publicly exposed your cluster, so you do not need to complete the steps in [Accessing clusters through the public cloud service endpoint](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_public_se).

At this point, you can do any of the following actions:



* Log in to the Red Hat OpenShift web console by using the IBM Cloud console. In the console, select OpenShift > Clusters > select your cluster > OpenShift Web Console.
* Connect to Red Hat OpenShift on the command line by:



* [Logging in to IBM Cloud](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login) by using the IBM Cloud CLI.
Red Hat OpenShift 4.7 user provider infrastructure installation 

Red Hat® OpenShift® 4 introduced the following concepts:



* Installer Provisioned Infrastructure (IPI) - For use on supported platforms, only AWS currently. The installer provisions the underlying infrastructure for the cluster and it configures the cluster.
* User Provisioned Infrastructure (UPI) - For use on bare metal, vSphere, and other clouds that do not support IPI. The user is required to provision the infrastructure; compute, network, storage that the Red Hat OpenShift cluster is hosted on. The installer configures only the cluster.



These instructions use the Red Hat OpenShift installer in the UPI mode. Terraform is used to provision the seven VMs for the bootstrap, control-plane, and compute nodes. The following process is completed:



1. A yaml file is created that is processed by the Red Hat OpenShift installer.
2. The installer is run and creates a number of files, including the Ignition files. The Ignition files are used to configure the bootstrap, control-plane, and compute nodes at the first start.
3. The Ignition file for the bootstrap node is copied to the NGINX default directory on the bastion node so that the bootstrap node can fetch it on the first start.
4. The Ignition Terraform file is updated with the DNS server.
5. The terraform.tfvars file is created to hold the variables for the Terraform installation.
6. Terraform is run, which provisions the VMs. The VMs are started, configured, and the Red Hat OpenShift cluster is created.



For more information about installing the Red Hat OpenShift user provider infrastructure, see [Installing a cluster on vSphere with user-provisioned infrastructure](https://docs.openshift.com/container-platform/4.7/installing/installing_vsphere/installing-vsphere.html).



 Creating the Red Hat OpenShift Installer yaml file 

Use the following table to document the parameters you need for your deployment.
For more information, see [Getting support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
* End your IBM Cloud subscription: After you end your IBM Cloud subscription, Red Hat OpenShift on IBM Cloud removes the customer root key in IBM Key Protect that IBM created and managed for you as well as all the personal and sensitive information from the etcd data store and Object Storage backup.







 Does Red Hat collect information about my cluster? 

Yes. To improve the OpenShift Container Platform service, a telemetry component is installed in your cluster by default that collects anonymized health reports about your cluster. For more information, see the [Red Hat OpenShift documentation](https://docs.openshift.com/container-platform/4.11/support/remote_health_monitoring/about-remote-health-monitoring.html).

To remove the telemetry component, see [Disabling remote health reporting](https://cloud.ibm.com/docs/openshift?topic=openshift-health-monitoroc_disable_telemetry_reports).
Load balancer and load balancer monitor for IBM Cloud Provider 2420 2486 Updated Go to version 1.19.7 and updated dependencies. 
 Red Hat OpenShift on IBM Cloud. 4.11.31 4.11.35 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-35). 
 Red Hat OpenShift on IBM Cloud configuration N/A N/A Set proper topology spread constraints for the default Red Hat OpenShift on IBM Cloud image registry configuration used by classic clusters. 
 OpenVPN Operator image v1.4.22 v1.4.23 Updated base image to resolve CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361). 
 Portieris admission controller v0.13.3 v0.13.4 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.4).
Operator or site reliability engineer [Administrator platform access role for a cluster, region, or resource group](https://cloud.ibm.com/docs/openshift?topic=openshift-iam-platform-access-roles), [Reader service access role for a cluster or region](https://cloud.ibm.com/docs/openshift?topic=openshift-iam-service-access-roles) or [Manager service access role for all cluster namespaces](https://cloud.ibm.com/docs/openshift?topic=openshift-iam-service-access-roles) to be able to use kubectl top nodes,pods commands. 



* Where can I find a list of security bulletins that affect my cluster?

If vulnerabilities are found in Red Hat OpenShift, Red Hat OpenShift releases CVEs in security bulletins to inform users and to describe the actions that users must take to remediate the vulnerability. Red Hat OpenShift security bulletins that affect Red Hat OpenShift on IBM Cloud users or the IBM Cloud platform are published in the [IBM Cloud security bulletin](https://cloud.ibm.com/status?component=containers-kubernetes&selected=security).

Some CVEs require the latest patch update for a version that you can install as part of the regular [cluster update process](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) in Red Hat OpenShift on IBM Cloud. Make sure to apply security patches in time to protect your cluster from malicious attacks. For more information about what is included in a security patch, refer to the [version change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions_available).
* Does the service offer support for bare metal and GPU?

Certain VPC worker node flavors offer GPU support. For more information, see the [VPC flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavors).

Yes, you can provision your worker node as a single-tenant physical bare metal server.
OpenShift Data Foundation add-on change log 

View information for updates to the OpenShift Data Foundation add-on in your Red Hat® OpenShift® on IBM Cloud® clusters.

Note that the add-on supportsn+1 cluster versions.

To view a list of add-ons and the supported Red Hat OpenShift versions, see the [supported add-on versions table](https://cloud.ibm.com/docs/openshift?topic=openshift-supported-cluster-addon-versions) or run the following command.

ibmcloud oc cluster addon versions --addon openshift-data-foundation



 Version 4.13 



 Version 4.13.0, release 10 July 2023 



* Initial 4.13 release.
* Adds support for encryption in transit by specificying the encryptionInTransit parameter when installing the add-on.









 Version 4.12 



 Version 4.12.6, release 28 June 2023 



* Golang updated to 1.20.5.







 Version 4.12.5, release 09 June 2023 



* Golang updated to 1.19.9.
* Updates the UBI image to 8.8-860.







 Version 4.12.4, release 05 May 2023 



* LSO channel updated.
* Golang updated to 1.19.8.
* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-24536](https://nvd.nist.gov/vuln/detail/CVE-2023-24536), [CVE-2023-24537](https://nvd.nist.gov/vuln/detail/CVE-2023-24537), [CVE-2023-24538](https://nvd.nist.gov/vuln/detail/CVE-2023-24538).







 Version 4.12.0, released 16 March 2023 

Initial release.







 Version 4.11
Deploy microservices with Red Hat OpenShift on IBM Cloud 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

This tutorial demonstrates how to deploy applications to [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/kubernetes/catalog/about?platformType=openshift). Red Hat OpenShift on IBM Cloud provides a great experience for developers to deploy software applications and for System Administrators to scale and observe the applications in production.



 Objectives 



* Deploy a Red Hat OpenShift on IBM Cloud cluster
* Deploy a microservice
* Scale the microservice
* Use an operator to deploy IBM Cloudant and bind to a microservice
* Observe the cluster using Log Analysis
* Observe the cluster using IBM Cloud Monitoring



Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution55-openshift-microservices/Architecture.svg)

Figure 1. Architecture diagram of the tutorial



1. A developer initializes a Red Hat OpenShift application with a repository URL resulting in a Builder, DeploymentConfig, and Service.
2. The Builder clones the source, creates an image, pushes it to Red Hat OpenShift registry for DeploymentConfig provisioning.
3. Users access the frontend application.
4. The IBM Cloudant database instance is provisioned through an IBM Cloud Operator Service.
5. The backend application is connected to the database with an IBM Cloud Operator Binding.
6. Log Analysis is provisioned and agent deployed.
7. Monitoring is provisioned and agent deployed.
8. An Administrator monitors the app with Log Analysis and Monitoring.
Red Hat OpenShift 3.11.154 3.11.161 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.htmlocp-3-11-161). 
 Red Hat OpenShift router configuration N/A N/A Improved general availability of the Red Hat OpenShift router and enhanced the configuration for multizone clusters. Now, the router runs 3 pods with a scheduling configuration that prefers running pods across worker nodes and zones. 
 OpenVPN server 2.4.6-r3-IKS-121 2.4.6-r3-IKS-131 Updated image for [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). 







 Change log for worker node fix pack 3.11.157_1537_openshift, released 23 December 2019 

The following table shows the changes that are in the worker node fix pack 3.11.157_1537_openshift.



Changes since version 3.11.154_1534

 Component Previous Current Description 

 RHEL 7 packages N/A N/A Updated worker node images with package updates for [CVE-2019-11729](https://nvd.nist.gov/vuln/detail/CVE-2019-11729) and [CVE-2019-11745](https://nvd.nist.gov/vuln/detail/CVE-2019-11745). 
 Red Hat OpenShift node 3.11.154 3.11.157 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.htmlocp-3-11-157).
5.3.2 Red Hat OpenShift on IBM Cloud has a set of [default Calico network policies defined](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesdefault_policy) and [additional network policies can optionally be added](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesadding_network_policies). 
 5.4.1 Red Hat OpenShift on IBM Cloud deploys some system components that could prefer using secrets as files over secrets as environment variables. 
 5.4.2 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). 
 5.5.1 Red Hat OpenShift on IBM Cloud can optionally [enable image security enforcement](https://cloud.ibm.com/docs/openshift?topic=openshift-imagesportieris-image-sec). 
 5.6.2 Red Hat OpenShift on IBM Cloud does not annotate all pods with [seccomp profiles](https://kubernetes.io/docs/concepts/security/pod-security-policy/). 
 5.6.3 Red Hat OpenShift on IBM Cloud deploys some system components that do not set a [pod or container securityContext](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/).
Red Hat OpenShift on IBM Cloud. 4.9.48 4.9.49 For more information, see the [change log](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-49). 







 Change log for master fix pack 4.9.48_1556_openshift, released 26 September 2022 

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



Changes since version 4.9.461554openshift

 Component Previous Current Description 

 Cluster health image v1.3.10 v1.3.11 Updated Go dependencies and to Go version 1.18.6. 
 IBM Calico extension 1006 1096 Updated image for [CVE-2022-2526](https://nvd.nist.gov/vuln/detail/CVE-2022-2526). 
 IBM Cloud Block Storage driver and plug-in v2.2.9 v2.3.1 Updated to Go version 1.18.6. Updated universal base image (UBI) to version 8.6-941 to resolve CVEs. 
 IBM Cloud Controller Manager v1.22.13-1 v1.22.14-2 Updated to support the Kubernetes 1.22.14 release. 
 IBM Cloud File Storage for Classic plug-in and monitor 414 416 Updated to Go version 1.18.6. Updated universal base image (UBI) to version 8.6-941 to resolve CVEs. 
 Key Management Service Provider v2.5.8 v2.5.9 Updated Go dependencies and to Go version 1.18.6. 
 Red Hat OpenShift on IBM Cloud 4.9.46 4.9.48 See the [Red Hat OpenShift on IBM Cloud Release Notes](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-48).
5.2.5 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.6 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.7 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.8 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.9 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.3.2 Red Hat OpenShift on IBM Cloud has a set of [default Calico network policies defined](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesdefault_policy) and [additional network policies can optionally be added](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiesadding_network_policies). 
 5.4.1 Red Hat OpenShift on IBM Cloud deploys some system components that could prefer using secrets as files over secrets as environment variables. 
 5.4.2 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).
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.

Red Hat OpenShift on IBM Cloud provides scalable compute resources and the associated DevOps dashboards to create, scale, and tear down apps and services as needed. Using industry-standard containers technology apps can be quickly developed and shared across multiple Development, Test, and Production environments. This setup provides the immediate benefit of scalability. Using Kubernetes rich set of deployment and runtime objects, the HR team can monitor and manage upgrades to apps reliably. They can also replicate and scale the apps, by using defined rules and the automated Kubernetes orchestrator.



 Step 1: Containers, microservices, and the Garage Method 



* Apps are built in a set of cooperative microservices that run in Red Hat OpenShift on IBM Cloud. The architecture represents the functional areas of the app with the most quality problems.
* Deploy apps to container in Red Hat OpenShift on IBM Cloud, continuously scanned with IBM Vulnerability Advisor.
* Provide standardized DevOps dashboards through Kubernetes.
* Adopt the essential agile and iterative development practices within the IBM Garage Method to enable frequent releases of new functions, patches, and fixes without downtime.







 Step 2: Connections to existing benefits back-end 



* IBM® Secure Gateway for IBM Cloud® is used to create a secure tunnel to on-premises systems that host the benefits systems.
* Combination of on-premises data and Red Hat OpenShift on IBM Cloud lets them access sensitive data while they adhere to regulations.
* Chatbot conversations fed back into HR policies, allowing the benefits site to reflect which benefits were most and least popular, including targeted improvements to poorly performing initiatives.







 Step 3: Chatbot and personalization
RHEL 7 Packages N/A N/A N/A 
 RHEL 8 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud N/A N/A N/A 







 Change log for master fix pack 4.7.59_1582_openshift, released 26 September 2022 

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



Changes since version 4.7.561580openshift

 Component Previous Current Description 

 Cluster health image v1.3.10 v1.3.11 Updated Go dependencies and to Go version 1.18.6. 
 IBM Calico extension 1006 1096 Updated image for [CVE-2022-2526](https://nvd.nist.gov/vuln/detail/CVE-2022-2526). 
 IBM Cloud Block Storage driver and plug-in v2.2.9 v2.3.1 Updated to Go version 1.18.6. Updated universal base image (UBI) to version 8.6-941 to resolve CVEs. 
 IBM Cloud File Storage for Classic plug-in and monitor 414 416 Updated to Go version 1.18.6. Updated universal base image (UBI) to version 8.6-941 to resolve CVEs. 
 Key Management Service Provider v2.5.8 v2.5.9 Updated Go dependencies and to Go version 1.18.6. 
 Red Hat OpenShift on IBM Cloud 4.7.56 4.7.59 See the [Red Hat OpenShift on IBM Cloud Release Notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-59). 
 OpenVPN Operator image v1.4.8 v1.4.9 Updated ansible operator base image to v1.23.0 to resolve CVEs.
Load balancer and load balancer monitor for IBM Cloud Provider 2057 2109 Updated Go dependencies and to Go version 1.17.13. 
 Red Hat OpenShift on IBM Cloud. 4.6.59 4.6.60 See the [Red Hat OpenShift on IBM Cloud Release Notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-60). 
 OpenVPN client 2.5.6-r1-IKS-629 2.5.6-r1-IKS-648 Update image for [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097) and [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434). 
 OpenVPN Operator image v1.4.7 v1.4.8 Updated Ansible operator base image to version v1.22.2 to resolve CVEs. 
 OpenVPN server 2.5.6-r1-IKS-628 2.5.6-r1-IKS-647 Update image for [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097) and [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434). 
 Portieris admission controller v0.12.5 v0.12.6 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.12.6).