vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Updating the master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster).

Worker nodes in standard clusters are provisioned in to your IBM Cloud infrastructure account. The worker nodes are dedicated to your account and you are responsible to request timely updates to the worker nodes to ensure that the worker node OS and IBM Cloud Kubernetes Service components apply the latest security updates and patches. Security updates and patches are made available by IBM Site Reliability Engineers (SREs) who continuously monitor the Linux image that is installed on your worker nodes to detect vulnerabilities and security compliance issues. For more information, see [Updating worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node).





 Are the master and worker nodes highly available? 

The IBM Cloud Kubernetes Service architecture and infrastructure is designed to ensure reliability, low processing latency, and a maximum uptime of the service. By default, every cluster in IBM Cloud Kubernetes Service is set up with multiple Kubernetes master instances to ensure availability and accessibility of your cluster resources, even if one or more instances of your Kubernetes master are unavailable.

You can make your cluster even more highly available and protect your app from a downtime by spreading your workloads across multiple worker nodes in multiple zones of a region. This setup is called a [multizone cluster](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmz-clusters) and ensures that your app is accessible, even if a worker node or an entire zone is not available.

To protect against an entire region failure, create [multiple clusters and spread them across IBM Cloud regions](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmultiple-clusters-glb). By setting up a network load balancer (NLB) for your clusters, you can achieve cross-region load balancing and cross-region networking for your clusters.
Change log for worker node fix pack 1.23.17_1574, released 11 April 2023 

The following table shows the changes that are in the worker node fix pack 1.23.17_1574. 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.17_1572

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-206 4.15.0-208 Worker node kernel & package updates for [CVE-2021-3669](https://nvd.nist.gov/vuln/detail/CVE-2021-3669), [CVE-2022-0413](https://nvd.nist.gov/vuln/detail/CVE-2022-0413), [CVE-2022-1629](https://nvd.nist.gov/vuln/detail/CVE-2022-1629), [CVE-2022-1674](https://nvd.nist.gov/vuln/detail/CVE-2022-1674), [CVE-2022-1720](https://nvd.nist.gov/vuln/detail/CVE-2022-1720), [CVE-2022-1733](https://nvd.nist.gov/vuln/detail/CVE-2022-1733), [CVE-2022
Change log for worker node fix pack 1.16.13_1542, released 3 August 2020 

The following table shows the changes that are in the worker node fix pack 1.16.13_1542. 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.13_1539

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-111-generic 4.15.0-112-generic Updated worker node images with kernel and package updates for [CVE-2019-17514](https://nvd.nist.gov/vuln/detail/CVE-2019-17514), [CVE-2019-20907](https://nvd.nist.gov/vuln/detail/CVE-2019-20907), [CVE-2019-9674](https://nvd.nist.gov/vuln/detail/CVE-2019-9674), [CVE-2020-10713](https://nvd.nist.gov/vuln/detail/CVE-2020-10713), [CVE-2020-10757](https://nvd.nist.gov/vuln/detail/CVE-2020-10757), [CVE-2020-11935
: 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.

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/containers?topic=containers-storage-plan).



* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
* [Update the master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster). The worker node version can't be higher than the API server version that runs in your Kubernetes master.
-p, --worker-pool WORKER_POOL
: Required: The name of the worker node pool that you want to view the details of. To list available worker pools, run ibmcloud ks worker-pool ls --cluster <cluster_name_or_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-pool label rm command 

ibmcloud ks worker-pool label rm --worker-pool pool1 --cluster my_cluster







 ibmcloud ks worker-pool label set 

Virtual Private Cloud

Classic infrastructure

Set custom Kubernetes labels in the format key=value for all the worker nodes in the worker pool. To keep any existing custom labels on the worker pool, you must include those labels in this command.

ibmcloud ks worker-pool label set --cluster CLUSTER --label LABEL [--label LABEL ...] --worker-pool POOL [-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 the worker pool is located.

--label LABEL
: Required: A custom label in the format key=value to set for all the worker nodes in the worker pool. For multiple labels, repeat this option. To keep any existing custom labels on the worker pool, include those labels with this option. You can list the existing custom labels on worker nodes in the worker pool by running ibmcloud ks worker-pool get -c <cluster_name_or_ID> --worker-pool <pool>.

-p, --worker-pool WORKER_POOL
: Required: The name of the worker node pool that you want to view the details of. To list available worker pools, run ibmcloud ks worker-pool ls --cluster <cluster_name_or_ID>.

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

-q
: If you want to use existing storage that you provisioned earlier, but never used in your cluster before, you must make the storage available in the same subnet as your worker nodes.



1. From the [IBM Cloud infrastructure portal](https://cloud.ibm.com/classic), click Storage.
2. Click File Storage for Classic and from the Actions menu, select Authorize Host.
3. Select Subnets.
4. From the drop-down list, select the private VLAN subnet that your worker node is connected to. To find the subnet of your worker node, run ibmcloud oc worker ls --cluster <cluster_name> and compare the Private IP of your worker node with the subnet that you found in the drop-down list.
5. Click Submit.
6. Click the name of the File Storage for Classic.
7. Note the Mount Point, the size, and the Location field. The Mount Point field is displayed as <nfs_server>:<file_storage_path>.







 Creating a persistent volume and a persistent volume claim 



1. Create a storage configuration file for your PV. Include the values that you retrieved earlier.

apiVersion: v1
kind: PersistentVolume
metadata:
name: mypv
labels:
failure-domain.beta.kubernetes.io/region: <region>
failure-domain.beta.kubernetes.io/zone: <zone>
spec:
capacity:
storage: "<size>"
accessModes:
- ReadWriteMany
nfs:
server: "<nfs_server>"
path: "<file_storage_path>"

name
: Enter the name of the PV object to create.

labels
: Enter the region and the zone that you retrieved earlier. You must have at least one worker node in the same region and zone.

storage
: Enter the storage size of the existing NFS file share that you retrieved earlier.
Change log for worker node fix pack 1.24.13_1567, released 9 May 2023 

The following table shows the changes that are in the worker node fix pack 1.24.13_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.24.13_1566

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-209-generic 4.15.0-210-generic Worker node kernel & package updates for [CVE-2023-1786](https://nvd.nist.gov/vuln/detail/CVE-2023-1786), [CVE-2023-0464](https://nvd.nist.gov/vuln/detail/CVE-2023-0464), [CVE-2023-0466](https://nvd.nist.gov/vuln/detail/CVE-2023-0466), [CVE-2023-1829](https://nvd.nist.gov/vuln/detail/CVE-2023-1829), [CVE-2023-25652](https://nvd.nist.gov/vuln/detail/CVE-2023-25652), [CVE-2023-25815](https://nvd.nist.gov/vuln/detail/CVE-2023-25815), [CVE-2023-29007](https://nvd.nist.gov/vuln/detail/CVE-2023-29007).
Change log for worker node fix pack 1.24.14_1572, released 19 June 2023 

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

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A Worker node package updates for [CVE-2020-11080](https://nvd.nist.gov/vuln/detail/CVE-2020-11080),[CVE-2023-24329](https://nvd.nist.gov/vuln/detail/CVE-2023-24329),[CVE-2023-2603](https://nvd.nist.gov/vuln/detail/CVE-2023-2603),[CVE-2023-2609](https://nvd.nist.gov/vuln/detail/CVE-2023-2609),[CVE-2023-2610](https://nvd.nist.gov/vuln/detail/CVE-2023-2610),[CVE-2023-32681](https://nvd.nist.gov/vuln/detail/CVE-2023-32681)
-p, --worker-pool WORKER_POOL
: Required: The name of the worker node pool that you want to view the details of. To list available worker pools, run ibmcloud ks worker-pool ls --cluster <cluster_name_or_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-pool label set command 

ibmcloud ks worker-pool label set --worker-pool pool1 --cluster my_cluster --label app=dev







 ibmcloud ks worker-pool ls 

Virtual Private Cloud

Classic infrastructure

List all worker pools in a cluster.

ibmcloud ks worker-pool ls --cluster CLUSTER [--output json] [-q]

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

Command options:

-c, --cluster CLUSTER_NAME_OR_ID
: Required: The name or ID of the cluster for which you want to list worker pools.

--output json
: Optional: Prints the command output in JSON format.

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



 Example worker-pool ls command 

ibmcloud ks worker-pool ls --cluster my_cluster







 ibmcloud ks worker-pool rebalance 

Virtual Private Cloud

Classic infrastructure

Rebalance a worker pool in a cluster after you delete a worker node. When you run this command, a new worker or workers are added to your worker pool so that the worker pool has the same number of nodes per zone that you specified.

ibmcloud ks worker-pool rebalance --cluster CLUSTER --worker-pool WORKER_POOL [-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.

-p, --worker-pool WORKER_POOL
Updated base image. 







 Change log for worker node fix pack 1.26.5_1540, released 19 June 2023 

The following table shows the changes that are in the worker node fix pack 1.26.5_1540. 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.5_1539

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A Worker node package updates for [CVE-2020-11080](https://nvd.nist.gov/vuln/detail/CVE-2020-11080),[CVE-2023-24329](https://nvd.nist.gov/vuln/detail/CVE-2023-24329),[CVE-2023-2603](https://nvd.nist.gov/vuln/detail/CVE-2023-2603),[CVE-2023-2609](https://nvd.nist.gov/vuln/detail/CVE-2023-2609),[CVE-2023-2610](https://nvd.nist.gov/vuln/detail/CVE-2023-2610),[CVE-2023-32681](https://nvd.nist.gov/vuln/detail/CVE-2023-32681)
* [Software-defined storage (SDS) machines](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodessds)



* [Planning considerations for SDS](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodessds-planning)
* [Available flavors for SDS](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodessds-table)



* [Worker node resource reserves](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesresource_limit_node)







 Creating clusters 

[Preparing to create clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersclusters)



* [Preparing to create clusters at the account level](https://cloud.ibm.com/docs/openshift?topic=openshift-clusterscluster_prepare)
* [Deciding on your cluster setup](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersprepare_cluster_level)
* [Next steps](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersnext_steps)



[Creating classic clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-classiccluster-create-classic)



* [Creating a classic cluster in the console](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-classicclusters_ui)
* [Creating a standard classic cluster in the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-classicclusters_cli_steps)
Ubuntu 18.04 bare metal kernel 4.15.0-126-generic 4.15.0-123-generic Bare metal worker nodes: Reverted the kernel version for bare metal worker nodes while Canonical addresses issues with the previous version that prevented worker nodes from being reloaded or updated. 







 Change log for worker node fix pack 1.18.12_1534, released 7 December 2020 

The following table shows the changes that are in the worker node fix pack 1.18.12_1534. 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.12_1533

 Component Previous Current Description 

 Containerd v1.3.4 1.3.9 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.3.9). The update resolves CVE-2020–15257 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6387878)). 
 HA proxy 1.8.26-384f42 db4e6d Added provenance labels for source tracking. 
 Ubuntu 18.04 packages 4.15.0-123-generic 4.15.0-126-generic Updated worker node image with kernel and package updates for [CVE-2020-14351](https://nvd.nist.gov/vuln/detail/CVE-2020-14351) and [CVE-2020-4788](https://nvd.nist.gov/vuln/detail/CVE-2020-4788).
* [Classic: Manually adding block storage to specific worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesmanual_block)
* [Classic: Attaching raw block storage to non-SDS worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesattach_block)
* [VPC: Adding raw Block Storage for VPC to VPC worker nodes by using the API](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_api_attach)



* [Detaching raw and unformatted Block Storage for Classic from a worker node in a VPC cluster by using the API](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_api_detach)
* [Reviewing volume attachment details for a VPC worker node by using the API](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_api_get_worker)



* [VPC: Attaching raw Block Storage for VPC to VPC worker nodes by using the CLI](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_cli_attach)



* [Removing raw Block Storage for VPC from VPC worker nodes by using the CLI](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesstorage-util-rm-vpc-cli)



* [Backing up and restoring PVC data for file and block storage](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesibmcloud-backup-restore)



* [Setting up an IBM Cloud Object Storage service instance](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesbackup_restore_setup_object_storage)
* [Using IBM Cloud Object Storage to back up and restore PVC data](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesbackup-restore-pvc)
(https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



To update stand-alone worker nodes to worker pools:



1. List existing stand-alone worker nodes in your cluster and note the ID, the Machine Type, and Private IP.

ibmcloud ks worker ls --cluster <cluster_name_or_ID>
2. Create a worker pool and decide on the flavor and the number of worker nodes that you want to add to the pool.

ibmcloud ks worker-pool create classic --name <pool_name> --cluster <cluster_name_or_ID> --flavor <flavor> --size-per-zone <number_of_workers_per_zone>
3. List available zones and decide where you want to provision the worker nodes in your worker pool. To view the zone where your stand-alone worker nodes are provisioned, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>. If you want to spread your worker nodes across multiple zones, choose a [classic](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-mz) or [VPC](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc) multizone.

ibmcloud ks zone ls
4. List available VLANs for the zone that you chose in the previous step. If you don't have a VLAN in that zone yet, the VLAN is automatically created for you when you add the zone to the worker pool.

ibmcloud ks vlan ls --zone <zone>
5. Add the zone to your worker pool. When you add a zone to a worker pool, the worker nodes that are defined in your worker pool are provisioned in the zone and considered for future workload scheduling. IBM Cloud® Kubernetes Service automatically adds the failure-domain.beta.kubernetes.io/region label for the region and the failure-domain.beta.kubernetes.io/zone label for the zone to each worker node.
* See [Getting help](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar) for more details about using the forums.









 Contacting support 

Before you open a support case, gather relevant information about your cluster environment.



1. Get your cluster details.

ibmcloud oc cluster get -c <cluster_name_or_ID>
2. If your issue involves worker nodes, get the worker node details.



1. List all worker nodes in the cluster, and note the ID of any worker nodes with an unhealthy State or Status.

ibmcloud oc worker ls -c <cluster_name_or_ID>
2. Get the details of the unhealthy worker node.

ibmcloud oc worker get -w <worker_ID> -c <cluster_name_or_ID>



3. For issues with resources within your cluster such as pods or services, log in to the cluster and use the Kubernetes API to get more information about them.

You can also use the [IBM Cloud Kubernetes Service Diagnostics and Debug Tool](https://cloud.ibm.com/docs/openshift?topic=openshift-debug-tool) to gather and export pertinent information to share with IBM Support.
4. Contact IBM Support by [opening a case](https://cloud.ibm.com/unifiedsupport/cases/form). To learn about opening an IBM support case, or about support levels and case severities, see [Contacting support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
5. For the Problem type, search for or select Red Hat OpenShift on IBM Cloud.
6. For the Case details, provide a descriptive title and include the details that you previously gathered. From the Resources, you can also select the cluster that the issue is related to.







 Requesting access to allowlisted features 



1.
Kubernetes NodeLocal DNS cache N/A N/A Updated to run with a least privileged security context. 







 Change log for worker node fix pack 1.19.5_1530, released 21 December 2020 

The following table shows the changes that are in the worker node fix pack 1.19.5_1530. 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.5_1529

 Component Previous Current Description 

 Ubuntu 16.04 packages N/A N/A Updated worker node image with package updates for: [CVE-2020-1971](https://nvd.nist.gov/vuln/detail/CVE-2020-1971), [CVE-2020-27350](https://nvd.nist.gov/vuln/detail/CVE-2020-27350), [CVE-2020-27351](https://nvd.nist.gov/vuln/detail/CVE-2020-27351), [CVE-2020-8284](https://nvd.nist.gov/vuln/detail/CVE-2020-8284), [CVE-2020-8285](https://nvd.nist.gov/vuln/detail/CVE-2020-8285), and [CVE-2020-8286](https://nvd.nist.gov/vuln/detail/CVE-2020-8286).
Containerd v1.5.8 v1.5.9 See the [change log](https://github.com/containerd/containerd/releases/tag/v1.5.9). 







 Change log for worker node fix pack 1.21.7_1544, released 4 January 2022 

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

 Component Previous Current Description 

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