vania-janet/multiturn-rag-retrieval-data huggingface dataset:
on linux_amd64
Show more





 Version 2.27 

To view the contents of version 2.27, from the running image, type default_versions.sh.

The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image updated its version of node.js to 16.18.1. If you need to use a different version of node.js, use nvm install v<node version> at the beginning of your script. You cannot use the current version of LTS (18.12.1) yet. This image now contains the Terraform CLI.

This image includes the following tools:

 node --version
v16.18.1

 npm --version
8.19.2

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version v4.30.6

 kubectl version --client
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Alarm reviewed as part of proactive daily checks. [Troubleshooting licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3C4E8BF7-B0A9-46F0-BA50-D69F950AB958.html) 
 The host license edition is not compatible with the vCenter Server license edition Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [Troubleshooting host licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-B9DAAF47-94EC-47F5-8523-9C8C019412E1.html) 
 Timed out starting Secondary VM * Not configured as it monitors VMware Fault Tolerance, which is not recommended for vCenter Server instances. [Timeout starting Secondary VM alarm (2064169)](https://kb.vmware.com/s/article/2064169) 
 No compatible host for Secondary VM Not configured as it monitors VMware Fault Tolerance, which is not recommended for vCenter Server instances. No additional information 
 Virtual machine Fault Tolerance state changed Not configured as it monitors VMware Fault Tolerance, which is not recommended for vCenter Server instances. No additional information 
 Virtual machine fault tolerance vLockStep interval status changed Not configured as it monitors VMware Fault Tolerance, which is not recommended for vCenter Server instances. No additional information 
 Host processor status Configure to send email one time when monitor changes from green to red. [Contact IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support) 
 Host memory status Configure to send email one time when monitor changes from green to red.
Built: Thu Sep 8 23:05:51 2022
OS/Arch: linux/amd64
Context: default

 dc --version
dc (GNU bc 1.07.1) 1.4.1

 ed --version
GNU Ed 1.10
Show more





 Version 2.22 

To view the contents of version 2.22, from the running image, type default_versions.sh.

The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image updated its version of node.js to the current LTS version 16.17.0. If you need to use a different version of node.js, use nvm install v<node version> at the beginning of your script.

This image includes the following tools:

 node --version
v16.17.0

 npm --version
8.15.0

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version 4.27.2

 kubectl version --client
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
[vSAN Health Service - Performance Service - Stats DB object check (2144403)](https://kb.vmware.com/s/article/2144403) 
 vSAN health alarm Stats master election Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [vSAN Health Service - Performance Service - Stats master election check (2144408)](https://kb.vmware.com/s/article/2144408) 
 vSAN health alarm Stretched cluster health Not considered essential for notification. Alarm reviewed as part of proactive daily checks. No additional information 
 vSAN health alarm Time is not synchronized across hosts and VC Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [vSAN Health Service - Cluster Health - Time Synchronization Across Hosts and VC (2149505)](https://kb.vmware.com/s/article/2149505) 
 vSAN health alarm Unexpected number of fault domains Consider alarm only if vSAN has been stretched. [vSAN Health Service - Unexpected number of fault domains (2130581)](https://kb.vmware.com/s/article/2130581) 
 vSAN health alarm Unicast agent configuration inconsistent Consider alarm only if vSAN has been stretched. [vSAN Health Service - Unicast agent configuration inconsistent (2130580)](https://kb.vmware.com/s/article/2130580) 
 vSAN health alarm Unicast agent not configured Consider alarm only if vSAN has been stretched. [vSAN Health Service - Unicast agent not configured (2130582)](https://kb.vmware.com/s/article/2130582) 
 vSAN health alarm vCenter or hosts are not connected to Key Management Servers Consider alarm only if vSAN encryption is enabled. [vSAN Health Service - Encryption - Key Management Servers Connection Check (2149497)](https://kb.vmware.com/s/article/2149497) 
 vSAN health alarm vCenter state is authoritative Not considered essential for notification.
on linux_amd64
Show more





 Version 2.28 

To view the contents of version 2.28, from the running image, type default_versions.sh.

The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image updated its version of node.js to 16.18.1. If you need to use a different version of node.js, use nvm install v<node version> at the beginning of your script. You cannot use the current version of LTS (18.12.1) yet. This image now contains the Terraform CLI.

This image includes the following tools:

 node --version
v16.18.1

 npm --version
8.19.2

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version v4.30.8

 kubectl version --client
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/2302-ea5fe79f-52c3-4f05-86ae-9540a10489f5",
"id": "2302-ea5fe79f-52c3-4f05-86ae-9540a10489f5",
"name": "my-subnet",
"resource_type": "subnet"
},
"transit_encryption": "none",
"virtual_network_interface": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/virtual_network_interfaces/4727d842-f94f-4a2d-824a-9bc9b02c523b",
"id": "4727d842-f94f-4a2d-824a-9bc9b02c523b",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:[...]",
"href": "$vpc_api_endpoint/v1/vpcs/8c95b3c1-fe3c-45c-97a6-e43d14088287",
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}
Show more

The mount target is deleted in the background. Confirm the deletion by trying to view the mount target information.
[Knowledge - KB0012729 v0.01](https://watson.service-now.com/nav_to.do?uri=kb_knowledge.do?sys_id=15dddea2db857300d5a971198c961995) 
 Virtual machine disk commands canceled Do not set initially. Consider for critical appliances at second stage. No additional information 
 Virtual machine disk reset Do not set initially. Consider for critical appliances at second stage. No additional information 
 License inventory monitoring Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [Troubleshooting licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3C4E8BF7-B0A9-46F0-BA50-D69F950AB958.html) and [Licensing ESXi 6.x and vCenter Server 6.x](https://kb.vmware.com/s/article/2107538) 
 License user threshold monitoring Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [Troubleshooting licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3C4E8BF7-B0A9-46F0-BA50-D69F950AB958.html) 
 License capacity monitoring Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [Troubleshooting licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3C4E8BF7-B0A9-46F0-BA50-D69F950AB958.html)
[Creating and Using vSphere HA Clusters](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-5432CA24-14F1-44E3-87FB-61D937831CF6.html) 
 License error * Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [Troubleshooting licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3C4E8BF7-B0A9-46F0-BA50-D69F950AB958.html) 
 Health status changed * Configure to send email one time if status changes to critical. [Troubleshooting hosts](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-6F6CE545-58FA-490B-8C8A-3CB8196CAEA8.html) 
 Storage DRS recommendation Not considered essential for notification. Alarm is reviewed as part of proactive daily checks. [DRS troubleshooting information](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-5E7F6DEC-02A2-4221-AABA-EDFB9AE9EC70.html) 
 Storage DRS is not supported on a host Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks.
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/2302-ea5fe79f-52c3-4f05-86ae-9540a10489f5",
"id": "2302-ea5fe79f-52c3-4f05-86ae-9540a10489f5",
"name": "my-subnet",
"resource_type": "subnet"
},
"transit_encryption": "none",
"virtual_network_interface": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/virtual_network_interfaces/4727d842-f94f-4a2d-824a-9bc9b02c523b",
"id": "4727d842-f94f-4a2d-824a-9bc9b02c523b",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:[...]",
"href": "$vpc_api_endpoint/v1/vpcs/8c95b3c1-fe3c-45c-97a6-e43d14088287",
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}

The mount target is deleted in the background. Confirm the deletion by trying to view the mount target information. If you get _404 Not Found_ error, the mount target is successfully deleted.
Upgrading the Windows logging agent from V2 to V3 

The logging agent is responsible for collecting and forwarding logs to your IBM Log Analysis instance. If you have installed V2 of the Windows agent you will want to upgrade to V3.

To uninstall the you existing V2 Windows agent, run the following command.

choco uninstall logdna-agent

Then install the V3 Windows agent using [these instructions.](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_agent_windows_v3)
VMware vCenter Server instances
: The 4.3 release applies the following upgrades and improvements for newly deployed instances, clusters, and hosts.



* VMware vSphere ESXi



* 7.0 Update 2a (build 17867351)
* 6.7 P05 (build 17700523)
* 6.5 P06 (build 17477841)



* VMware vCenter Server Appliance



* 7.0 Update 2b (build 17958471/17958471)
* 6.7 Update 3n (build 18010531/18010599)



* VMware NSX-T 3.1.0.0.0 (build 17107167)
* VMware NSX-V 6.4.10 (build 17626462)
* VMware vSAN 7.0 Update 2 (build 17630552) or 6.7 P05



vCenter Server multizone instances - deprecated
: New deployments of vCenter Server multizone instances are no longer supported.

You can still add and delete clusters, add and remove ESXi servers, and add and delete storage for existing multizone instances.

VMware Regulated Workloads - support for consolidated cluster
: Rather than requiring that the VMware Regulated Workloads solution deploys a separate management cluster and separate clusters for workloads, now you can start with a smaller footprint by deploying a consolidated management and workload cluster.

VMware Regulated Workloads - support for save configuration
: A new Save configuration button is added to the Summary pane of the ordering page for VMware Regulated Workloads. Use this option to save your instance settings as a configuration template without placing an order. You can manage the configuration templates by further editing or deleting them as well.

Security and Compliance Readiness Bundle
: A new Save configuration button is added to the Summary pane of the ordering page for Security and Compliance Readiness Bundle instances. Use this option to save your instance settings as a configuration template without placing an order. You can manage the configuration templates by further editing or deleting them as well.

Add-on services
Like all locations, the IBM Cloud® London location (eu-gb) uses token-based Identity and Access Management (IAM) authentication. All new services instances that you create in this location use IAM authentication.

Update to version string : The Discovery tooling now uses the API version of 2018-12-03(it previously used 2018-08-01).





 12 December 2018 

New feature for Stopwords : Added the ability to define and upload a custom stopwords list. Custom stopwords are implemented with the Discovery API. See [Defining stopwords](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptsstopwords) for details.





 3 December 2018 

New confidence score support : For all queries written, using the API version of 2018-12-03 or above, with the exception of filter-only queries, Discovery now returns a confidence score in the query results set, even if the collection was not trained, using a supervised training method, such as [Relevancy training](https://cloud.ibm.com/docs/discovery?topic=discovery-improving-result-relevance-with-the-tooling) or [Continuous Relevancy Training](https://cloud.ibm.com/docs/discovery?topic=discovery-crt). In addition, Discovery returns a document_retrieval_strategy field that indicates the source of the confidence score of untrained, relevancy_training, or continuous_relevancy_training. For more information, see [Confidence scores](https://cloud.ibm.com/docs/discovery?topic=discovery-improving-result-relevance-with-the-toolingconfidence).

Update to version string : The version string for all API calls changed to 2018-12-03 from 2018-10-15. The Discovery tooling does not yet use this API version (it currently uses 2018-08-01), so queries written using the Discovery tooling does not return a confidence score for untrained collections.





 8 November 2018 

New Tokyo location now available : Discovery launched in the Tokyo location 8 November 2018. Premium and Dedicated environments are not currently available in Tokyo.





 30 October 2018
* [CVE-2021-44717](https://nvd.nist.gov/vuln/detail/CVE-2021-44717)







 Change log for version 2.1.8, released 17 January 2022 



* Updates the UBI to version 8.5-218.
* Resolves [CVE-2021-3712](https://nvd.nist.gov/vuln/detail/CVE-2021-3712).
* Fixes an issue that prevented masking keys in the PVC logs.







 Change log for version 2.1.7, released 18 November 2021 



* Updates the UBI to version 8.5-204.
* Updates Golang to version 1.16.10.
* Resolves [CVE-2021-41772](https://nvd.nist.gov/vuln/detail/CVE-2021-41772), [CVE-2021-41771](https://nvd.nist.gov/vuln/detail/CVE-2021-41771), and [CVE-2021-22947](https://nvd.nist.gov/vuln/detail/CVE-2021-22947).







 Change log for version 2.1.6, released 22 October 2021 



* Image tags: 1.8.36
* Updates s3fs fuse to version 1.90
* Updates dependencies







 Change log for version 2.1.5, released 5 October 2021 



* Image tags: 1.8.34
* Resolves [CVE-2021-36221](https://nvd.nist.gov/vuln/detail/CVE-2021-36221), [CVE-2021-29923](https://nvd.nist.gov/vuln/detail/CVE-2021-29923), and [CVE-2021-33196](https://nvd.nist.gov/vuln/detail/CVE-2021-33196).
* Updates the UBI to 8.4-210.
Name replica-share-3
CRN crn:v1:staging:public:is:us-south-3:a/efe5afc483594adaa8325e2b4d1290df::share:4de3d510-b0db-4674-9dea-c9b93e26b1c3
Lifecycle state pending
Zone us-south-3
Profile tier-5iops
Size(GB) 40
IOPS 3000
Encryption provider_managed
Mount targets ID Name VPC ID VPC Name
No mounted targets found.

Resource group ID Name
11caaa983d9c4beb82690daab08717e9 Default

Created 2022-09-28T10:45:13+05:30
Last sync at 2022-09-28T05:53:28+05:53
Latest job running
Replication share ID Name Resource type

Replication cron spec 10 05 * * 
Replication role replica
Replication status initializing
Source share ID Name Resource type
2c4c32f9-9d25-43df-9d59-3874a81ec46e share-3 share







 Add replication to file share with the API 

Use the API to add replication to new or existing file shares. Before you begin, first set up the [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environment&interface=api). For more information about the file shares VPC API, see the [VPC API reference](https://cloud.ibm.com/apidocs/vpc-beta).



 Create a file share with replication with the API 

When you create a file share, you can specify that a replica file share is also created in a different zone. Make a POST /shares request and specify the replica_share property to define the replica file share.
* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-24536](https://nvd.nist.gov/vuln/detail/CVE-2023-24536), [CVE-2023-24537](https://nvd.nist.gov/vuln/detail/CVE-2023-24537), [CVE-2023-24538](https://nvd.nist.gov/vuln/detail/CVE-2023-24538).







 Version 4.11.4, released 14 February 2023 

Updates the UBI image to version 8.7-1049.1675784874.





 Version 4.11.3, released 18 January 2023 

Updates the UBI image to version 8.7-1049.





 Version 4.11.2, released 03 January 2023 

Updates Golang to 1.18.9.





 Version 4.11.0, released 21 December 2022 

Initial release.







 Version 4.10 



 Version 4.10.27, release 28 June 2023 



* Golang updated to 1.20.5.







 Version 4.10.26 release 09 June 2023 



* Golang updated to 1.19.9.
* Updates the UBI image to 8.8-860.







 Version 4.10.24, release 05 May 2023 



* Golang updated to 1.19.8.
* [CVE-2021-22925](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22925)



: For more information, see the [Istio security bulletin 2021-008](https://istio.io/latest/news/security/istio-security-2021-008/).







 Version 1.10 (unsupported) 

Review the changes that are in version 1.10 of the managed Istio add-on.

Version 1.10 of the managed Istio add-on is unsupported.



 Change log for 1.10.6, released 13 January 2022 

Review the changes that are included in version 1.10.6 of the managed Istio add-on.

Previous version
: 1.10.5

Current version
: 1.10.6

Updates in this version
: See the Istio release notes for [Istio 1.10.6](https://istio.io/latest/news/releases/1.10.x/announcing-1.10.6/).





 Change log for 1.10.5, released 28 October 2021 

Review the changes that are in version 1.10.5 of the managed Istio add-on.

Previous version
: 1.10.4

Current version
: 1.10.5

Updates in this version
: See the Istio release notes for [Istio 1.10.5](https://istio.io/latest/news/releases/1.10.x/announcing-1.10.5/).
: Resolves the following CVEs



* [CVE-2021-22945](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22945)
* [CVE-2021-22946](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22946)
RHEL 7 Packages 3.10.0-1160.36.2.el7 3.10.0-1160.42.2.el7 Updated worker node image with package updates for [CVE-2021-25214](https://nvd.nist.gov/vuln/detail/CVE-2021-25214), [CVE-2020-27777](https://nvd.nist.gov/vuln/detail/CVE-2020-27777), [CVE-2021-22555](https://nvd.nist.gov/vuln/detail/CVE-2021-22555), [CVE-2021-29154](https://nvd.nist.gov/vuln/detail/CVE-2021-29154), [CVE-2021-29650](https://nvd.nist.gov/vuln/detail/CVE-2021-29650), [CVE-2021-32399](https://nvd.nist.gov/vuln/detail/CVE-2021-32399), [CVE-2021-3715](https://nvd.nist.gov/vuln/detail/CVE-2021-3715). 







 Change log for worker node fix pack 4.7.24_1530_openshift, released 30 August 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.7.24_1530_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.7.23_1528_openshift

 Component Previous Current Description 

 OpenShift Container Platform 4.7.23 4.7.24 See [change logs](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-43). 







 Change log for master fix pack 4.7.23_1529_openshift, released 25 August 2021
.
: Resolves the following CVEs:



* [usn-5473-1](https://ubuntu.com/security/notices/USN-5473-1)
* [CVE-2022-32205](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32205)
* [CVE-2022-32206](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32206)
* [CVE-2022-32207](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32207)
* [CVE-2022-32208](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32208)
* [CVE-2022-1304](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1304)
* [CVE-2022-2097](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2097)
* [CVE-2022-2068](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2068)







 Change log for 1.13.5, released 21 June 2022 

Review the changes that are included in version 1.13.5 of the managed Istio add-on.

Previous version
: 1.13.4

Current version
: 1.13.5

Updates in this version
* Updates Go to version 1.19.7.







 Revision 8, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 7, released 06 March 2023 



* Resolves the following CVEs: [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415)[CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735)[CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861)[CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061)[CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897)[CVE-2022-41723](https://nvd.nist.gov/vuln/detail/CVE-2022-41723)[CVE-2022-41724](https://nvd.nist.gov/vuln/detail/CVE-2022-41724)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.
IBM Cloud RBAC Operator 4ca5637 3430e03 Updated universal base image (UBI) to the latest 8.5 version to resolve CVEs. Updated to use Go version 1.16.10. 
 Key Management Service provider v2.3.10 v2.3.12 Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs. Updated to use Go version 1.16.10. 
 Konnectivity agent v0.0.24_268_iks v0.0.26_282_iks See the [Konnectivity release notes](https://github.com/kubernetes-sigs/apiserver-network-proxy/releases/tag/v0.0.26). 
 Konnectivity server v0.0.24_268_iks v0.0.26_282_iks See the [Konnectivity release notes](https://github.com/kubernetes-sigs/apiserver-network-proxy/releases/tag/v0.0.26). Updated to use TLS version 1.3 ciphers. 
 Kubernetes v1.22.3 v1.22.4 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.22.4). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1590 1659 Updated Alpine base image to the latest 3.14 version to resolve CVEs. Updated to use Go version 1.16.10.