vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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. containers-kubernetes.cluster.create containers-kubernetes.account.update 
 POST/v2/disablePrivateServiceEndpoint Disable a private cloud service endpoint for a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.update 
 POST/v2/disablePublicServiceEndpoint Disable a public cloud service endpoint for a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.update 
 POST/v2/enableKMS Enable a key management service (KMS) for a cluster containers-kubernetes.cluster.create containers-kubernetes.account.update 
 POST/v2/enablePrivateServiceEndpoint Enable the private cloud service endpoint for a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.update 
 POST/v2/enablePublicServiceEndpoint Enable the public cloud service endpoint for a cluster. containers-kubernetes.cluster.create containers-kubernetes.cluster.update 
 POST/v2/enablePullSecret Create image pull secret to IBM Cloud Container Registry in the default Kubernetes namespace. containers-kubernetes.cluster.operate containers-kubernetes.cluster.update 
 POST/v2/refreshMaster Refresh the Kubernetes master. containers-kubernetes.cluster.operate containers-kubernetes.account.update 
 POST/v2/updateMaster Update the version of the Kubernetes cluster master node.
-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/containers?topic=containers-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.
Updating VPC worker nodes that use OpenShift Data Foundation 

Virtual Private Cloud

For VPC clusters with a storage solution such as OpenShift Data Foundation you must cordon, drain, and replace each worker node sequentially. If you deployed OpenShift Data Foundation to a subset of worker nodes in your cluster, then after you replace the worker node, you must then edit the ocscluster resource to include the new worker node.

The following tutorial covers both major and minor updates. Each step is flagged with

Major

or

Minor

.



Major

Applies to major updates, for example if you are updating your worker nodes to a new major version, such as from 4.11 to 4.12 as well as OpenShift Data Foundation from 4.11 to 4.12
Minor

Applies to minor patch updates, for example if you are updating from 4.12.15_1542_openshift to 4.12.16_1544_openshift while keeping OpenShift Data Foundation at version 4.12.



Skipping versions during an upgrade, such as from 4.8 to 4.12 is not supported.

[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)

Before updating your worker nodes, make sure to back up your app data. Also, plan to complete the following steps for one worker node at a time. Repeat the steps for each worker node that you want to update.



 Step 1: Update the cluster master 

Major



1. If you are updating your worker nodes to a new major version, such as from 4.11 to 4.12, update the cluster master first.

ibmcloud oc cluster master update --cluster CLUSTER [--version MAJOR.MINOR.PATCH] [--force-update] [-f] [-q]

Example command:

ibmcloud oc cluster master update --cluster mycluster --version 4.11.42 --force-update
2. Wait until the master update finishes.
These worker node fix packs can be at a higher version than the master because some build fix packs are specific to worker nodes. Other change logs are for master fix packs, and apply only to the cluster master. Master fix packs might not be automatically applied. You can choose to [apply them manually](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update). For more information about patch types, see [Update types](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsupdate_types).





 Version 1.23 change log 

Review the version 1.23 change log.



 Change log for master fix pack 1.23.17_1576, released 27 April 2023 

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



Changes since version 1.23.17_1569

 Component Previous Current Description 

 Cluster health image v1.3.17 v1.3.19 Updated Go to version 1.19.8 and updated dependencies. 
 Gateway-enabled cluster controller 2024 2106 Support Ubuntu 20 and update image to resolve CVEs. 
 GPU device plug-in a873e90 fc4cf22 Updated Go to version 1.19.7. 
 GPU installer a873e90 28d80a0 Updated Go to version 1.19.8. 
 IBM Calico extension 1366-amd64 1390-amd64 Eliminate IP syscall. 
 IBM Cloud Controller Manager v1.23.17-5 v1.23.17-10 Updated Go dependencies. 
 IBM Cloud File Storage for Classic plug-in and monitor 429 431 Updated Go to version 1.19.8 and updated dependencies. Update UBI base image. 
 Key Management Service provider v2.6.4 v2.6.5 Updated Go to version 1.19.7 and updated dependencies.
Then, perform a complete operating system reload in your infrastructure provider, reattach the host to your location, and reassign the host to a cluster.<br> * Apply available updates to your [worker node](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-workers) or [control plane hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-location). If the version update fails, you must remove your host, reload and troubleshoot any issues with the host, and reattach the host until the update is applied.<br><br><br> 
 Satellite Config <br><br> * Provide an interface to initiate change management activities, such as to update configurations or subscriptions.<br> * Automatically initiate the roll out of changes to a configuration to subscribed clusters.<br> * Automatically delete Kubernetes resources that run in subscribed clusters when you delete a configuration.<br><br><br> <br><br> * Use the provided [Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig) and [Red Hat OpenShift tools](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployupdating) to manage all changes to your apps. You are completely responsible for your app lifecycle, including any downtime that might occur when you update an app version, depending on your update rollout strategy.<br><br><br>
The following table shows the changes that are in the patch 1.12.6_1544.



Changes since version 1.12.6_1541

 Component Previous Current Description 

 Cluster DNS configuration N/A N/A Fixed a bug that might cause cluster master operations, such as refresh or update, to fail when the unused cluster DNS must be scaled down. 
 Cluster master HA proxy configuration N/A N/A Updated configuration to better handle intermittent connection failures to the cluster master. 
 CoreDNS configuration N/A N/A Updated the CoreDNS configuration to support [multiple Corefiles](https://coredns.io/2017/07/23/corefile-explained/). 
 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). 
 IBM Cloud File Storage for Classic plug-in 344 345 Added support for [private cloud service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_clusterset-up-private-se). 
 Kernel 4.4.0-141 4.4.0-143 Updated worker node images with kernel update for [CVE-2019-6133](https://ubuntu.com/security/CVE-2019-6133.html).
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/containers?topic=containers-ca_changelog).







 October 2022 



 31 October 2022 

Ingress ALB change log updates
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog) for version 1.3.0_2907_iks.





 27 October 2022 

ALB OAuth Proxy add-on version 2.0.0_1297
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-alb-oauth-proxy-changelog).

Master fix pack 1.22.15_1576, 1.23.13_1550, 1.24.7_1542, and 1.25.3_1520
: For more information, see the change logs: [1.22](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), [1.23](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123), [1.24](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124), and [1.25](https://cloud.ibm.com/docs/containers?topic=containers-changelog_125).





 26 October 2022 

Worker node fix pack 1.22.15_1575, 1.23.12_1549, 1.24.6_1541, and 1.25.2_1519
: You can create or [update clusters to Kubernetes version 1.24](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_124). With Kubernetes 1.24, you get the latest stable enhancements from the Kubernetes community as well as enhancements to the IBM Cloud product.

Deprecated and unsupported Kubernetes versions
: With the release of Kubernetes 1.24, clusters that run version 1.21 are deprecated, with a tentative unsupported date of 31 Aug 2022. Update your cluster to at least [version 1.22](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_122) as soon as possible.





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





 6 June 2022 

Worker node fix pack
: Kubernetes [1.20.15_1583](https://cloud.ibm.com/docs/containers?topic=containers-changelog_120), [1.21.13_1562](https://cloud.ibm.com/docs/containers?topic=containers-changelog_121), [1.22.10_1554](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), [1.23.7_1532](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123).





 3 June 2022 

Master fix pack update
ibmcloud ks cluster master public-service-endpoint disable --cluster <cluster_name_or_ID>
3. Refresh the Kubernetes master API server to remove the public cloud service endpoint by following the CLI prompt or by manually running the following command. It might take several minutes for the master to refresh.

ibmcloud ks cluster master refresh --cluster <cluster_name_or_ID>
4. [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.
5. Update all the worker nodes in your cluster to remove the public 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 with the ibmcloud ks worker reload[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload). 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>

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 with the ibmcloud ks worker reload[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload). 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.
Cluster master HA configuration N/A N/A Updated configuration to improve performance of master update operations. 
 Default IBM file storage class N/A N/A Fixed a bug that might cause cluster master operations such as patch updates to clear the default IBM file storage class. 
 Gateway-enabled cluster controller N/A 844 New! For classic clusters with a gateway enabled, a DaemonSet is installed to configure settings for routing network traffic to worker nodes. 
 IBM Cloud Provider v1.15.3-112 v1.15.4-136 Updated to support the Kubernetes 1.15.4 release. In addition, version 1.0 and 2.0 network load balancers (NLBs) were updated to support classic clusters with a gateway enabled. 
 Key Management Service provider 212 221 Improved Kubernetes [key management service provider](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkeyprotect) caching of IBM Cloud IAM tokens. In addition, fixed a problem with Kubernetes secret decryption when the cluster's root key is rotated. 
 Kubernetes v1.15.3 v1.15.4 See the [Kubernetes release notes)](https://github.com/kubernetes/kubernetes/releases/tag/v1.15.4). 
 Kubernetes Metrics Server v0.3.3 v0.3.4 See the [Kubernetes Metrics Server release notes)](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.3.4). 
 Load balancer and load balancer monitor for IBM Cloud Provider 148 153 Fixed issues with version 2.0 network load balancers (NLBs) that might cause all network traffic to drop or to be sent only to pods on one worker node.
For more information on this field, see [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/) 







 Update after master 

The following table shows the actions that you must take after you update the Kubernetes master.



Changes to make after you update the master to Kubernetes 1.21

 Type Description 

 Unsupported:kubect alpha debug removed The kubectl alpha debug command is removed. Instead, use the kubectl debug command. 
 Unsupported:kubectl run removed deprecated options The kubectl run command removes the following deprecated flags: --generator, --replicas, --service-generator, --service-overrides and --schedule. If your scripts use kubectl run to create resources other than pods, such as deployments, or if your scripts use the removed options, update the scripts to use the kubectl create or kubectl apply commands instead. 
 kubectl get removes managedFields by default Now, the kubectl get command omits managedFields in the -o json or -o yaml output by default. If you use kubectl get to retrieve managedFields by using -o json or -o yaml output, update your kubectl get calls to include the --show-managed-fields=true option. 
 Unsupported: Select kubelet metrics The following cAdvisor kubelet metrics are removed: /stats/container, /stats/<pod_name>/<container_name>, and /stats/<namespace>/<pod_name>/<pod_uid>/<container_name>. Stop using these metrics. 
 Ingress resource API version The support for networking.k8s.io/v1beta1 and extensions/v1beta1 API versions in Ingress resources are deprecated and are planned for removal in Kubernetes version 1.22. The networking.k8s.io/v1 API version is supported instead.
If you have automation that relies on the previous format, update it for new clusters.



* Cluster ID: In the regex format {a-v0-9}7]{a-z0-9}[2]{a-v0-9}[11].
* Worker node ID: In the format: kube-<cluster_ID>-<cluster_name_truncated>-<resource_group_truncated>-<worker_ID>



Ingress ALB change log
: Updated the ALB nginx-ingress image to build 497.

Troubleshooting clusters
: Added [troubleshooting steps](https://cloud.ibm.com/docs/containers?topic=containers-common_worker_nodes_issues) for when you can't manage clusters and worker nodes because the time-based one-time passcode (TOTP) option is enabled for your account.

Version change logs
: Updated the change logs for [1.14.4_1526](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1144_1526), [1.13.8_1529](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog1138_1529), and [1.12.10_1560](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog11210_1560) master fix pack updates.





 8 July 2019 

Version change logs
Master patch updates are applied automatically.



Changes since version 4.9.37_1544_openshift

 Component Previous Current Description 

 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). 
 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. Updated to support RHEL 8 worker nodes. 
 IBM Cloud Controller Manager v1.22.10-3 v1.22.11-3 Updated Go dependencies. Updated to support the Kubernetes 1.22.11 release. 
 IBM Cloud File Storage for Classic plug-in and monitor 410 412 Updated to use Go version 1.18.3. Updated universal base image (UBI) to version 8.6-854 to resolve CVEs. Improved Kubernetes resource watch configuration. 
 IBM Cloud RBAC Operator 8c96932 0a187a4 Updated universal base image (UBI) to resolve CVEs. 
 Key Management Service provider v2.5.6 v2.5.7 Updated Go dependencies and to use Go version 1.18.4.
Change log for master fix pack 4.3.31_1536_openshift, released 21 August 2020 

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



Changes since version 4.3.31_1534_openshift

 Component Previous Current Description 

 Cluster master operations N/A N/A Fixed a problem that might cause cluster master operations to fail for clusters with a private cloud service endpoint enabled. 
 IBM Cloud Controller Manager v1.17.9-1 v1.17.11-1 Updated to support the Kubernetes 1.17.11 release and to use Go version 1.13.15. 







 Change log for master fix pack 4.3.31_1534_openshift, released 18 August 2020 

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



Changes since version 4.3.29_1533_openshift

 Component Previous Current Description 

 Cluster health image v1.1.8 v1.1.9 Updated to use Go version 1.13.13. 
 Cluster master operations N/A N/A Cluster master update operations are now canceled if a broken [Kubernetes admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) is detected. 
 etcd v3.4.9 v3.4.10 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.10). 
 IBM Cloud Block Storage driver and plug-in 1.17 1.17.1 Updated to use Go version 1.13.8. 
 IBM Cloud File Storage for Classic plug-in and monitor 375 377 Fixed a bug that prevents persistent volume claim (PVC) creation failures from being retried. Updated to use Go version 1.13.8.
Master patch updates are applied automatically.



Changes since version 4.10.17_1524_openshift

 Component Previous Current Description 

 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). 
 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. Updated to support RHEL 8 worker nodes. 
 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. Updated universal base image (UBI) to version 8.6-854 to resolve CVEs. Improved Kubernetes resource watch configuration. 
 IBM Cloud RBAC Operator 8c96932 0a187a4 Updated universal base image (UBI) to resolve CVEs. 
 Key Management Service provider v2.5.6 v2.5.7 Updated Go dependencies and to use Go version 1.18.4.
The following table shows the changes that are in the master fix pack 1.22.12_1564. Master patch updates are applied automatically.



Changes since version 1.22.11_1556

 Component Previous Current Description 

 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.22.10-3 v1.22.11-3 Updated Go dependencies. Updated to support the Kubernetes 1.22.11 release. 
 IBM Cloud File Storage for Classic plug-in and monitor 410 412 Updated to use Go version 1.18.3. Updated universal base image (UBI) to version 8.6-854 to resolve CVEs. Improved Kubernetes resource watch configuration. 
 IBM Cloud RBAC Operator 8c96932 0a187a4 Updated universal base image (UBI) to resolve CVEs. 
 Key Management Service provider v2.5.6 v2.5.7 Updated Go dependencies and to use Go version 1.18.4.