vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Changes since version 1.15.12_1547

 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.15.12_1547, released 20 July 2020 

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



Changes since version 1.15.12_1544

 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 you have a vSAN cluster, you must update the vSAN license. Contact [IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support) to obtain the new licenses for vSphere 7.



 Procedure to update the vCenter Server license 

Complete the following steps from the vCenter Server user interface.



1. Select Administration menu > Licensing > Licenses.
2. From the Licenses page, click + Add New Licenses.
3. Enter the new vCenter Server 7.0 license key in the New Licenses field. Then, enter a name for the license and click OK.
4. From the Assets page, select the vCenter instance under VCENTER SERVER SYSTEMS and click Assign License. Then, select the new license and click OK.
5. From the Licenses page, find the license with the product name VMware vCenter Server 6 Standard and click Remove Licenses.







 Procedure to update ESXi host licenses 



1. From the Licenses page, click + Add New Licenses.
2. Enter the new vSphere 7 license keys in the New Licenses field. If you have multiple vSphere 7 license keys, input the all of the licenses in the New Licenses filed, enter a name for each license, and click OK.
3. Complete the following steps from the Assets page.



1. Select HOSTS.
2. Select the host and click Assign License.
3. Select one of the new vSphere 7 license keys and click OK.
4. Repeat this step for each upgraded host.



4. From the Licenses page, select all of the old vSphere 6 licenses and click Remove Licenses.







 Procedure to update the vSAN cluster license 



1. From the Licenses page, click + Add New Licenses.
2. Enter the new vSAN license keys in the New Licenses field. If you have multiple vSAN license keys, enter all the licenses in the New Licenses field, specify a name for each license, and then click OK.
3. Complete the following steps from the Assets page.



1.
Change log for master fix pack 1.18.15_1538, released 19 January 2021 

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



Changes since version 1.18.14_1537

 Component Previous Current Description 

 Cluster health image v1.1.14 v1.1.16 Updated image to implement additional IBM security controls. 
 Gateway-enabled cluster controller 1184 1195 Updated image for [CVE-2020-1971](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1971). 
 GPU device plug-in and installer c26e2ae af5a6cb Updated image for [CVE-2021-3114](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3114), [CVE-2021-3115](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3115), [CVE-2020-27350](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27350), [CVE-2020-29361](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29361), [CVE-2020-29362
: Master patch updates are available for Kubernetes [1.15.5_1520](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog1155_1520), [1.14.8_1536](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1148_1536), [1.13.12_1539](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog11312_1539), and Red Hat OpenShift [3.11.146_1528_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311146_1528).





 14 October 2019 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 0.4.38](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog).

Cloud Paks
: By using the IBM Cloud catalog, you can [add Cloud Paks to your Red Hat OpenShift clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_cloud_paks).

Cluster autoscaler
: You can [install the cluster autoscaler](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-classic-vpc) Helm chart on Red Hat OpenShift clusters with Helm Tiller version 2.12 or later.

Let's Encrypt rate limits for Ingress
: Added troubleshooting steps for when no subdomain or secret is generated for the Ingress ALB when you create or delete clusters of the same name.

Version change logs
After you update from a deprecated to a supported version, your cluster can resume normal operations and continue receiving support. You can find out whether your cluster is unsupported by reviewing the State field in the output of the ibmcloud ks cluster ls command or in the [IBM Cloud Kubernetes Service console](https://cloud.ibm.com/kubernetes/clusters).





 Preparing to update 

Updating a cluster to a new version from the previous version is likely to have an impact on deployed apps. For a complete list of changes, review the [community Kubernetes change logs](https://github.com/kubernetes/kubernetes/tree/master/CHANGELOG), [IBM version change logs](https://cloud.ibm.com/docs/containers?topic=containers-changelog), and [Kubernetes helpful warnings](https://kubernetes.io/blog/2020/09/03/warnings/).

For actions you should take before and after updating your cluster, see the version information links in [Available IBM Cloud® Kubernetes Service versions](https://cloud.ibm.com/docs/containers?topic=containers-changelogcs_versions_available).





 Archive 

Unsupported clusters are not provided with security and patch updates and are not supported by IBM Cloud Support. Although your cluster and apps might continue to run for a time, you can no longer create, reload, or take other corrective actions on your cluster master or worker nodes when an issue occurs. You can still delete the cluster or worker nodes, or update the cluster to the next version. Review the potential impacts and immediately [update the cluster](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) to continue receiving important security updates and support.
To update the CRN, use the ibmcloud ks ingress secret update command. If you do not update the CRN, these secrets do not update at the next scheduled certificate renewal.

ibmcloud ks ingress instance default set --cluster CLUSTER --crn CRN --name NAME [-q] [--secret-group GROUP]

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.

--crn
: Required. The CRN of the IBM Cloud Secret Manager instance.

--name NAME
: Required. The name of the Secret Manager instance.

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

--secret-group GROUP
: Secret group ID of the IBM Cloud Secret Manager instance where the secrets are persisted. To get a secret group ID, see the [Secrets Manager CLI reference](https://cloud.ibm.com/docs/secrets-manager-cli-plugin?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-cli-secret-groups-command).

Example:

ibmcloud ks ingress instance default set --cluster --cluster a111aaa11a1aaaaaaa1 --crn crn:v1:staging:public:secrets-manager:eu-gb:a/1a11a1a111aa11aa111aa1a1111aa1a1:1aaa1a1a-aaaa-11aa-1a11-a11aaa1a11a1:secret:a1a11a11-111a-11a1-aa11-11aaa1a11a11 --name my-secret-manager --namespace default --secret-group 90e059dd-d04e-a32b-010f-4d303b9050b8





 ibmcloud ks ingress instance default unset 

Virtual Private Cloud

Classic infrastructure

Remove a Secrets Manager instance as the default instance.
To see available versions, run [ibmcloud ks versions](https://cloud.ibm.com/docs/cli?topic=cli-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).
PATCH/v1/clusters/{idOrName}/addons Enable, disable, or update add-ons for a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.update 
 PATCH/v1/clusters/{idOrName}/subnets/{subnetId} Detach a public or private portable subnet from a cluster. containers-kubernetes.cluster.operate 
 POST/v1/clusters Create a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.create 
 POST/v1/clusters/{idOrName}/kms Create a key management service (KMS) provider configuration for a cluster. containers-kubernetes.cluster.create containers-kubernetes.account.update 
 POST/v1/clusters/{idOrName}/services Bind an IBM Cloud service to a cluster. containers-kubernetes.cluster.update containers-kubernetes.service.create 
 POST/v1/clusters/{idOrName}/usersubnets Add an existing user-managed subnet to a cluster. containers-kubernetes.cluster.operate containers-kubernetes.subnet.create 
 POST/v1/clusters/{idOrName}/vlans/{vlanId} Create an IBM Cloud infrastructure subnet and add it to an existing cluster. containers-kubernetes.cluster.create containers-kubernetes.vlan.create 
 POST/v1/clusters/{idOrName}/webhooks Add a webhook to a cluster. containers-kubernetes.cluster.update containers-kubernetes.cluster.create 
 POST/v2/applyRBACAndGetKubeconfig Apply IAM roles to the cluster, then retrieve the cluster's kubeconfig file. Optionally include the network configuration file. containers-kubernetes.cluster.create containers-kubernetes.cluster.update 
 POST/v2/autoUpdateMaster Set the autoupdate status of the cluster master.
Before you run this 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 the old CA certificates is updated to use the new certificates and to update your worker nodes.

ibmcloud ks cluster ca rotate --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 rotate command 

ibmcloud ks cluster ca rotate --cluster my_cluster







 ibmcloud ks cluster ca status 

Virtual Private Cloud

Classic infrastructure

After you run [ibmcloud ks cluster ca rotate](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_cluster_ca_rotate), view the rotation status of certificate authority (CA) certificates for a cluster.

ibmcloud ks cluster ca status --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 ca status command 

ibmcloud ks cluster ca status --cluster my_cluster







 ibmcloud ks cluster config 

Virtual Private Cloud

Classic infrastructure

After logging in to IBM Cloud, download the Kubernetes configuration data and certificates as a kubeconfig file to your local machine so that you can connect to your cluster and run kubectl commands.
: You can create or [update clusters to Kubernetes version 1.25](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_125). With Kubernetes 1.25, you get the latest stable enhancements from the Kubernetes community as well as enhancements to the IBM Cloud product.

Master fix pack
: Kubernetes [1.25.2_1517](https://cloud.ibm.com/docs/containers?topic=containers-changelog_125).

Worker node fix pack
: Kubernetes [1.25.2_1516](https://cloud.ibm.com/docs/containers?topic=containers-changelog_125)





 4 October 2022 

Istio add-on
: Version [1.14.4](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1144) and version [1.13.8](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1138) are available.





 3 October 2022 

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

Ingress ConfigMap change log updates
: Updated the [Ingress ConfigMap change log](https://cloud.ibm.com/docs/containers?topic=containers-ibm-k8s-controller-config-change-log).

Ingress ALB change log updates
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog) for versions 1.2.1_2646_iks and 1.1.2_2645_iks.

ALB OAuth Proxy add-on
Change log for master fix pack 1.25.6_1529, released 30 January 2023 

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



Changes since version 1.25.5_1525

 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 Cloud Block Storage driver and plug-in v2.3.4 v2.3.6 Updated UBI images to 8.7-1031 
 IBM Calico extension 1257 1280 Publish s390x image. 
 IBM Cloud Controller Manager v1.25.4-2 v1.25.6-2 Updated to support the Kubernetes 1.25.6 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).
5. [Create a configmap](https://cloud.ibm.com/docs/containers?topic=containers-updateworker-up-configmap) to control the maximum number of worker nodes that can be unavailable at a time in your cluster. When you update your worker nodes, the ConfigMap helps prevent downtime for your apps as the apps are rescheduled orderly onto available worker nodes.
6. Update all the worker nodes in your cluster to pick up the private cloud service endpoint configuration.

By issuing the update command, the worker nodes are reloaded to pick up the service endpoint configuration. 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. If the cluster is in an environment behind a firewall:



* [Allow your authorized cluster users to run kubectl commands to access the master through the private cloud service endpoint.](https://cloud.ibm.com/docs/containers?topic=containers-firewall)
* [Allow outbound network traffic to the private IPs](https://cloud.ibm.com/docs/containers?topic=containers-firewallfirewall_outbound) for infrastructure resources and for the IBM Cloud services that you plan to use.



8. Optional: To use the private cloud service endpoint only:



1. [Disable the public cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_clusterdisable-public-se).
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).
If you want to update from Portworx 2.11 to version 2.12, follow the migration steps in the [Portworx documentation](https://docs.portworx.com/operations/operate-kubernetes/migrate-daemonset/).

Cluster autoscaler add-on version 1.0.7_883.
: For more information, see [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).







 October 2022 



 27 October 2022 

Master fix pack 4.6.61_1605_openshift, 4.7.59_1587_openshift, 4.8.51_1578_openshift, 4.9.49_1561_openshift, 4.10.36_1541_openshift, and 4.11.8_1528_openshift.
: For more information, see the change logs: [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.8](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.7](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_47), [4.6](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_46).
[Update Ordering service consortium member](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/del-add-node.png)

Figure 10. Ordering service admin MSP update







 Step six: Update ordering service admin on ordering service system channel 

If your cluster does not use a system channel, skip this step. To verify if a cluster uses a system channel, click the cluster tile and check the Orderer Type.

If the updated certificate is for the ordering service MSP admin, you need to update the ordering service.



1. From the Nodes tab, open the ordering service tile.
2. Under Ordering service administrators click the Settings icon on the ordering service organization MSP tile.

Zoom

![Ordering service admin MSP update](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/os-msp-gear-icon.png)

Figure 11. Ordering service admin MSP update
3. From the Existing MSP ID tab, select the MSP that needs to be updated and then select the original identity to sign the request. You must use the original identity for this step because it's the only one with permission to make channel updates. This action replaces the existing MSP definition for the ordering service admin with the updated MSP with the new admin certificate.







 Step seven: Update orderer organization MSP on channel 

Similar to step four, this update needs to be performed by a channel operator and the change will follow the channel update approval process according to the policy that was configured when the channel was created.

If the orderer organization MSP was not originally created with the Node OU configuration enabled, you also need to update all application channels that include the MSP so that it will use the new admin certificate.
The following table shows the changes that are in the master fix pack patch update 1.18.14_1537. Master patch updates are applied automatically.



Changes since version 1.18.13_1535

 Component Previous Current Description 

 IBM Calico extension 544 556 Updated image to include the ip command. 
 IBM Cloud Controller Manager v1.18.13-1 v1.18.14-1 Updated to support the Kubernetes 1.18.14 release. 
 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). 
 Key Management Service provider v2.0.7 v2.2.2 Updated the key management service (KMS) provider support as follows.<br><br><br><br> * Updated to use Go version 1.15.2.<br> * Added support for [service-to-service authentication](https://cloud.ibm.com/docs/account?topic=account-serviceauth).<br> * Updated to use the KMS provider secret to identify when a [Key Protect](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkeyprotect) key is enabled and disabled so that encryption and decryption requests are updated accordingly.<br><br><br> 
 Kubernetes v1.18.13 v1.18.14 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.14). 
 Kubernetes NodeLocal DNS cache N/A N/A Updated to run with a least privileged security context.
: You can create or (/docs/containers?topic=containers-cs_versions_121)update your cluster to Kubernetes version 1.21. With Kubernetes 1.21, you get the latest stable enhancements from the community, such as stable CronJob, EndpointSlice, and PodDisruptionBudget resources. You also get enhancements to the IBM Cloud product, such as a refreshed user interface experience. For more information, see the [blog announcement](https://www.ibm.com/cloud/blog/announcements/kubernetes-version-121-now-available-in-ibm-cloud-kubernetes-service).

Deprecated Kubernetes 1.18
: With the release of Kubernetes 1.21, clusters that run version 1.18 are deprecated, with a tentative unsupported date of 10 October 2021. Update your cluster to at least [version 1.19](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_119) as soon as possible.

Expanded Troubleshooting
: You can now find troubleshooting steps for IBM Cloud persistent storage in the following pages.



* [File Storage for Classic](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_storage_file)
* [Block Storage for Classic](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_storage_block)
* [Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_storage_cos)
* [Portworx](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_storage_px)







 07 June 2021 

Worker node versions