vania-janet/multiturn-rag-retrieval-data huggingface dataset:
IBM Cloud Provider v1.12.8-210 v1.12.9-227 Updated to support the Kubernetes 1.12.9 release. 
 Kubernetes v1.12.8 v1.12.9 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.12.9). 
 Kubernetes Metrics Server v0.3.1 v0.3.3 See the [Kubernetes Metrics Server release notes](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.3.3).
* Resolves intermittent networking issues for macOS users.







 Version 0.2.75 

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



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







 Version 0.2.61 

Version 0.2.61 of the CLI was released on 26 February 2019.



* Adds the cluster pull-secret apply command, which creates an IAM service ID for the cluster, policies, API key, and image pull secrets so that containers that run in the default Kubernetes namespace can pull images from IBM Cloud Container Registry. For new clusters, image pull secrets that use IAM credentials are created by default. Use this command to update existing clusters or if your cluster has an image pull secret error during creation. For more information, see [the doc](https://cloud.ibm.com/docs/containers?topic=containers-registrycluster_registry_auth).
* Fixes a bug where ibmcloud ks init failures caused help output to be printed.







 Version 0.2.53 

Version 0.2.53 of the CLI was released on 19 February 2019.



* Fixes a bug where the region was ignored for ibmcloud ks api-key reset, ibmcloud ks credential get/set, and ibmcloud ks vlan spanning get.
* Improves performance for ibmcloud ks worker update.
* Adds the version of the add-on in ibmcloud ks cluster addon enable prompts.







 Version 0.2.44 

Version 0.2.44 of the CLI was released on 8 February 2019.



* Adds --skip-rbac option to the ibmcloud ks cluster config command to skip adding user Kubernetes RBAC roles based on the IBM Cloud IAM service access roles to the cluster configuration. Include this option only if you [manage your own Kubernetes RBAC roles](https://cloud.ibm.com/docs/containers?topic=containers-usersrbac).
1.21 version information and update actions 

Kubernetes version 1.21 becomes unsupported on 14 September 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.

Review information about version 1.21 of IBM Cloud® Kubernetes Service, released 09 Jun 2021.

Looking for general information on updating IBM Cloud® Kubernetes Service clusters, or information on a different version? See [Kubernetes version information and update actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).

Zoom

![This badge indicates Kubernetes version 1.21 certification for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/certified-kubernetes-color.svg)

Figure 1. Kubernetes version 1.21 certification badge

IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.21 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.

For more information about Kubernetes project version 1.21, see the [Kubernetes change log](https://relnotes.k8s.io/).



 Release timeline 

The following table includes the expected release timeline for version 1.21 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release timeline for IBM Cloud Kubernetes Service version 1.21

 Version Supported?
cx2-8x16 Cascade Lake 2593.910 8 130840.32 2.99 1590 
 cx2-16x32 Cascade Lake 2593.910 16 260456.10 2.70 1820 
 cx2-32x64 Cascade Lake 2593.938 32 491829.84 2.61 2270 
 cx2-48x96 Cascade Lake 2593.948 48 740440.18 2.35 1720 







 How IBM Cloud measures performance 

The CoreMark benchmark is created in [PerforKitBenchmarker](https://github.com/GoogleCloudPlatform/PerfKitBenchmarker), an open source cloud benchmarking framework with [ibmcloud provider](https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/tree/master/perfkitbenchmarker/providers/ibmcloud), which is contributed by IBM Cloud® engineers.

For Linux measurements, virtual servers are created with the Red Hat version 8.4 image in the IBM Cloud® public catalog. For Windows measurements, servers are created with the Windows Server 2019 image.
During an upgrade to IKS version 1.25, existing service account token secrets remain in the cluster and continue to function as expected. 
 Application updates required for natPortRange changes. Updates might be required if your app makes a lot of egress network connections from pod-network pods out to something external to the cluster. For example, if your app or has either 30,000+ of egress connections open on a single worker node at once, or opens over 30,000 egress connections on a single worker node within a few minutes of each other. For more information, see [Why am I running out of SNAT ports for egress connections from pods in my cluster?](https://cloud.ibm.com/docs/containers?topic=containers-ts-network-snat-125). 
 Kubernetes CSI snapshot controller installed by default IBM Cloud Kubernetes Service now installs and manages the [Kubernetes CSI snapshot controller](https://github.com/kubernetes-csi/external-snapshotter/releases). As a result, upgrade your storage drivers and plug-ins to versions that don't require installing their own version of the Kubernetes CSI snapshot controller. For example, see [Setting up snapshots with the Block Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-vpc-volume-snapshot) for instructions to enable support for VPC block storage volume snapshots. You do not need to uninstall an existing [Kubernetes CSI snapshot controller](https://github.com/kubernetes-csi/external-snapshotter/releases) install before the upgrade. However after the upgrade, IBM Cloud Kubernetes Service will take over management of the install. 







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

 Type Description 

 kubectl diff ignores managed fields by default The kubectl diff command was changed to ignore managed fields by default.
5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 







 5.6 General policies 



Section 5.6 General policies benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 5.6.1 Create administrative boundaries between resources using namespaces. Not Scored 1 Pass Shared 
 5.6.2 Ensure that the seccomp profile is set to docker/default in your pod definitions. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 
 5.6.3 Apply security context to your pods and containers. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 
 5.6.4 The default namespace should not be used. Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-124cis-benchmark-remediations-124) Shared 









 IBM remediations and explanations 

Review information from IBM on the CIS Benchmark results.



Explanation and remediation

 Section Remediation/Explanation 

 1.2.1 IBM Cloud Kubernetes Service utilizes RBAC for cluster protection, but allows anonymous discovery, which is considered reasonable per [CIS Kubernetes Benchmark](https://www.cisecurity.org/benchmark/kubernetes/). 
 1.2.10 IBM Cloud Kubernetes Service does not enable the [EventRateLimit](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/eventratelimit) admission controller since it is a Kubernetes alpha feature.
1.23 version information and update actions 

Kubernetes version 1.23 becomes unsupported on 08 May 2023. Update your cluster to at least [version 1.24](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_124) as soon as possible.

Review information about version 1.23 of IBM Cloud® Kubernetes Service, released 09 Feb 2022.

Looking for general information on updating IBM Cloud® Kubernetes Service clusters, or information on a different version? See [Kubernetes version information and update actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).

Zoom

![This badge indicates Kubernetes version 1.23 certification for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/certified-kubernetes-color.svg)

Figure 1. Kubernetes version 1.23 certification badge

IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.23 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.

For more information about Kubernetes project version 1.23, see the [Kubernetes change log](https://kubernetes.io/releases/notes/.)



 Release timeline 

The following table includes the expected release timeline for version 1.23 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release timeline for IBM Cloud Kubernetes Service version 1.23

 Version Supported?
* [5.2 Pod Security Policies](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-119cis-benchmark-52-119)
* [5.3 Network policies and CNI](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-119cis-benchmark-53-119)
* [5.4 Secrets management](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-119cis-benchmark-54-119)
* [5.5 Extensible admission control](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-119cis-benchmark-55-119)
* [5.6 General policies](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-119cis-benchmark-56-119)



* [IBM remediations and explanations](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-119cis-benchmark-remediations-119)



[Version 1.18 change log](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog118_changelog)



* [Change log for worker node fix pack 1.18.20_1566, released 27 September 2021](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1566)
* [Change log for master fix pack 1.18.20_1565, released 28 September 2021](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1565)
* [Change log for worker node fix pack 1.18.20_1564, released 13 September 2021](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11820_1564)
Why does my cluster master status say it is approaching its resource limit? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

You see a master status similar to the following example.

The master is approaching its allotted memory resource limit (93%).  Please consider reducing load on your master.  Exceeding the defined resource limit could cause reduced performance for your cluster's master control plane.

  Why it’s happening 

Our managed customer masters have a resource cap that limits the amount of memory and CPU that they can consume.

If your master status shows the previous message, then your master is consuming enough resources to approach its given limit. At this point, this message is a warning. Your master control plane is still healthy and functioning as normal. However, if you don't act, your master can reach the limits, potentially causing performance and functional issues.

  How to fix it 

You have a few options when it comes to dealing with this.



*  Identify the cause of the high resource usage and make changes to reduce the usage.



*  Look for applications that may be generating high load against your master.
*  Reduce the number of resources, such as secrets, configmaps, and replicasets. If a cluster contains a high number of resources, then the queries can cause the master to be overloaded. Use the kubectl get raw command to find the top resources by count. For example, run

kubectl get --raw /metrics | grep ^apiserver_storage_objects | sort -n -k2



*  Request a higher resource limit for your master. To request a higher limit, [open a support ticket](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helphelp-support) with justification. Requests are reviewed and granted on a cluster by cluster basis.
*  Do nothing and risk future performance and functional issues in your master control plane.
1.25 version information and update actions 

Review information about version 1.25 of IBM Cloud® Kubernetes Service, released 03 October 2022.

Looking for general information on updating IBM Cloud® Kubernetes Service clusters, or information on a different version? See [Kubernetes version information and update actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).

Zoom

![This badge indicates Kubernetes version 1.25 certification for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/certified-kubernetes-color.svg)

Figure 1. Kubernetes version 1.25 certification badge

IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.25 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.

For more information about Kubernetes project version 1.25, see the [Kubernetes change log](https://kubernetes.io/releases/notes/.)



 Release timeline 

The following table includes the expected release timeline for version 1.25 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release timeline for IBM Cloud Kubernetes Service version 1.25

 Version Supported? IBM Cloud Kubernetes Service <br>release date IBM Cloud Kubernetes Service <br>unsupported date 

 1.25 Yes 06 October 2022 13 December 2023 







 Preparing to update 

This information summarizes updates that are likely to have and impact on deployed apps when you update a cluster to version 1.25.
Default version
: Kubernetes 1.19 is now the default cluster version.





 23 February 2021 

VPE
: Worker node communication to the Kubernetes master is now established over the [VPC virtual private endpoint (VPE)](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_vpe).





 22 February 2021 

Master versions
: Master fix pack update change log documentation is available for version [1.20.4_1530](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1201204_1530), [1.19.8_1537](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1191198_1537), [1.18.16_1543](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11816_1543), and [1.17.17_1555](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1555).





 20 February 2021 

Certified Kubernetes
: Version [1.20](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_120) release is now certified.





 17 February 2021 

New! Kubernetes 1.20
: You can create or [update](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_120) your cluster to Kubernetes version 1.20. With Kubernetes 1.20, you get the latest stable enhancements from the community, as well as beta access to features such as [API server priority](https://cloud.ibm.com/docs/containers?topic=containers-kubeapi-priority).
* [4 Worker node security configuration](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-section-4-122)



* [4.1 Worker node configuration files](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-41-122)
* [4.2 Kubelet](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-42-122)



* [5 Kubernetes policies](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-section-5-122)



* [5.1 RBAC and service accounts](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-51-122)
* [5.2 Pod Security Policies](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-52-122)
* [5.3 Network policies and CNI](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-53-122)
* [5.4 Secrets management](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-54-122)
* [5.5 Extensible admission control](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-55-122)
* [5.6 General policies](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-56-122)
* [IBM remediations and explanations](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-122cis-benchmark-remediations-122)
IBM Cloud Controller Manager v1.25.6-2 v1.26.1-2 Updated to support the Kubernetes 1.26.1 release. Updated Go dependencies and to Go version 1.19.5. VPC load balancer creation now honors a user specified name. VPC load balancer update now handles an empty default pool name. 
 Key Management Service provider v2.5.13 v2.6.2 Delayed KMS pod termination until the Kubernetes API server terminates. Updated Go dependencies and to Go version 1.19.4. 
 Konnectivity agent and server v0.0.34_491_iks v0.1.0_503_iks See the [Konnectivity release notes](https://github.com/kubernetes-sigs/apiserver-network-proxy/releases/tag/v0.1.0). 
 Kubernetes v1.25.6 v1.26.1 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.26.1). 
 Kubernetes configuration N/A N/A Updated the [kube-proxy configuration](https://cloud.ibm.com/docs/containers?topic=containers-service-settingskube-proxy). 
 Kubernetes add-on resizer 1.8.15 1.8.16 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.8.16). In addition, a liveness probe has been configured to improve availability. 
 Kubernetes DNS autoscaler configuration N/A N/A Memory resource requests were increased from 5Mi to 7Mi to better align with normal resource utilization. In addition, a liveness probe has been configured to improve availability.
* Konnectivity: IBM Cloud Kubernetes Service-specific component to provide secured network connectivity for all Kubernetes master to worker node communication. The Konnectivity server works with the Konnectivity agent to securely connect the master to the worker node. This connection supports apiserver proxy requests to your pods and services, and kubectl top, exec, attach, and logs requests to the kubelet. The connection from the worker nodes to the master is automatically secured with TLS certificates.



Continuous monitoring by IBM Site Reliability Engineers (SREs)
: The Kubernetes master, including all the master components, compute, networking, and storage resources are continuously monitored by IBM Site Reliability Engineers (SREs). The SREs apply the latest security standards, detect and remediate malicious activities, and work to ensure reliability and availability of IBM Cloud Kubernetes Service.

CIS Kubernetes master benchmark
: To configure IBM Cloud Kubernetes Service, IBM engineers follow relevant cybersecurity practices from the Kubernetes master benchmark that is published by the [Center of Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). The cluster master and all worker nodes are deployed with images that meet the benchmark.

Secure communication via TLS
: To use IBM Cloud Kubernetes Service, you must authenticate with the service by using your credentials. When you are authenticated, IBM Cloud Kubernetes Service generates TLS certificates that encrypt the communication to and from the Kubernetes API server and etcd data store to ensure a secure end-to-end communication between the worker nodes and the Kubernetes master. These certificates are never shared across clusters or across Kubernetes master components.

Need to revoke existing certificates and create new certificates for your cluster? Check out [Rotating CA certificates in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-securitycert-rotate).

Connectivity to worker nodes
: Although Kubernetes secures the communication between the master and worker nodes by using the https protocol, no authentication is provided on the worker node by default.
1.20 version information and update actions 

Kubernetes version 1.20 is unsupported as of 19 June 2022. Update your cluster to at least [version 1.21](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_121) as soon as possible.

Review information about version 1.20 of IBM Cloud® Kubernetes Service, released 16 Feb 2021.

Looking for general information on updating IBM Cloud® Kubernetes Service clusters, or information on a different version? See [Kubernetes version information and update actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions).

Zoom

![This badge indicates Kubernetes version 1.20 certification for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/certified-kubernetes-color.svg)

Figure 1. Kubernetes version 1.20 certification badge

IBM Cloud Kubernetes Service is a Certified Kubernetes product for version 1.20 under the CNCF Kubernetes Software Conformance Certification program. Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries, and is used pursuant to a license from The Linux Foundation.

For more information about Kubernetes project version 1.20, see [Kubernetes documentation](https://kubernetes.io/docs/home/).



 Release timeline 

The following table includes the expected release timeline for version 1.20 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release timeline for IBM Cloud Kubernetes Service version 1.20

 Version Supported?