vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Change log for worker node fix pack 4.3.38_1542_openshift, released 12 October 2020 

The following table shows the changes that are in the worker node fix pack update 4.3.38_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.3.38_1541_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1127.19.1.el7 3.10.0-1160.2.1.el7 Updated worker node image with kernel and package updates for: [CVE-2019-12450](https://nvd.nist.gov/vuln/detail/CVE-2019-12450), [CVE-2019-14822](https://nvd.nist.gov/vuln/detail/CVE-2019-14822), [CVE-2020-12243](https://nvd.nist.gov/vuln/detail/CVE-2020-12243), [CVE-2019-14866](https://nvd.nist.gov/vuln/detail/CVE-2019-14866), [CVE-2017-12652](https://nvd.nist.gov/vuln/detail/CVE-2017-12652), [CVE-2017-18551](https://nvd.nist.gov/vuln/detail/CVE-2017-18551), [CVE-2018-20836](https://nvd.nist.gov/vuln/detail/CVE-2018-20836), [CVE-2019-9454](https://nvd.nist.gov/vuln/detail/CVE-2019-9454), [CVE
Change log for worker node fix pack 4.6.59_1591_openshift, released 18 July 2022 

The following table shows the changes that are in the worker node fix pack 4.6.59_1591_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.6.59_1590_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.66.1 3.10.0-1160.71.1 Worker node package updates for [CVE-2020-26116](https://nvd.nist.gov/vuln/detail/CVE-2020-26116), [CVE-2020-26137](https://nvd.nist.gov/vuln/detail/CVE-2020-26137), [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177), [CVE-2022-0391](https://nvd.nist.gov/vuln/detail/CVE-2022-0391), [CVE-2022-1729](https://nvd.nist.gov/vuln/detail/CVE-2022-1729), [CVE-2022-1966](https://nvd.nist.gov/vuln/detail/CVE-2022-1966). 
 Red Hat OpenShift on IBM Cloud N/A N/A N/A 







 Change log for worker node fix pack 4.6.59_1590_openshift, released 11 July 2022 

The following table shows the changes that are in the worker node fix pack 4.6.59_1590_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.6.59_1589_openshift

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

The following table shows the changes that are in the worker node fix pack 4.12.13_1539_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.10_1536_openshift

 Component Previous Current Description 

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







 Change log for worker node fix pack 4.12.10_1536_openshift, released 11 April 2023 

The following table shows the changes that are in the worker node fix pack 4.12.10_1536_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.8_1535_openshift

 Component Previous Current Description
Kubernetes N/A N/A N/A 







 Change log for worker node fix pack 1.24.14_1571, released 5 June 2023 

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



Changes since version 1.24.14_1570

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-211-generic 4.15.0-212-generic Worker node kernel & package updates for [CVE-2019-17595](https://nvd.nist.gov/vuln/detail/CVE-2019-17595), [CVE-2021-39537](https://nvd.nist.gov/vuln/detail/CVE-2021-39537), [CVE-2022-29458](https://nvd.nist.gov/vuln/detail/CVE-2022-29458), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2023-1380](https://nvd.nist.gov/vuln/detail/CVE-2023-1380), [CVE-2023-25584]
Change log for worker node fix pack 4.8.52_1579_openshift, released 07 November 2022 

The following table shows the changes that are in the worker node fix pack 4.8.52_1579_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.51_1576_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.76.1 3.10.0-1160.80.1 Worker node kernel & package updates for [CVE-2022-21233](https://nvd.nist.gov/vuln/detail/CVE-2022-21233), [CVE-2022-23816](https://nvd.nist.gov/vuln/detail/CVE-2022-23816), [CVE-2022-23825](https://nvd.nist.gov/vuln/detail/CVE-2022-23825), [CVE-2022-2588](https://nvd.nist.gov/vuln/detail/CVE-2022-2588), [CVE-2022-26373](https://nvd.nist.gov/vuln/detail/CVE-2022-26373), [CVE-2022-29900](https://nvd.nist.gov/vuln/detail/CVE-2022-29900), [CVE-2022-29901](https://nvd.nist.gov/vuln/detail/CVE-2022-29901), [CVE-2022-41974](https://nvd.nist.gov/vuln/detail/CVE-2022-41974).
Change log for worker node fix pack 1.21.3_1526, released 02 August 2021 

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



Changes since version 1.21.2_1524

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-147 4.15.0-151 Updated worker node images & Kernel with package updates: [CVE-2020-13529](https://nvd.nist.gov/vuln/detail/CVE-2020-13529), [CVE-2021-22898](https://nvd.nist.gov/vuln/detail/CVE-2021-22898), [CVE-2021-22924](https://nvd.nist.gov/vuln/detail/CVE-2021-22924)[CVE-2021-22925](https://nvd.nist.gov/vuln/detail/CVE-2021-22925), [CVE-2021-33200](https://nvd.nist.gov/vuln/detail/CVE-2021-33200), [CVE-2021-33909](https://nvd.nist.gov/vuln/detail/CVE-2021-33909), and [CVE-2021-33910](https://nvd.nist.gov/vuln/detail/CVE-2021-33910). 
 HA proxy aae810 68e6b3 Updated image with fixes for [CVE-2021-33910](https://nvd.nist.gov/vuln/detail/CVE-2021-33910). 
 Registry endpoints N/A N/A Added zonal public registry endpoints for clusters with both private and public service endpoints enabled. 
 Read only disk self healing N/A N/A For VPC Gen2 workers. Added automation to recover from disks going read only.
Change log for worker node fix pack 4.10.54_1562_openshift, released 27 March 2023 

The following table shows the changes that are in the worker node fix pack 4.10.54_1562_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.10.53_1559_openshift

 Component Previous Current Description 

 RHEL 8 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. 4.10.53 4.10.54 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-54). 
 Haproxy af5031 8398d1 [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916). 
 CRI-O configuration N/A N/A CRI-O configuration now sets container network sysctl tuning for net.ipv4.tcp_keepalive_intvl to 15, net.ipv4.tcp_keepalive_probes to 6 and net.ipv4.tcp_keepalive_time to 40. 







 Change log for worker node fix pack 4.10.53_1559_openshift, released 13 March 2023 

The following table shows the changes that are in the worker node fix pack 4.10.53_1559_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.10.52_1556_openshift

 Component Previous Current Description 

 RHEL 8 Packages N/A N/A Worker node package updates for [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916).
Update type Examples of version labels Updated by Impact 

 Major 1.x.x You Operation changes for clusters, including scripts or deployments. 
 Minor x.22.x You Operation changes for clusters, including scripts or deployments. 
 Patch x.x.4_1510 IBM and you Kubernetes patches, as well as other IBM Cloud Provider component updates such as security and operating system patches. IBM updates masters automatically, but you apply patches to worker nodes. See more about patches in the following section. 



Major and minor updates (1.x)
: First, [update your master node](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster) and then [update the worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node).



* You can't update a Kubernetes master two or more minor versions ahead (n+2). For example, if your current master is version 1.22 and you want to update to 1.24, you must update to 1.23 first.
* Worker nodes can't run a Kubernetes major or minor version that is greater than the masters. Additionally, your worker nodes can be only up to two versions behind the master version (n-2).
* If you use a kubectl CLI version that does not match at least the major.minor version of your clusters, you might experience unexpected results. Make sure to keep your Kubernetes cluster and [CLI versions](https://cloud.ibm.com/docs/containers?topic=containers-cli-install) up-to-date.



Patch updates (x.x.4_1510)
: Changes across patches are documented in the change log of each version. Master patches are applied automatically, but you initiate worker node patches and updates. Worker nodes can also run patch versions that are greater than the masters. As updates become available, you are notified when you view information about the master and worker nodes in the IBM Cloud console or CLI, such as with the following commands: ibmcloud ks cluster ls, cluster get, worker ls, or worker get.
If your cluster runs an unsupported Kubernetes version, follow the [version archive instructions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive). To avoid getting in an unsupported state and operational impact, keep your cluster up-to-date.

Can my worker nodes run a later version than the master?
: Your worker nodes can't run a later major.minor Kubernetes version than the master. Additionally, your worker nodes can be only up to two versions behind the master version (n-2). First, [update your master](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate_master) to the latest Kubernetes version. Then, [update the worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node) in your cluster.

Worker nodes can run later patch versions than the master, such as patch versions that are specific to worker nodes for security updates.

How are patch updates applied?
: By default, patch updates for the master are applied automatically over the course of several days, so a master patch version might show up as available before it is applied to your master. The update automation also skips clusters that are in an unhealthy state or have operations currently in progress. Occasionally, IBM might disable automatic updates for a specific master fix pack, such as a patch that is only needed if a master is updated from one minor version to another. In any of these cases, you can [check the versions change log](https://cloud.ibm.com/docs/containers?topic=containers-changelog) for any potential impact and choose to safely use the ibmcloud ks cluster master update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update) yourself without waiting for the update automation to apply.

Unlike the master, you must update your workers for each patch version.

What happens during the master update?
: Your master is highly available with three replica master pods.
Updating clusters, worker nodes, and cluster components 

You can install updates to keep your Kubernetes clusters up-to-date in IBM Cloud® Kubernetes Service.



 Updating the Kubernetes master 

Periodically, the Kubernetes project releases [major, minor, or patch updates](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types). Updates can affect the Kubernetes API server version or other components in your Kubernetes master. IBM updates the patch version, but you must update the master major and minor versions.



 About updating the master 

How do I know when to update the master?
: You are notified in the IBM Cloud console and CLI when updates are available, and can also check the [supported versions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions) page.

How many versions behind the latest can the master be?
: IBM generally supports three versions of Kubernetes at a time. You can update the Kubernetes API server only to the next version ahead of its current version (n+1). Additionally, your worker nodes can be up to two versions behind the master version (n-2).

For example, if your current Kubernetes API server version is 1.18 (n) and you want to update to 1.20, you must first update to 1.19 (n+1) and then to 1.20 (n+2). Next, you can update the worker nodes up to two version ahead, such as 1.18 to 1.20 (n+2).

If your cluster runs an unsupported Kubernetes version, follow the [version archive instructions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive). To avoid getting in an unsupported state and operational impact, keep your cluster up-to-date.

Can my worker nodes run a later version than the master?
: Your worker nodes can't run a later major.minor Kubernetes version than the master.
Ubuntu 18.04 packages and kernel 4.15.0-64-generic 4.15.0-65-generic Updated worker node images with kernel and package updates for [CVE-2019-5094](https://nvd.nist.gov/vuln/detail/CVE-2019-5094), [CVE-2018-20976](https://nvd.nist.gov/vuln/detail/CVE-2018-20976), [CVE-2019-16056](https://nvd.nist.gov/vuln/detail/CVE-2019-16056), and [CVE-2019-16935](https://nvd.nist.gov/vuln/detail/CVE-2019-16935). 







 Change log for 1.15.4_1518, released 1 October 2019 

The following table shows the changes that are in the patch 1.15.4_1518. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).



Changes since version 1.15.3_1517

 Component Previous Current Description 

 Calico v3.8.1 v3.8.2 See the [Calico release notes)](https://docs.tigera.io/archive/v3.8/release-notes/). 
 Cluster master HA configuration N/A N/A Updated configuration to improve performance of master update operations. 
 Default IBM file storage class N/A N/A Fixed a bug that might cause cluster master operations such as patch updates to clear the default IBM file storage class. 
 Gateway-enabled cluster controller N/A 844 New! For classic clusters with a gateway enabled, a DaemonSet is installed to configure settings for routing network traffic to worker nodes.
Ubuntu 20.04 packages 5.4.0-139-generic 5.4.0-148-generic Worker node kernel & package updates for [CVE-2023-2004](https://nvd.nist.gov/vuln/detail/CVE-2023-2004). 
 Kubernetes 1.25.9 1.25.10 [CVE-2023-2431](https://nvd.nist.gov/vuln/detail/CVE-2023-2431). For more information, see [IBM Cloud Kubernetes Service is affected by a kubelet security vulnerability (CVE-2023-2431)](https://www.ibm.com/support/pages/node/7009655). See [change logs](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.10). 
 Haproxy N\A N\A N\A 







 Change log for worker node fix pack 1.25.9_1544, released 9 May 2023 

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



Changes since version 1.25.9_1543

 Component Previous Current Description
To remove duplicates, see [troubleshooting](https://cloud.ibm.com/docs/containers?topic=containers-cs_duplicate_nodes).









 Applying version updates to worker nodes by replacing hosts 

Hosts that are attached to a location do not update automatically. To apply a version update, you can first attach and assign new hosts to your [Satellite-enabled IBM Cloud service](https://cloud.ibm.com/docs/satellite?topic=satellite-managed-services) and then remove the old hosts. You can also apply [minor and patch version updates in place](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-workershost-update-workers-inplace).



1. List your current hosts and make note of their IDs. These are the hosts to remove after you attach updated hosts.

ibmcloud ks worker ls -c <cluster_name_or_ID>

Review the example output.

ID Primary IP Flavor State Status Zone Version
sat-satliberty-5b4c7f3a7bfc14cf58cbb14ad5c08429475274fe 208.43.36.202 upi normal Ready zone-1 4.7.19_1525_openshift
2. [Attach new hosts to your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts). The number of hosts you attach must match the number of hosts that you want to update.
3. [Assign the newly attached hosts to your Satellite resource](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-assign-manual). These hosts automatically receive the update when you assign them.
4. After the new hosts are successfully assigned to your Satellite resource, [remove and delete the old hosts that you previously noted](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove).







 Updating worker node hosts in the Red Hat OpenShift on IBM Cloud console
Ubuntu 16.04 packages N/A N/A Updated worker node images with package updates for [CVE-2019-3689](https://nvd.nist.gov/vuln/detail/CVE-2019-3689) and [CVE-2020-8177](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8177). 
 Worker node drain automation N/A N/A Fixes a race condition that can cause worker node drain automation to fail. 







 Change log for 1.15.12_1543, released 22 June 2020 

The following table shows the changes that are in the master and worker node update 1.15.12_1543. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).



Changes since version 1.15.12_1541

 Component Location Previous Current Description 

 Calico Master v3.8.6 v3.8.9 See the [Calico release notes](https://docs.tigera.io/archive). The master update resolves CVE-2020-13597 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6226322)). 
 Cluster health image Master v1.1.5 v1.1.8 Additional status information is included when an add-on health state is critical. Improved performance when handling cluster status updates. 
 Cluster master operations Master N/A N/A Cluster master operations such as refresh or update are now canceled if a broken [Kubernetes admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) is detected.
Ubuntu 16.04 packages N/A N/A Updated worker node images with package updates for [CVE-2019-3689](https://nvd.nist.gov/vuln/detail/CVE-2019-3689) and [CVE-2020-8177](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8177). 
 Worker node drain automation N/A N/A Fixes a race condition that can cause worker node drain automation to fail. 







 Change log for 1.18.4_1517, released 22 June 2020 

The following table shows the changes that are in the master and worker node update 1.18.4_1517. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).



Changes since version 1.18.3_1515

 Component Location Previous Current Description 

 Calico Master v3.13.3 v3.13.4 See the [Calico release notes](https://docs.tigera.io/archive). The master update resolves CVE-2020-13597 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6226322)). 
 Cluster health image Master v1.1.5 v1.1.8 Additional status information is included when an add-on health state is critical. Improved performance when handling cluster status updates. 
 Cluster master operations Master N/A N/A Cluster master operations such as refresh or update are now canceled if a broken [Kubernetes admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) is detected.
Ubuntu 16.04 packages N/A N/A Updated worker node images with package updates for [CVE-2019-3689](https://nvd.nist.gov/vuln/detail/CVE-2019-3689) and [CVE-2020-8177](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8177). 
 Worker node drain automation N/A N/A Fixes a race condition that can cause worker node drain automation to fail. 







 Change log for 1.17.7_1529, released 22 June 2020 

The following table shows the changes that are in the master and worker node update 1.17.7_1529. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).



Changes since version 1.17.6_1527

 Component Location Previous Current Description 

 Calico Master v3.12.1 v3.12.2 See the [Calico release notes](https://docs.tigera.io/archive). The master update resolves CVE-2020-13597 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6226322)). 
 Cluster health image Master v1.1.5 v1.1.8 Additional status information is included when an add-on health state is critical. Improved performance when handling cluster status updates. 
 Cluster master operations Master N/A N/A Cluster master operations such as refresh or update are now canceled if a broken [Kubernetes admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) is detected.