vania-janet/multiturn-rag-retrieval-data huggingface dataset:
In the previous example output, the app pod cf-py-d7b7d94db-vp8pq is on a worker node with the IP address 10.xxx.xx.xxx.
3. List the worker nodes in the worker pool that you designated in your app deployment.

ibmcloud ks worker ls --cluster <cluster_name_or_ID> --worker-pool <worker_pool_name_or_ID>

Example output

ID Public IP Private IP Machine Type State Status Zone Version
kube-dal10-crb20b637238bb471f8b4b8b881bbb4962-w7 169.xx.xxx.xxx 10.176.48.78 b3c.4x16 normal Ready dal10 1.8.6_1504
kube-dal10-crb20b637238bb471f8b4b8b881bbb4962-w8 169.xx.xxx.xxx 10.176.48.83 b3c.4x16 normal Ready dal10 1.8.6_1504
kube-dal12-crb20b637238bb471f8b4b8b881bbb4962-w9 169.xx.xxx.xxx 10.176.48.69 b3c.4x16 normal Ready dal12 1.8.6_1504

If you created an app affinity rule based on another factor, get that value instead. For example, to verify that the app pod deployed to a worker node on a specific VLAN, view the VLAN that the worker node is on by running ibmcloud ks worker get --cluster <cluster_name_or_ID> --worker <worker_ID>.
4. In the output, verify that the worker node with the private IP address that you identified in the previous step is deployed in this worker pool.









 Deploying an app on a GPU machine
Change log for worker node fix pack 1.25.5_1528, released 16 January 2023 

The following table shows the changes that are in the worker node fix pack 1.25.5_1528. 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.5_1527

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-200 4.15.0-202 Worker node kernel & package updates for [CVE-2021-44758](https://nvd.nist.gov/vuln/detail/CVE-2021-44758), [CVE-2022-0392](https://nvd.nist.gov/vuln/detail/CVE-2022-0392), [CVE-2022-2663](https://nvd.nist.gov/vuln/detail/CVE-2022-2663), [CVE-2022-3061](https://nvd.nist.gov/vuln/detail/CVE-2022-3061), [CVE-2022-3437](https://nvd.nist.gov/vuln/detail/CVE-2022-3437), [CVE-2022-
Change log for worker node fix pack 1.23.12_1547, released 26 September 2022 

The following table shows the changes that are in the worker node fix pack 1.23.12_1547. 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.23.10_1545

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-192 4.15.0-193 Worker node kernel & package updates for [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2021-33655](https://nvd.nist.gov/vuln/detail/CVE-2021-33655), [CVE-2021-33656](https://nvd.nist.gov/vuln/detail/CVE-2021-33656), [CVE-2022-0943](https://nvd.nist.gov/vuln/detail/CVE-2022-0943), [CVE-2022-1154](https://nvd.nist.gov/vuln/detail/CVE-2022-1154), [CVE-2022-1616](https://nvd.nist.gov/vuln/detail/CVE-2022-1616), [CVE-2022-
Change log for worker node fix pack 1.20.13_1564, released 6 December 2021 

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

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-162 4.15.0-163 Updated worker node images and kernel with package updates. Contains fixes for [CVE-2021-43527](https://nvd.nist.gov/vuln/detail/CVE-2021-43527) 
 Kubernetes 1.20.12 1.20.13 See the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.20.13) 
 Containerd v1.4.11 v1.4.12 See the [change log](https://github.com/containerd/containerd/releases/tag/v1.4.12) and the [security bulletin](https://www.ibm.com/support/pages/node/6524974). 







 Change log for worker node fix pack 1.20.12_1562, released 22 November 2021 

The following table shows the changes that are in the worker node fix pack patch update 1.20.12_1562. 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.11_1560

 Component Previous Current Description 

 Kubernetes 1.20.11 1.20.12 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.20.12).
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.6_1539

 Component Previous Current Description 

 Containerd v1.4.5 v1.4.6 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.4.6). The update resolves CVE-2021-30465 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6456943)). 
 HA proxy e0fa2f 26c5cc Updated image with fixes for [CVE-2020-26116](https://nvd.nist.gov/vuln/detail/CVE-2020-26116), [CVE-2020-27619](https://nvd.nist.gov/vuln/detail/CVE-2020-27619), [CVE-2021-23336](https://nvd.nist.gov/vuln/detail/CVE-2021-23336), [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177), [CVE-2019-3842](https://nvd.nist.gov/vuln/detail/CVE-2019-3842), [CVE-2020-13776](https://nvd.nist.gov/vuln/detail/CVE-2020-13776), [CVE-2019-18276](https://nvd.nist.gov/vuln/detail/CVE-2019-18276), [CVE-
Retrieving apply plan logs 

You can retrieve the logs from either the Schematics workspace or the bootstrap node to view both successful and failed cluster deployments.



 Retrieving apply plan logs in Schematics workspace 

After you apply a plan, a new log file is generated, which can be viewed in the Jobs tab in the Schematics workspace. See the following sections for instructions and examples of successful or failed deployments.



 Successful cluster deployment 



1. In the Jobs tab in the Schematics workspace, select the job and expand the log file.
2. If the job was successful in creating all of the resources that are part of the deployment, then your workspace goes to an active state.
3. Use the SSH command in the output of your apply plan log to log in as vpcuser for the bootstrap, compute, and storage node through the bastion host as ubuntu user. See the following sample response of a successful deployment:



Sample response

2022/05/09 14:35:53 Terraform apply | Apply complete! Resources: 41 added, 0 changed, 0 destroyed.
2022/05/09 14:35:53 Terraform apply 
2022/05/09 14:35:53 Terraform apply | Outputs:
2022/05/09 14:35:53 Terraform apply 
2022/05/09 14:35:53 Terraform apply | ssh_command = "ssh -J ubuntu@141.125.161.0 vpcuser@10.241.1.5"
2022/05/09 14:35:53 Command finished successfully.





 Failed cluster deployment 



1. In the Jobs tab in the Schematics workspace, select the job and expand the log file for a better view.
2. If the job fails to create any of the resources that are a part of the deployment, then your workspace goes to a failed state. Deployment might error out if any of the deployment values are incorrect or if there are any issues at the infrastructure level.
3. Fix the errors, and then click Apply plan again. See the following sample response of a failed deployment:



Sample response
Change log for worker node fix pack 1.22.15_1573, released 26 September 2022 

The following table shows the changes that are in the worker node fix pack 1.22.15_1573. 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.22.13_1571

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-192 4.15.0-193 Worker node kernel & package updates for [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2021-33655](https://nvd.nist.gov/vuln/detail/CVE-2021-33655), [CVE-2021-33656](https://nvd.nist.gov/vuln/detail/CVE-2021-33656), [CVE-2022-0943](https://nvd.nist.gov/vuln/detail/CVE-2022-0943), [CVE-2022-1154](https://nvd.nist.gov/vuln/detail/CVE-2022-1154), [CVE-2022-1616](https://nvd.nist.gov/vuln/detail/CVE-2022-1616), [CVE-2022-
Change log for worker node fix pack 1.26.1_1521, released 13 February 2023 

The following table shows the changes that are in the worker node fix pack 1.26.1_1521. 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.26.1_1520

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-202 4.15.0-204 Worker node kernel & package updates for [CVE-2022-28321](https://nvd.nist.gov/vuln/detail/CVE-2022-28321), [CVE-2022-3437](https://nvd.nist.gov/vuln/detail/CVE-2022-3437), [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-2022-45142](https://nvd.nist.gov/vuln/detail/CVE-2022-45142), [CVE-2022-47016](https://nvd.nist.gov/vuln/detail/CVE-2022-47016), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286).
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.7_1524

 Component Previous Current Description 

 GPU worker node provisioning N/A N/A Fixed bug where new GPU worker nodes could not automatically join clusters that run Kubernetes version 1.16 or 1.17. 
 Ubuntu 18.04 packages 4.15.0-76-generic 4.15.0-88-generic Updated worker node images with package updates for [CVE-2019-5108](https://nvd.nist.gov/vuln/detail/CVE-2019-5108), [CVE-2019-20096](https://nvd.nist.gov/vuln/detail/CVE-2019-20096), [CVE-2019-18885](https://nvd.nist.gov/vuln/detail/CVE-2019-18885), [CVE-2019-19082](https://nvd.nist.gov/vuln/detail/CVE-2019-19082), [CVE-2019-19078](https://nvd.nist.gov/vuln/detail/CVE-2019-19078), [CVE-2019-19332](https://nvd.nist.gov/vuln/detail/CVE-2019-19332), [CVE-2016-9840](https://nvd.nist.gov/vuln/detail/CVE-2016-9840), [CVE-2016-9841](https://nvd.nist.gov/vuln/detail/CVE-2016-9841), [CVE-2016-9842](https://nvd.nist.gov/vuln/detail/CVE-2016-9842), and [CVE-2016-9843](https://nvd.nist.gov/vuln/detail/CVE-2016-9843).
* Allocate worker nodes and HSM as specified in [Before you begin](https://cloud.ibm.com/docs/key-protect?topic=key-protect-satellite-aboutsatellite-about-before-begin).
* Ensure network connectivity between HSM and worker nodes has been established.
* Provision Key Protect on Satellite using the instructions in [Deploying Key Protect on Satellite](https://cloud.ibm.com/docs/key-protect?topic=key-protect-satellite-ui-deploy).
* Give the Key Protect service the following service-to-service authorizations in your Satellite location: [Satellite Cluster Creator](https://cloud.ibm.com/docs/satellite?topic=satellite-iamiam-resource-loc), [Satellite Link Source Access Controller](https://cloud.ibm.com/docs/satellite?topic=satellite-iamiam-resource-link) and [Satellite Link Administrator](https://cloud.ibm.com/docs/satellite?topic=satellite-iamiam-resource-link). Until these authorizations are given, it is not possible for a Satellite cluster to be created for Key Protect. Once the authorization is set, Key Protect is allowed to start the process of deploying Key Protect on your worker nodes, a process that can take up to several hours. Once the deployment is completed, you will receive a completion status on your Key Protect instance provision.
* When you update the operating System in your worker nodes, ensure that it does not disrupt the service. Check out [Change management](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-servicesatis-change-management) for more information.
* Updating [worker nodes](https://cloud.ibm.com/docs/satellite?topic=satellite-hostshost-update-workers) in your Satellite location.



Key Protect on Satellite responsibilities:



* Running Key Protect maintenance and updates in your Satellite location.
* Ensuring the security of key operations and key-related processes.
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.4.18_1516_openshift

 Component Previous Current Description 

 CRI-O 1.17.4 1.17.5 See the [CRI-O release notes](https://github.com/cri-o/cri-o/releases/tag/v1.17.5). 
 Red Hat OpenShift 4.4.18 4.4.20 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.htmlocp-4-4-20). The update resolves CVE-2020-8557 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6343881)). 
 RHEL 7 packages N/A N/A Updated worker node image with package updates. 







 Change log for worker node fix pack 4.4.18_1516_openshift, released 31 August 2020 

The following table shows the changes that are in the worker node fix pack update 4.4.18_1516_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.4.16_1513_openshift

 Component Previous Current Description 

 Master proxy 1.8.25-384f42 1.8.26-561f1a See the [HAProxy change logs](https://www.haproxy.org/download/1.8/src/CHANGELOG). 
 Red Hat OpenShift 4.4.16 4.4.18 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.htmlocp-4-4-18).
* Patch: A worker node patch update includes security fixes. You can update the classic worker node to the latest patch by using the ibmcloud ks worker reload or update commands. Keep in mind that the update command also updates the worker node to the same major.minor version as the master and latest patch version, if a major.minor version update is also available.
* Major.minor: A major.minor update moves up the Kubernetes version of the worker node to the same version as the master. This type of update often includes changes to the Kubernetes API or other behaviors that you must prepare your cluster for. Remember that your worker nodes can be only up to two versions behind the master version (n-2). You can update the classic worker node to the same patch by using the ibmcloud ks worker update command.



For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).

What happens to my apps during an update?
: If you run apps as part of a deployment on worker nodes that you update, the apps are rescheduled onto other worker nodes in the cluster. These worker nodes might be in a different worker pool, or if you have stand-alone worker nodes, apps might be scheduled onto stand-alone worker nodes. To avoid downtime for your app, you must ensure that you have enough capacity in the cluster to carry the workload.

How can I control how many worker nodes go down at a time during an update or reload?
: If you need all your worker nodes to be up and running, consider [resizing your worker pool](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_pool_resize) or [adding stand-alone worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_add) to add more worker nodes. You can remove the additional worker nodes after the update is completed.
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.29_1533_openshift

 Component Previous Current Description 

 Red Hat OpenShift 4.3.29 4.3.31 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.3/release_notes/ocp-4-3-release-notes.htmlocp-4-3-31). The update resolves CVE-2020-8558 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6319989)). 
 RHEL 7 packages N/A N/A Updated worker node images with package updates. 







 Change log for worker node fix pack 4.3.29_1533_openshift, released 3 August 2020 

The following table shows the changes that are in the worker node fix pack update 4.3.29_1533_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.29_1532_openshift

 Component Previous Current Description
You notice that an update is available for your worker nodes in a [classic infrastructure](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers) cluster. What does that mean? As security updates and patches are put in place for the API server and other master components, you must be sure that the worker nodes remain in sync. You can make two types of updates: updating only the patch version, or updating the major.minor version with the patch version.

Applies to only classic clusters. Have a VPC cluster? See [Updating VPC worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-updatevpc_worker_node) instead.

For the latest security patches and fixes, make sure to update your worker nodes to the latest patch as soon as possible after it is available. For more information about the latest updates, review the [change log](https://cloud.ibm.com/docs/containers?topic=containers-changelog).

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).



* Patch: A worker node patch update includes security fixes. You can update the classic worker node to the latest patch by using the ibmcloud oc worker reload or update commands. Keep in mind that the update command also updates the worker node to the same major.minor version as the master and latest patch version, if a major.minor version update is also available.
* Major.minor: A major.minor update moves up the Kubernetes version of the worker node to the same version as the master. This type of update often includes changes to the Kubernetes API or other behaviors that you must prepare your cluster for. Remember that your worker nodes can only be one version behind the master version (n-1). You can update the classic worker node to the same patch by using the ibmcloud oc worker update command.
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.9.57_1580_openshift

 Component Previous Current Description 

 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 
 Haproxy af5031 8398d1 [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916). 







 Change log for worker node fix pack 4.9.57_1580_openshift, released 13 March 2023 

The following table shows the changes that are in the worker node fix pack 4.9.57_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 4.9.56_1576_openshift

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

 Component Previous Current Description 

 Red Hat OpenShift on IBM Cloud. 4.11.42 4.11.43 see [change logs](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-43). 
 RHEL 8 Packages N/A N/A Worker node package updates for [CVE-2023-32067](https://nvd.nist.gov/vuln/detail/CVE-2023-32067),[CVE-2023-24329](https://nvd.nist.gov/vuln/detail/CVE-2023-24329). 







 Change log for worker node fix pack 4.11.42_1558_openshift, released 5 June 2023 

The following table shows the changes that are in the worker node fix pack 4.11.42_1558_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.11.40_1556_openshift

 Component Previous Current Description 

 Red Hat OpenShift on IBM Cloud. 4.11.40 4.11.42 see [change logs](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-42). 
 RHEL 7 Packages N/A N/A N/A
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.16_1521_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271). 
 HAProxy 468c09 04f862 [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271). 
 Red Hat OpenShift on IBM Cloud. 4.10.16 4.10.18 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-18). 







 Change log for worker node fix pack 4.10.16_1521_openshift, released 7 June 2022 

The following table shows the changes that are in the worker node fix pack 4.10.16_1521_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.14_1519_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-24903](https://nvd.nist.gov/vuln/detail/CVE-2022-24903). 
 Red Hat OpenShift on IBM Cloud. 4.10.14 4.10.16 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-14).
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.7.51_1566_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271). 
 Haproxy 468c09 04f862 [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271). 
 Red Hat OpenShift on IBM Cloud. 4.7.51 4.7.53 For more information, see the [change log](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-53). 







 Change log for worker node fix pack 4.7.51_1566_openshift, released 7 June 2022 

The following table shows the changes that are in the worker node fix pack 4.7.51_1566_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.7.50_1564_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-24903](https://nvd.nist.gov/vuln/detail/CVE-2022-24903). 
 Red Hat OpenShift on IBM Cloud. 4.7.50 4.7.51 For more information, see the [change log](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-51).