vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Component Previous Current Description 

 Kernel 4.4.0-137 4.4.0-139 Updated worker node images with kernel update for [CVE-2018-7755](https://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_4.4.0-139.165/changelog). 







 Change log for 1.10.8_1530, released 7 November 2018 

The following table shows the changes that are in patch 1.10.8_1530.



Table 1. Changes since version 1.10.8_1528

 Component Previous Current Description 

 Cluster master N/A N/A Updated the cluster master configuration to increase high availability (HA). Clusters now have three Kubernetes master replicas that are set up with a highly available (HA) configuration, with each master deployed on separate physical hosts. Further, if your cluster is in a multizone-capable zone, the masters are spread across zones. 
 Cluster master HA proxy N/A 1.8.12-alpine Added an ibm-master-proxy-* pod for client-side load balancing on all worker nodes, so that each worker node client can route requests to an available HA master replica. 
 etcd v3.2.18 v3.3.1 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.1). 
 Encrypting data in etcd N/A N/A Previously, etcd data was stored on a master’s NFS file storage instance that is encrypted at rest. Now, etcd data is stored on the master’s local disk and backed up to IBM Cloud Object Storage. Data is encrypted during transit to IBM Cloud Object Storage and at rest. However, the etcd data on the master’s local disk is not encrypted. If you want your master’s local etcd data to be encrypted, [enable IBM Key Protect in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkeyprotect).
For more information, see [Worker node resource reserves](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesresource_limit_node). 







 Change log for master fix pack 1.13.4_1515, released 26 March 2019 

The following table shows the changes that are in the master fix pack 1.13.4_1515.



Table 1. Changes since version 1.13.4_1513

 Component Previous Current Description 

 Cluster DNS configuration N/A N/A Fixed the update process from Kubernetes version 1.11 to prevent the update from switching the cluster DNS provider to CoreDNS. You can still set up CoreDNS as the cluster DNS provider after the update. 
 IBM Cloud File Storage for Classic plug-in 345 346 Updated image for [CVE-2019-9741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741). 
 Key Management Service provider 166 167 Fixes intermittent context deadline exceeded and timeout errors for managing Kubernetes secrets. In addition, fixes updates to the key management service that might leave existing Kubernetes secrets unencrypted. Update includes fix for [CVE-2019-9741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741). 
 Load balancer and load balancer monitor for IBM Cloud Provider 143 146 Updated image for [CVE-2019-9741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741). 







 Change log for 1.13.4_1513, released 20 March 2019 

The following table shows the changes that are in the patch 1.13.4_1513.



Table 1. Changes since version 1.13.4_1510

 Component Previous Current Description
This topic applies only to the cluster autoscaler add-on.

If you upgrade your cluster to a version that isn't supported by the cluster autoscaler add-on, your apps might experience downtime and your cluster might not scale.

The cluster autoscaler has two types of updates.

Patch updates
: Patch updates are delivered automatically by IBM and don't contain any feature updates or changes in the supported add-on and cluster versions.

Release updates
: Release updates contain new features for the cluster autoscaler or changes in the supported add-on or cluster versions. You must manually apply release updates to your cluster autoscaler add-on.



1. Check the version of the cluster autoscaler add-on that is deployed in your cluster. If an update is available, review the [release notes](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog) for the latest add-on version.

ibmcloud oc cluster addon ls --cluster <cluster_name>
2. Disable the cluster autoscaler add-on. You might see a warning that resources or data might be deleted. For the cluster autoscaler update, any autoscaling operations that are in process when you disable fail. When you re-enable the add-on, the autoscaling operation is restarted for you. Existing cluster autoscaler resources like the iks-ca-configmap are retained even after you disable the add-on. Your worker nodes are not deleted because of disabling the add-on.

ibmcloud oc cluster addon disable cluster-autoscaler --cluster <cluster_name>

Example output

Data and resources that you created for the add-on might be deleted when the add-on is disabled. Continue? [y/N]>
3. Enable the add-on to install the latest version.

ibmcloud oc cluster addon enable cluster-autoscaler --cluster <cluster_name>
4. Verify the add-on is successfully updated and Ready.
IBM Cloud Provider Master v1.16.9-219 v1.16.10-243 Updated to support the Kubernetes 1.16.10 release. Updated network load balancer (NLB) events to use the latest IBM Cloud troubleshooting documentation. 
 Kubernetes Both v1.16.9 v1.16.10 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.16.10). 
 Kubernetes Dashboard Master v2.0.0-rc7 v2.0.0 See the [Kubernetes Dashboard release notes](https://github.com/kubernetes/dashboard/releases/tag/v2.0.0). 
 Kubernetes Metrics Server Master N/A N/A Increased the CPU per node for the metrics-server container to improve availability of the metrics server API service for large clusters. 
 Kubernetes NodeLocal DNS cache Master 1.15.4 1.15.13 <br><br> * See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.15.13)<br> * Now, when you [apply the label to set up node local DNS caching](https://cloud.ibm.com/docs/containers?topic=containers-cluster_dnsdns_cache), the requests are handled immediately and you don't need to reload the worker nodes.<br> * The NodeLocal DNS cache configuration now allows customization of stub domains and upstream DNS servers.<br> * The node-local-dns daemon set is updated to include the prometheus.io/port and prometheus.io/scrape annotations on the pods.<br><br><br> 
 Load balancer and load balancer monitor for IBM Cloud Provider Master 177 208 Updated the version 2.0 network load balancers (NLB) to clean up unnecessary IPVS rules. Improved application logging.
If you are using the OLM components then you must manage updates. If unused, you may [uninstall the OLM components](https://cloud.ibm.com/docs/containers?topic=containers-ts-delete-olm). Refer to the [open source documentation](https://olm.operatorframework.io/) for information on available resources including how to install a new instance of OLM on your cluster. 
 Recreate volume snapshots Volume snapshots must be recreated after the update. Run kubectl get volumesnapshots -A to get a list of volume snapshots.
Worker node patch updates can be applied by updating or reloading the worker node For more information, see [Update types](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions).



Changes since version 3.11.216_1550_openshift

 Component Location Previous Current Description 

 Cluster health image Master v1.1.1 v1.1.5 When cluster add-ons don't support the current cluster version, a warning is now returned in the cluster health state. 
 etcd Master v3.3.18 v3.3.20 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.20). 
 IBM Cloud Controller Manager Master v1.15.11-274 v1.15.12-316 Updated to support the Kubernetes 1.15.12 release. 
 IBM Cloud File Storage for Classic plug-in and monitor Master 358 373 Updated image for [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967) and [CVE-2020-11655](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11655). 
 IBM Cloud Paks Master N/A N/A Removed duplicate repositories in ClusterImagePolicies resources that are installed by IBM Cloud Paks. 
 Load balancer and load balancer monitor for IBM Cloud Provider Master 169 203 Version 2.0 network load balancers (NLB) were updated to fix problems with long-lived network connections to endpoints that failed readiness probes. Updated image for [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967).
If no version is specified, the add-on is updated to the default version. To list available add-on versions, run ibmcloud ks cluster addon versions.





 ibmcloud ks cluster addon versions 

Virtual Private Cloud

Classic infrastructure

View a list of supported versions for managed add-ons in IBM Cloud Kubernetes Service.

ibmcloud ks cluster addon versions [--addon ADD-ON_NAME] [--output json] [-q]

Minimum required permissions
: None

Command options:

--addon ADD-ON_NAME
: Optional: Specify an add-on name such as istio to filter versions for.

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

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



 Example addon versions command 

ibmcloud ks cluster addon versions --addon istio







 ibmcloud ks cluster ca create 

Virtual Private Cloud

Classic infrastructure

Create a new certificate authority (CA) for your cluster. After the CA is created and new CA certificates are issued for components in your cluster, the API server of the cluster is automatically refreshed.

After you run this command and before you run the ibmcloud ks cluster ca rotate command, follow the steps in [Rotating CA certificates in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-securitycert-rotate) to ensure that any tooling that uses certificates that are signed by the old CA is updated to use the new certificates and to update your worker nodes.

ibmcloud ks cluster ca create --cluster CLUSTER [-f] [-q]

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

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-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 cluster ca create command
The following table shows the changes that are in the master fix pack patch update 1.17.17_1555. Master patch updates are applied automatically.



Changes since version 1.17.17_1551

 Component Previous Current Description 

 Cluster health image v1.1.16 v1.1.18 Updated to use Go version 1.15.7. Updated image to implement additional IBM security controls. 
 Gateway-enabled cluster controller 1195 1232 Updated to use Go version 1.15.7. 
 IBM Calico extension 567 618 Updated to use Go version 1.15.7. 
 IBM Cloud Controller Manager v1.17.17-1 v1.17.17-6 Updated image for for [DLA-2509-1](https://www.debian.org/lts/security/2020/dla-2509). 
 IBM Cloud File Storage for Classic plug-in and monitor 385 388 Improved the retry logic for provisioning persistent volume claims (PVCs). 
 Key Management Service provider v1.0.7 v1.0.10 Updated image for [CVE-2020-1971](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1971) and [CVE-2020-24659](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24659). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1078 1165 Updated to use Go version 1.15.7.
Certificates that are signed by this new CA are issued for the cluster master components, and the API server is refreshed.

ibmcloud oc cluster ca create -c CLUSTER
2. Ensure that your cluster's master health is normal, the API server refresh is complete, and any master updates are complete. It might take several minutes for the master API server to refresh.

ibmcloud oc cluster get --cluster CLUSTER
3. Check the status of the CA creation. In the output, note the timestamp in the Action Completed field.

ibmcloud oc cluster ca status -c CLUSTER

Example output

Status: CA certificate creation complete. Ensure that your worker nodes are reloaded before you start a CA certificate rotation.
Action Started: 2020-08-30T16:17:56+0000
Action Completed: 2020-08-30T16:21:13+0000
4. Download the updated Kubernetes configuration data and certificates in your cluster's kubeconfig file.

ibmcloud oc cluster config -c CLUSTER --admin --network
5. Update any tooling that relies on the previous certificates.



* If you use IBM® Blockchain, you must [re-establish connectivity between the Blockchain management console and your cluster](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-refresh).
* If you use the certificate from your cluster's kubeconfig file in your own service such as Travis or Jenkins, or if you use calicoctl to manage Calico network policies, update your services and automation to use the new certificates.



6. Verify that the timestamps on your new certificates are later than the timestamp that you found in step 3. To check the date on your certificates, you can use a tool such as [KeyCDN](https://tools.keycdn.com/ssl).
7.
After you run this command, use the [ibmcloud ks cluster master private-service-endpoint allowlist command](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_master_pse_allowlist_add) to add subnets to the allowlist. Only authorized requests to your cluster master that originate from subnets in the allowlist are permitted through the cluster's private cloud service endpoint. If the public cloud service endpoint is enabled for your cluster, authorized requests are still permitted through the public cloud service endpoint.

ibmcloud ks cluster master private-service-endpoint allowlist enable --cluster CLUSTER [-f] [-q]

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

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

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

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



 Example cluster master private-service-endpoint allowlist enable command 

ibmcloud ks cluster master private-service-endpoint allowlist enable --cluster mycluster







 ibmcloud ks cluster master private-service-endpoint allowlist get 

Virtual Private Cloud

Classic infrastructure

List all subnets in the allowlist for a cluster's private cloud service endpoint.

This list includes subnets that you manually added by using the ibmcloud ks cluster master private-service-endpoint allowlist add command and subnets that are automatically added and managed by IBM, such as worker node subnets.

ibmcloud ks cluster master private-service-endpoint allowlist get --cluster CLUSTER [-q]

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

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

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



 Example cluster master private-service-endpoint allowlist get command
The following table shows the changes that are in the master fix pack patch update 1.18.20_1562. Master patch updates are applied automatically.



Changes since version 1.18.20_1559

 Component Previous Current Description 

 Cluster health image v1.2.14 v1.2.15 Updated to use Go version 1.15.15. Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs. 
 Gateway-enabled cluster controller 1348 1444 Updated image for [CVE-2021-36159](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36159). 
 GPU device plug-in and installer 82ee77b a9461a8 Updated to use Go version 1.16.6. 
 IBM Calico extension 747 763 Updated to use Go version 1.16.6. Updated universal base image (UBI) to the latest 8.4-205 version to resolve CVEs. 
 IBM Cloud File Storage for Classic plug-in and monitor 395 398 Updated to use Go version 1.16.6. Updated image for [CVE-2021-33910](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33910). 
 Key Management Service provider v2.3.6 v2.3.7 Updated to use Go version 1.15.15. Updated UBI to the latest 8.4 version to resolve CVEs. 
 Kubernetes Dashboard metrics scraper v1.0.6 v1.0.7 See the [Kubernetes Dashboard metrics scraper release notes](https://github.com/kubernetes-sigs/dashboard-metrics-scraper/releases/tag/v1.0.7). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1328 1510 Updated image for [CVE-2020-27780](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27780).
Change log for master fix pack 1.24.10_1551, released 30 January 2023 

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



Changes since version 1.24.9_1547

 Component Previous Current Description 

 Cluster health image v1.3.14 v1.3.15 Updated Go dependencies and to Go version 1.19.4. 
 GPU device plug-in and installer 03fd318 79a2232 Updated Go to version 1.19.4. 
 IBM Calico extension 1257 1280 Publish s390x image. 
 IBM Cloud Block Storage driver and plug-in v2.3.4 v2.3.6 Updated UBI images to 8.7-1031 
 IBM Cloud Controller Manager v1.24.8-3 v1.24.10-2 Updated to support the Kubernetes 1.24.10 release. Updated Go dependencies and to Go version 1.19.5. 
 IBM Cloud File Storage for Classic plug-in and monitor 421 425 Fixes for [CVE-2022-40303](https://nvd.nist.gov/vuln/detail/CVE-2022-40303) and [CVE-2022-40304](https://nvd.nist.gov/vuln/detail/CVE-2022-40303). 
 Key Management Service provider v2.5.12 v2.5.13 Updated Go dependencies and to Go version 1.19.4. Changed to focal distribution. 
 Konnectivity agent and server v0.0.33_418_iks v0.0.34_491_iks See the [Konnectivity release notes](https://github.com/kubernetes-sigs/apiserver-network-proxy/releases/tag/v0.0.34).
Public service endpoint for Kubernetes master N/A N/A Fixed an issue to [enable the public cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_clusterset-up-public-se). 
 Ubuntu 16.04 kernel 4.4.0-148-generic 4.4.0-150-generic Updated worker node images with kernel and package updates for [CVE-2019-10906](https://ubuntu.com/security/CVE-2019-10906). 
 Ubuntu 18.04 kernel 4.15.0-50-generic 4.15.0-51-generic Updated worker node images with kernel and package updates for [CVE-2019-10906](https://ubuntu.com/security/CVE-2019-10906). 







 Change log for 1.13.6_1524, released 4 June 2019 

The following table shows the changes that are in the patch 1.13.6_1524.



Table 1. Changes since version 1.13.6_1522

 Component Previous Current Description 

 Cluster DNS configuration N/A N/A Fixed a bug that might leave both Kubernetes DNS and CoreDNS pods running after cluster create or update operations. 
 Cluster master HA configuration N/A N/A Updated configuration to minimize intermittent master network connectivity failures during a master update. 
 etcd v3.3.11 v3.3.13 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.13).
To see available versions, run [ibmcloud ks versions](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_versions_command).

--force-update
: Optional: Attempt the update even if the change is greater than two minor versions from the worker node version.

-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 cluster master update command 

ibmcloud ks cluster master update --cluster my_cluster







 ibmcloud ks cluster pull-secret apply 

Virtual Private Cloud

Classic infrastructure

Make an IBM Cloud IAM service ID for the cluster, create a policy for the service ID that assigns the Reader service access role in IBM Cloud Container Registry, and then create an API key for the service ID. The API key is then stored in a Kubernetes image pull secret so that you can pull images from your IBM Cloud Container Registry namespaces for containers that are in the default Kubernetes namespace. This process happens automatically when you create a cluster. If you got an error during the cluster creation process or have an existing cluster, you can use this command to apply the process again.

This API key method replaces the previous method of authorizing a cluster to access IBM Cloud Container Registry by automatically creating a [token](https://www.ibm.com/cloud/blog/announcements/announcing-end-of-ibm-cloud-container-registry-support-for-uaa-tokens) and storing the token in an image pull secret. Now, by using IAM API keys to access IBM Cloud Container Registry, you can customize IAM policies for the service ID to restrict access to your namespaces or specific images. For example, you can change the service ID policies in the cluster's image pull secret to pull images from only a certain registry region or namespace. Before you can customize IAM policies, you must [enable IBM Cloud IAM policies for IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-user).
Cluster master HA proxy configuration N/A N/A Updated configuration to better handle intermittent connection failures to the cluster master. 
 GPU device plug-in and installer e32d51c 9ff3fda Updated the GPU drivers to [418.43](https://www.nvidia.com/object/unix.html). Update includes fix for [CVE-2019-9741](https://ubuntu.com/security/CVE-2019-9741.html). 
 IBM Cloud File Storage for Classic plug-in 344 345 Added support for [private cloud service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_clusterset-up-private-se). 
 Kernel 4.4.0-141 4.4.0-143 Updated worker node images with kernel update for [CVE-2019-6133](https://ubuntu.com/security/CVE-2019-6133.html). 
 Key Management Service provider 136 166 Updated image for [CVE-2018-16890](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16890), [CVE-2019-3822](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3822), and [CVE-2019-3823](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3823).
* Updates ibmcloud oc cluster ls command so that if you include the --ouput json option but don't include the --provider option, only classic clusters are returned.
* Corrects the example master update command that is displayed in the output of the ibmcloud oc cluster get command when a master update is available.
* Adds information about the effects of worker node replacement in the warning message for the ibmcloud oc worker replace command.
* Standardizes the help text for options that have a list of supported values.
* Updates the help text in various languages.







 Version 1.0.118 

Version 1.0.118 of the CLI was released on 7 July 2020.



* Deprecates the ibmcloud oc cluster user-subnet add, ibmcloud oc cluster user-subnet rm, and ibmcloud oc va commands.
* Updates the Go version to 1.13.12 for [CVE-2020-7919](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7919).
* Fixes a bug for downloading the Calico configuration by using the --network option in the ibmcloud oc cluster config command.
* Updates the help text for the --endpoint option of the ibmcloud oc kms enable command.
* Updates the help text in various languages.







 Version 1.0.99 

Version 1.0.99 of the CLI was released on 15 June 2020.



* Adds the --cos-instance option to the ibmcloud oc cluster create vpc-gen2 command to back up the images from your Red Hat OpenShift internal registry to a bucket in your IBM Cloud Object Storage instance.
* Updates the help text in various places.







 Version 1.0.94 

Version 1.0.94 of the CLI was released on 9 June 2020.