vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Change log for 1.14.10_1545, released 20 January 2020 

The following table shows the changes that are in the master and worker node patch update 1.14.10_1545. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).



Changes since version 1.14.9_1544

 Component Previous Current Description 

 Cluster master HA Proxy 1.8.21-alpine 1.8.23-alpine See the [HAProxy release notes](https://www.haproxy.org/download/1.8/src/CHANGELOG). Update resolves [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). 
 etcd v3.3.17 v3.3.18 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.18). Update resolves [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). 
 GPU device plug-in and installer f2e7bd7 da19df3 Updated image for [CVE-2019-13627](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13627) and [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). Updated the GPU drivers to version [440.44](https://www.nvidia.com/Download/driverResults.aspx/156086/).
Use the same version of Helm that you used to install the initial Helm chart and release.

Before you begin, see the [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-helmca_helm_up_prereqs).



1. Update the Helm repo to retrieve the latest version of all Helm charts in this repo.

helm repo update
2. Optional: Download the latest Helm chart to your local machine. Then, extract the package and review the release.md file to find the latest release information.

helm pull iks-charts/ibm-iks-cluster-autoscaler
3. Find the name of the cluster autoscaler release that you installed in your cluster.

helm list -n <namespace> | grep cluster-autoscaler

Example output

myhelmchart 1 Mon Jan 7 14:47:44 2022 DEPLOYED ibm-iks-cluster-autoscaler-1.0.1 kube-system
4. Upgrade the cluster autoscaler release to the latest version.

helm upgrade --force --recreate-pods <helm_chart_name> iks-charts/ibm-iks-cluster-autoscaler
5. Verify that the [cluster autoscaler configmap](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-enable)workerPoolsConfig.json section is set to "enabled": true for the worker pools that you want to scale.

kubectl describe cm iks-ca-configmap -n kube-system

Example output

NAME: iks-ca-configmap
Namespace: kube-system
Labels: <none>
Ubuntu 18.04 packages 4.15.0-158 4.15.0-159 Updated worker node images and kernel with package updates [CVE-2021-3778](https://nvd.nist.gov/vuln/detail/CVE-2021-3778) and [CVE-2021-3796](https://nvd.nist.gov/vuln/detail/CVE-2021-3796). 







 Change log for master fix pack 1.22.2_1522 and worker node fix pack 1.22.2_1523, released 29 September 2021 

The following table shows the changes that are in the master fix pack 1.22.2_1522 and the worker node fix pack patch update 1.22.2_1523. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.21.5_1531 (master) and 1.21.5_1532 (worker node).

 Component Previous Current Description 

 Calico v3.19.3 v3.20.1 See the [Calico release notes](https://docs.tigera.io/archive). 
 containerd configuration N/A N/A Cluster administrators may now update the containerd registry host configurations on their clusters. See [Updating your cluster's containerd registry host configuration](https://cloud.ibm.com/docs/containers?topic=containers-registryupdate_containerd_registry_config) and the [containerd CRI plugin configuration guide](https://github.com/containerd/containerd/blob/v1.5.5/docs/cri/config.mdregistry-configuration). 
 IBM Cloud Controller Manager v1.21.5-1 v1.22.2-1 Updated to support the Kubernetes 1.22.2 release. In addition, the code for this component is now [open source](https://github.com/IBM-Cloud/cloud-provider-ibm).
Change log for master fix pack 1.24.2_1526, released 22 June 2022 

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



Changes since version 1.24.1_1523

 Component Previous Current Description 

 IBM Cloud Block Storage driver and plug-in v2.2.4 v2.2.6 Bug fixes for the driver installation. Block plugin base images were updated to ubi: 8.6-751.1655117800 for CVE-2022-1271 
 Kubernetes v1.24.1 v1.24.2 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.2). 
 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.24.2_1526, released 20 June 2022 

The following table shows the changes that are in the worker node fix pack 1.24.2_1526. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.1_1522

 Component Previous Current Description
This process continues until the rollout is complete and all 10 replicas run the new version.

If you want to perform a blue-green instantaneous switch style update, set the maxSurge to 100%. The deployment creates all the new required replicas, then scales down the old version replicas to 0.
3. [Roll out](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/updating-a-deployment) a change. For example, you might want to change the image that you used in your initial deployment.



1. Get the deployment name.

oc get deployments
2. Get the pod name.

oc get pods
3. Get the name of the container that runs in the pod.

oc describe pod <pod_name>
4. Set the new image for the deployment to use.

oc set image deployment/<deployment_name><container_name>=<image_name>



When you run the commands, the change is immediately applied and logged in the roll-out history.
4. Check the status of your deployment.

oc rollout status deployments/<deployment_name>

If you notice something in the status that you want time to follow up on, you can pause and resume your rollout with the following commands.

oc rollout pause deployment <deployment_name>

oc rollout resume deployment <deployment_name>
5. Roll back a change.



1. View the roll-out history for the deployment and identify the revision number of your last deployment.

oc rollout history deployment/<deployment_name>

Tip: To see the details for a specific revision, include the revision number.

oc rollout history deployment/<deployment_name> --revision=<number>
2. Roll back to the previous version, or specify a revision. To roll back to the previous version, use the following command.

oc rollout undo deployment/<depoyment_name> --to-revision=<number>









 Setting up continuous integration and delivery
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)



1. Make sure that your worker node applies the latest patch for your minor version to run your worker node with the latest security settings. The patch version also ensures that the root password on the worker node is renewed.

If you did not apply updates or reload your worker node within the last 90 days, your root password on the worker node expires and the installation of the storage plug-in might fail.



1. List the current patch version of your worker nodes.

ibmcloud ks worker ls --cluster <cluster_name_or_ID>

Example output

OK
ID Public IP Private IP Machine Type State Status Zone Version
kube-dal10-crb1a23b456789ac1b20b2nc1e12b345ab-w26 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16.encrypted normal Ready dal10 1.26_1523

If your worker node does not apply the latest patch version, you see an asterisk () in the Version column of your CLI output.
2. Review the [version change log](https://cloud.ibm.com/docs/containers?topic=containers-changelog) to find the changes that are in the latest patch version.
3. Apply the latest patch version by reloading your worker node. Follow the instructions in the [ibmcloud ks worker reload command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) to safely reschedule any running pods on your worker node before you reload your worker node. Note that during the reload, your worker node machine is updated with the latest image and data is deleted if not [stored outside the worker node](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan).
Cluster version <br><br> * Provide a suite of tools to automate cluster management, such as the IBM Cloud Kubernetes Service [API](https://containers.cloud.ibm.com/global/swagger-global-api//), [CLI plug-in](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli), and [console](https://cloud.ibm.com/kubernetes/clusters).<br> * Automatically apply Kubernetes master patch OS, version, and security updates.<br> * Make major and minor updates for master nodes available for you to apply.<br> * Provide worker node major, minor, and patch OS, version, and security updates.<br> * Fulfill automation requests to update cluster master and worker nodes.<br><br><br> <br><br> * Use the API, CLI, or console tools to [apply](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) the provided major and minor Kubernetes master updates and major, minor, and patch worker node updates.<br><br><br> 







 Identity and access management 

You and IBM share responsibilities for controlling access to your IBM Cloud Kubernetes Service instances. For IBM Cloud® Identity and Access Management responsibilities, consult that product's documentation. You are responsible for identity and access management to your application data.



Table 4. Responsibilities for identity and access management

 Resource IBM responsibilities Your responsibilities 

 Observability <br><br> * Provide the ability to integrate IBM Cloud Activity Tracker with your cluster to audit the actions that users take in the cluster.<br><br><br> <br><br> * Set up IBM Cloud Activity Tracker or other capabilities to track user activity in the cluster.<br><br><br> 







 Security and regulation compliance 

IBM is responsible for the security and compliance of IBM Cloud Kubernetes Service. Compliance to industry standards varies depending on the infrastructure provider that you use for the cluster, such as classic or VPC.
Updating vSAN clusters 

vSAN™ generates system baselines and baseline groups for use with VMware® Update Manager (VUM) and you can use these recommended baselines to update software, patches, and extensions for the vSphere® ESXi™ hosts in your VMware vCenter Server® instance using vSAN. vSAN 6.6.1 and later generates automated build recommendations for vSAN clusters. vSAN combines information in the VMware Compatibility Guide and vSAN Release catalog with information about the installed vSphere ESXi releases.

These recommended updates provide the best available release to keep your hardware in a supported state.



* vSAN System Baselines - vSAN build recommendations are provided through vSAN system baselines for VUM. vSAN generates one baseline group for each vSAN cluster and are listed in the Baselines pane of the Baselines and Groups tab. VUM automatically scans each vSAN cluster to check compliance against the baseline group. However, to upgrade your vSAN cluster, you must manually remediate the system baseline through VUM you can remediate vSAN system baseline on a single host or on the entire cluster.
* vSAN Release catalog - The vSAN release catalog maintains information about available releases, preference order for releases, and critical patches needed for each release. vSAN requires internet connectivity to access the release catalog. You don't need to be enrolled in the Customer Experience Improvement Program (CEIP) for vSAN to access the release catalog.
* Working with vSAN Build Recommendations - VUM checks the installed vSphere ESXi releases against information in the Hardware Compatibility List (HCL) in the VMware Compatibility Guide. It determines the correct upgrade path for each vSAN cluster, based on the current vSAN Release catalog. vSAN also includes the necessary drivers and patch updates for the recommended release in its system baseline. vSAN build recommendations ensure sure that each vSAN cluster remains at the current hardware compatibility status or better. If hardware in the vSAN cluster is not included on the HCL, vSAN recommends an upgrade to the latest release.



The vSAN cluster upgrade proceeds in the following sequence of tasks:
: Updated the version of the Istio managed add-on to 1.1.7 and the Knative managed add-on to 0.6.0.

Removing persistent storage
: Updated the information for how you are billed when you delete persistent storage.

Service bindings with private endpoint
: [Added steps](https://cloud.ibm.com/docs/containers?topic=containers-service-binding) for how to manually create service credentials with the private cloud service endpoint when you bind the service to your cluster.

Version change logs
: Updated the change logs for [1.14.3_1523](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1143_1523), [1.13.7_1526](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog1137_1526), [1.12.9_1557](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog1129_1557), and [1.11.10_1562] (/docs/containers?topic=containers-111_changelog11110_1562) patch updates.





 14 June 2019 

kubectl troubleshooting
: Added a [troubleshooting topic](https://cloud.ibm.com/docs/containers?topic=containers-ts_cliskubectl_fails) for when you have a kubectl client version that is 2 or more versions apart from the server version or the Red Hat OpenShift version of kubectl, which does not work with community Kubernetes clusters.

Tutorials landing page
: Replaced the related links page with a new tutorials landing page for all tutorials that are specific to Kubernetes Service.

Using existing subnets to create a cluster
Change log for 1.13.12_1548, released 20 January 2020 

The following table shows the changes that are in the master and worker node patch update 1.13.12_1548. Master patch updates are applied automatically. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).



Changes since version 1.13.12_1547

 Component Previous Current Description 

 Cluster master HA Proxy 1.8.21-alpine 1.8.23-alpine See the [HAProxy release notes](https://www.haproxy.org/download/1.8/src/CHANGELOG). Update resolves [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). 
 etcd v3.3.17 v3.3.18 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.18). Update resolves [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). 
 GPU device plug-in and installer f2e7bd7 da19df3 Updated image for [CVE-2019-13627](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13627) and [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). Updated the GPU drivers to version [440.44](https://www.nvidia.com/Download/driverResults.aspx/156086/).
Change log for 1.16.2_1514, released 4 November 2019 

The following tables show the changes that are in the patch 1.16.2_1514. If you update to this version from an earlier version, you choose when to update your cluster master and worker nodes. For more information, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types) and [Version 1.16](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive).



 Master patch 



Master patch: Changes since version 1.15.5_1520

 Component Previous Current Description 

 Calico v3.8.2 v3.9.2 See the [Calico release notes](https://docs.tigera.io/archive/v3.9/release-notes/). 
 CoreDNS 1.3.1 1.6.2 See the [CoreDNS release notes](https://coredns.io/2019/08/13/coredns-1.6.2-release/). This update includes the following configuration changes. - CoreDNS now runs 3 replica pods by default, and the pods prefer to schedule across worker nodes and zones to improve cluster DNS availability. If you update your cluster to version 1.16 from an earlier version, you can [configure the CoreDNS autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster_dnsdns_autoscale) to use a minimum of 3 pods.<br><br><br><br> * CoreDNS caching is updated to better support older DNS clients. If you disabled the CoreDNS cache plug-in, you can now re-enable the plug-in.<br> * The CoreDNS deployment is now configured to check readiness by using the ready plug-in.<br> * CoreDNS version 1.6 no longer supports the proxy plug-in, which is replaced by the forward plug-in.
The following table shows the changes that are in the master fix pack 1.16.3_1520.



Changes since version 1.16.3_1519

 Component Previous Current Description 

 Gateway-enabled cluster controller 924 1032 Support for Adding classic infrastructure servers to gateway-enabled classic clusters is now generally available (GA). In addition, the controller is updated to use Alpine base image version 3.10 and to use Go version 1.12.11. 
 IBM Calico extension N/A 130 New!: Added a Calico node init container that creates Calico private host endpoints for worker nodes. 
 IBM Cloud File Storage for Classic plug-in and monitor 353 354 Updated to support [non-root user access to an NFS file share](https://cloud.ibm.com/docs/containers?topic=containers-cs_storage_nonroot) by allocating a group ID (GID) in the storage class. 
 IBM Cloud Provider v1.16.3-94 v1.16.3-115 Updated version 1.0 and 2.0 network load balancers (NLBs) to prefer scheduling NLB pods on worker nodes that don't currently run any NLB pods. In addition, the Virtual Private Cloud (VPC) load balancer plug-in is updated to use Go version 1.12.11. 
 Key Management Service provider 254 270 Improves performance of secret management by minimizing the number of data encryption keys (DEKs) that are used to unwrap secrets in the cluster. In addition, the IBM Key Protect Go client is updated. 
 Kubernetes add-on resizer 1.8.5 1.8.7 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.8.7).
In any of these cases, you can choose to safely use the [ibmcloud ks cluster master update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update) command yourself without waiting for the update automation to apply.







 Release lifecycle 

Each supported version of IBM Cloud Kubernetes Service goes through a lifecycle of testing, development, general release, support, deprecation, and becoming unsupported. Review the descriptions of each phase of a version's lifecycle.

Estimated days and versions are provided for general understanding. Actual availability and release dates are subject to change and depend on various factors, such as community updates, security patches, and technology changes between versions.



1. Community release: The community releases the new version. IBM engineers begin testing and hardening the community version in preparation to release a supported IBM Cloud Kubernetes Service version.
2. Supported version lifecycle:

Development release
: Release is under development and might be available as a Beta to select customers. IBM provides best effort support for the release.

General availability
: Release is generally available (GA). IBM provides full support for the release. IBM provides a tentative target date for the release to be unsupported. Release will become the default version used during cluster creation once there are minimal restrictions and a reasonable adoption rate for the release.

Maintenance
: Release has entered maintenance support as defined by the Kubernetes community. IBM provides maintenance support for Kubernetes based on community policy. IBM provides full support otherwise.
3. Deprecated version: The version is deprecated. IBM provides an updated unsupported target date for the release. An unsupported countdown to this date will be provided at least 45 days before the release becomes unsupported. IBM provides minimal support for the release in alignment with the Kubernetes community. This support phase is generally the final phase before the release becomes unsupported and overrides the maintenance and extended support phases should there be any overlap. Security patch updates might not be provided.
Enable the [private cloud service endpoint](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_basicsworkeruser-master) to make your cluster master privately accessible.

To run this command:



1. Enable [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) in your IBM Cloud infrastructure account. To check whether a VRF is already enabled, use the ibmcloud account show command.
2. [Enable your IBM Cloud account to use service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint).
3. Run ibmcloud oc cluster master private-service-endpoint enable --cluster <cluster_name>.
4. Follow the prompt in the CLI to refresh the Kubernetes master API server.
5. [Reload all the worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reload) in your cluster to pick up the private endpoint configuration.



ibmcloud oc cluster master private-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 and reload worker nodes with no user prompts.



 Example cluster master private-service-endpoint enable command 

ibmcloud oc cluster master private-service-endpoint enable --cluster my_cluster







 ibmcloud oc cluster master public-service-endpoint enable 

Virtual Private Cloud

Classic infrastructure
Change log for master fix pack 1.19.6_1531, released 6 January 2021 

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



Changes since version 1.19.5_1529

 Component Previous Current Description 

 IBM Calico extension 538 556 Updated image to include the ip command. 
 IBM Cloud Controller Manager v1.19.5-1 v1.19.6-1 Updated to support the Kubernetes 1.19.6 release and to use Go version 1.15.5. 
 IBM Cloud File Storage for Classic plug-in N/A N/A Updated to run with a privileged security context. 
 IBM Cloud RBAC Operator c148a8a f859228 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). 
 Kubernetes v1.19.5 v1.19.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.19.6). 
 Kubernetes NodeLocal DNS cache N/A N/A Updated to run with a least privileged security context. 







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

The following table shows the changes that are in the worker node fix pack 1.19.5_1530. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.19.5_1529

 Component Previous Current Description