vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Reviewing master health 

Virtual Private Cloud

Classic infrastructure

Review your cluster master health.



 Reviewing master health, status, and states 

Your IBM Cloud Kubernetes Service cluster includes an IBM-managed master with highly available replicas, automatic security patch updates applied for you, and automation in place to recover in case of an incident. You can check the health, status, and state of the cluster master by running ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The Master Health reflects the state of master components and notifies you if something needs your attention. The health might be one of the following states.



* error: The master is not operational. IBM is automatically notified and takes action to resolve this issue. You can continue monitoring the health until the master is normal. You can also [open an IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).
* normal: The master is operational and healthy. No action is required.
* unavailable: The master might not be accessible, which means some actions such as resizing a worker pool are temporarily unavailable. IBM is automatically notified and takes action to resolve this issue. You can continue monitoring the health until the master is normal.
* unsupported: The master runs an unsupported version of Kubernetes. You must [update your cluster](https://cloud.ibm.com/docs/containers?topic=containers-update) to return the master to normal health.



The Master Status provides details of what operation from the master state is in progress. The status includes a timestamp of how long the master has been in the same state, such as Ready (1 month ago). The Master State reflects the lifecycle of possible operations that can be performed on the master, such as deploying, updating, and deleting. Each state is described in the following table.



Master states

 Master state Description 

 deployed The master is successfully deployed. Check the status to verify that the master is Ready or to see if an update is available. 
 deploying The master is currently deploying.
Kubernetes 1.26.5 1.26.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.26.md). 







 Change log for master fix pack 1.26.6_1541, released 27 June 2023 

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



Changes since version 1.26.5_1537

 Component Previous Current Description 

 Cluster health image v1.3.20 v1.3.21 Updated Go dependencies and to Go version 1.19.10. 
 etcd v3.5.8 v3.5.9 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.5.9). 
 Gateway-enabled cluster controller 2106 2322 Updated image to resolve [CVE-2023-2650](https://nvd.nist.gov/vuln/detail/CVE-2023-2650). 
 GPU device plug-in and installer 28d80a0 202b284 Updated to Go version 1.19.9 
 IBM Cloud Controller Manager v1.26.4-7 v1.26.6-1 Updated to support the Kubernetes 1.26.6 release. Updated Go dependencies and to Go version 1.19.10. Updated calicoctl and vpcctl. 
 IBM Cloud File Storage for Classic plug-in and monitor 431 433 Updated Go to version 1.20.4. Updated UBI base image. 
 IBM Cloud Metrics Server Config Watcher d842983 d293d8b Updated Go to version 1.20.5. Updates to build and base images. 
 Key Management Service provider v2.6.6 v2.6.7 Updated Go dependencies and to Go version 1.19.10.
* [Version 4.13 parameters](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcodf-vpc-params-413)
* [Version 4.10, 4.11, and 4.12 parameters](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcodf-vpc-params-412)
* [Version 4.9 parameters](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcodf-vpc-params-48)





[Updating VPC worker nodes that use OpenShift Data Foundation](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpcopenshift-storage-update-vpc)



* [Update the cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpcupdate-cluster-master-vpc)
* [Determine which storage nodes you want to update](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpcdetermine-storage-nodes-vpc)
* [Scale down OpenShift Data Foundation](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpcscale-down-odf-vpc)
* [Cordon and drain the worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpccordon-drain-worker-node-vpc)
* [Upgrade the worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpcupgrade-worker-node-vpc)
: Required: Specify an add-on name, such as istio, to update. To see installed add-ons, run ibmcloud oc cluster addon ls --cluster <cluster_name_or_ID>.

-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.

--version VERSION
: Optional: Specify the version to update the add-on to. If no version is specified, the add-on is updated to the default version. To list available add-on versions, run ibmcloud oc cluster addon versions.





 ibmcloud oc cluster addon versions 

Virtual Private Cloud

Classic infrastructure

View a list of supported versions for managed add-ons in IBM Cloud Kubernetes Service.

ibmcloud oc cluster addon versions [--addon ADD-ON_NAME] [--output json] [-q]

Minimum required permissions
: None

Command options:

--addon ADD-ON_NAME
: Optional: Specify an add-on name such as istio to filter versions for.

--output json
: Optional: Prints the command output in JSON format.

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



 Example addon versions command 

ibmcloud oc cluster addon versions --addon istio







 ibmcloud oc cluster ca create 

Virtual Private Cloud

Classic infrastructure

Create a new certificate authority (CA) for your cluster. After the CA is created and new CA certificates are issued for components in your cluster, the API server of the cluster is automatically refreshed.
* If the gateway for your cluster is listed and its status is Stable, you might have firewall or security group rules that are blocking worker node communication to the cluster master. [Configure your security group rules to allow outgoing traffic to the appropriate ports and IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-vpc-security-group).



2. Refresh the cluster master. If the VPE gateway does not exist in your VPC, it is created, and connectivity to the reserved IP addresses on the subnets that your worker nodes are connected to is re-established. After you refresh the cluster, wait a few minutes to allow the operation to complete.

ibmcloud ks cluster master refresh -c <cluster_name_or_ID>
3. Verify that the VPE gateway for your cluster is created by opening the [Virtual private endpoint gateways for VPC dashboard](https://cloud.ibm.com/vpc-ext/network/endpointGateways) and looking for the VPE gateway in the format iks-<cluster_ID>.
4. If you still can't manage worker nodes after the cluster master is refreshed, replace the worker nodes that you can't access.



1. List all worker nodes in your cluster and note the name of the worker node that you want to replace.

kubectl get nodes

The name that is returned in this command is the private IP address that is assigned to your worker node. You can find more information about your worker node when you run the ibmcloud ks worker ls --cluster <cluster_name_or_ID> command and look for the worker node with the same Private IP address.
2. Replace the worker node. As part of the replace process, the pods that run on the worker node are drained and rescheduled onto remaining worker nodes in the cluster. The worker node is also cordoned, or marked as unavailable for future pod scheduling. Use the worker node ID that is returned from the ibmcloud ks worker ls --cluster <cluster_name_or_ID> command.
Kubernetes N/A N/A N/A 
 Containerd 1.6.18 1.6.19 For more information, see the [change log](https://github.com/containerd/containerd/releases/tag/v1.6.19). 







 Change log for master fix pack 1.23.16_1567, released 2 March 2023 

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



Changes since version 1.23.16_1560

 Component Previous Current Description 

 Cluster health image v1.3.15 v1.3.16 Updated Go dependencies and to Go version 1.19.6. Updated universal base image (UBI) to resolve CVEs. 
 etcd v3.4.22 v3.4.23 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.23). 
 Gateway-enabled cluster controller 1902 1987 Updated armada-utils to version v1.9.35 
 IBM Calico extension 1280-amd64 1308-amd64 Updated universal base image (UBI) to resolve [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629). 
 IBM Cloud Controller Manager v1.23.16-3 v1.23.16-11 Updated Go dependencies. Updated k8s.io/utils digest to a5ecb01. Updated vpcctl binary to 3785. 
 IBM Cloud File Storage for Classic plug-in and monitor 425 427 Updated universal base image (UBI) to resolve CVEs. 
 Key Management Service provider v2.5.13 v2.6.3 Updated Go dependencies and to Go version 1.19.6. 
 Konnectivity agent and server v0.0.34_491_iks v0.1.1_569_iks-amd64 Updated to Konnectivity version v0.1.0.
Updating Portworx in your cluster 

Beginning with version 2.12 Portworx uses an operator-based deployment model instead of the Helm based model use in version 2.11 and earlier. If you are updating 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/).



 VPC: Updating worker nodes with Portworx volumes 

Virtual Private Cloud

When you update a worker node in a VPC cluster, the worker node is removed from your cluster and replaced with a new worker node. If Portworx volumes are attached to the worker node that you replaced, you must attach the volumes to the new worker node.

Update only one worker node at a time. When the worker node update is complete, attach your Block Storage for VPC and restart the Portworx pod.



1. [Enter maintenance mode on the worker nodes that you want to update](https://docs.portworx.com/portworx-install-with-kubernetes/operate-and-maintain-on-kubernetes/troubleshooting/enter-maintenance-mode/).
2. [Update your VPC worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updatevpc_worker_node).
3. [Attach raw Block Storage for VPC to your worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesvpc_api_attach).
4. Verify that your storage is attached by running the following command.

oc get pv -o yaml | grep "attachstatus"
5. Restart the Portworx pod on the new worker node.

oc delete pod <portworx_pod> -n <portworx_namespace>
6. Exit maintenance mode

pxctl service maintenance --exit
7.
Cluster DNS configuration N/A N/A Fixed a bug that might leave both Kubernetes DNS and CoreDNS pods running after cluster create or update operations. 
 Cluster master HA configuration N/A N/A Updated configuration to minimize intermittent master network connectivity failures during a master update. 
 etcd v3.3.11 v3.3.13 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.3.13). 
 GPU device plug-in and installer 55c1f66 32257d3 Updated image for [CVE-2018-10844](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10844), [CVE-2018-10845](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10845), [CVE-2018-10846](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10846), [CVE-2019-3829](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3829), [CVE-2019-3836](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3836), [CVE-2019-9893](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9893), [CVE-2019-5435](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5435), and [CVE-2019-5436](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5436).
Change log for master fix pack 3.11.232_1560_openshift, released 24 July 2020 

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



Changes since version 3.11.232_1559_openshift

 Component Previous Current Description 

 Heapster configuration N/A N/A Configuration changes now properly trigger a restart of the heapster pod in kube-system namespace. 
 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 3.11.232_1559_openshift, released 20 July 2020 

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



Changes since version 3.11.232_1555_openshift

 Component Previous Current Description 

 IBM Cloud Block Storage driver configuration N/A N/A Added a pod memory limit. 
 IBM Cloud File Storage for Classic plug-in and monitor configuration N/A N/A Added a pod memory limit. 
 Red Hat OpenShift 3.11.219 3.11.232 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.htmlocp-3-11-232). The update resolves CVE-2019-11254 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6249873)) and CVE-2020-8555 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6249891)). 







 Change log for worker node fix pack 3.11.232_1558_openshift, released 20 July 2020
* Updates the code base to synchronize with the community autoscaler. For more information, see the [Kubernetes autoscaler documentation](https://github.com/kubernetes/autoscaler/releases).







 Change log for patch update 1.0.1_210, released 13 January 2021 

Review the changes in version 1.0.1_210 of the cluster autoscaler add-on.



* Image tags: 1.16.2-9, 1.17.0-10, 1.18.1-9, and 1.19.0-4.
* Supported cluster versions: 4.3 - 4.6
* Update addresses [DLA-2509-1](https://www.debian.org/lts/security/2020/dla-2509).







 Change log for patch update 1.0.1_205, released 15 December 2020 

Review the changes in version 1.0.1_205 of the cluster autoscaler add-on.



* Image tags: 1.11.0-7, 1.16.2-8, 1.17.0-9, 1.18.1-8, and 1.19.0-3.
* Supported cluster versions: 4.3 - 4.6
* Updates the initContainer to use the universal base image (UBI).







 Change log for patch update 1.0.1_195, released 10 December 2020 

Review the changes in version 1.0.1_195 of the cluster autoscaler add-on.



* Image tags: 1.11.0-7, 1.16.2-8, 1.17.0-9, 1.18.1-8, and 1.19.0-3.
* Supported cluster versions: 4.3 - 4.6
* Images are now signed.
* Resources that are deployed by the cluster autoscaler add-on are now linked with the corresponding source code and build URLs.
* Updates the Go version to 1.15.5.







 Change log for patch update 1.0.1_146, released 03 December 2020
To update the IAM API key, use the ibmcloud ks api-key reset[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_api_key_reset). To update the IBM Cloud infrastructure key, use the ibmcloud ks credential set[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_credentials_set).
3. Wait about 10 - 15 minutes for the storage-secret-store Kubernetes secret to update, then verify that the key is updated.

kubectl get secret storage-secret-store -n kube-system -o yaml | grep slclient.toml: | awk '{print $2}' | base64 --decode



3. If the API key is correct, verify that the key has the correct permission to provision persistent storage.



1. Contact the account owner to verify the permission of the API key.
2. As the account owner, select Manage > Access (IAM) from the navigation in the IBM Cloud console.
3. Select Users and find the user whose API key you want to use.
4. From the actions menu, select Manage user details.
5. Go to the Classic infrastructure tab.
6. Expand the Account category and verify that the Add/ Upgrade Storage (Storage Layer) permission is assigned.
7. Expand the Services category and verify that the Storage Manage permission is assigned.



4. Remove the PVC that failed.

kubectl delete pvc <pvc_name>
5. Re-create the PVC.

kubectl apply -f pvc.yaml
Change log for master fix pack 1.23.16_1560, released 30 January 2023 

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



Changes since version 1.23.15_1555

 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 Calico extension 1257 1280 Publish s390x image. 
 IBM Cloud Controller Manager v1.23.14-2 v1.23.16-3 Updated to support the Kubernetes 1.23.16 release. Updated Go dependencies. 
 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. 
 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). 
 Kubernetes v1.23.15 v1.23.16 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.23.16). 







 Change log for worker node fix pack 1.23.16_1561, released 30 January 2023
Review the changes that are in version 1.0.2 of the managed cluster autoscaler add-on.



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

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



* Image tags: 1.17.4-3, 1.18.3-3, 1.19.1-3, and 1.20.0-3.
* Supported cluster versions: 1.17 <1.21.0
* Includes a bug fix for the worker replace command on VPC clusters that caused worker creation to fail.







 Change log for patch update 1.0.2_256, released 19 April 2021 

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



* Image tags: 1.17.4-2, 1.18.3-2, 1.19.1-2, and 1.20.0-2
* Supported cluster versions: 1.17 - 1.20
* Includes fixes for [CVE-2021-27919](https://nvd.nist.gov/vuln/detail/CVE-2021-27919) and [CVE-2021-27918](https://nvd.nist.gov/vuln/detail/CVE-2021-27918).







 Change log for patch update 1.0.2_249, released 01 April 2021 

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



* Image tags: 1.16.7-1, 1.17.4-1, 1.18.3-1, 1.19.1-1, and 1.20.0-1.
* Supported cluster versions: 1.17 - 1.20
* Includes fixes for [CVE-2021-3114](https://nvd.nist.gov/vuln/detail/CVE-2021-3114) and [CVE-2021-3115](https://nvd.nist.gov/vuln/detail/CVE-2021-3114).
* Removes the init container.
* Adds the [ibmcloud ks cluster-refresh](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_refresh) alias to the apiserver-refresh command.
* Adds the resource group name to the output of ibmcloud ks cluster get and ibmcloud ks cluster ls.







 Version 0.1.635 

Version 0.1.635 of the CLI was released on 6 November 2018.

Adds commands for managing automatic updates of the Ingress ALB cluster add-on:



* [ibmcloud ks alb autoupdate disable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_autoupdate_disable)
* [ibmcloud ks alb autoupdate enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_autoupdate_enable)
* [ibmcloud ks alb autoupdate get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_autoupdate_get)
* ibmcloud ks alb rollback
* [ibmcloud ks alb-update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_update)







 Version 0.1.621 

Version 0.1.621 of the CLI was released on 30 October 2018.



* Adds the [ibmcloud ks credential get command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_credential_get).
* Adds support for the storage log source to all cluster logging commands. For more information, see [Understanding cluster and app log forwarding](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging).
"buildDate": "2019-03-21T10:08:03Z",
"goVersion": "go1.11.5",
"compiler": "gc",
"platform": "linux/amd64"
}
7. Review the Kubernetes API documentation]] ! ! ! ! to find a list of supported APIs for the latest Kubernetes version. Make sure to use the API documentation that matches the Kubernetes version of your cluster. If you don't use the latest Kubernetes version, append your version at the end of the URL. For example, to access the API documentation for version 1.12, add v1.12.<-- </ol> --><-- </section "id="section-kube_api" "> --><-- <section "id="section-cs_api_refresh" "> --> Refreshing IAM access tokens and obtaining new refresh tokens with the API Every IBM Cloud Identity and Access Management (IAM) access token that is issued via the API expires after one hour. You must refresh your access token regularly to assure access to the IBM Cloud API. You can use the same steps to obtain a new refresh token.Before you begin, make sure that you have an IBM Cloud IAM refresh token or an IBM Cloud API key that you can use to request a new access token.<-- <ul> --> * Refresh token: Follow the instructions in Automating the cluster creation and management process with the IBM Cloud API]Automating cluster deployments with the API] . * API key: Retrieve your IBM Cloud]] !!! ! !!!!!! API key as follows.
<-- <ol> -->

1. From the menu bar, click Manage > Access (IAM).
2. Click the Users page and then select yourself.
3. In the API keys pane, click Create an IBM Cloud API key.
4. Enter a Name and Description for your API key and click Create.
The following table shows the changes that are in the master fix pack 1.10.13_1553.



Table 1. Changes since version 1.10.13_1551

 Component Previous Current Description 

 IBM Cloud File Storage for Classic plug-in 345 346 Updated image for [CVE-2019-9741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741). 
 Key Management Service provider 166 167 Fixes intermittent context deadline exceeded and timeout errors for managing Kubernetes secrets. In addition, fixes updates to the key management service that might leave existing Kubernetes secrets unencrypted. Update includes fix for [CVE-2019-9741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741). 
 Load balancer and load balancer monitor for IBM Cloud Provider 143 146 Updated image for [CVE-2019-9741](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741). 







 Change log for 1.10.13_1551, released 20 March 2019 

The following table shows the changes that are in the patch 1.10.13_1551.



Table 1. Changes since version 1.10.13_1548

 Component Previous Current Description 

 Cluster master HA proxy configuration N/A N/A Updated configuration to better handle intermittent connection failures to the cluster master. 
 GPU device plug-in and installer e32d51c 9ff3fda Updated the GPU drivers to [418.43](https://www.nvidia.com/object/unix.html). Update includes fix for [CVE-2019-9741](https://ubuntu.com/security/CVE-2019-9741.html).