vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Update your cluster to at least [version 1.20](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_120) as soon as possible.

Master fix pack and worker node fix pack update
: Change log documentation is available for Kubernetes version [1.22.2_1522 and 1.22.2_1523](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1221222_1522_and_1222_1523).





 27 September 2021 

Master fix pack update
: Change log documentation is available for version [1.21.5_1531](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1211215_1531), [1.20.11_1553](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12012011_1553), [1.19.15_1560](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911915_1560), [1.18.20_1565](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1565).

Worker node fix pack update
: Change log documentation is available for version [1.18.20_1566](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1566), [1.19.15_1561](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911915_1561), [12011_1554](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12012011_1554), and [1.21.5_1532](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1211215_1532).





 23 September 2021 

Review the release notes for 23 September 2021.
To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The Kubernetes API server that runs in your Kubernetes master is being updated to a new Kubernetes API version. During the update, you can still access and change the cluster. However, you cannot initiate concurrent master operations, such as enabling API server auditing. Worker nodes, apps, and resources that the user deployed aren't modified and continue to run. Wait for the update to complete to review the health of your cluster.





 Unsupported 

Review the following description of the Unsupported cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The [Kubernetes version](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions) that the cluster runs is no longer supported. Your cluster's health is no longer actively monitored or reported. Additionally, you can't add or reload worker nodes. To continue receiving important security updates and support, you must update your cluster. Review the [version update preparation actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsprep-up), then [update your cluster](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate) to a supported Kubernetes version.





 Warning 

Review the following description of the Warning cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

At least one worker node in the cluster is not available, but other worker nodes are available and can take over the workload. Try to [reload](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reload) the unavailable worker nodes.
If your cluster does not run the latest patch version, update the cluster and worker nodes.



1. [Update the cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-updatemaster) to the latest patch version for your cluster major and minor version.

ibmcloud oc cluster master update -c <cluster_name_or_ID> --version <major.minor>_openshift-f
2. List your worker nodes.

ibmcloud oc worker ls -c <cluster_name_or_ID>
3. [Update the worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-updateworker_node) to match the cluster master version.

ibmcloud oc worker update -c <cluster_name_or_ID> -w <worker1_ID> -w <worker2_ID> -w<worker3_ID>



4. Check the cluster State. If the state is not normal, see [Debugging clusters(#debug_clusters).
5. Check the Master health. If the state is not normal, see [Reviewing master health(#debug_master).
6. Check the worker nodes that the Red Hat OpenShift components might run on. If the state is not normal, see [Debugging worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).

ibmcloud oc worker ls -c <cluster_name_or_ID>







 Step 5: Log in to your cluster 

[Log in to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster). Note that if the Red Hat OpenShift web console does not work for you to get the login token, you can [access the cluster from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_oc_cli).
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.16.13_1540, released 20 July 2020 

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



Changes since version 1.16.11_1537

 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]
Update your cluster to at least [version 4.6](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) as soon as possible.

Master fix pack and worker node fix pack update
: Change log documentation is available for OpenShift version [4.8.11_1526_openshift and 4.8.12_1527_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48).





 27 September 2021 

Master fix pack update
: Change log documentation is available for version [4.7.30_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474730_1532),[4.6.44_1556_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464644_1556), [4.5.41_1552_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4541_1552), and [3.11.521_1604_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311521_1604).

Worker node fix pack update
Check the status to verify that the master is Ready or to see if an update is available. 
 deploying The master is currently deploying. Wait for the state to become deployed before working with your cluster, such as adding worker nodes. 
 deploy_failed The master failed to deploy. IBM Support is notified and works to resolve the issue. Check the Master Status field for more information, or wait for the state to become deployed. 
 deleting The master is currently deleting because you deleted the cluster. You can't undo a deletion. After the cluster is deleted, you can no longer check the master state because the cluster is completely removed. 
 delete_failed The master failed to delete. IBM Support is notified and works to resolve the issue. You can't resolve the issue by trying to delete the cluster again. Instead, check the Master Status field for more information, or wait for the cluster to delete. You can also [open an IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help). 
 scaled_down The master resources have been scaled down to zero replicas. This is a temporary state that occurs while etcd is being restored after a backup. You cannot interact with your cluster while it is in this state. Wait for the etcd restoration to complete and the master state to return to deployed. 
 updating The master is updating its Kubernetes version. The update might be a patch update that is automatically applied, or a minor or major version that you applied by updating the cluster. During the update, your highly available master can continue processing requests, and your app workloads and worker nodes continue to run. After the master update is complete, you can [update your worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node). If the update is unsuccessful, the master returns to a deployed state and continues running the previous version. IBM Support is notified and works to resolve the issue. You can check if the update failed in the Master Status field.
You can't undo a deletion. After the cluster is deleted, you can no longer check the master state because the cluster is completely removed. 
 delete_failed The master failed to delete. IBM Support is notified and works to resolve the issue. You can't resolve the issue by trying to delete the cluster again. Instead, check the Master Status field for more information, or wait for the cluster to delete. You can also [open an IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help). 
 scaled_down The master resources have been scaled down to zero replicas. This is a temporary state that occurs while etcd is being restored after a backup. You cannot interact with your cluster while it is in this state. Wait for the etcd restoration to complete and the master state to return to deployed. 
 updating The master is updating its Kubernetes version. The update might be a patch update that is automatically applied, or a minor or major version that you applied by updating the cluster. During the update, your highly available master can continue processing requests, and your app workloads and worker nodes continue to run. After the master update is complete, you can [update your worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node). If the update is unsuccessful, the master returns to a deployed state and continues running the previous version. IBM Support is notified and works to resolve the issue. You can check if the update failed in the Master Status field. 
 update_cancelled The master update is canceled because the cluster was not in a healthy state at the time of the update. Your master remains in this state until your cluster is healthy and you manually update the master. To update the master, use the ibmcloud ks cluster master update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update).
-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 ks cluster master private-service-endpoint enable --cluster my_cluster







 ibmcloud ks cluster master public-service-endpoint disable 

Virtual Private Cloud

Classic infrastructure

Disable the public cloud service endpoint for a cluster.

Important: Before you disable the public endpoint, you first must complete the following steps to enable the private cloud service endpoint:



1. Enable the private cloud service endpoint by running ibmcloud ks cluster master private-service-endpoint enable --cluster <cluster_name>.
2. Follow the prompt in the CLI to refresh the Kubernetes master API server.
3. [Reload all the worker nodes in your cluster to pick up the private endpoint configuration.](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_worker_reload)



ibmcloud ks cluster master public-service-endpoint disable --cluster CLUSTER [-q] [-f]

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.

-y
: Optional: Refresh the cluster master and reload worker nodes with no user prompts.



 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.
You can continue to monitor the health of the master until the master reaches a normal state. If the master remains in this state for more than 1 day, [open an IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help). IBM Support might identify other issues in your cluster that you must fix before the master can be updated. 







 Understanding the impact of a master outage 

The [Kubernetes master](https://cloud.ibm.com/docs/containers?topic=containers-service-arch) is the main component that keeps your cluster up and running. The master stores cluster resources and their configurations in the etcd database that serves as the single point of truth for your cluster. The Kubernetes API server is the main entry point for all cluster management requests from the worker nodes to the master, or when you want to interact with your cluster resources.

If a master failure occurs, your workloads continue to run on the worker nodes, but you can't use kubectl commands to work with your cluster resources or view the cluster health until the Kubernetes API server in the master is back up. If a pod goes down during the master outage, the pod can't be rescheduled until the worker node can reach the Kubernetes API server again.

During a master outage, you can still run ibmcloud ks commands against the IBM Cloud Kubernetes Service API to work with your infrastructure resources, such as worker nodes or VLANs. If you change the current cluster configuration by adding or removing worker nodes to the cluster, your changes don't happen until the master is back up.

Do not restart or reboot a worker node during a master outage. This action removes the pods from your worker node. Because the Kubernetes API server is unavailable, the pods can't be rescheduled onto other worker nodes in the cluster.
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 8b02302 31d4bb6 Updated image for [CVE-2020-3810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3810). 
 IBM Cloud Controller Manager Master v1.17.6-1 v1.17.7-1 Updated to support the Kubernetes 1.17.7 release. Updated the version 2.0 private network load balancers (NLBs) to manage Calico global network policies. Updated calicoctl version to 3.12.2. 
 IBM Cloud File Storage for Classic plug-in Master 373 375 Fixed a bug that might cause error handling to create additional persistent volumes. 
 Kubernetes Both v1.17.6 v1.17.7 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.17.7). The master update resolves CVE-2020-8558 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6249905)).
: 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

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

For Red Hat OpenShift on IBM Cloud clusters, public service endpoints can't be disabled. If you enable a public service endpoint in a Red Hat OpenShift cluster, you can't later convert the cluster from public to private.

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

ibmcloud oc 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 oc cluster master public-service-endpoint enable --cluster my_cluster







 ibmcloud oc cluster master refresh 

Virtual Private Cloud

Classic infrastructure

Apply configuration changes for the Kubernetes master that are requested with the ibmcloud oc 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.
* Ensure that you keep a record of all the new passwords and credentials that you create as part of the upgrade process. IBM Support requires these credentials at the end of the upgrade process to update their internal database.







 Procedure to set the cluster Distributed Resource Schedule to manual 

You must set the cluster Distributed Resource Schedule (DRS) to manual to prevent unexpected migrations during the upgrade process.

Complete the following steps from the vCenter Server user interface.



1. Select Host and Clusters > Cluster > Configure > DRS.
2. Click EDIT.
3. Set the DRS field to Manual.







 Procedure to create a standard switch for the new vCenter Server Appliance 

Temporarily install the new vCenter Server Appliance that you deploy onto a vSphere Standard Switch. One of the existing vmnics is reassigned from the distributed switch during the upgrade.

Complete the following steps from the vCenter Server user interface.



1. Select Hosts and Clusters > HOST > Configure > Virtual Switches. Select a host for the new vCenter Server Appliance.
2. For the private network switch, select Managed Physical Adapters. The private network switch name ends with -private.
3. Select uplink1/vmnic2, then click the Close icon ![Close icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/close-icon.svg) to delete the adapter. Click OK.
4. Return to the Virtual Switches panel and click Add Networking.



1. Select Virtual Machine Port Group for a standard switch and click Next.
2. For New Standard Switch, set the MTU to 9000 and click Next.
3. Click the green Add icon !
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.

When you create a location, a key is generated that the Satellite API server uses to attach hosts to the location and assign hosts to the control plane or to [Satellite-enabled IBM Cloud services](https://cloud.ibm.com/docs/satellite?topic=satellite-managed-services). This generated key is an API key, which should be treated and protected as sensitive information. This key expires every 365 days. For more information about how to update the host key after the key expires, see [Why do my unassigned hosts have an Unresponsive status?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-host-unassigned-unknown). As you use your location, you might want to reset the existing host key. For example, in the case of a potential security incident, you can reset the key when you request a host attachment script. All existing hosts that run the previous version of the script can no longer communicate with the API for your Satellite location, and you can remove and reattach the existing hosts by using the script with the new key.

When you reset the host key, all existing hosts that are attached to your location can no longer communicate with the Satellite API server. Until they are reattached, existing hosts have authentication errors and cannot be managed by the control plane, such as for updates.



1. List all hosts that are attached to your location.

ibmcloud sat host ls --location <location_name_or_ID>
2. Reset the host key for the Satellite location.
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.3.20 v3.3.22 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.22). 
 GPU device plug-in and installer Master 8b02302 31d4bb6 Updated image for [CVE-2020-3810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3810). 
 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 Provider Master v1.16.10-243 v1.16.11-267 Updated to support the Kubernetes 1.16.11 release. Updated the version 2.0 private network load balancers (NLBs) to manage Calico global network policies. Updated calicoctl version to 3.9.6. 
 Kubernetes Both v1.16.10 v1.16.11 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.16.11). The master update resolves CVE-2020-8558 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6249905)).
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.3.20 v3.3.22 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.22). 
 GPU device plug-in and installer Master 8b02302 31d4bb6 Updated image for [CVE-2020-3810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3810). 
 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 Provider Master v1.15.12-316 v1.15.12-343 Updated calicoctl version to 3.8.9. 
 Kubernetes configuration Master N/A N/A The Kubernetes API server audit policy configuration is updated to include auditing the apiextensions.k8s.io API group and the persistentvolumeclaims and persistentvolumes resources. Additionally, the http2-max-streams-per-connection option is set to 1000 to mitigate network disruption impacts on the kubelet connection to the API server.