vania-janet/multiturn-rag-retrieval-data huggingface dataset:
kubectl label cm -n kube-system coredns --overwrite "ibm-cloud.kubernetes.io/deploy-zone-aware-dns-"
8. [Refresh the cluster master](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_refresh) to the delete zone-aware DNS resources.

ibmcloud ks cluster master refresh --cluster <cluster-name-or-id>
9. Watch for the refresh operation to complete by [reviewing the Master Health in the cluster details](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_get).

ibmcloud ks cluster get -c <cluster_name_or_ID>
You can subscribe to notifications to be alerted when a new update is 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/openshift?topic=openshift-updateupdate) to continue receiving important security updates and support. If your cluster master is two or more versions behind the oldest supported version, you must [make a new cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-clustersclusters) and [deploy your apps](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_app) to the new cluster.

Unsupported Red Hat OpenShift on IBM Cloud versions:
: [Archived version history](https://cloud.ibm.com/docs/openshift?topic=openshift-sitemapsitemap_archived_version_history)
On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3. If you do not see that the new NFS storage is added to the list in the cluster, check your email or view the console notifications to find more details.







 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
* [Planning for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning)
* [Requirements for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Adding clusters to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters)
* [Place a host in maintenance mode](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-8F705E83-6788-42D4-93DF-63A2B892367F.html)
To apply a version update, you must detach, reload, and reattach your host to the Satellite location. Then, you can assign the host back to the control plane or to another resource that runs in the location.

When you update control plane hosts, do not assign or remove multiple hosts at the same time as doing so may break the control plane. You must wait for a host assignment or removal to complete before assigning or removing another host.



1. Optional: [Attach](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) and [assign](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-assign-manual) extra hosts to the Satellite location control plane to handle the compute capacity while your existing hosts are updating.
2. [Remove the host that you want to update from your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove).
3. Follow the guidelines from your infrastructure provider to reload the operating system of your host.
4. [Attach the host](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) back to your Satellite location.
5. [Assign the host](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-assign-manual) back to your Satellite location control plane.



As part of the bootstrapping process, the latest images and Red Hat OpenShift version that matches the cluster master is updated for your host and SSH access to the host is removed.





 Updating the Kubernetes API Server 

To update your Kubernetes API server, run the [cluster master update](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_update) command.





 Resetting the host key 

Reset the key that the control plane uses to communicate with all the hosts in the Satellite location.
Kubernetes 1.24.2 1.24.3 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.3). 







 Change log for master fix pack 1.24.3_1531, released 26 July 2022 

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



Changes since version 1.24.2_1526

 Component Previous Current Description 

 Calico v3.23.1 v3.23.3 See the [Calico release notes](https://docs.tigera.io/archive). Updated the Calico custom resource definitions to include preserveUnknownFields: false. 
 Cluster health image v1.3.8 v1.3.9 Updated Go dependencies and to use Go version 1.18.4. Fixed minor typographical error in the add-on daemonset not available health status. 
 Gateway-enabled cluster controller 1680 1792 Updated to use Go version 1.17.11. Updated image for [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097) and [CVE-2022-29458](https://nvd.nist.gov/vuln/detail/CVE-2022-29458). 
 GPU device plug-in and installer 2b0b6d1 d8f1be0 Updated Go dependencies and to use Go version 1.18.3. 
 IBM Calico extension 980 997 Updated to use Go version 1.17.11. Updated universal base image (UBI) to version 8.6-854 to resolve CVEs. 
 IBM Cloud Block Storage driver and plug-in v2.2.6 v2.2.8 Updated to use Go version 1.18.3. Updated universal base image (UBI) to version 8.6-854 to resolve CVEs.
: Refreshed [networking diagrams for VPC scenarios](https://cloud.ibm.com/docs/containers?topic=containers-service-archarchitecture_vpc).

VPC cluster master access
: Updated [accessing the master via a private cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-access_clustervpc_private_se) for VPC clusters.





 27 April 2020 

Ingress ALB change log
: Updated the [ingress-auth image build to 401](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).

Version change logs
: Kubernetes [1.17.5_1523](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1175_1523), [1.16.9_1530](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog1169_1530), [1.15.11_1537](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11511_1537), and [1.14.10_1553](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog11410_1553)





 23 April 2020 

Version change logs
IBM Cloud Controller Manager Master v1.18.2-3 v1.18.3-1 Updated to support the Kubernetes 1.18.3 release. 
 IBM Cloud File Storage for Classic plug-in and monitor Master 371 373 Image updated for [CVE-2020-11655](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11655). 
 Kubernetes Both v1.18.2 v1.18.3 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.3). 
 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.12 1.15.13 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.15.13). Updated the node-local-dns daemon set to include the prometheus.io/port and prometheus.io/scrape annotations on the pods. 
 Load balancer and load balancer monitor for IBM Cloud Provider Master 207 211 Updated the version 2.0 network load balancers (NLB) to clean up unnecessary IPVS rules.
Component Location Previous Current Description 

 Cluster health image Master N/A N/A Cluster health status now includes links to IBM Cloud documentation. 
 IBM Cloud Controller Manager Master v1.17.3-1 v1.17.4-1 Updated to support the Kubernetes 1.17.4 release and to use Go version 1.13.8. Fixed VPC load balancer error message to use the current IBM Cloud Kubernetes Service plug-in CLI syntax. 
 Kubernetes Both v1.17.3 v1.17.4 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.17.4). 
 Load balancer and load balancer monitor for IBM Cloud Provider Master 169 177 Version 2.0 network load balancers (NLB) were updated to fix problems with long-lived network connections to endpoints that failed readiness probes. 
 Operator Lifecycle Manager Catalog Master v1.5.9 v1.5.11 See the [Operator Lifecycle Manager Catalog release notes](https://github.com/operator-framework/operator-registry/releases/tag/v1.5.11).
Change log for master fix pack 1.22.11_1556, released 22 June 2022 

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



Changes since version 1.22.10_1553

 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.22.10-1 v1.22.10-3 Update prometheus/client_golang@v1.11.0 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.22.10 v1.22.11 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.22.11). 
 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.22.11_1556, released 20 June 2022 

The following table shows the changes that are in the worker node fix pack 1.22.11_1556. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.
For the latest version of the cluster autoscaler, [install the add-on](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-install-addon). You can not have both the cluster autoscaler Helm chart and the cluster autoscaler add-on installed at the same time.

You can upgrade your existing cluster autoscaler release to the latest version of the Helm chart. To check your current release version, run helm list -n <namespace> | grep cluster-autoscaler. Compare your version to the latest available release by reviewing the Chart Version in the [IBM Cloud Helm Catalog](https://cloud.ibm.com/kubernetes/helm/iks-charts/ibm-iks-cluster-autoscaler).



 Prerequisites 

Before you begin to upgrade your cluster autoscaler release, complete the following steps.

This topic applies only to the cluster autoscaler Helm chart.



1. [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)
2. To review the change log of chart versions, [download the source code tar file](https://cloud.ibm.com/kubernetes/helm/iks-charts/ibm-iks-cluster-autoscaler) and open the RELEASENOTES.MD file.







 Upgrading the cluster autoscaler release version 

This topic applies only to the cluster autoscaler Helm chart.

To upgrade your cluster autoscaler release, you can update the Helm chart repo and re-create the cluster autoscaler pods. 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.
After updating your Certificate Authority (CA) nodes, update your orderer nodes, as follows:



1. Using your console, navigate to the ordering service and select the first ordering node. Click on upgrade available and select 2.2.10-2 or later. Click through the confirmations dialogs.
2. The node will restart using the 2.2.10-2 (or selected) image. Transaction processing will continue during the node restart, because the remaining four orderer nodes make a quorum. The selected orderer node will be unavailable for 1-2 minutes during the update. ATTENTION!!: If the updating orderer node does not restart and come back online successfully, please contact IBM Support. DO NOT attempt to update any remaining orderer nodes before contacting IBM Support.
3. Repeat the procedure for each remaining orderer node.







 Update your peers 

After updating both your Certificate Authority (CA) and orderer nodes, update your peer nodes, as follows:

ATTENTION!!: When creating new v2.2 peers using the steps below, selecting 2.2.10-2 is highly recommended - other selectable versions may have chaincode implications.



1. Before upgrading any peer with CouchDB installed, you must rebuild the CouchDB state database from CouchDB v2.x to v3.x. The recommended process is to add a new peer, and then let the database synchronize. This removes the downtime that would occur when upgrading in place. Then continue as follows, for peers both with and without CouchDB:
2. Add a new peer using your console. Do NOT install chaincode on the new peer.
3. Remove the new peer from both peer gossip and service discovery, as follows:

a) Get the Custom Resource Definition (CRD) of the new peer, by running:

kubectl get ibppeer -n [NAMESPACE]

b) Back up the CRD: kubectl get ibppeer [IBPPEER_NAME] -n [NAMESPACE] -o yaml > ibppeer_crd_backup.yaml
Upgrading using IBM Cloud Catalog 

After Data Security Broker is installed on your cluster, you can upgrade it at any time using the IBM Cloud Schematics workspace ([https://cloud.ibm.com/schematics/workspaces](https://cloud.ibm.com/schematics/workspaces))



 Pre-requisite: 

The user must be aware of the workspace name which is provided during the Data Security Broker Manager and Data Security Broker Shield installation process.





 Upgrading Data Security Broker Manager: 

Log into IBM Cloud Schematics workspace and follow the steps below to upgrade the Data Security Broker Manager version:



1. Search for the workspace name that you provided during the Data Security Broker Manager install and click on the workspace to open it.

Zoom

![IBM Schematicss Workspace](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/schematics_workspace.svg)

IBM Schematicss Workspace
2. Click Settings option in the left navigation.

Zoom

![Data Security Broker Manager Upgrade](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/manager_update.svg)

Data Security Broker Manager Upgrade
3. If the new version is available for the Data Security Broker Manager, then the Update button is enabled and you can click the Update button to proceed with upgrading the Data Security Broker Manager.
4. In the Update Workspace resources window, select the version of the Data Security Broker Manager, which you wish to upgrade to, and click Update.

Zoom

!
Click Channel details and scroll down to Channel members.
3. Click the channel member that you want to update.
4. On the Update MSP definition panel, select the updated MSP and the original identity and click Update MSP definition. You must use the original identity for this step because it's currently the only one with permission to make channel updates. This action replaces the existing peer organization admin MSP definition with the updated MSP that includes the new admin certificate. Now this channel has the newest organization admin certificate.







 Step five: Update channel member 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 this is a peer admin MSP that is an ordering service consortium member, the ordering service admin needs to update the ordering service system channel. Because the ordering service system channel serves as a template for new application channels, taking this action keeps it current as the associated MSPs are updated. Before attempting these steps, the ordering service admin should have already imported the updated MSP from step two into their console.



1. From the Nodes tab, the ordering service admin opens the ordering service tile.
2. Delete the existing consortium member that contains the original MSP definition, and then add the consortium again with the new admin certificate by clicking Add organization. Browse to the new MSP JSON file from [step two](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-msp).

Zoom

![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.
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/containers?topic=containers-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.
* Adds support for enabling [master-to-worker communication with service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-plan_basicsworkeruser-master) in standard clusters in [VRF-enabled accounts](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf).
* Adds the --private-service-endpoint and --public-service-endpoint options to the [ibmcloud ks cluster-create](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_create) command.
* Adds the Public Service Endpoint URL and Private Service Endpoint URL fields to the output of ibmcloud ks cluster get.
* Adds the [ibmcloud ks cluster master private-service-endpoint enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_master_pse_enable) command.
* Adds the [ibmcloud ks cluster master public-service-endpoint enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_master_pub_se_enable) command.
* Adds the [ibmcloud ks cluster master public-service-endpoint disable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_master_pub_se_disable) command.
* Updates the help text in various languages.
* Updates the Go version to 1.11.6.
* Resolves intermittent networking issues for macOS users.







 Version 0.2.75 

Version 0.2.75 of the CLI was released on 14 March 2019.



* Hides raw HTML from error outputs.
* Fixes typos in help text.
* Updates the help text in various languages.







 Version 0.2.61 

Version 0.2.61 of the CLI was released on 26 February 2019.
Optional: Add capacity to your cluster by [resizing the worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersresize_pool). The pods on the worker node can be rescheduled and continue running on the added worker nodes during the update.
3. List the worker nodes in your cluster and note the ID and Primary IP of the worker node that you want to update.

ibmcloud oc worker ls --cluster CLUSTER
4. Replace the worker node to update either the patch version or the major.minor version that matches the master version.



* To update the worker node to the same major.minor version as the master, include the --update option.

ibmcloud oc worker replace --cluster CLUSTER --worker WORKER-NODE-ID --update
* To update the worker node to the latest patch version at the same major.minor version, don't include the --update option.

ibmcloud oc worker replace --cluster CLUSTER --worker WORKER-NODE-ID



5. Repeat these steps for each worker node that you must update.
6. Optional: After the replaced worker nodes are in a Ready status, [resize the worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersresize_pool) to meet the cluster capacity that you want.



If you are running Portworx in your VPC cluster, you must [manually attach your Block Storage for VPC volume to your new worker node.](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_update)





 Updating VPC worker nodes in the console 

You can update your VPC worker nodes in the console. Before you begin, consider [adding more worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workers) to the cluster to help avoid downtime for your apps.



1.
Kubernetes 1.23.8 1.23.9 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.23.9). 







 Change log for master fix pack 1.23.9_1539, released 26 July 2022 

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



Changes since version 1.23.8_1534

 Component Previous Current Description 

 Calico v3.21.5 v3.23.3 See the [Calico release notes](https://docs.tigera.io/archive). Updated the Calico custom resource definitions to include preserveUnknownFields: false. 
 Cluster health image v1.3.8 v1.3.9 Updated Go dependencies and to use Go version 1.18.4. Fixed minor typographical error in the add-on daemonset not available health status. 
 Gateway-enabled cluster controller 1680 1792 Updated to use Go version 1.17.11. Updated image for [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097) and [CVE-2022-29458](https://nvd.nist.gov/vuln/detail/CVE-2022-29458). 
 GPU device plug-in and installer 2b0b6d1 d8f1be0 Updated Go dependencies and to use Go version 1.18.3. 
 IBM Calico extension 980 997 Updated to use Go version 1.17.11. Updated universal base image (UBI) to version 8.6-854 to resolve CVEs. 
 IBM Cloud Controller Manager v1.23.7-7 v1.23.8-7 Updated Go dependencies and to use Go version 1.17.11. Updated to support the Kubernetes 1.23.8 release. 
 IBM Cloud File Storage for Classic plug-in and monitor 410 412 Updated to use Go version 1.18.3.