vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Cluster health image Master v1.1.5 v1.1.8 Additional status information is included when an add-on health state is critical. Improved performance when handling cluster status updates. 
 Cluster master operations Master N/A N/A Cluster master operations such as refresh or update are now canceled if a broken [Kubernetes admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) is detected. 
 etcd Master v3.4.7 v3.4.9 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.9). 
 GPU device plug-in and installer Master b9a418c 2bcf8e4 Updated image for [CVE-2020-3810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3810). 
 IBM Cloud Controller Manager Master v1.18.3-1 v1.18.4-1 Updated to support the Kubernetes 1.18.4 release. Updated the version 2.0 private network load balancers (NLBs) to manage Calico global network policies. Updated calicoctl version to 3.13.4. 
 IBM Cloud File Storage for Classic plug-in Master 373 375 Fixed a bug that might cause error handling to create additional persistent volumes. 
 IBM Cloud RBAC operator Master N/A 08ce50e New!: Added a control plane operator to synchronize [IBM Cloud Identity and Access Management (IAM) service access roles](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-roles) with Kubernetes role-based access control (RBAC) roles. 
 Kubernetes Both v1.18.3 v1.18.4 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.4).
[(Deprecated) Installing the cluster autoscaler Helm chart in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmcluster-scaling-helm)



* [Customizing the cluster autoscaler Helm chart values](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_chart_values)
* [Upgrading a cluster autoscaler Helm chart release](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_helm_up)



* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_helm_up_prereqs)
* [Upgrading the cluster autoscaler release version](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_helm_up_general)



* [Removing the cluster autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_rm)
* [Cluster autoscaler Helm chart parameter reference](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_helm_ref)



[Updating clusters, worker nodes, and cluster components](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate)



* [Updating the Kubernetes master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster)



* [About updating the master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster-about)
* [Steps to update the cluster master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster-steps)



* [Updating classic worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node)
* [ibmcloud ks cluster master public-service-endpoint enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_master_pub_se_enable)
* [ibmcloud ks cluster master refresh](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_refresh)
* [ibmcloud ks cluster master update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update)
* [ibmcloud ks cluster pull-secret apply](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_pull_secret_apply)
* [ibmcloud ks cluster rm](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_rm)
* [ibmcloud ks cluster service bind](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_service_bind)
* [ibmcloud ks cluster service ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_services)
* [ibmcloud ks cluster service unbind](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_service_unbind)
* [ibmcloud ks cluster subnet add](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_subnet_add)
* [ibmcloud ks cluster subnet create](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_subnet_create)
Example cluster master public-service-endpoint disable command 

ibmcloud ks cluster master public-service-endpoint disable --cluster my_cluster







 ibmcloud ks cluster master public-service-endpoint enable 

Virtual Private Cloud

Classic infrastructure

Enable the [public cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-plan_basicsworkeruser-master) to make your cluster master publicly accessible.

After you run this command, you must refresh the API server to use the service endpoint by following the prompt in the CLI.

ibmcloud ks cluster master public-service-endpoint enable --cluster CLUSTER [-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.

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

-y
: Optional: Refresh the cluster master with no user prompts.



 Example cluster master public-service-endpoint enable command 

ibmcloud ks cluster master public-service-endpoint enable --cluster my_cluster







 ibmcloud ks cluster master refresh 

Virtual Private Cloud

Classic infrastructure

Apply configuration changes for the Kubernetes master that are requested with the ibmcloud ks cluster master commands. The highly available Kubernetes master components are restarted in a rolling restart. Your worker nodes, apps, and resources are not modified and continue to run.

The apiserver-refresh and cluster-refresh aliases for this command are deprecated.

ibmcloud ks cluster master refresh --cluster CLUSTER [-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.

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





 ibmcloud ks cluster master update 

Virtual Private Cloud

Classic infrastructure

Satellite
Change log for master fix pack 1.21.14_1564, released 22 June 2022 

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



Changes since version 1.21.13_1561

 Component Previous Current Description 

 Cluster health image v1.3.7 v1.3.8 Updated Go to version 1.17.11 and also updated the dependencies. 
 CoreDNS 1.8.6 1.8.7 See the [CoreDNS release notes](https://coredns.io/2021/12/09/coredns-1.8.7-release/). 
 GPU device plug-in and installer 382ada9 2b0b6d1 Updated universal base image (UBI) to version 8.6-751. Updated Go to version 1.17.10. 
 IBM Cloud Controller Manager v1.21.13-2 v1.21.13-5 Update prometheus/client_golang@v1.7.1 to v1.11.1 
 Key Management Service provider v2.5.5 v2.5.6 Updated Go to version 1.17.11 and also updated the dependencies. 
 Kubernetes v1.21.13 v1.21.14 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.21.14). 
 Kubernetes add-on resizer 1.8.14 1.8.15 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.18.15). 







 Change log for worker node fix pack 1.21.14_1564, released 20 June 2022 

The following table shows the changes that are in the worker node fix pack 1.21.14_1564. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.
Change log for master fix pack 1.23.8_1534, released 22 June 2022 

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



Changes since version 1.23.7_1531

 Component Previous Current Description 

 Cluster health image v1.3.7 v1.3.8 Updated Go to version 1.17.11 and also updated the dependencies. 
 GPU device plug-in and installer 382ada9 2b0b6d1 Updated universal base image (UBI) to version 8.6-751. Updated Go to version 1.17.10. 
 IBM Cloud Controller Manager v1.23.7-4 v1.23.7-7 Update module github.com/IBM/vpc-go-sdk to v0.20.0. Update module github.com/stretchr/testify to v1.7.2. 
 Key Management Service provider v2.5.5 v2.5.6 Updated Go to version 1.17.11 and also updated the dependencies. 
 Kubernetes v1.23.7 v1.23.8 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.23.8). 
 Kubernetes add-on resizer 1.8.14 1.8.15 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.18.15). 







 Change log for worker node fix pack 1.23.8_1534, released 20 June 2022 

The following table shows the changes that are in the worker node fix pack 1.23.8_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.23.7_1532

 Component Previous Current Description
* [Adding worker nodes and zones to clusters](https://cloud.ibm.com/docs/containers?topic=containers-add_workers)
* [Removing clusters](https://cloud.ibm.com/docs/containers?topic=containers-remove)
* [Changing service endpoints or VLAN connections](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_cluster)



Cluster version updates
: Updated the [unsupported versions policy](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions) to note that you can't update clusters if the master version is three or more versions behind the oldest supported version. You can view if the cluster is unsupported by reviewing the State field when you list clusters.

Istio
: Updated the [Istio page](https://cloud.ibm.com/docs/containers?topic=containers-istio) to remove the limitation that Istio does not work in clusters that are connected to a private VLAN only. Added a step to the [Updating managed add-ons topic](https://cloud.ibm.com/docs/containers?topic=containers-managed-addonsupdating-managed-add-ons) to re-create Istio gateways that use TLS sections after the update of the Istio managed add-on is complete.

Popular topics
: Replaced the popular topics with this release notes page for new features and updates that are specific to Kubernetes Service. For the latest information on IBM Cloud products, check out the [Announcements](https://www.ibm.com/cloud/blog/announcements).





 20 May 2019 

Version change logs
: Added [worker node fix pack change logs](https://cloud.ibm.com/docs/containers?topic=containers-changelog).





 16 May 2019 

CLI reference
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. 
 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)([https://github.com/etcd-io/etcd/releases/v3.3.1](https://github.com/etcd-io/etcd/releases/v3.3.1)]{: external}. 
 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). 







 Change log for worker node fix pack 1.11.3_1531, released 26 October 2018 

The following table shows the changes that are in the worker node fix pack 1.11.3_1531.



Changes since version 1.11.3_1525

 Component Previous Current Description 

 OS interrupt handling N/A N/A Replaced the interrupt request (IRQ) system daemon with a more performant interrupt handler. 







 Change log for master fix pack 1.11.3_1527, released 15 October 2018
If no worker update is available, you must [reload the worker nodes manually](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli). If you reload, be sure to cordon, drain, and manage the order to control the maximum number of worker nodes that are unavailable at a time.

ibmcloud ks worker update --cluster <cluster_name_or_ID> --worker <worker1,worker2>
7. Optional: To use the private cloud service endpoint only,



1. Disable the public cloud service endpoint.

ibmcloud ks cluster master public-service-endpoint disable --cluster <cluster_name_or_ID>
2. [Set up access to the master on the private cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_clusteraccess_private_se).









 Changing your worker node VLAN connections 

When you create a cluster, you choose whether to connect your worker nodes to a private and a public VLAN or to a private VLAN only. Your worker nodes are part of worker pools, which store networking metadata that includes the VLANs to use to provision future worker nodes in the pool. You might want to change your cluster's VLAN connectivity setup later, in cases such as the following.



* The worker pool VLANs in a zone run out of capacity, and you need to provision a new VLAN for your cluster worker nodes to use.
* You have a cluster with worker nodes that are on both public and private VLANs, but you want to change to a [private-only cluster](https://cloud.ibm.com/docs/containers?topic=containers-plan_basicsprivate_clusters).
* You have a private-only cluster, but you want some worker nodes such as a worker pool of [edge nodes](https://cloud.ibm.com/docs/containers?topic=containers-edgeedge) on the public VLAN to expose your apps on the internet.



Trying to change the service endpoint for master-worker communication instead?
Change log for master fix pack 1.26.5_1537, released 23 May 2023 

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



Changes since version 1.26.4_1535

 Component Previous Current Description 

 Cluster health image v1.3.19 v1.3.20 Updated Go to version 1.19.9 and updated dependencies. Updated the base image. Resolved add-on health bugs. 
 etcd v3.5.7 v3.5.8 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.5.8). 
 GPU device plug-in fc4cf22 28d80a0 Updated Go to version 1.19.8 
 IBM Cloud Controller Manager v1.26.4-1 v1.26.4-7 Updated support of the Kubernetes 1.26.4 release. Updated Go dependencies. Key rotation. 
 IBM Cloud RBAC Operator 778ef2b 4e2f346 Make armada-rbac-sync FIPS compliant 
 Key Management Service provider v2.6.5 v2.6.6 Updated Go to version 1.19.9 and updated dependencies. 
 Kubernetes v1.26.4 v1.26.5 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.26.5). 
 Kubernetes DNS autoscaler 1.8.6 v1.8.8 See the [Kubernetes DNS autoscaler release notes](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler/releases/tag/v1.8.8).
Review the changes included in version 1.0.3 of the managed cluster autoscaler add-on.



 Change log for patch update 1.0.3_360, released 26 August 2021 

Review the changes in version 1.0.3_360 of the cluster autoscaler add-on.



* Image tags: 1.17.4-5, 1.18.3-5, 1.19.1-5, 1.20.0-5, and 1.21.0-1.
* Supported cluster versions: >=4.3
* Updates the Golang version to 1.16.6 which includes a fix for PVR0281096.
* Increases the default resource requests and limits.



* Previous values:

resourcesLimitsCPU: "600m"
resourcesLimitsMemory: "600Mi"
resourcesRequestsCPU: "200m"
resourcesRequestsMemory: "200Mi"
* Updated values:

resourcesLimitsCPU: "800m"
resourcesLimitsMemory: "1000Mi"
resourcesRequestsCPU: "200m"
resourcesRequestsMemory: "400Mi"









 Change log for patch update 1.0.3_352, released 23 June 2021 

Review the changes in version 1.0.3_352 of the cluster autoscaler add-on.



* Image tags: 1.17.4-4, 1.18.3-4, 1.19.1-4, 1.20.0-4, and 1.21.0-0.
* Supported cluster versions: >=4.3
* Adds support for Kubernetes 1.21.









 Version 1.0.2 

Review the changes that are in version 1.0.2 of the managed cluster autoscaler add-on.



 Change log for patch update 1.0.2_267, released 10 May 2021 

Review the changes in version 1.0.2_267 of the cluster autoscaler add-on.



* Image tags: 1.17.4-3, 1.18.3-3, 1.19.1-3, and 1.20.0-3.
Change log for master fix pack 1.25.10_1545, released 23 May 2023 

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



Changes since version 1.25.9_1543

 Component Previous Current Description 

 Cluster health image v1.3.19 v1.3.20 Updated Go to version 1.19.9 and updated dependencies. Updated the base image. Resolved add-on health bugs. 
 etcd v3.5.7 v3.5.8 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.5.8). 
 GPU device plug-in fc4cf22 28d80a0 Updated Go to version 1.19.8 
 IBM Cloud Controller Manager v1.25.9-1 v1.25.9-7 Updated support of the Kubernetes 1.25.9 release. Updated Go dependencies. Key rotation. 
 IBM Cloud RBAC Operator 778ef2b 4e2f346 Make armada-rbac-sync FIPS compliant 
 Key Management Service provider v2.6.5 v2.6.6 Updated Go to version 1.19.9 and updated dependencies. 
 Kubernetes v1.25.9 v1.25.10 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.10). 
 Kubernetes NodeLocal DNS cache 1.22.18 1.22.21 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.22.21). 
 Portieris admission controller v0.13.4 v0.13.5 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.5).
However after the upgrade, IBM Cloud Kubernetes Service will take over management of the install. 







 Update after master 

The following table shows the actions that you must take after you update the Kubernetes master.



Changes to make after you update the master to Kubernetes 1.25

 Type Description 

 kubectl diff ignores managed fields by default The kubectl diff command was changed to ignore managed fields by default. A new --show-managed-fields option has been added to allow you to include managed fields in the diff command. If your scripts rely on the previous behavior, update them.
Changes since version 1.17.9_1533

 Component Previous Current Description 

 Cluster master operations N/A N/A Fixed a problem that might cause pods to fail authentication to the Kubernetes API server after a cluster master operation. 
 IBM Cloud File Storage for Classic plug-in and monitor 375 376 Updated to use Go version 1.13.8. 







 Change log for master fix pack 1.17.9_1533, released 20 July 2020 

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



Changes since version 1.17.7_1530

 Component Previous Current Description 

 GPU device plug-in and installer 31d4bb6 8c24345 Updated image for [CVE-2017-12133](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12133), [CVE-2017-18269](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18269), [CVE-2018-11236](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11236), [CVE-2018-11237](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11237), [CVE-2018-19591]
Changes since version 1.18.6_1521

 Component Previous Current Description 

 Cluster master operations N/A N/A Fixed a problem that might cause pods to fail authentication to the Kubernetes API server after a cluster master operation. 
 IBM Cloud File Storage for Classic plug-in and monitor 375 376 Updated to use Go version 1.13.8. 







 Change log for master fix pack 1.18.6_1521, released 20 July 2020 

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



Changes since version 1.18.4_1518

 Component Previous Current Description 

 GPU device plug-in and installer 31d4bb6 8c24345 Updated image for [CVE-2017-12133](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12133), [CVE-2017-18269](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18269), [CVE-2018-11236](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11236), [CVE-2018-11237](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11237), [CVE-2018-19591]
If KMS was enabled before this version, [update your cluster](https://cloud.ibm.com/docs/containers?topic=containers-update) to at least version 1.19.4_1527 and then [reenable KMS encryption](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkeyprotect) with a new root key. If you are unsure when KMS was enabled, log in to the IBM Cloud console and click on your KMS instance under [Resources](https://cloud.ibm.com/resources). Find your root key and click the Actions icon ![Action menu icon](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/icons/action-menu-icon.svg) > Key associated resources. If a CRN number is listed for your root key, then you do not need to upgrade your cluster.



* Enable the cluster to use root keys to encrypt secrets.
* Cluster secrets are automatically updated after rotating root keys. Note For versions before 1.19.4_1527, you must rewrite cluster secrets manually after rotating root keys. You can rewrite secrets by using the kubectl get secrets --all-namespaces -o json | kubectl replace -f - command.
* You can view clusters that use the root key from the KMS provider interface.
* Clusters automatically respond if you disable, enable, or restore root keys.
* Disabling a root key restricts cluster functionality until you reenable the key.
* Deleting a root key makes the cluster unusable and unrecoverable.
* Root keys can't be deleted if the key is used by a cluster.









 Encrypting the Kubernetes secrets by using a KMS provider 

Virtual Private Cloud

Classic infrastructure