vania-janet/multiturn-rag-retrieval-data huggingface dataset:
These worker node fix packs can be at a higher version than the master because some build fix packs are specific to worker nodes. Other change logs are for master fix packs, and apply only to the cluster master. Master fix packs might not be automatically applied. You can choose to [apply them manually](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update). For more information about patch types, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).





 Version 1.20 change log 

Kubernetes version 1.20 is unsupported as of 19 June 2022. Update your cluster to at least [version 1.21](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_121) as soon as possible.



 Change log for worker node fix pack 1.20.15_1583, released 7 June 2022 

The following table shows the changes that are in the worker node fix pack 1.20.15_1583. 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.20.15_1581

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-177 4.15.0-180 Worker node kernel & package updates for [CVE-2019-13050](https://nvd.nist.gov/vuln/detail/CVE-2019-13050), [CVE-2022-1664](https://nvd.nist.gov/vuln/detail/CVE-2022-1664), [CVE-2022-29581](https://nvd.nist.gov/vuln/detail/CVE-2022-29581). 







 Change log for master fix pack 1.20.15_1582, released 3 June 2022 

The following table shows the changes that are in the master fix pack 1.20.15_1582.
You can use IBM-provided labels or custom labels that you added to the worker node.



 Checking if a version update is available for worker node hosts 

You can check if a version update is available for a host that is assigned as a worker node to a [Satellite-enabled IBM Cloud service](https://cloud.ibm.com/docs/satellite?topic=satellite-managed-services) by using the IBM Cloud CLI or the IBM Cloud console.

To review the changes that are included in each version update, see the [Version change log for Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).



 Checking if a version update is available with the IBM Cloud CLI 



1. Log in to IBM Cloud. Include the --sso option if you have a federated account.

ibmcloud login [--sso]
2. List the Satellite clusters in your account.

ibmcloud ks cluster ls --provider satellite
3. List the worker nodes in the cluster that you want to update the version for. In the output, check for an asterisk * with a message that indicates a version update is available.

ibmcloud ks worker ls -c <cluster_name_or_ID>

Example output

ID Primary IP Flavor State Status Zone Version
sat-worker-<ID> <IP_address> upi normal Ready zone-1 4.5.35_1534_openshift

* To update to 4.5.37_1537_openshift version, run 'ibmcloud ks worker replace'. Review and make any required version changes before you update: 'https://ibm.biz/upworker'







 Checking if a version update is available from the IBM Cloud console 



1. Log in to the [Satellite console](https://cloud.ibm.com/satellite/locations).
2. Click the location with the hosts that you want to update.
3. Click the Hosts tab.
4.
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.16.11_1536, released 22 June 2020 

The following table shows the changes that are in the master and worker node update 1.16.11_1536. 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.16.10_1534

 Component Location Previous Current Description 

 Calico Master v3.9.5 v3.9.6 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.
Review and make any required version changes before you update: 'https://ibm.biz/upworker'







 Checking if a version update is available from the IBM Cloud console 



1. Log in to the [Satellite console](https://cloud.ibm.com/satellite/locations).
2. Click the location with the hosts that you want to update.
3. Click the Hosts tab.
4. From the host list, click the link to the Cluster for the host that you want to update. A new tab opens for the Red Hat OpenShift on IBM Cloud cluster details.
5. Click the Worker nodes tab.
6. In the Version column, check for an information icon that says Update available when you click on the icon. If no update is available, no icon is present.
7. [Determine if the version update is a major, minor, or patch update](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-workershost-update-workers-type).









 Identifying worker node hosts 

Determine whether your hosts are part of the control plane, assigned to a managed service, or attached to the location.



1. List your location hosts and make note of their IDs. The worker node hosts do not have infrastructure listed in the Cluster column of the output.

ibmcloud sat host ls --location <location>

Review the example output.

Name ID State Status Zone Cluster Worker ID Worker IP

satdemo-cp1 0bc3b92f55968a230985 assigned Ready zone-1 infrastructure sat-satdemocp1-2bda578e901b4047c6e48d766cd99bc11a45fddd 169.62.42.178
satdemo-cp2 999cd38c39ddffe4b672 assigned Ready zone-2 infrastructure sat-satdemocp2-940134e69c2609c5421b2426a7640fa80569668d 169.62.42.183
Version 1.17 change log (unsupported as of 2 July 2021) 

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



 Change log for worker node fix pack 1.17.17_1568, released 19 July 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1568. 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.17.17_1567

 Component Previous Current Description 

 Ubuntu 16.04 packages N/A N/A Updated worker node images with kernel package updates. 
 Ubuntu 18.04 packages N/A N/A Updated worker node images with kernel package updates. 







 Change log for worker node fix pack 1.17.17_1567, released 6 July 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1567. 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.17.17_1566

 Component Previous Current Description
Then, [update the worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-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/openshift?topic=openshift-openshift_versions) for any potential impact and choose to safely use the ibmcloud oc 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. The master pods have a rolling update, during which only one pod is unavailable at a time. Two instances are up and running so that you can access and change the cluster during the update. Your worker nodes, apps, and resources continue to run.

Can I roll back the update?
: No, you can't roll back a cluster to a previous version after the update process takes place. Be sure to use a test cluster and follow the instructions to address potential issues before you update your production master.

What process can I follow to update the master?
: The following diagram shows the process that you can take to update your master.

Zoom

!
Ubuntu 16.04 packages N/A N/A Updated worker node image with package updates for [CVE-2020-14365](https://nvd.nist.gov/vuln/detail/CVE-2020-14365) and [CVE-2020-26137](https://nvd.nist.gov/vuln/detail/CVE-2020-26137). 







 Change log for worker node fix pack 1.16.15_1548, released 28 September 2020 

The following table shows the changes that are in the worker node fix pack 1.16.15_1548. 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.16.14_1546

 Component Previous Current Description 

 Kubernetes v1.16.14 v1.16.15 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.16.15).
Ubuntu 16.04 packages 4.4.0-178-generic 4.4.0-179-generic Updated worker node images with package and kernel updates for [CVE-2019-1547](https://nvd.nist.gov/vuln/detail/CVE-2019-1547), [CVE-2019-1551](https://nvd.nist.gov/vuln/detail/CVE-2019-1551), [CVE-2019-1563](https://nvd.nist.gov/vuln/detail/CVE-2019-1563), and [CVE-2020-12762](https://nvd.nist.gov/vuln/detail/CVE-2020-12762). 







 Change log for 1.18.3_1514, released 26 May 2020 

The following table shows the changes that are in the master and worker node update 1.18.3_1514. 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.2_1512

 Component Location Previous Current Description 

 IBM Calico extension Master 349 353 Skips creating a Calico host endpoint when no endpoint is needed. 
 IBM Cloud Controller Manager Master v1.18.2-3 v1.18.3-1 Updated to support the Kubernetes 1.18.3 release. 
 IBM Cloud File Storage for Classic plug-in and monitor Master 371 373 Image updated for [CVE-2020-11655](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11655).
To avoid downtime, [ensure that you have enough worker nodes to handle your workload while the selected worker nodes are updating](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node).

To update Satellite worker nodes, see [Updating hosts that are assigned as worker nodes to Satellite-enabled services](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-workers).

You might need to change your YAML files for deployments before you update. Review this [release note](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions) for details.

ibmcloud oc worker update --cluster CLUSTER --worker WORKER_ID [-f] [-q]

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

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where you list available worker nodes.

-w, --worker WORKER
: Specify a worker node ID. To reload multiple worker nodes, use multiple options, such as -w worker1_id -w worker2_id.

-f
: Optional: Force the command to run with no user prompts.

-q
: Optional: Do not show the message of the day or update reminders.



 Example worker update command 

ibmcloud oc worker update --cluster my_cluster -w kube-dal10-cr18a61a63a6a94b658596aa93d087aaa9-w1 -w kube-dal10-cr18a61a63a6a94b658596aa93d087aaa9-w2









 worker-pool commands 

View and modify worker pools for a cluster.



 ibmcloud oc worker-pool create classic 

Classic infrastructure

You can create a worker pool in your cluster. When you add a worker pool, it is not assigned a zone by default.
Ubuntu 16.04 packages 4.4.0-194-generic 4.4.0-197-generic Updated worker node image with kernel and package updates for [CVE-2020-0427](https://nvd.nist.gov/vuln/detail/CVE-2020-0427), [CVE-2020-12352](https://nvd.nist.gov/vuln/detail/CVE-2020-12352), [CVE-2020-14351](https://nvd.nist.gov/vuln/detail/CVE-2020-14351), [CVE-2020-25645](https://nvd.nist.gov/vuln/detail/CVE-2020-25645), and [CVE-2020-4788](https://nvd.nist.gov/vuln/detail/CVE-2020-4788). 







 Change log for worker node fix pack 1.16.15_1552, released 23 November 2020 

The following table shows the changes that are in the worker node fix pack 1.16.15_1552. 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.16.15_1551

 Component Previous Current Description
Ubuntu 16.04 packages N/A N/A Updated worker node image with package updates for{: external}, [CVE-2021-21300](https://nvd.nist.gov/vuln/detail/CVE-2021-21300), [CVE-2021-27218](https://nvd.nist.gov/vuln/detail/CVE-2021-27218), [CVE-2021-27219](https://nvd.nist.gov/vuln/detail/CVE-2021-27219), and [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177). 







 Change log for worker node fix pack 1.17.17_1555, released 1 March 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1555. 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.17.17_1553

 Component Previous Current Description
2. From the side menu, expand the SOURCES & TAR FILE section.
3. Download and open the source code.
4. Check the README.md or RELEASENOTES.md files for supported versions.
5. If the plug-in must be updated to run in the Kubernetes version that you want to update your cluster to, update the plug-in by following the plug-in instructions.





4. Update your API server and associated master components by using the [IBM Cloud console](https://cloud.ibm.com/login) or running the CLI ibmcloud ks cluster master update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update).
5. Wait a few minutes, then confirm that the update is complete. Review the API server version on the IBM Cloud clusters dashboard or run ibmcloud ks cluster ls.
6. Install the version of the [kubectl cli](https://cloud.ibm.com/docs/containers?topic=containers-cli-install) that matches the API server version that runs in the master. Kubernetes does not support kubectl client versions that are two or more versions apart from the server version (n +/- 2).



When the master update is complete, you can update your worker nodes, depending on the type of cluster infrastructure provider that you have.



* [Updating classic worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node).
* [Updating VPC worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updatevpc_worker_node).









 Updating classic worker nodes 

You notice that an update is available for your worker nodes in a [classic infrastructure](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providers) cluster. What does that mean?
: 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.
: Patches can be for worker nodes, masters, or both.



* Worker node patches: Check monthly to see whether an update is available, and use the [ibmcloud ks worker update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_update) command or the [ibmcloud ks worker reload](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) command to apply these security and operating system patches. During an update or reload, your worker node machine is reimaged, and data is deleted if not [stored outside the worker node](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan).
* Master patches: Master patches 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, as noted in the change log, 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 choose to safely use the [ibmcloud ks cluster master update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update) command yourself without waiting for the update automation to apply.







 Release lifecycle 

Each supported version of IBM Cloud Kubernetes Service goes through a lifecycle of testing, development, general release, support, deprecation, and becoming unsupported.
Portieris admission controller v0.10.2 v0.10.3 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.10.3). 







 Change log for worker node fix pack 1.19.11_1550, released 22 June 2021 

The following table shows the changes that are in the worker node fix pack 1.19.11_1550. 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.19.11_1549

 Component Previous Current Description 

 HA proxy 26c5cc d3dc33 Updated image with fixes for [CVE-2020-24977](https://nvd.nist.gov/vuln/detail/CVE-2020-24977), [CVE-2020-13434](https://nvd.nist.gov/vuln/detail/CVE-2020-13434), [CVE-2020-15358](https://nvd.nist.gov/vuln/detail/CVE-2020-15358), [CVE-2020-29361](https://nvd.nist.gov/vuln/detail/CVE-2020-29361), [CVE-2020-29362](https://nvd.nist.gov/vuln/detail/CVE-2020-29362), [CVE-2020-29363](https://nvd.nist.gov/vuln/detail/CVE-2020-29363), [CVE-2019-2708](https://nvd.nist.gov/vuln/detail/CVE-2019-2708), [CVE-2019-13012
Version 1.18 change log 

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



 Change log for worker node fix pack 1.18.20_1566, released 27 September 2021 

The following table shows the changes that are in the worker node fix pack patch update 1.18.20_1566. 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.18.20_1564

 Component Previous Current Description 

 Disk identification N/A N/A Enhanced the disk identification logic to handle the case of 2+ partitions. 
 HA proxy 9c98dc5 07f1e9 Updated image with fixes for [CVE-2021-22922](https://nvd.nist.gov/vuln/detail/CVE-2021-22922), [CVE-2021-22923](https://nvd.nist.gov/vuln/detail/CVE-2021-22923), [CVE-2021-22924](https://nvd.nist.gov/vuln/detail/CVE-2021-22924), [CVE-2021-36222](https://nvd.nist.gov/vuln/detail/CVE-2021-36222), and [CVE-2021-37750](https://nvd.nist.gov/vuln/detail/CVE-2021-37750).
Ubuntu 16.04 packages 4.4.0-174-generic 4.4.0-176-generic Updated worker node images with package updates for [CVE-2020-10531](https://nvd.nist.gov/vuln/detail/CVE-2020-10531), [CVE-2020-2732](https://nvd.nist.gov/vuln/detail/CVE-2020-2732), [CVE-2017-11109](https://nvd.nist.gov/vuln/detail/CVE-2017-11109), [CVE-2017-6349](https://nvd.nist.gov/vuln/detail/CVE-2017-6349), and [CVE-2017-6350](https://nvd.nist.gov/vuln/detail/CVE-2017-6350). 







 Change log for worker node fix pack 1.14.10_1549, released 16 March 2020 

The following table shows the changes that are in the worker node fix pack 1.14.10_1549. 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.14.10_1548

 Component Previous Current Description
You can remove the additional worker nodes after the update is completed.

In addition, you can create a Kubernetes config map that specifies the maximum number of worker nodes that can be unavailable at a time, such as during an update. Worker nodes are identified by the worker node labels. You can use IBM-provided labels or custom labels that you added to the worker node.

The Kubernetes config map rules are used for updating worker nodes only. These rules do not impact worker node reloads which means reloading happens immediately when requested.

What if I choose not to define a config map?
: When the config map is not defined, the default is used. By default, a maximum of 20% of all your worker nodes in each cluster can be unavailable during the update process.



 Prerequisites 

Before you update your classic infrastructure worker nodes, review the prerequisite steps.

Updates to worker nodes can cause downtime for your apps and services. Your worker node machine is reimaged, and data is deleted if not [stored outside the pod](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).



* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
* [Update the master](https://cloud.ibm.com/docs/openshift?topic=openshift-updatemaster). The worker node version can't be higher than the API server version that runs in your Kubernetes master.
* Make any changes that are marked with Update after master in the [Red Hat OpenShift version preparation guide](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).
* If you want to apply a patch update, review the [Red Hat OpenShift version change log](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).