vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: 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.

After you run this command and before you run the ibmcloud oc cluster ca rotate command, follow the steps in [Rotating CA certificates in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-securitycert-rotate) to ensure that any tooling that uses certificates that are signed by the old CA is updated to use the new certificates and to update your worker nodes.

ibmcloud oc cluster ca create --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 create command 

ibmcloud oc cluster ca create --cluster my_cluster







 ibmcloud oc cluster ca get 

Virtual Private Cloud

Classic infrastructure

View the details of a cluster's CA certificate.

ibmcloud oc cluster ca get --cluster CLUSTER [ --output OUTPUT] [-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.

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

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



 Example cluster ca get command 

ibmcloud oc cluster ca get --cluster my_cluster
Update your cluster to at least [version 4.6](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) as soon as possible.

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



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







 07 June 2021 

Worker node versions
: Worker node fix pack update change log documentation is available for version [4.6.31_1545_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464631_1545), [4.5.40_1541_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4540_1541), and [3.11.439_1592_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311439_1592).





 3 June 2021 

IBM Cloud Object Storage plug-in
: Version 2.0.8 of the IBM Cloud Object Storage plug-in is released.
Updating maximum number of worker nodes 



 Making updates to the Symphony configuration using the GUI 

You can make updates to your Symphony configuration by using the GUI console or through the CLI.



 Configuration updates using Symphony GUI console 

For more information on how to use the Symphony GUI console, see [Symphony GUI console](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-gui-console&interface=ui).

After you login to the console, complete the following steps to update the maximum number of worker nodes:



1. From the cluster management console, click Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) Resources > Cloud > Configuration.
2. In the Cloud Configuration page, update the HostFactory service configuration, your cloud provider's host template, or both. If your updates do not include optional parameters, the parameters default values are used.
3. To update the cloud provider's host template definition, select ibmcloudgen2inst from the provider list and edit your existing template definition in the templates text box.
4. Modify the values for following:

a. maxNumber changes the maximum number of worker nodes.

b. imageId changes the ID of the custom image.

c. vmType changes the instance type. If you modify the instance type, you will also need to modify the corresponding values for ncpus and nram in the attributes section. For example, if you choose bx2-2x8, this instance type has 2 VCPUs and 8GB of RAM. Since VCPUs includes hyper-threads, use VCPUs divided by 2, to get ncpus. Set ncpus to 1 and nram to 8192.

d. postProvisionFile changes the location of the post provision script.

e. hostPrefix changes the prefix of provisioned hosts



The changes take effect automatically. There is no need to restart the HostFactory service.





 Configuration updates using Symphony CLI 



1.
Kubernetes 1.25.10 1.25.11 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.25.md). 







 Change log for master fix pack 1.25.11_1549, released 27 June 2023 

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



Changes since version 1.25.10_1545

 Component Previous Current Description 

 Calico v3.24.5 v3.25.1 See the [Calico release notes](https://docs.tigera.io/calico/3.25/release-notes/v3.25.1). 
 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.25.9-7 v1.25.11-1 Updated to support the Kubernetes 1.25.11 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. 
 Key Management Service provider v2.6.6 v2.6.7 Updated Go dependencies and to Go version 1.19.10.
Your cluster is deployed with the following managed components and associated resources that can't be changed, except to scale pods or edit configmaps for certain performance benefits. If you try to change one of these deployment components, their original settings are restored on a regular interval when they are updated with the cluster master. However, note that resources that you create that are associated with these components, such as Calico network policies that you create to be implemented by the Calico deployment components, are not updated.



* calico components
* coredns components
* ibm-cloud-provider-ip
* ibm-file-plugin
* ibm-keepalived-watcher
* ibm-master-proxy
* ibm-storage-watcher
* kubernetes-dashboard components
* metrics-server
* olm-operator and catalog components (1.16 and later)
* vpn



Can I install other plug-ins or add-ons than the default components?
: Yes. Red Hat OpenShift on IBM Cloud provides other plugin-ins and add-ons that you can choose from to add capabilities to your cluster. For example, you might want to [use Helm charts](https://cloud.ibm.com/docs/openshift?topic=openshift-helm) to install [strongSwan VPN](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvpn-setup). Or you might want to enable IBM-managed add-ons in your cluster, such as the Diagnostics and Debug Tool. You must update these Helm charts and add-ons separately by following the instructions in the Helm chart readme files or by following the steps to [update managed add-ons](https://cloud.ibm.com/docs/containers?topic=containers-managed-addonsupdating-managed-add-ons).



 Managing automatic updates for Fluentd 

When you create a logging configuration for a source in your cluster to forward to an external server, a Fluentd component is created in your cluster. To change your logging or filter configurations, the Fluentd component must be at the latest version.
Change log for master fix pack 1.18.18_1549, released 27 April 2021 

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



Changes since version 1.18.17_1546

 Component Previous Current Description 

 Cluster health image v1.1.19 v1.1.21 Updated to use Go version 1.15.11. Updated image to implement additional IBM security controls and for [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449), [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450), and [CVE-2021-20305](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20305). 
 CoreDNS 1.8.0 1.8.3 See the [CoreDNS release notes](https://coredns.io/tags/notes/). 
 GPU device plug-in and installer c1c6dd3 19bf25c Updated image for [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449), [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450), and [CVE-2021-20305](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20305). 
 IBM Cloud Controller Manager v1.18.17-1 v1.18.18-1 Updated to support the Kubernetes 1.18.18 release.
Change log for master fix pack 1.21.6_1539, released 17 November 2021 

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



Changes since version 1.21.5_1536

 Component Previous Current Description 

 Cluster health image v1.2.16 v1.2.18 Updated Go module dependencies and to use Go version 1.16.9. Updated image for [CVE-2021-22946](https://nvd.nist.gov/vuln/detail/CVE-2021-22946), [CVE-2021-22947](https://nvd.nist.gov/vuln/detail/CVE-2021-22947), [CVE-2021-33928](https://nvd.nist.gov/vuln/detail/CVE-2021-33928), [CVE-2021-33929](https://nvd.nist.gov/vuln/detail/CVE-2021-33929) and [CVE-2021-33930](https://nvd.nist.gov/vuln/detail/CVE-2021-33930). 
 etcd v3.4.17 v3.4.18 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.18). 
 Gateway-enabled cluster controller 1510 1567 Updated to use Go version 1.16.9.
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).

Cluster autoscaler add-on versions 1.0.7_988 and 1.0.8_987.
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).





 28 March 2023 

Master fix packs 4.8.57_1596_openshift, 4.9.57_1583_openshift, 4.10.53_1561_openshift, 4.11.31_1548_openshift, and 4.12.7_1534_openshift.
: For more information, see the change logs: [4.8](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), and [4.12](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_412).

Worker node fix packs 4.8.57_1597_openshift, 4.9.57_1584_openshift, 4.10.54_1562_openshift, 4.11.32_1549_openshift, and 4.12.8_1535_openshift.
Include the --show-resources option to view more cluster resources such as add-ons for storage pods or subnet VLANs for public and private IPs.

You can review information about the overall cluster, the IBM-managed master, and your worker nodes. To troubleshoot your cluster and worker nodes, see [Troubleshooting clusters](https://cloud.ibm.com/docs/containers?topic=containers-debug_clusters).



* [Cluster states](https://cloud.ibm.com/docs/openshift?topic=openshift-health-monitorstates).
* [Worker node states](https://cloud.ibm.com/docs/openshift?topic=openshift-worker-node-state-reference).





 Master 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.
Did you create a cluster with only a private cloud service endpoint before you enabled your account for [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) and [service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint)? Try [setting up the public cloud service endpoint](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_clusterset-up-public-se) so that you can use your cluster until your support cases are processed to update your account.



1. Enable [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) in your IBM Cloud infrastructure account. To check whether a VRF is already enabled, use the ibmcloud account show command.
2. [Enable your IBM Cloud account to use service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint).
3. Enable the private cloud service endpoint.

ibmcloud ks cluster master private-service-endpoint enable --cluster <cluster_name_or_ID>
4. Refresh the Kubernetes master API server to use the private cloud service endpoint. You can follow the prompt in the CLI, or manually run the following command. It might take several minutes for the master to refresh.

ibmcloud ks cluster master refresh --cluster <cluster_name_or_ID>
5. [Create a configmap](https://cloud.ibm.com/docs/containers?topic=containers-updateworker-up-configmap) to control the maximum number of worker nodes that can be unavailable at a time in your cluster. When you update your worker nodes, the ConfigMap helps prevent downtime for your apps as the apps are rescheduled orderly onto available worker nodes.
6.
Note: If you don't include the --provider option, only classic clusters are returned.

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



 Example cluster ls command 

ibmcloud ks cluster ls -l ams03 -l wdc -l ap







 ibmcloud ks cluster master audit-webhook 

Modify the webhook back end that forwards API server audit logs to a remote server.

The apiserver-config-get|set|unset audit-webhook aliases for these commands are deprecated.



 ibmcloud ks cluster master audit-webhook get 

View the URL for the remote logging service that you are sending API server audit logs to. The URL was specified when you created the webhook back end for the API server configuration.

ibmcloud ks cluster master audit-webhook get --cluster CLUSTER [-q]

Classic infrastructure

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.

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

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



 Example cluster master audit-webhook get command 

ibmcloud ks cluster master audit-webhook get --cluster mycluster







 ibmcloud ks cluster master audit-webhook set 

Classic infrastructure

Set the webhook back end for the API server configuration. The webhook back end forwards API server audit logs to a remote server. After you set the webhook, you must run the ibmcloud ks cluster master refresh command to apply the changes to the Kubernetes master.
Change log for master fix pack 1.22.2_1526, released 29 October 2021 

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



Changes since version 1.22.2_1522

 Component Previous Current Description 

 Cluster health image v1.2.15 v1.2.16 Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs: [CVE-2021-36222](https://nvd.nist.gov/vuln/detail/CVE-2021-36222), [CVE-2021-37750](https://nvd.nist.gov/vuln/detail/CVE-2021-37750), [CVE-2021-22922](https://nvd.nist.gov/vuln/detail/CVE-2021-22922), [CVE-2021-22923](https://nvd.nist.gov/vuln/detail/CVE-2021-22923), and [CVE-2021-22924](https://nvd.nist.gov/vuln/detail/CVE-2021-22924). 
 CoreDNS 1.8.4 1.8.6 See the [CoreDNS release notes](https://coredns.io/2021/10/07/coredns-1.8.6-release/). 
 etcd v3.4.16 v3.4.17 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.17). 
 IBM Calico extension 763 864 Updated to use Go version 1.16.9. Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs. 
 IBM Cloud Controller Manager v1.22.2-1 v1.22.2-3 Updated to ignore VPC load balancer (LB) state when a LB delete is requested.
* [ibmcloud ks cluster master public-service-endpoint enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_master_pub_se_enable)



* [ibmcloud ks cluster master refresh](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_refresh)
* [ibmcloud ks cluster master update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_update)



* cluster pull-secret: Manage image pull secrets for the cluster to access images in IBM Cloud Container Registry.



* [ibmcloud ks cluster pull-secret apply](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_pull_secret_apply)



* [ibmcloud ks cluster rm](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_rm)
* cluster service: View, bind, and unbind IBM Cloud services on a cluster.



* [ibmcloud ks cluster service bind](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_service_bind)
* [ibmcloud ks cluster service ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_services)
* [ibmcloud ks cluster service unbind](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_service_unbind)



* cluster subnet: Add and create portable subnets for a classic cluster.



* [ibmcloud ks cluster subnet add](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_subnet_add)
Review this [release note](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions) for details.

ibmcloud ks worker update --cluster CLUSTER --worker WORKER_ID [-f] [-q]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where you list available worker nodes.

-w, --worker WORKER
: Specify a worker node ID. To reload multiple worker nodes, use multiple options, such as -w worker1_id -w worker2_id.

-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 worker update command 

ibmcloud ks worker update --cluster my_cluster -w kube-dal10-cr18a61a63a6a94b658596aa93d087aaa9-w1 -w kube-dal10-cr18a61a63a6a94b658596aa93d087aaa9-w2









 worker-pool commands 

View and modify worker pools for a cluster.



 ibmcloud ks worker-pool create classic 

Classic infrastructure

You can create a worker pool in your cluster. When you add a worker pool, it is not assigned a zone by default. You specify the number of workers that you want in each zone and the flavors for the workers. The worker pool is given the default Kubernetes versions. To finish creating the workers, [add a zone or zones](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_zone_add) to your pool.
: Replaced the popular topics with this release notes page for new features and updates that are specific to Kubernetes Service. For the latest information on IBM Cloud products, check out the [Announcements](https://www.ibm.com/cloud/blog/announcements).





 20 May 2019 

Version change logs
: Added [worker node fix pack change logs](https://cloud.ibm.com/docs/containers?topic=containers-changelog).





 16 May 2019 

CLI reference
: Updated the [CLI reference page](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli) to add COS endpoints for logging collect commands and to clarify that cluster master refresh restarts the Kubernetes master components.

Unsupported: Kubernetes version 1.10
: [Kubernetes version 1.10](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive) is now unsupported.





 15 May 2019 

Default Kubernetes version
: The default Kubernetes version is now 1.13.6.

Service limits
: Added a [service limitations topic](https://cloud.ibm.com/docs/containers?topic=containers-limitationstech_limits).





 13 May 2019 

Version change logs
"sha": "64245e5f3f1e9c4048b18db3abd1450d4b6f9e263ac1b33df6fc1ae96fcbdebb",
"tags": ["virtualservers"],
"metadata": {
"operating_system": {
"dedicated_host_only": false,
"vendor": "CentOS",
"name": "centos-7-amd64",
"href": "https://us-south-stage01.iaasdev.cloud.ibm.com/v1/operating_systems/centos-7-amd64",
"display_name": "CentOS 7.x - Minimal Install (amd64)",
"family": "CentOS",
"version": "7.x - Minimal Install",
"architecture": "amd64"
},
"minimum_provisioned_size": 100,
"file": {
"size": 1
},
"images": [{"id": "r134-14903434-faf0-4a66-b861-7b35198de393", "name": "virtual-server-image", "region": "us-south"}]
}
}'
Show more







 ibmcloud catalog offering update 

To update a product in your private catalog, you first need get the product and then you can update.

Run the offering get command. For more information, see [ibmcloud catalog offering get](https://cloud.ibm.com/docs/account?topic=account-manage-catalogs-pluginget-offering).

ibmcloud catalog offering get -c <CATALOGID> -o <OFFERINGID> --output json

Run the offering update command.

ibmcloud catalog offering update -c <CATALOGID> -o <OFFERINGID> --updated-offering <UPDATED_OFFERING.json>





 ibmcloud catalog offering version preinstall