vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Red Hat OpenShift on IBM Cloud. 4.11.32 4.11.34 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-34). 
 Haproxy 8398d1 8895ad [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361). 







 Change log for master fix pack 4.11.31_1548_openshift, released 28 March 2023 

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



Changes since version 4.11.27_1546_openshift

 Component Previous Current Description 

 Calico v3.23.5 v3.25.0 See the [Calico release notes](https://docs.tigera.io/calico/latest/release-notes/v3.25.0). 
 Calico Operator v1.27.17 v1.29.0 See the [Calico Operator release notes](https://github.com/tigera/operator/releases/tag/v1.29.0). 
 Cluster health image v1.3.16 v1.3.17 Updated Go to version 1.19.7 and updated dependencies. 
 IBM Calico extension 1308-amd64 1366-amd64 Updated to resolve [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916). 
 IBM Cloud Block Storage driver and plug-in v2.3.7 v2.4.0 Removed ExpandInUsePersistentVolumes feature gate. 
 IBM Cloud Controller Manager v1.24.10-10 v1.24.12-1 Updated to support the Kubernetes 1.24.12 release.
Red Hat OpenShift on IBM Cloud. 4.10.33 4.10.35 For more information, see the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-35). 







 Change log for master fix pack 4.10.32_1536_openshift, released 26 September 2022 

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



Changes since version 4.10.261534openshift

 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.23.9-3 v1.23.11-1 Updated Go dependencies and to use Go version 1.17.13. Updated to support the Kubernetes 1.23.11 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 organizes your resources into projects, which are Kubernetes namespaces with annotations, and includes many more components than community Kubernetes clusters to run Red Hat OpenShift features such as the catalog. Select components of projects are described in the following rows. For more information, see [Working with projects](http://docs.openshift.com/container-platform/4.11/applications/projects/working-with-projects.html).

calico-system, tigera-operator
: Calico manages network policies for your cluster, and includes a few components to manage container network connectivity, IP address assignment, and network traffic control. The Tigera operator installs and manages the lifecycle of Calico components.

default
: This project is used if you don't specify a project or create a project for your Kubernetes resources.

ibm-system
: This project includes the ibm-cloud-provider-ip deployment that works with keepalived to provide health checking and Layer 4 load balancing for requests to app pods.

kube-system
: This project includes many components that are used to run Kubernetes on the worker node.



* ibm-master-proxy: The ibm-master-proxy is a daemon set that forwards requests from the worker node to the IP addresses of the highly available master replicas. In single zone clusters, the master has three replicas on separate hosts. For clusters that are in a multizone-capable zone, the master has three replicas that are spread across zones. A highly available load balancer forwards requests to the master domain name to the master replicas.
* kubelet: The kubelet is a worker node agent that runs on every worker node and is responsible for monitoring the health of pods that run on the worker node and for watching the events that the API server sends. Based on the events, the kubelet creates or removes pods, ensures liveness and readiness probes, and reports back the status of the pods to the API server.
* vpn: The Konnectivity agent works with the Konnectivity server to securely connect the master to the worker node.
The Red Hat OpenShift master is accessible through the private cloud service endpoint if authorized cluster users are in your IBM Cloud private network or are connected to the private network, such as through a [VPC VPN connection](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example). However, communication with the Kubernetes master over the private cloud service endpoint must go through the 166.X.X.X IP address range, which you must configure in your VPN gateway and connection setup.



1. Set up your IBM Cloud VPC VPN and connect to your private network through the VPN.



1. [Configure a VPN gateway on your local machine](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example). For example, you might choose to set up StrongSwan on your machine.
2. [Create a VPN gateway in your VPC, and create the connection between the VPC VPN gateway and your local VPN gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-create-gatewayvpn-create-ui). In the New VPN connection for VPC section, add the 166.8.0.0/14 subnet to the Local subnets field. If you have a multizone cluster, repeat this step to configure a VPC gateway on a subnet in each zone where you have worker nodes.
3. Verify that you are connected to the private network through your IBM Cloud VPC VPN connection.



2. To log in to your cluster, choose from the following options.



* Log in as admin:



1. Make sure that you have the [Administrator platform access role for the cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-usersadd_users).
2. Set your command line context for the cluster and download the TLS certificates and permission files for the administrator.
The Red Hat OpenShift on IBM Cloud registries include Certified Operators, Marketplace Operators, and community Operators. This capability is supported by the beta release of IBM Cloud Partner Center and our general availability release of private catalog capabilities. For more information, see [Onboarding a Certified Operator bundle from a Red Hat registry](https://cloud.ibm.com/docs/third-party?topic=third-party-bundle-register).







 June 2021 



 01 June 2021 

New invitation flow for existing IBM Cloud users
: To enhance security and user protection, IBM Cloud® now requires all users to accept an invitation in order to become an active user within a new account. The new invitation flow has an impact only on inviting existing IBM Cloud® users. Previously, existing users were being automatically onboarded to each new account as they were invited. After this change, these users need to accept an invitation in their notifications, by email, or by using the CLI to onboard to a new account.
: To accept invitations in the CLI, existing members of IBM Cloud® must use the [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliaccept-invitation-to-join-a-new-account-) command. They need to target the account that they are invited to join and use the new --accept flag.

As an account administrator, you might want to remind your users to accept these invitations.







 May 2021 



 07 May 2021 

Support for third-party virtual server images with Terraform
: Third-party providers can now offer virtual server images deployed by using Terraform in IBM Cloud. This capability is supported by the beta release of IBM Cloud Partner Center and our previously general availability release of private catalog capabilities. For more information, see [Onboarding a virtual server image with Terraform](https://cloud.ibm.com/docs/third-party?topic=third-party-vsimage-register).







 April 2021 



 21 April 2021 

Delivering notifications by using webhooks
: You can now easily add webhooks to the notification distribution list in addition to adding email addresses.
Red Hat OpenShift on IBM Cloud. N/A N/A N/A 







 Change log for master fix pack 4.8.52_1580_openshift, released 16 November 2022 

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



Changes since version 4.8.51_1578_openshift

 Component Previous Current Description 

 Calico v3.21.6 v3.22.5 See the [Calico release notes](https://docs.tigera.io/archive/v3.22/release-notes/v3225). 
 Calico Operator v1.23.8 v1.25.13 See the [Calico Operator release notes](https://github.com/tigera/operator/releases/tag/v1.25.13). 
 Cluster health image v1.3.12 v1.3.13 Updated Go dependencies, golangci-lint, gosec, and to Go version 1.19.3. Updated base image version to 116. 
 etcd v3.4.18 v3.4.21 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.21). 
 Gateway-enabled cluster controller 1823 1902 Go module updates.
Use the Red Hat® OpenShift® on IBM Cloud® observability plug-in to create a monitoring configuration for IBM Cloud Monitoring in your cluster, and use this monitoring configuration to automatically collect and forward metrics to IBM Cloud Monitoring.

You can set up a monitoring configuration for your cluster from the console or CLI.



* [Forward cluster and app metrics to an IBM Cloud Monitoring instance](https://cloud.ibm.com/docs/openshift?topic=openshift-health-monitoropenshift_monitoring)







 Forward Kubernetes API audit logs to Log Analysis 

To forward audit logs to IBM Cloud Log Analysis, you can [create a Kubernetes audit system by using the provided image and deployment](https://cloud.ibm.com/docs/openshift?topic=openshift-health-auditaudit-api-server-la).





 Next Steps 

The next step on the deployment journey is:



* [Configure DNS](https://cloud.ibm.com/docs/cloud-native-journey?topic=cloud-native-journey-configure-dns)
protocol: TCP
type: LoadBalancer



For more information, see the [MetalLB documentation](https://docs.openshift.com/container-platform/4.9/networking/metallb/about-metallb.html).





 Exposing apps with Red Hat OpenShift routes 

Quickly expose the services in your cluster on the Red Hat OpenShift Ingress controller's external IP address by using a route.

An [Red Hat OpenShift route](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routes) exposes a service as a hostname in the format <service_name>-<project>.<cluster_name>-<random_hash>-0000.upi.containers.appdomain.cloud. A Ingress controller is deployed by default to your cluster, which enables routes to be used by external clients. The Ingress controller uses the service selector to find the service and the endpoints that back the service. You can configure the service selector to direct traffic through one route to multiple services. You can also create either unsecured or secured routes by using the TLS certificate that is assigned by the Ingress controller for your hostname. Note that the Ingress controller supports only the HTTP and HTTPS protocols.

Before you begin with routes, review the following considerations.

Host network connectivity
: If the hosts for your cluster have public network connectivity, your cluster is created with a public Ingress controller by default. You can use this Ingress controller to create public routes for your app. If the hosts for your cluster have private network connectivity only, your cluster is created with a private Ingress controller by default. You can use this Ingress controller to create private routes for your app that are accessible only from within your hosts' private network. To set up public routes in clusters that have private network connectivity only, first [set up your own third-party load balancer](https://cloud.ibm.com/docs/openshift?topic=openshift-sat-expose-appssat-expose-byolb) that has public network connectivity in front of your private Ingress controller before completing the following steps.

Health checks
[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. List your namespaces to determine whether you have an openshift-storage namespace. If you don't have an openshift-storage namespace, create it.

oc get namespaces | grep openshift-storage



1. Create an openshift-storage namespace in your cluster. The driver pods are deployed to this namespace. Copy the following YAML and save it as os-namespace.yaml on your local machine.

apiVersion: v1
kind: Namespace
metadata:
labels:
openshift.io/cluster-monitoring: "true"
name: openshift-storage
2. Create the openshift-storage namespace by using the YAML file that you saved.

oc create -f os-namespace.yaml
3. Verify that the namespace is created.

oc get namespaces | grep storage



2. Encode both the ID of your root key and the API key of the service ID that you created to base64.

printf "ROOT-KEY-ID" | base64

printf "SERVICE-ID-API-KEY" | base64
3. Create the Kubernetes secret in the openshift-storage namespace that uses your Hyper Protect Crypto Services credentials.



1. Save the following secret as a YAML file called ibm-hpcs-secret.yaml.

apiVersion: v1
data:
  IBM_KP_CUSTOMER_ROOT_KEY: AaAAAaZAAAAy11AAAyAAkaAaQtAAk0AAA2AzY5AjYaaa67aa your base64 encoded root key ID
  IBM_KP_SERVICE_API_KEY: AAAaaajAAAAAncmAAaaaaAAAAdAAId1AtVjBJRU1aAAaAeTh1aEw=AaaaA your base64 encoded API
kind: Secret
metadata:
  name: ibm-hpcs-secret
Red Hat OpenShift 4.8.29 4.8.32 For more information, see the [change logs](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-32) 
 HA proxy f6a2b3 15198fb Contains fixes for [CVE-2022-24407](https://nvd.nist.gov/vuln/detail/CVE-2022-24407). 







 Change log for worker node fix pack 4.8.29_1544_openshift, released 14 February 2022 



Changes since version 4.8.28_1543_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A 
 Red Hat OpenShift 4.8.28 4.8.29 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-29). 
 HA proxy d38fa1 f6a2b3 [CVE-2021-3521](https://nvd.nist.gov/vuln/detail/CVE-2021-3521)[CVE-2021-4122](https://nvd.nist.gov/vuln/detail/CVE-2021-4122). 







 Change log for worker node fix pack 4.8.28_1543_openshift, released 31 January 2022 

The following table shows the changes that are in the worker node fix pack 4.8.28_1543_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.26_1541_openshift

 Component Previous Current Description
Red Hat OpenShift on IBM Cloud. N/A N/A N/A 







 Change log for master fix pack 4.9.51_1565_openshift, released 16 November 2022 

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



Changes since version 4.9.49_1561_openshift

 Component Previous Current Description 

 Calico v3.22.4 v3.22.5 See the [Calico release notes](https://docs.tigera.io/archive/v3.22/release-notes/v3225). 
 Calico Operator v1.25.11 v1.25.13 See the [Calico Operator release notes](https://github.com/tigera/operator/releases/tag/v1.25.13). 
 Cluster health image v1.3.12 v1.3.13 Updated Go dependencies, golangci-lint, gosec, and to Go version 1.19.3. Updated base image version to 116. 
 etcd v3.4.18 v3.4.21 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.21). 
 Gateway-enabled cluster controller 1823 1902 Go module updates.
Data <br><br> * Maintain [platform-level standards](https://cloud.ibm.com/docs/overview?topic=overview-security) so that your data can be stored with controls commensurate to leading international security compliance standards.<br> * Provision clusters with Red Hat OpenShift components installed so that you can access the Red Hat OpenShift API to help manage your app data, such as with secrets and configmaps.<br> * Integrate with IBM Cloud services that you can use to store and manage your data, such as IBM Cloud Databases or Object Storage.<br> * Integrate with IBM Watson services that you can use to maximize the insights and use of your data with the latest artificial intelligence technology.<br><br><br> <br><br> * Maintain responsibility for your data and how your apps consume the data.<br><br><br>
Red Hat OpenShift on IBM Cloud does not support the [Portworx experimental InitializerConfiguration admission controller](https://docs.portworx.com/portworx-install-with-kubernetes/storage-operations/hyperconvergence/initializer-experimental-feature-in-stork-v1-1). 
 Private clusters To install Portworx in a cluster that doesn't have VRF or access to private cloud service endpoints (CSEs), you must create a rule in the default security group to allow inbound and outbound traffic for the following IP addresses: 166.9.24.81, 166.9.22.100, and 166.9.20.178. For more information, see [Updating the default security group](https://cloud.ibm.com/docs/vpc?topic=vpc-updating-the-default-security-groupupdating-the-default-security-group). 







 Overview of the Portworx lifecycle 



1. Create a [multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clusters).



1. Infrastructure provider: For Satellite clusters, make sure to add block storage volumes to your hosts before attaching them to your location. If you use classic infrastructure, you must choose a bare metal flavor for the worker nodes. For classic clusters, virtual machines have only 1000 Mbps of networking speed, which is not sufficient to run production workloads with Portworx. Instead, provision Portworx on bare metal machines for the best performance.
2. Worker node flavor: Choose an SDS or bare metal flavor. If you want to use virtual machines, use a worker node with 16 vCPU and 64 GB memory or more, such as b3c.16x64. Virtual machines with a flavor of b3c.4x16 or u3c.2x4 don't provide the required resources for Portworx to work properly.
3. Minimum number of workers: Two worker nodes per zone across three zones, for a minimum total of six worker nodes.



2.
: Red Hat OpenShift [3.11.154_1536_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311154_1536).

Assigning access
: Updated the steps to [assign access to your clusters through the IBM Cloud IAM console](https://cloud.ibm.com/docs/openshift?topic=openshift-usersadd_users).





 11 December 2019 

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

CLI installation
: Updated the link to download the [oc CLI client](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-install).

Configuring VPC subnets
: [Added information](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-subnets) about configuring VPC subnets, public gateways, and network segmentation for your VPC clusters.





 9 December 2019 

Version change log
: Worker node patch updates are available.
: Red Hat OpenShift [3.11.154_1534_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311154_1534_worker).





 4 December 2019 

Exposing apps with load balancers or Ingress ALBs
: Added quick start pages to help you get up and running with [load balancers](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-qs) and [Ingress ALBs](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about).
Red Hat OpenShift 3.11.346 3.11.380 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-380). 







 Change log for worker node fix pack 3.11.380_1580_openshift, released 15 February 2021 

The following table shows the changes that are in the worker node fix pack 3.11.380_1580_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 3.11.374_1579_openshift

 Component Previous Current Description 

 Red Hat OpenShift 3.11.374 3.11.380 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-380).
Archived version change logs 

The following versions are no longer supported for Red Hat® OpenShift® on IBM Cloud®. You can review the archive of the change logs.

Unsupported versions: [Archived version history](https://cloud.ibm.com/docs/openshift?topic=openshift-sitemapsitemap_archived_version_history)

Looking for the change logs of supported versions? See [Red Hat OpenShift version change log](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).



 Version 4.5 change log (Unsupported as of 10 October 2021) 

Version 4.5 is unsupported. You can review the following archive of the 4.5 change logs.



 Change log for worker node fix pack 4.5.41_1553_openshift, released 27 September 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.5.41_1553_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.5.41_1551_openshift

 Component Previous Current Description 

 Disk identification N/A N/A Enhanced the disk identification logic to handle the case of 2+ partitions.
Red Hat OpenShift 4.7.40 4.7.41 See the Red Hat OpenShift [change logs](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-41). 







 Change log for master fix pack 4.7.40_1547_openshift, released 26 January 2022 

The following table shows the changes that are in the master fix pack patch update 4.7.40_1547_openshift. Master patch updates are applied automatically.



Changes since version 4.7.37_1546_openshift

 Component Previous Current Description 

 Calico N/A N/A Changed to improve Calico availability during updates. 
 Cluster health image v1.2.20 v1.2.21 Updated to use Go version 1.17.5, updated Go dependencies and golangci-lint. 
 IBM Calico extension 900 923 Updated universal base image (UBI) to the 8.5-218 version to resolve CVEs. Updated to use Go version 1.16.13. 
 IBM Cloud Block Storage for Classic driver and plug-in v2.1.3 v2.1.6 Updated to use Go version 1.16.13. 
 IBM Cloud Controller Manager v1.20.13-4 v1.20.15-1 Updated to support the Kubernetes 1.20.15 release. 
 IBM Cloud File Storage for Classic plug-in and monitor 402 404 Updated universal base image (UBI) to the 8.5-218 version to resolve CVEs. Updated to use Go version 1.16.13. 
 IBM Cloud RBAC Operator 3430e03 0fc9949 Updated universal base image (UBI) to the 8.5-218 version to resolve CVEs. Updated to use Go version 1.16.13. 
 Key Management Service provider v2.3.12 v2.3.13 Updated Go dependencies and golangci-lint. 
 Load balancer and load balancer monitor for IBM Cloud Provider 1659 1747 Updated the Alpine base image to the 3.15 version to resolve CVEs.