vania-janet/multiturn-rag-retrieval-data huggingface dataset:
HA proxy db4e6d 9b2dca Image update for [CVE-2020-1971](https://nvd.nist.gov/vuln/detail/CVE-2020-1971) and [CVE-2020-24659](https://nvd.nist.gov/vuln/detail/CVE-2020-24659). 







 Change log for master fix pack 1.19.5_1529, released 14 December 2020 

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



Changes since version 1.19.4_1527

 Component Previous Current Description 

 Cluster health image v1.2.3 v1.2.4 Updated image to implement additional IBM security controls. 
 etcd v3.4.13 v3.4.14 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.14). 
 Gateway-enabled cluster controller 1105 1184 Updated to use Go version 1.15.5. Updated image to implement additional IBM security controls. 
 GPU device plug-in and installer b966c41 c26e2ae Updated the GPU drivers to version [450.80.02](https://www.nvidia.com/download/driverResults.aspx/165294). Updated image for [CVE-2020-28367](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28367), [CVE-2020-28366](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28366), and [CVE-2020-28362](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28362). Updated image to implement additional IBM security controls.
IBM Cloud File Storage for Classic plug-in and monitor 371 373 Image updated for [CVE-2020-11655](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11655). 
 Load balancer and load balancer monitor for IBM Cloud Provider 206 208 Version 2.0 network load balancers (NLB) were updated to cleanup unnecessary IPVS rules. 
 Red Hat OpenShift 4.3.18 4.3.19 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-19). 







 Change log for master fix pack 4.3.18_1522_openshift, released 12 May 2020 

The following table shows the changes that are in the master fix pack update 4.3.18_1522_openshift. Master patch updates are applied automatically. For more information, see [Update types](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).



Changes since version 4.3.13_1521_openshift

 Component Previous Current Description 

 Cluster health image v1.1.0 v1.1.4 When cluster add-ons don't support the current cluster version, a warning is now returned in the cluster health state. 
 etcd v3.4.3 v3.4.7 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.7). 
 Gateway-enabled cluster controller 1045 1082 Updated image for [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967).
Change log for master fix pack 1.20.4_1531, released 27 February 2021 

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



Changes since version 1.20.4_1530.

 Component Previous Current Description 

 Calico v3.17.2 v3.17.3 See the [Calico release notes](https://docs.tigera.io/archive). 
 IBM Cloud Controller Manager v1.20.4-2 v1.20.4-4 Updated to use calicoctl version 3.17.3. 
 Load balancer and load balancer monitor for IBM Cloud Provider 1165 1274 Fixed a bug that might cause version 2.0 network load balancers (NLBs) to crash and restart on load balancer updates. 







 Change log for master fix pack 1.20.4_1530, released 22 February 2021 

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



Changes since version 1.20.2_1528.

 Component Previous Current Description 

 IBM Cloud Controller Manager v1.20.2-15 v1.20.4-2 Updated to support the Kubernetes 1.20.4 release and to use Go version 1.15.8. Updated image to implement additional IBM security controls. 
 Key Management Service provider v2.2.4 v2.3.0 Updated to use Go version 1.15.7. Updated image to implement additional IBM security controls. 
 Kubernetes v1.20.2 v1.20.4 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.20.4).
GET/v1/logging/{idOrName}/updatepolicy Check if automatic updates for the Fluentd logging add-on are enabled in the cluster. containers-kubernetes.cluster.read N/A 
 POST/v1/log-collector/{idOrName}/masterlogs Create a new master log collection request. containers-kubernetes.cluster.create containers-kubernetes.masterlog-retrieve 
 POST/v1/logging/{idOrName}/filterconfigs Create a logging filter configuration. containers-kubernetes.cluster.update containers-kubernetes.logging-filter.create 
 POST/v1/logging/{idOrName}/loggingconfig/{logSource} Create a log forwarding configuration. containers-kubernetes.cluster.update containers-kubernetes.logging-config.create 
 PUT/v1/logging/{idOrName}/filterconfigs/{id} Update a logging filter configuration. containers-kubernetes.cluster.update N/A 
 PUT/v1/logging/{idOrName}/loggingconfig/{logSource}/{id} Update a log forwarding configuration. containers-kubernetes.cluster.update N/A 
 PUT/v1/logging/{idOrName}/refresh Refresh the cluster's logging configuration. containers-kubernetes.cluster.update containers-kubernetes.logging-config.refresh 
 PUT/v1/logging/{idOrName}/updatepolicy Enable or disable automatic updates for the Fluentd logging add-on in the cluster. containers-kubernetes.cluster.create containers-kubernetes.logging-autoupdate.changed 







 NLB DNS 

Review the following network load balancer (NLB) domain name system (DNS) API methods, their corresponding actions in IBM Cloud IAM, and the events that are sent to IBM Cloud Activity Tracker for Red Hat OpenShift on IBM Cloud.



NLB DNS API methods, IAM actions, and Activity Tracker events.

 API Method Description IAM action for the API Activity Tracker event
To enable a managed add-on in your cluster from the CLI, use the [ibmcloud ks cluster addon enable command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_addon_enable). To enable a managed add-on in your cluster in the [Kubernetes clusters console](https://cloud.ibm.com/kubernetes/clusters), use the Add-ons pane of the cluster details page. When you enable the managed add-on, a supported version of the tool, including all Kubernetes resources are automatically installed in your cluster. Refer to the documentation of each managed add-on to find the prerequisites that your cluster must meet before you install the managed add-on.

For more information about the prerequisites for each add-on, see:



* [ALB OAuth Proxy](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsapp-id-auth)
* [Block Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block)
* [Cluster Autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpc)
* [Diagnostics and Debug Tool](https://cloud.ibm.com/docs/containers?topic=containers-debug-tool)
* [Istio](https://cloud.ibm.com/docs/containers?topic=containers-istio)
* [Static routes](https://cloud.ibm.com/docs/containers?topic=containers-static-routes)







 Updating managed add-ons 

The versions of each managed add-on are tested by IBM Cloud and approved for use in IBM Cloud Kubernetes Service. To update the components of an add-on to the most recent version supported by IBM Cloud Kubernetes Service, use the following steps.

Review the following links for specific update steps for each add-on.
: Added version change logs for the [HPCS Router](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) and [Image Key Synchronizer](https://cloud.ibm.com/docs/openshift?topic=openshift-image-key-synchronizer-changelog) add-ons.

Master versions
: Master fix pack update change log documentation is available for version [4.6.21_1535_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464621_1535), [4.5.35_1533_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4535_1533), [4.4.33_1536_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1536), and [3.11.394_1583_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311394_1583).





 29 March 2021 

Worker node versions
POST/v2/alb/updateAlb Update ALBs in a cluster. containers-kubernetes.cluster.update cluster-alb.update 
 POST/v2/alb/vpc/createAlb Create a public or private ALB in a VPC cluster. containers-kubernetes.cluster.update cluster-alb.create 
 POST/v2/alb/vpc/disableAlb Disable an ALB in a VPC cluster. containers-kubernetes.cluster.update cluster-alb.delete 
 POST/v2/alb/vpc/enableAlb Enable an existing ALB in a VPC cluster. containers-kubernetes.cluster.update cluster-alb.enable 
 PUT/v1/alb/albsecrets Update an ALB secret that you imported from Secrets Manager. containers-kubernetes.cluster.create cluster-ingress-secret.update 
 PUT/v1/alb/clusters/{idOrName}/update Force a one-time update of all ALB pods to the latest build. containers-kubernetes.cluster.update cluster-alb.update 
 PUT/v1/alb/clusters/{idOrName}/updatepolicy Enable or disable automatic updates for the Ingress ALBs in a cluster. containers-kubernetes.cluster.update cluster-alb-policy.update 
 PUT/v1/alb/clusters/{idOrName}/updaterollback Roll back all ALB pods in a cluster to their previously running build. containers-kubernetes.cluster.update cluster-alb-policy.update 







 Ingress load balancer 



Ingress load balancer API methods, IAM actions, and Activity Tracker events.

 API Method Description IAM action for the API Activity Tracker event 

 GET/ingress/v2/load-balancer/configuration Get the configuration of load balancers for Ingress ALBs. containers-kubernetes.cluster.read N/A 
 PATCH/ingress/v2/load-balancer/configuration Update the configuration of load balancers for Ingress ALBs.
Preparing classic and VPC Gen 2 clusters for autoscaling 

With the cluster-autoscaler add-on, you can scale the worker pools in your Red Hat® OpenShift® on IBM Cloud® classic or VPC cluster automatically to increase or decrease the number of worker nodes in the worker pool based on the sizing needs of your scheduled workloads. The cluster-autoscaler add-on is based on the [Kubernetes Cluster-Autoscaler project](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler). For a list of supported add-on versions by cluster version, see [Supported cluster add-on versions](https://cloud.ibm.com/docs/openshift?topic=openshift-supported-cluster-addon-versions).

Looking to use autoscaling in your Satellite clusters? See, [Preparing to autoscale Satellite clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-prepare-autoscale-sat).

Want to autoscale your pods instead? Check out [Scaling apps](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appapp_scaling).

You can't enable the cluster autoscaler on worker pools that use reservations.



 Understanding scale-up and scale-down 

The cluster autoscaler periodically scans the cluster to adjust the number of worker nodes within the worker pools that it manages in response to your workload resource requests and any custom settings that you configure, such as scanning intervals. Every minute, the cluster autoscaler checks for the following situations.



* Pending pods to scale up: A pod is considered pending when insufficient compute resources exist to schedule the pod on a worker node. When the cluster autoscaler detects pending pods, the autoscaler scales up your worker nodes evenly across zones to meet the workload resource requests.
: Change log added for master fix pack [4.10.15_1520_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410).

Cluster autoscaler add-on
: Version 1.1.0_729 is available. See [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).





 19 July 2022 

Cluster autoscaler add-on
: Version 1.0.5_728 is available. See [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).

Node Tuning Operator
: You can apply custom profiles to your worker nodes to improve performance. For more information, see [Modifying worker node settings by using the Node Tuning Operator](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-nto).





 18 July 2022 

Block Storage for VPC add-on.
: [Version 4.3.4_1551](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog) and [Version 4.4.8_1550](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog) are available.

Worker node fix pack
We advise that after a new host is added into the cluster, that it is placed in Maintenance Mode so that it can be reviewed for compliance drift and remediated before you host any workloads.

The following sequence is required to check compliance:



1. Create a Host Profile from an existing host.
2. Attach the new host to the Host Profile.
3. Check the compliance of the new host with the Host Profile.
4. Review compliance failures and remediate.





 Creating a host profile from an existing host 



1. From the vSphere Web Client Home, click Policies and Profiles.
2. Click Host Profiles and navigate to the Host Profiles view.
3. Click the Extract Profile from a Host icon.
4. Select an existing host that acts as the reference host and click Next.
5. Enter the name and enter a description for the new profile and click Next.
6. Review the summary information for the new profile and click Finish.



The new profile appears in the profile list.





 Attaching the new host to the host profile 



1. From the Profile List in the Host Profiles main view, select the Host Profile that was previously created to be applied to the new host.
2. Click the Attach/Detach a host profile to hosts and clusters icon.
3. Select the new host from the expanded list and click Attach.
4. The new host is added to the Attached Entities list.
5. Click Next and then click Finish.







 Checking the compliance of the new host with the host profile 



1. Go to the host profile that was previously completed.
2. Click the Check Host Profile Compliance icon.

On the Objects tab, the compliance status is updated as Compliant, Unknown or Non-compliant. A non-compliant status indicates a discovered and specific inconsistency between the profile and the new host.







 Reviewing compliance failures and remediation 



1. To see more detail on compliance failures, select the Host Profile from the Objects tab that is used in the compliance check.
2.
4. Get your cluster autoscaler pod.

oc get pods -n kube-system
5. Review the Events section of the cluster autoscaler pod for a ConfigUpdated event to verify that the ConfigMap is successfully updated. The event message for your ConfigMap is in the following format: minSize:maxSize:PoolName:<SUCCESS|FAILED>:error message.

oc describe pod -n kube-system <cluster_autoscaler_pod>

Example output

Name: ibm-iks-cluster-autoscaler-857c4d9d54-gwvc6
Namespace: kube-system
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------

Normal ConfigUpdated 3m ibm-iks-cluster-autoscaler-857c4d9d54-gwvc6 {"1:3:default":"SUCCESS:"}



If you enable a worker pool for autoscaling and then later add a zone to this worker pool, restart the cluster autoscaler pod so that it picks up this change: oc delete pod -n kube-system <cluster_autoscaler_pod>.



 Customizing the cluster autoscaler configuration values 

Customize the cluster autoscaler settings such as the amount of time it waits before scaling worker nodes up or down.

Before you begin:



* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
* [Install the ibm-iks-cluster-autoscaler add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addon).





 Customizing the cluster autoscaler add-on ConfigMap 

When you modify a ConfigMap parameter other than the worker pool minSize, maxSize, or if you enable or disable a worker pool, the cluster autoscaler pods are restarted.
4. Get your cluster autoscaler pod.

kubectl get pods -n kube-system
5. Review the Events section of the cluster autoscaler pod for a ConfigUpdated event to verify that the ConfigMap is successfully updated. The event message for your ConfigMap is in the following format: minSize:maxSize:PoolName:<SUCCESS|FAILED>:error message.

kubectl describe pod -n kube-system <cluster_autoscaler_pod>

Example output

Name: ibm-iks-cluster-autoscaler-857c4d9d54-gwvc6
Namespace: kube-system
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------

Normal ConfigUpdated 3m ibm-iks-cluster-autoscaler-857c4d9d54-gwvc6 {"1:3:default":"SUCCESS:"}



If you enable a worker pool for autoscaling and then later add a zone to this worker pool, restart the cluster autoscaler pod so that it picks up this change: kubectl delete pod -n kube-system <cluster_autoscaler_pod>.



 Customizing the cluster autoscaler configuration values 

Customize the cluster autoscaler settings such as the amount of time it waits before scaling worker nodes up or down.

Before you begin:



* [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)
* [Install the ibm-iks-cluster-autoscaler add-on](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-install-addon).





 Customizing the cluster autoscaler add-on ConfigMap
resourceVersion: "12757878"
selfLink: /api/v1/namespaces/kube-system/configmaps/iks-ca-configmap
uid: bd661f95-35ef-433d-97e0-5d1ac092eafb



7. Repeat these steps for every cluster where you want to provision the cluster autoscaler.
8. Optional: If you did not set any worker pools for autoscaling with the installation, you can [Update the cluster autoscaler configuration](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-enable).





 Customizing the cluster autoscaler Helm chart values 

The cluster autoscaler Helm chart is deprecated. For the latest version of the cluster autoscaler, [install the add-on](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-install-addon)



1. To change any of the cluster autoscaler configuration values, update the config map or the Helm chart with the new values. Include the --recreate-pods option so that any existing cluster autoscaler pods are re-created to pick up the custom setting changes. The following example command changes the scan interval to 2m and enables autoscaling for the autoscale worker pool, with a maximum of 5 and minimum of 3 worker nodes per zone.

helm upgrade --set scanInterval=2m --set workerpools[0].default.max=5,workerpools[0].autoscale.min=3,workerpools[0].default.enabled=true ibm-iks-cluster-autoscaler iks-charts/ibm-iks-cluster-autoscaler -i --recreate-pods --namespace kube-system

To reset the Helm chart to the default values:

helm upgrade --reset-values ibm-iks-cluster-autoscaler iks-charts/ibm-iks-cluster-autoscaler --recreate-pods
2. Verify your changes.
CUDA 576234 cce0cf [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527). 







 Change log for master fix pack 1.22.16_1578, released 16 November 2022 

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



Changes since version 1.22.15_1576

 Component Previous Current Description 

 Cluster health image v1.3.12 v1.3.13 Updated Go dependencies, golangci-lint, gosec, and to Go version 1.19.3. Updated base image version to 116. 
 etcd v3.4.18 v3.4.21 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.21). 
 Gateway-enabled cluster controller 1823 1902 Go module updates. 
 GPU device plug-in and installer 373bb9f cce0cfa Updated the GPU driver 470 minor version
: Master fix pack update change log documentation is available for version [4.6.21_1535_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464621_1535), [4.5.35_1533_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4535_1533), [4.4.33_1536_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1536), and [3.11.394_1583_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311394_1583).





 29 March 2021 

Worker node versions
: Worker node fix pack update change log documentation is available for version [4.6.22_1536_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464622_1536), [4.5.35_1534_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4535_1534), [4.4.33_1537_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1537), and [3.11.404_1584_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311404_1584).





 25 March 2021 

CIS Kubernetes Benchmark
: Versions 4.6.0_1986, 4.7.0_1985, 4.8.0_1984, and 4.9.0_1983 of the [HPCS Router add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) are released. Cloud Image Key Synchronizer add-on
: Version 1.0.0_1022 of the [Cloud Image Key Synchronizer add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-image-key-synchronizer-changelog) is released.

Block Storage for VPC add-on.
: [Version 5.0.0-beta_1125](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog) is available for allowlisted accounts.





 9 June 2022 

New! Kubernetes 1.24
: You can create or [update clusters to Kubernetes version 1.24](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_124). With Kubernetes 1.24, you get the latest stable enhancements from the Kubernetes community as well as enhancements to the IBM Cloud product.

Deprecated and unsupported Kubernetes versions
: With the release of Kubernetes 1.24, clusters that run version 1.21 are deprecated, with a tentative unsupported date of 31 Aug 2022. Update your cluster to at least [version 1.22](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_122) as soon as possible.





 7 June 2022 

CLI change log update
: The [CLI change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog) is updated for version 1.0.419.





 6 June 2022 

Worker node fix pack
: For more information, see the change logs: [1.24](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124), [1.25](https://cloud.ibm.com/docs/containers?topic=containers-changelog_125), and [1.26](https://cloud.ibm.com/docs/containers?topic=containers-changelog_126).





 25 May 2023 

CLI version 1.0.523.
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog).

Kubernetes version 1.27 certification
: Version [1.27](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_127) release is now certified.





 24 May 2023 

New! IBM Cloud Kubernetes Service version 1.27.
: You can create or [update clusters to Kubernetes version 1.27](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_127). With Kubernetes 1.27, you get the latest stable enhancements from the Kubernetes community as well as enhancements to the IBM Cloud product.

Master fix pack 1.27.2_1524 and worker node fix pack 1.27.2_1526.
: For more information, see the [1.27 change log](https://cloud.ibm.com/docs/containers?topic=containers-changelog_127).

Worker node fix packs 1.24.14_1570, 1.25.10_1546, and 1.26.5_1538.