vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Worker node fix pack update change log documentation is available for version [4.6.23_1539_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464623_1539), [4.5.35_1535_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4535_1535), [4.4.33_1538_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1538), and [3.11.404_1585_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311404_1585).





 5 April 2021 

Deprecated data centers for classic clusters
: Houston (hou02) and Oslo (osl01) are deprecated and become unsupported later this year. To prevent any interruption of service, [redeploy all your cluster workloads](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appcopy_apps_cluster) to a [supported data center](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-mz) and remove your osl01 or hou02 clusters by 1 August 2021. Before the unsupported date, you are blocked from adding new worker nodes and clusters starting on 1 July 2021. For more information, see [Data center closures in 2021](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure).





 2 April 2021 

Master versions
Change log for worker node fix pack 3.11.524_1606_openshift, released 11 October 2021 

The following table shows the changes that are in the worker node fix pack patch update 3.11.524_1606_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 3.11.521_1605_openshift

 Component Previous Current Description 

 OpenShift Container Platform node 3.11.521 3.11.524 See the [OpenShift Container Platform release notes](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.htmlocp-3-11-524). The update resolves CVE-2021-25741 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6515606)). 







 Change log for master fix pack 3.11.521_1604_openshift, released 28 September 2021 

The following table shows the changes that are in the worker node fix pack patch update 3.11.521_1604_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 3.11.487_1601_openshift

 Component Previous Current Description 

 IBM Cloud File Storage for Classic plug-in and monitor 398 400 Updated to use Go version 1.16.7. Updated universal base image (UBI) to the latest 8.4-208 version to resolve CVEs. 
 Load balancer and load balancer monitor for IBM Cloud Provider 1510 1550 Updated image for [CVE-2021-3711](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3711) and [CVE-2021-3712](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3712).
1550165 10.xxx.xx.xxx/26 10.xxx.xx.xxx 2234947 private
1602829 169.xx.xxx.xxx/28 169.xx.xxx.xxx 2234945 public
2. [Create a cluster from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-classic) by using the VLAN ID that you identified. Include the --no-subnet option to prevent a new portable public IP subnet and a new portable private IP subnet from being created automatically.

ibmcloud oc cluster create classic --zone dal10 --flavor b3c.4x16 --no-subnet --public-vlan 2234945 --private-vlan 2234947 --workers 3 --name my_cluster

If you can't remember which zone the VLAN is in for the --zone option, you can check whether the VLAN is in a certain zone by running ibmcloud oc vlan ls --zone <zone>.
3. Verify that the cluster was created. It can take up to 15 minutes for the worker node machines to be ordered and for the cluster to be set up and provisioned in your account.

ibmcloud oc cluster ls

When your cluster is fully provisioned, the State changes to deployed.

NAME ID State Created Workers Zone Version Resource Group Name Provider
mycluster aaf97a8843a29941b49a598f516da72101 deployed 20170201162433 3 dal10 1.26 Default classic
4. Check the status of the worker nodes.

ibmcloud oc worker ls --cluster <cluster_name_or_ID>

Before continuing to the next step, the worker nodes must be ready. The State changes to normal and the Status is Ready.

ID Public IP Private IP Machine Type State Status Zone Version
Change log for worker node fix pack 4.8.28_1543_openshift, released 31 January 2022 

The following table shows the changes that are in the worker node fix pack 4.8.28_1543_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.26_1541_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Updated worker node images with package updates for [CVE-2021-4034](https://nvd.nist.gov/vuln/detail/CVE-2021-4034). 
 Red Hat OpenShift 4.8.26 4.8.28 See the Red Hat OpenShift [change logs](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-28). 







 Change log for master fix pack 4.8.26_1542_openshift, released 26 January 2022 

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



Changes since version 4.8.21_1541_openshift

 Component Previous Current Description 

 Calico N/A N/A Changed to improve Calico availability during updates. 
 IBM Cloud Block Storage for Classic driver and plug-in v2.1.3 v2.1.6 Updated to use Go version 1.16.13. 
 IBM Calico extension 900 923 Updated universal base image (UBI) to the 8.5-218 version to resolve CVEs. Updated to use Go version 1.16.13. 
 Cluster health image v1.2.20 v1.2.21 Updated to use Go version 1.17.5, updated Go dependencies and golangci-lint.
: Optional: Download the Calico configuration file, TLS certificates, and permission files that are required to run calicoctl commands in your cluster. This option can't be used with the --yaml option.

--skip-rbac
: Skip adding user Kubernetes RBAC roles based on the IBM Cloud IAM service access roles to the cluster configuration. Include this option only if you [manage your own Kubernetes RBAC roles](https://cloud.ibm.com/docs/containers?topic=containers-usersrbac). If you use [IBM Cloud IAM service access roles](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-roles) to manage all your RBAC users, don't include this option.

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

--yaml
: Optional: Prints the command output in YAML format.



 Example cluster config command 

ibmcloud ks cluster config --cluster my_cluster







 ibmcloud ks cluster create classic 

Classic infrastructure

Create a cluster with worker nodes on classic infrastructure.

ibmcloud ks cluster create classic [--hardware HARDWARE] --zone ZONE --flavor FLAVOR --name NAME [--operating-system UBUNTU_20_64|UBUNTU_18_64] [--version MAJOR.MINOR.PATCH] [--no-subnet] [--sm-group GROUP] [--sm-instance INSTANCE] [--private-vlan PRIVATE_VLAN] [--public-vlan PUBLIC_VLAN] [--private-only] [--gateway-enabled] [--private-service-endpoint] [--public-service-endpoint] [--workers WORKER] [--disable-disk-encrypt] [--pod-subnet SUBNET] [--service-subnet SUBNET] [--skip-advance-permissions-check] [-q]
ibmcloud ks cluster create classic --zone <zone> --flavor <flavor> --hardware <shared_or_dedicated> --public-vlan <public_VLAN_ID> --private-vlan <private_VLAN_ID> --workers <number> --name <cluster_name> --version <major.minor.patch> [--public-service-endpoint] [--private-service-endpoint] [--pod-subnet] [--service-subnet] [--disable-disk-encrypt]
* To create a cluster with private network connectivity only, such as to extend your on-premises data center:

ibmcloud ks cluster create classic --zone <zone> --flavor <flavor> --hardware <shared_or_dedicated> --private-vlan <private_VLAN_ID> --private-only --workers <number> --name <cluster_name> --version <major.minor.patch> --public-service-endpoint [--pod-subnet] [--service-subnet] [--disable-disk-encrypt]



--zone <zone>
: Specify the IBM Cloud zone ID that you chose earlier and that you want to use to create your cluster.

--flavor <flavor>
: Specify the flavor for your worker node that you chose earlier.

--hardware <shared_or_dedicated>
: Specify with the level of hardware isolation for your worker node. Use dedicated to have available physical resources dedicated to you only, or shared to allow physical resources to be shared with other IBM customers. The default is shared. This value is optional for VM standard clusters. For bare metal flavors, specify dedicated.

--public-vlan <public_vlan_id>
: If you already have a public VLAN set up in your IBM Cloud infrastructure account for that zone, enter the ID of the public VLAN that you retrieved earlier. If you don't have a public VLAN in your account, don't specify this option. IBM Cloud Kubernetes Service automatically creates a public VLAN for you.
* If you generated an IBM Cloud Identity and Access Management (IAM) allowlist by specifying which IP addresses have access to your cluster, you must [add the CIDRs of the Red Hat OpenShift on IBM Cloud control plane for the zones in the region where your cluster is located to the allowlist](https://cloud.ibm.com/docs/openshift?topic=openshift-firewall).
* Classic only: If you have a firewall, [open the required ports and IP addresses in your firewall](https://cloud.ibm.com/docs/openshift?topic=openshift-firewall).
* VPC only: If you control traffic with VPC ACLs or security groups, make sure that you allow the minimum required [inbound and outbound rules](https://cloud.ibm.com/docs/openshift?topic=openshift-firewall).







 Step 4: Check the cluster setup 

Check that your cluster is set up properly. If you just created your cluster, wait awhile for your cluster components to fully provision.



1. Get the details of your cluster.

ibmcloud oc cluster get -c <cluster_name_or_ID>
2. Review the output of the previous step to check the Ingress Subdomain.



* If your cluster does not have a subdomain, see [No Ingress subdomain exists after cluster creation](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress_subdomain).
* If your cluster does have a subdomain, continue to the next step.



3. Verify that your cluster runs the latest patch Version. If your cluster does not run the latest patch version, update the cluster and worker nodes.



1. [Update the cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-updatemaster) to the latest patch version for your cluster major and minor version.

ibmcloud oc cluster master update -c <cluster_name_or_ID> --version <major.minor>_openshift-f
2.
ibmcloud ks zone add vpc-gen2 --zone <zone> --subnet-id <subnet_id> --cluster <cluster_name_or_ID> --worker-pool <worker_pool_name>
8. Verify that worker nodes provision in the zone that you added. Your worker nodes are ready when the State changes from provisioning to normal.

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

Example output

ID Primary IP Flavor State Status Zone Version
kube-<ID_string>-<cluster_name>-<pool_name>-00000002 10.xxx.xx.xxx c2.2x4 provisioning Infrastructure instance status is 'pending' us-south-1 -
kube-<ID_string>-<cluster_name>-<pool_name>-00000003 10.xxx.xx.xxx c2.2x4 normal Ready us-south-1 1.26_1511







 Adding a zone to a worker pool 

You can span your VPC cluster across multiple zones within one region by adding a zone to your existing 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 new 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. The Kubernetes scheduler uses these labels to spread pods across zones within the same region.

If you have multiple worker pools in your cluster, add the zone to all them so that worker nodes are spread evenly across your cluster. Note that when you add worker nodes to your cluster, the new worker nodes run the same major.minor version as the cluster master, but the latest worker node patch of that major.minor version.
Log rotate N/A N/A Switched to use systemd timers instead of cronjobs to prevent logrotate from failing on worker nodes that are not reloaded or updated within 90 days. Note: In all earlier versions for this minor release, the primary disk fills up after the cron job fails because the logs are not rotated. The cron job fails after the worker node is active for 90 days without being updated or reloaded. If the logs fill up the entire primary disk, the worker node enters a failed state. The worker node can be fixed by using the ibmcloud ks worker reload[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) or the ibmcloud ks worker update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_update). 
 Root password expiration N/A N/A Root passwords for the worker nodes expire after 90 days for compliance reasons. If your automation tooling needs to log in to the worker node as root or relies on cron jobs that run as root, you can disable the password expiration by logging into the worker node and running chage -M -1 root. Note: If you have security compliance requirements that prevent running as root or removing password expiration, don't disable the expiration. Instead, you can [update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_update) or [reload](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) your worker nodes at least every 90 days. 
 Worker node runtime components (kubelet, kube-proxy, containerd) N/A N/A Removed dependencies of runtime components on the primary disk. This enhancement prevents worker nodes from failing when the primary disk is filled up. 
 systemd N/A N/A Periodically clean transient mount units to prevent them from becoming unbounded.
To list the IDs of your subnets in all resource groups, run ibmcloud ks subnets --provider vpc-gen2 --vpc-id &lt,VPC_ID> --zone <subnet_zone>.

--flavor <worker_flavor>
: Enter the worker node flavor that you want to use. The flavor determines the amount of virtual CPU, memory, and disk space that is set up in each worker node and made available to your apps. VPC worker nodes can be created as virtual machines on shared infrastructure only. Bare metal or software-defined storage machines are not supported. For more information, see [Planning your worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes). To view available flavors, first list available VPC zones with ibmcloud ks zone ls --provider vpc-gen2, and then use the zone to list supported flavors by running ibmcloud ks flavors --zone <VPC_zone> --provider vpc-gen2. After you create your cluster, you can add different flavors by adding a worker node or worker pool to the cluster.

--version <major.minor.patch>
: The Kubernetes version for the cluster master node. To see available versions, run ibmcloud ks versions.

--workers <number>
: Specify the number of worker nodes to include in the cluster. If you don't specify this option, a cluster with the minimum value of 1 is created. For more information, see [What is the smallest size cluster that I can make?](https://cloud.ibm.com/docs/containers?topic=containers-faqssmallest_cluster). This value is optional.

--operating-system SYSTEM
: Optional. The operating system of the worker nodes you want to provision in your cluster. For a list of available operating systems by cluster version, see [IBM Cloud Kubernetes Service version information](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).
Kernel 4.4.0-127 4.4.0-133 Updated worker node images with kernel update for [CVE-2018-3620,CVE-2018-3646](https://ubuntu.com/security/notices/USN-3741-1) 







 Change log for worker node fix pack 1.9.9_1521, released 13 August 2018 

The following table shows the changes that are in the worker node fix pack 1.9.9_1521.



Table 1. Changes since version 1.9.9_1520

 Component Previous Current Description 

 Ubuntu packages N/A N/A Updates to installed Ubuntu packages. 







 Change log for 1.9.9_1520, released 27 July 2018 

The following table shows the changes that are in patch 1.9.9_1520.



Table 1. Changes since version 1.9.8_1517

 Component Previous Current Description 

 IBM Cloud Provider v1.9.8-141 v1.9.9-167 Updated to support Kubernetes 1.9.9 release. In addition, LoadBalancer service create failure events now include any portable subnet errors. 
 IBM Cloud File Storage for Classic plug-in 320 334 Increased the timeout for persistent volume creation from 15 to 30 minutes. Changed the default billing type to hourly. Added mount options to the pre-defined storage classes. In the NFS file storage instance in your IBM Cloud infrastructure account, changed the Notes field to JSON format and added the Kubernetes namespace that the PV is deployed to. To support multizone clusters, added zone and region labels to persistent volumes. 
 Kubernetes v1.9.8 v1.9.9 See the Kubernetes [release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.9.9) 
 Kernel N/A N/A Minor improvements to worker node network settings for high performance networking workloads.
Instead, you can [update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_update) or [reload](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) your worker nodes at least every 90 days. 
 Worker node runtime components (kubelet, kube-proxy, containerd) N/A N/A Removed dependencies of runtime components on the primary disk. This enhancement prevents worker nodes from failing when the primary disk is filled up. 
 systemd N/A N/A Periodically clean transient mount units to prevent them from becoming unbounded. This action addresses [Kubernetes issue 57345](https://github.com/kubernetes/kubernetes/issues/57345). 







 Change log for 1.11.2_1516, released 4 September 2018 

The following table shows the changes that are in patch 1.11.2_1516.



Changes since version 1.11.2_1514

 Component Previous Current Description 

 Calico v3.1.3 v3.2.1 See the [Calico release notes](https://docs.tigera.io/calico/latest/release-notes/.). 
 containerd 1.1.2 1.1.3 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.1.3). 
 IBM Cloud Provider v1.11.2-60 v1.11.2-71 Changed the cloud provider configuration to better handle updates for load balancer services with externalTrafficPolicy set to local. 
 IBM Cloud File Storage for Classic plug-in configuration N/A N/A Removed the default NFS version from the mount options in the IBM-provided file storage classes. The host's operating system now negotiates the NFS version with the IBM Cloud infrastructure NFS server.
--__.. 0-128 (NOT start with periodOrDash) 
 IMAGEID a-z 0-9 : (startwith sha256: noOtherColon) 



The parts of the image name must meet the following criteria.



* REGISTRY must be 253 characters or fewer and can contain lowercase or uppercase letters, numbers, periods (.), hyphens (-), and underscores (_). Do not use a dash (.) as the last character. Do not use more than 127 periods (.) and the labels between them can be between 1 and 63 characters long.
* NAMESPACE must be between 4 and 30 characters and must begin and end with a lowercase letter or number. NAMESPACE can contain lowercase alphanumeric characters, hyphens (-), and underscores (_).
* DOCKERUSERorDOCKERORG can be used for Docker registries instead of NAMESPACE. Specify your Docker username or Docker organization. Your Docker username and organization must be between 4 and 30 characters and contains only lowercase alphanumeric characters or numbers.
* REPOSITORY must be between 2 and 255 characters and must begin and end with a lowercase letter or number. REPOSITORY can contain lowercase alphanumeric characters, forward slashes (/), periods (.), hyphens (-), and underscores (_).
* TAG must be between 0 and 128 characters and can contain lowercase or uppercase letters, numbers, periods (.), hyphens (-), and underscores (_). The TAG must not begin with a period or dash. If you do not include a TAG, do not include the colon either.
* IMAGEID is prefixed with sha256: and can contain lowercase letters and numbers.
: The cloud component to which your resource belongs. The allowed values are: cloud_foundry, containers, container-registry, vmware, resource_controller, is, atracker, ims, iam.

organization_id
: The Cloud Foundry organization GUID.

doc.space_id
: The Cloud Foundry space GUID.

doc.resource_group_id
: The ID of the resource group.

type
: The resource type. The allowed values are: k8-cluster, k8-location, namespace, cf-service-instance, cf-user-provided-service-instance, cf-organization, cf-service-binding, cf-space, cf-application, resource-instance, resource-alias, resource-binding, resource-group, vmware-solutions, vpc, volume, vpn, load-balancer, security-group, key, image, subnet, public-gateway, floating-ip, network-acl, flow-log-collector, instance, instance-group, dedicated-host, endpoint-gateway, snapshot, share, backup-policy, vpn-server, virtual-network-interface, placement-group, route, target, cloud-object-storage-infrastructure, block-storage, file-storage, cloud-backup, cdn-powered-by-akamai, direct-link-cloud-exchange, direct-link-cloud-connect, direct-link-colocation, direct-link-network-service-provider, hardware-firewall, hardware-firewall-dedicated, fortigate-security-appliance-1gb, fortigate-security-appliance-10gb, virtual-router-appliance-copy, network-gateway-byoa, network-gateway-juniper-vsrx, ibm-cloud-load-balancer, virtual-server, bare-metal, citrix-virtual-app-desktop, bare-metal-server, serviceid.

creation_date
: The date on which the resource is created.

modification_date
: The last modification date of the resource.

tags
: The tags that have been attached to the resource.

tagReferences.tag.name
: The tags that have been attached to a classic infrastructure resource.