vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If the worker node remains in this state for an extended period of time even after the Kubernetes master is successfully updated, try to [reload the worker node](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload).
* You might have another firewall that is protecting your worker nodes, or changed firewall settings recently. IBM Cloud Kubernetes Service requires certain IP addresses and ports to be opened to allow communication from the worker node to the Kubernetes master and vice versa. For more information, see [Firewall prevents worker nodes from connecting](https://cloud.ibm.com/docs/containers?topic=containers-firewallvyatta_firewall).
* The Kubernetes master is down. Contact IBM Cloud support by opening an [IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).







 Warning state 

You can view the current worker node state by running the ibmcloud ks worker ls --cluster <cluster_name_or_ID> command and locating the State and Status fields.

A Warning state means that your worker node is reaching the limit for memory or disk space. You can either reduce workload on your worker node or add a worker node to your cluster to help load balance the workload.
Updated image for [CVE-2020-8037](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8037) and [CVE-2020-28928](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28928). Updated image to implement additional IBM security controls. 
 OpenVPN client 2.4.6-r3-IKS-116 2.4.6-r3-IKS-301 Updated image to implement additional IBM security controls. 
 OpenVPN server 2.4.6-r3-IKS-131 2.4.6-r3-IKS-301 Updated image to implement additional IBM security controls. 







 Change log for worker node fix pack 4.3.40_1547_openshift, released 7 December 2020 

The following table shows the changes that are in the worker node fix pack update 4.3.40_1547_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.40_1546_openshift

 Component Previous Current Description 

 HAProxy 1.8.26-384f42 db4e6d Added provenance labels for source tracking. 
 RHEL 7 Packages N/A N/A Updated worker node image with package updates. 







 Change log for worker node fix pack 4.3.40_1546_openshift, released 23 November 2020 

The following table shows the changes that are in the worker node fix pack update 4.3.40_1546_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.40_1545_openshift

 Component Previous Current Description 

 Ephemeral storage reservations N/A N/A Local ephemeral storage is reserved on the Kubernetes data disk for system components.
If the worker node remains in this state for an extended period of time even after the Kubernetes master is successfully updated, try to [reload the worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reload).
* You might have another firewall that is protecting your worker nodes, or changed firewall settings recently. Red Hat OpenShift on IBM Cloud requires certain IP addresses and ports to be opened to allow communication from the worker node to the Kubernetes master and vice versa. For more information, see [Firewall prevents worker nodes from connecting](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallvyatta_firewall).
* The Kubernetes master is down. Contact IBM Cloud support by opening an [IBM Cloud support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).







 Warning state 

You can view the current worker node state by running the ibmcloud oc worker ls --cluster <cluster_name_or_ID> command and locating the State and Status fields.

A Warning state means that your worker node is reaching the limit for memory or disk space. You can either reduce workload on your worker node or add a worker node to your cluster to help load balance the workload.
Change log for worker node fix pack 4.3.14_1522_openshift, released 11 May 2020 

The following table shows the changes that are in the worker node fix pack update 4.3.13_1522_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.13_1521_openshift

 Component Previous Current Description 

 CRI-O 1.16.5 1.16.6 See the [CRI-O change logs](https://github.com/cri-o/cri-o/releases/tag/v1.16.6). 
 Red Hat OpenShift 4.3.13 4.3.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-3-18). 







 Change log for worker node fix pack 4.3.13_1521_openshift, released 27 April 2020 

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

 Component Previous Current Description 

 CRI-O 1.16.4 1.16.5 See the [CRI-O change logs](https://github.com/cri-o/cri-o/releases/tag/v1.16.5). 
 HA proxy 1.8.25-30b675 1.8.25-adb65d Update addresses [CVE-2020-1967](https://nvd.nist.gov/vuln/detail/CVE-2020-1967).
IBM Calico extension 730 747 Updated universal base image (UBI) to version 8.4-205 to resolve CVEs. 
 IBM Cloud Controller Manager v1.19.12-2 v1.19.13-1 Updated to support the Kubernetes 1.19.13 release and to use Go version 1.15.14. 
 IBM Cloud File Storage for Classic plug-in and monitor 394 395 Updated universal base image (UBI) to version 8.4-205 to resolve CVEs. 
 IBM Cloud RBAC Operator b68ea92 945df65 Updated image for [CVE-2021-33194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194). 
 Key Management Service provider v2.3.5 v2.3.6 Updated universal base image (UBI) to the latest version to resolve CVEs. 
 Kubernetes v1.19.12 v1.19.13 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.19.13). 







 Change log for worker node fix pack 1.19.12_1553, released 19 July 2021 

The following table shows the changes that are in the worker node fix pack 1.19.12_1553. 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.12_1552

 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.19.12_1552, released 6 July 2021 

The following table shows the changes that are in the worker node fix pack 1.19.12_1552. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.
IBM Calico extension 730 747 Updated universal base image (UBI) to version 8.4-205 to resolve CVEs. 
 IBM Cloud Controller Manager v1.20.8-2 v1.20.9-1 Updated to support the Kubernetes 1.20.9 release and to use Go version 1.15.14. 
 IBM Cloud File Storage for Classic plug-in and monitor 394 395 Updated universal base image (UBI) to version 8.4-205 to resolve CVEs. 
 IBM Cloud RBAC Operator b68ea92 945df65 Updated image for [CVE-2021-33194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194). 
 Key Management Service provider v2.3.5 v2.3.6 Updated universal base image (UBI) to the latest version to resolve CVEs. 
 Kubernetes v1.20.8 v1.20.9 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.20.9). 







 Change log for worker node fix pack 1.20.8_1546, released 19 July 2021 

The following table shows the changes that are in the worker node fix pack 1.20.8_1546. 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.8_1545

 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.20.8_1545, released 6 July 2021 

The following table shows the changes that are in the worker node fix pack 1.20.8_1545. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.
: Clusters also have process ID (PID) reservations and limits, to prevent a pod from using too many PIDs or ensure that enough PIDs exist for the kubelet and other IBM Cloud Kubernetes Service system components. If the PID reservations or limits are reached, Kubernetes does not create or assign new PIDs until enough processes are removed to free up existing PIDs. The total amount of PIDs on a worker node approximately corresponds to 8,000 PIDs per GB of memory on the worker node. For example, a worker node with 16 GB of memory has approximately 128,000 PIDs (16 × 8,000 = 128,000).

To review how much compute resources are currently used on your worker node, run [kubectl top node](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commandstop).

Worker node memory reserves by tier

Worker node CPU reserves by tier

Worker node PID reserves by tier



Worker node memory reserves by tier

 Memory tier % or amount reserved b3c.4x16 worker node (16 GB) example mg1c.28x256 worker node (256 GB) example 

 First 4 GB (0 - 4 GB) 25% of memory 1 GB 1 GB 
 Next 4 GB (5 - 8 GB) 20% of memory 0.8 GB 0.8 GB 
 Next 8 GB (9 - 16 GB) 10% of memory 0.8 GB 0.8 GB 
 Next 112 GB (17 - 128 GB) 6% of memory N/A 6.72 GB 
 Remaining GB (129 GB+) 2% of memory N/A 2.54 GB 
 Additional reserve for [kubelet eviction](https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/) 100 MB 100 MB (flat amount) 100 MB (flat amount) 
 Total reserved (varies) 2.7 GB of 16 GB total 11.96 GB of 256 GB total 



Sample worker node values are provided for example only. Your actual usage might vary slightly.
evicting pod "dns-operator-6d48cbff67-vrrsw"
evicting pod "router-default-6fc798b98b-9m6kh"
evicting pod "prometheus-adapter-5b77ffdd5f-hzqrp"
evicting pod "alertmanager-main-1"
evicting pod "prometheus-k8s-0"
evicting pod "network-check-source-66c7fbb86-2r78z"
3. Wait until draining finishes, then complete the following steps to replace the worker node.







 Step 5: Upgrade the worker node 

Major

Minor



1. List your worker nodes by using the ibmcloud oc worker ls command and find the worker node that you cordoned and drained in the previous step.

ibmcloud oc worker ls -c CLUSTER

Example output

ID Primary IP Flavor State Status Zone Version
kube-c85ra07w091uv4nid9ug-vpcoc-default-000001c1 10.241.128.4 bx2.4x16 normal Ready us-east-3 4.8.29_1544_openshift
kube-c85ra07w091uv4nid9ug-vpcoc-default-00000288 10.241.0.4 bx2.4x16 normal Ready us-east-1 4.8.29_1544_openshift
kube-c85ra07w091uv4nid9ug-vpcoc-default-00000352 10.241.64.4 bx2.4x16 normal Ready us-east-2 4.8.29_1544_openshift
2. Replace the worker node.

ibmcloud oc worker replace -c CLUSTER --worker kube- --update

Example output

The replacement worker node is created in the same zone with the same flavor, but gets new public or private IP addresses.
If you did not use a deployment, retrieve the YAML file that was used to create your pod by running oc get pod <pod_name> -o yaml >pod.yaml. Then, delete and manually re-create the pod.

oc delete pod <pod_name>
4. Check whether re-creating your pod resolved the issue. If not, reload the worker node.



1. Find the worker node where your pod runs and note the private IP address that is assigned to your worker node.

oc describe pod <pod_name> | grep Node

Example output:

Node: 10.75.XX.XXX/10.75.XX.XXX
Node-Selectors: <none>
2. Retrieve the ID of your worker node by using the private IP address from the previous step.

ibmcloud oc worker ls --cluster <cluster_name_or_ID>
3. Safely [reload the worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reload).
If you did not use a deployment, retrieve the YAML file that was used to create your pod by running kubectl get pod <pod_name> -o yaml >pod.yaml. Then, delete and manually re-create the pod.

kubectl delete pod <pod_name>
4. Check whether re-creating your pod resolved the issue. If not, reload the worker node.



1. Find the worker node where your pod runs and note the private IP address that is assigned to your worker node.

kubectl describe pod <pod_name> | grep Node

Example output:

Node: 10.75.XX.XXX/10.75.XX.XXX
Node-Selectors: <none>
2. Retrieve the ID of your worker node by using the private IP address from the previous step.

ibmcloud ks worker ls --cluster <cluster_name_or_ID>
3. Safely [reload the worker node](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload).
Change log for worker node fix pack 4.8.24_1540_openshift, released 4 January 2022 

The following table shows the changes that are in the worker node fix pack patch update 4.8.24_1540_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.24_1539_openshift

 Component Previous Current Description 

 HA proxy 3b8663 d38fa1 Contains fixes for [CVE-2021-3712](https://nvd.nist.gov/vuln/detail/CVE-2021-3712). 







 Change log for worker node fix pack 4.8.24_1539_openshift, released 20 December 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.8.24_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.8.22_1538_openshift

 Component Previous Current Description 

 Red Hat OpenShift node 4.8.20 4.8.22 See [change logs](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-22) 







 Change log for master fix pack 4.8.21_1537_openshift, released 7 December 2021 

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



Changes since version 4.8.18_1535_openshift

 Component Previous Current Description 

 Calico v3.20.2 v3.20.3 See the [Calico release notes](https://docs.tigera.io/archive).
Cluster health image v1.1.11 v1.1.12 Updated to use Go version 1.15.2. 
 Gateway-enabled cluster controller 1082 1105 Updated to use Go version 1.15.2. 
 Kubernetes NodeLocal DNS cache 1.15.13 1.15.14 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.15.14). 







 Change log for worker node fix pack 1.16.15_1549, released 12 October 2020 

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

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A Updated worker node image with package updates for [CVE-2019-8936](https://nvd.nist.gov/vuln/detail/CVE-2019-8936), [CVE-2020-26137](https://nvd.nist.gov/vuln/detail/CVE-2020-26137), and [CVE-2020-14365](https://nvd.nist.gov/vuln/detail/CVE-2020-14365). 
 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.
Change log for worker node fix pack 4.6.52_1568_openshift, released 4 January 2022 

The following table shows the changes that are in the worker node fix pack patch update 4.6.52_1568_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.52_1567_openshift

 Component Previous Current Description 

 HA proxy 3b8663 d38fa1 Contains fixes for [CVE-2021-3712](https://nvd.nist.gov/vuln/detail/CVE-2021-3712). 







 Change log for worker node fix pack 4.6.52_1567_openshift, released 20 December 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.6.52_1567_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.49_1566_openshift

 Component Previous Current Description 

 Red Hat OpenShift node 4.6.49 4.6.52 See the [change logs](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-52) 







 Change log for master fix pack 4.6.47_1565_openshift, released 7 December 2021 

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



Changes since version 4.6.47_1563_openshift

 Component Previous Current Description 

 Calico v3.17.5 v3.17.6 See the [Calico release notes](https://docs.tigera.io/archive).
Change log for worker node fix pack 4.7.60_1594_openshift, released 02 January 2023 

The following table shows the changes that are in the worker node fix pack 4.7.60_1594_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.60_1593_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 







 Change log for worker node fix pack 4.7.60_1593_openshift, released 19 December 2022 

The following table shows the changes that are in the worker node fix pack 4.7.60_1593_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.60_1591_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.80 3.10.0-1160.81 Worker node kernel & package updates for [CVE-2022-28733](https://nvd.nist.gov/vuln/detail/CVE-2022-28733). 
 RHEL 8 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. N/A N/A N/A 







 Change log for master fix pack 4.7.60_1592_openshift, released 14 December 2022 

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



Changes since version 4.7.59_1589_openshift

 Component Previous Current Description 

 Cluster health image v1.3.13 v1.3.14 Updated Go dependencies. Exclude ingress status from cluster status aggregation.
Fixes [CVE-2019-11244](https://nvd.nist.gov/vuln/detail/CVE-2019-11244). 







 Change log for worker node fix pack 3.11.161_1542_openshift, released 17 February 2020 

The following table shows the changes that are in the worker node fix pack update 3.11.161_1542_openshift. Worker node patch updates can be applied by updating or reloading the worker node



Changes since version 3.11.161_1540_openshift

 Component Previous Current Description 

 RHEL 7 packages 3.10.0-1062.9.1.el7 3.10.0-1062.12.1.el7 Updated worker node images with kernel and package updates for [CVE-2019-18408](https://nvd.nist.gov/vuln/detail/CVE-2019-18408), [CVE-2019-13734](https://nvd.nist.gov/vuln/detail/CVE-2019-13734), [CVE-2019-14816](https://nvd.nist.gov/vuln/detail/CVE-2019-14816), [CVE-2019-14895](https://nvd.nist.gov/vuln/detail/CVE-2019-14895), [CVE-2019-14898](https://nvd.nist.gov/vuln/detail/CVE-2019-14898), [CVE-2019-14901](https://nvd.nist.gov/vuln/detail/CVE-2019-14901), and [CVE-2019-17133](https://nvd.nist.gov/vuln/detail/CVE-2019-17133). 







 Change log for worker node fix pack 3.11.161_1540_openshift, released 3 February 2020 

The following table shows the changes that are in the worker node fix pack 3.11.161_1540_openshift.



Changes since version 3.11.161_1538_openshift
OpenVPN Operator image v1.1.2 v1.2.0 Fixed a bug that could prevent worker node VPN updates. 







 Change log for worker node fix pack 4.6.22_1536_openshift, released 29 March 2021 

The following table shows the changes that are in the worker node fix pack 4.6.22_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.6.20_1534_openshift

 Component Previous Current Description 

 Red Hat OpenShift 4.6.20 4.6.22 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-22).
When you initially deploy pods, if the worker node does not have enough allocatable resources, the deployment fails. Further, if pods exceed the worker node resource limit for memory and CPU, the pods are evicted. In Kubernetes, this limit is called a [hard eviction threshold](https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/hard-eviction-thresholds). For pods that exceed the PID limit, the pods receive as many PIDs as allocatable, but are not evicted based on PIDs.

If less PIDs, CPU or memory is available than the worker node reserves, Kubernetes starts to evict pods to restore sufficient compute resources and PIDs. The pods reschedule onto another worker node if a worker node is available. If your pods are evicted frequently, add more worker nodes to your cluster or set [resource limits](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/resource-requests-and-limits-of-pod-and-container) on your pods.

The resources that are reserved on your worker node depend on the amount of PIDs, CPU and memory that your worker node comes with. IBM Cloud Kubernetes Service defines PIDs, CPU and memory tiers as shown in the following tables. If your worker node comes with compute resources in multiple tiers, a percentage of your PIDs, CPU and memory resources is reserved for each tier.
: Clusters also have process ID (PID) reservations and limits, to prevent a pod from using too many PIDs or ensure that enough PIDs exist for the kubelet and other IBM Cloud Kubernetes Service system components. If the PID reservations or limits are reached, Kubernetes does not create or assign new PIDs until enough processes are removed to free up existing PIDs. The total amount of PIDs on a worker node approximately corresponds to 8,000 PIDs per GB of memory on the worker node. For example, a worker node with 16 GB of memory has approximately 128,000 PIDs (16 × 8,000 = 128,000).