vania-janet/multiturn-rag-retrieval-data huggingface dataset:
- -c
- sysctl -e -w net.ipv4.tcp_keepalive_time=40; sysctl -e -w net.ipv4.tcp_keepalive_intvl=15; sysctl -e -w net.ipv4.tcp_keepalive_probes=6;
image: us.icr.io/armada-master/alpine:latest
imagePullPolicy: IfNotPresent
name: sysctl-init
resources: {}
securityContext:
privileged: true
containers:
- name: test-sysctl
image: us.icr.io/armada-master/alpine:latest
command: ["sleep", "2592000"]
EOF

Show more





 Changing the Calico maximum transmission unit (MTU) 

Increase or decrease the Calico plug-in maximum transmission unit (MTU) to meet the network throughput requirements of your environment.

All VPC workers nodes support jumbo frames. However, on classic infrastructure, only bare metal workers support jumbo frames.

By default, the Calico network plug-in in your Red Hat OpenShift on IBM Cloud cluster has an MTU of 1480 bytes. For most cases, this default MTU value provides sufficient throughput for packets that are sent and received in your network workloads. Review the following cases in which you might need to modify the default Calico MTU:



* Jumbo frames have an MTU value in the range of 1500 to 9000. To ensure that your cluster's pod network can use this higher MTU value, you can increase the Calico MTU to 20 bytes less than the jumbo frame MTU. This 20 byte difference allows space for packet header on encapsulated packets. For example, if your worker nodes' jumbo frames are set to 9000, you can set the Calico MTU to 8980. Note that all worker nodes in the cluster must use the same Calico MTU, so to increase the Calico MTU, all worker nodes in the cluster must be bare metal and use jumbo frames.
x-amz-date: 20160825T183244Z
Host: s3.us.cloud-object-storage.appdomain.cloud

Sample response

HTTP/1.1 200 OK
Date: Wed, 7 Feb 2018 19:51:00 GMT
X-Clv-Request-Id: da214d69-1999-4461-a130-81ba33c484a6
Accept-Ranges: bytes
Server: 3.x
X-Clv-S3-Version: 2.5
ETag: "37d4c94839ee181a2224d6242176c4b5"
Content-Type: text/plain; charset=UTF-8
Last-Modified: Thu, 25 Aug 2017 17:49:06 GMT
Content-Length: 11
x-ibm-transition: transition="ARCHIVE", date="Mon, 03 Dec 2018 22:28:38 GMT"
x-amz-restore: ongoing-request="false", expiry-date="Thu, 06 Dec 2018 18:28:38 GMT"
x-amz-storage-class: "GLACIER"
x-ibm-restored-copy-storage-class: "Standard"



* Java
* Python
* Node



public ObjectMetadata()

response = client.head_object(
Bucket='string',
Key='string'
)

var params = {
Bucket: 'STRING_VALUE', /* required /
Key: 'STRING_VALUE', /* required /
};
s3.headObject(params, function(err,data) {
if (err) console.log(err, err.stack); // an error occurred
else
console.log(data); // successful response
});

Method Summary



 Method Description 

 clone() Returns a clone of this ObjectMetadata.
"LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0t ...<redacted>... QyBLRVktLS0tLQo="
}





 Required parameters 

-i, --instance-id
: The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command.

$ export KP_INSTANCE_ID=INSTANCE_ID





 Optional parameters 

-e, --expiration
: Specify an expiration time (in seconds) for an import token. This value determines how long the import token and its associated public key remain valid for operations.

The minimum value is 300 seconds (5 minutes), and the maximum value is 86400 seconds (24 hours). The default value is 600 seconds (10 minutes).







 kp import-token key-encrypt 

Encrypt the key material that you import into Key Protect by using the public key that's associated with your Key Protect instance.

Then, provide the retrieved encrypted key when you run ibmcloud kp key create to import the key to the service.

ibmcloud kp import-token key-encrypt
-i, --instance-id INSTANCE_ID
-k, --key KEY_MATERIAL
-p, --pubkey PUBLIC_KEY
[-a, --hash HASH_ALGORITHM]



 Example 

This example encrypts a key material using the public key created by kp import-token create.

 create an import token that expires in 5 minutes and allows 10 retrievals
$ ibmcloud kp import-token create -e 300 -m 10

 create a random, base64-encoded, 32-byte key material
$ KEY_MATERIAL=$(openssl rand -base64 32)

 extract the public key that was created by the "kp import-token create" command
$ PUBLIC_KEY=$(ibmcloud kp import-token show | jq -r '.["payload"]')

 encrypt the key material using the public key
: Version 2.1.10 of the IBM Cloud Object Storage plug-in [is available](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog).





 16 February 2022 

HPCS Router add-on
: Version 4.9.0 of the [HPCS Router add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) is available.





 14 February 2022 

Worker node fix pack
: Red Hat OpenShift [4.9.19_1526_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494919_1526), [4.8.29_1544_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_484829_1544), [4.7.42_1549_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474742_1549), [4.6.53_1572_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464653_1572), and [3.11.570_1621_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311570_1621).

IBM Cloud Object Storage doc restructuring.
ibmcloud hpcs uko managed-keys [--vault-id VAULT-ID] [--algorithm ALGORITHM] [--state STATE] [--limit LIMIT] [--offset OFFSET] [--sort SORT] [--label LABEL] [--activation-date ACTIVATION-DATE] [--activation-date-min ACTIVATION-DATE-MIN] [--activation-date-max ACTIVATION-DATE-MAX] [--deactivation-date DEACTIVATION-DATE] [--deactivation-date-min DEACTIVATION-DATE-MIN] [--deactivation-date-max DEACTIVATION-DATE-MAX] [--expiration-date EXPIRATION-DATE] [--expiration-date-min EXPIRATION-DATE-MIN] [--expiration-date-max EXPIRATION-DATE-MAX] [--created-at CREATED-AT] [--created-at-min CREATED-AT-MIN] [--created-at-max CREATED-AT-MAX] [--updated-at UPDATED-AT] [--updated-at-min UPDATED-AT-MIN] [--updated-at-max UPDATED-AT-MAX] [--size SIZE] [--size-min SIZE-MIN] [--size-max SIZE-MAX] [--referenced-keystores-type REFERENCED-KEYSTORES-TYPE] [--referenced-keystores-name REFERENCED-KEYSTORES-NAME] [--instances-keystore-type INSTANCES-KEYSTORE-TYPE]



* Command options

--vault-id ([]string)
: Optional. The Universally Unique Identifier (UUID) of the vault. You can use the ibmcloud hpcs uko managed-keys command to retrieve the UUID. The length must be 36 characters. The list items must match the regular expression /^[-0-9a-z]+$/.

--algorithm ([]string)
: Optional. The algorithm of returned keys. Values that can be set are aes, rsa, hmac, and ec.

--state ([]string)
: Optional. The state that returned keys are to be in.
Release notes for IBM Spectrum Scale 

Use these release notes to learn about the latest updates to IBM® Spectrum Scale that are grouped by date.



  March 2023 



  10 March 2023 

Persistent Spectrum Scale storage (GA)
:   The persistent Spectrum Scale storage feature is now generally available. Users can deploy a persistent storage configuration that uses bare metal servers with locally attached NVMe storage.







  November 2022 



  10 November 2022 

Spectrum Scale evaluation (Developer Edition) storage
:   With the evaluation storage feature, users can try out the Spectrum Scale solution on IBM Cloud® without a license. The automated deployment is done on virtual server instances with instance storage, with Spectrum Scale Developer Edition packages, and is available only for prototyping and testing purposes. For more information, see [Storage types](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-storage-types).







  September 2022 



  22 September 2022 

Persistent Spectrum Scale storage (Beta)
:   With the persistent Spectrum Scale storage beta feature, users can now deploy a persistent storage configuration that uses bare metal servers with locally attached NVMe storage. This is a beta feature that is available for evaluation and testing purposes. There are no warranties, SLAs, or support provided for persistent storage and it is not intended for production use.

Updated Spectrum Scale software version
:   The Spectrum Scale version used for configuration of the compute and storage clusters has been updated to version 5.1.4.1.







  June 2022 



  10 June 2022 

Introducing IBM Spectrum Scale storage for HPC solutions
:   You now have the option for automated deployment of compute and storage clusters that use IBM Spectrum Scale for high-performance, shared storage for your HPC solutions. The clusters use the compute and storage node configurations that you select.
Tokyo AP Cross Regional Object Storage 
 Osaka AP Cross Regional Object Storage 
 Sydney AP Cross Regional Object Storage 
 Toronto Montreal Object Storage 
 Chennai Chennai Object Storage 
 Sao Paolo Sao Paolo Object Storage 



For more details about Cloud Databases Object Storage locations, review the location's [documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-geo).





 Point-in-Time Recovery 

With Point-in-Time Recovery (PITR), the deployment continuously backs up incrementally and can replay transactions to bring a new deployment that is restored from a backup to any point in the last 7 days. Cloud Databases offers Point-In-Time Recovery (PITR) for the following services:



* [IBM Cloud® Databases for MySQL](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-pitr)
* [IBM Cloud® Databases for PostgreSQL](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr)
* [IBM Cloud® Databases for EnterpriseDB](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-pitr&interface=ui)
22 June 2023 

Storage template revisions
: Revisions of the Satellite storage templates are available. For more information, see the [Storage template version history](https://cloud.ibm.com/docs/satellite?topic=satellite-sitemapsitemap_storage_template_version_history).





 12 June 2023 

RHCOS enabled locations with reduced firewall
: You can now create Satellite locations with a reduced footprint. For more information, see [Creating Red Hat CoreOS enabled Locations with reduced firewall footprint](https://cloud.ibm.com/docs/satellite?topic=satellite-coreos-reduced-firewall).







 May 2023 



 17 May 2023 

Storage template revisions
: Revisions of the Satellite storage templates are available. For more information, see the [Storage template version history](https://cloud.ibm.com/docs/satellite?topic=satellite-sitemapsitemap_storage_template_version_history).





 04 May 2023 

Storage template revisions
: Revisions of the Satellite storage templates are available. For more information, see the [Storage template version history](https://cloud.ibm.com/docs/satellite?topic=satellite-sitemapsitemap_storage_template_version_history).







 April 2023 



 25 April 2023 

Storage template revisions
: Revisions of the Satellite storage templates are available. For more information, see the [Storage template version history](https://cloud.ibm.com/docs/satellite?topic=satellite-sitemapsitemap_storage_template_version_history).





 05 April 2023 

Storage template revisions
: Revisions of the Satellite storage templates are available. For more information, see the [Storage template version history](https://cloud.ibm.com/docs/satellite?topic=satellite-sitemapsitemap_storage_template_version_history).







 March 2023 



 27 March 2023 

New! You can download a .csv copy of your outbound network requirements.
: Optional. Endurance Storage Tier (IOPS per GB) of the file volume for which space is ordered. Options are: 0.25, 2, 4, 10.

-i, --iops
: Performance Storage IOPs. Range 100-6000, and in multiples of 100.

-u, --upgrade
: Flag to indicate that the order is an upgrade.

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file snapshot-order 12345678 -s 1000 -t 4

This commands orders a snapshot space for the volume with ID 12345678. The size is 1000 GB, and the tier level is 4 IOPS per GB.





 ibmcloud sl file snapshot-restore 

Restore a file volume by using a specified snapshot:

ibmcloud sl file snapshot-restore VOLUME_ID SNAPSHOT_ID

Examples:

ibmcloud sl file snapshot-restore 12345678 87654321

This command restores volume with ID 12345678 from snapshot with ID 87654321.





 ibmcloud sl file snapshot-schedule-list 

List snapshot schedules for a volume:

ibmcloud sl file snapshot-schedule-list VOLUME_ID

Examples:

ibmcloud sl file snapshot-schedule-list 12345678

This command list snapshot schedules for volume with ID 12345678.





 ibmcloud sl file volume-cancel 

Cancel an existing file storage volume:

ibmcloud sl file volume-cancel VOLUME_ID [OPTIONS]

Command options:

--reason
: An optional reason for cancellation.

--immediate
: Cancel the file storage volume immediately instead of on the billing anniversary.

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file volume-cancel 12345678 --immediate -f

This command cancels volume with ID 12345678 immediately and without asking for confirmation.





 ibmcloud sl file volume-count 

List number of file storage volumes per data center:
Osaka AP Cross Regional Object Storage 
 Sydney AP Cross Regional Object Storage 
 Toronto Montreal Object Storage 
 Chennai Chennai Object Storage 
 Sao Paolo Sao Paolo Object Storage 



For more details about Cloud Databases Object Storage locations, review the location's [documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-geo).





 Point-in-Time Recovery 

With Point-in-Time Recovery (PITR), the deployment continuously backs up incrementally and can replay transactions to bring a new deployment that is restored from a backup to any point in the last 7 days. Cloud Databases offers Point-In-Time Recovery (PITR) for the following services:



* [IBM Cloud® Databases for MySQL](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-pitr)
* [IBM Cloud® Databases for PostgreSQL](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr)
* [IBM Cloud® Databases for EnterpriseDB](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-pitr&interface=ui)
Continuous Delivery service location Object Storage backup service location 

 Dallas (us-south) US Cross Region (Dallas, Washington, San Jose) 
 Washington (us-east) US Cross Region (Dallas, Washington, San Jose) 
 London (eu-gb) EU Cross Region (Amsterdam, Frankfurt, Milan) 
 Frankfurt (eu-de) EU Cross Region (Amsterdam, Frankfurt, Milan) 
 Tokyo (jp-tok) AP Cross Region (Osaka, Sydney, Tokyo) 
 Sydney (au-syd) AP Cross Region (Osaka, Sydney, Tokyo) 
 Osaka (jp-osa) AP Cross Region (Osaka, Sydney, Tokyo) 
 Toronto (ca-tor) US Cross Region (Dallas, Washington, San Jose, Toronto) 
 Sao Paulo (br-sao) US Cross Region (Dallas, Washington, San Jose, Toronto, Sao Paulo) 



For more information about Object Storage locations, see [Regional Endpoints](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-region).

For more information about Continuous Delivery disaster recovery, see [Disaster recovery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-responsibilities-cddisaster-recovery).
* [Revision 10, released 04 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-object-storage-pluginibm-object-storage-plugin-2.2-rev-10-change-log)
* [Revision 9, released 21 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-object-storage-pluginibm-object-storage-plugin-2.2-rev-9-change-log)
* [Revision 8, released 06 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-object-storage-pluginibm-object-storage-plugin-2.2-rev-8-change-log)
* [Revision 7, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-object-storage-pluginibm-object-storage-plugin-2.2-rev-7-change-log)





[ibm-spectrum-fusion change log](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-spectrum-fusioncl-ibm-spectrum-fusion)



* [Version 2.4.0](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-spectrum-fusion2.4.0-change-log)



* [Revision 1, released 29 July 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-spectrum-fusionibm-spectrum-fusion-2.4.0-rev-1-change-log)





[ibm-system-storage-block-csi-driver change log](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ibm-system-storage-block-csi-drivercl-ibm-system-storage-block-csi-driver)
: For more information, see the change logs: [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410),[4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49).





 10 November 2022 

Istio add-on version 1.15.3
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1153).





 9 November 2022 

Block Storage for VPC add-on version 4.4.12_1700 and 5.0.1_1695
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).





 8 November 2022 

IBM Cloud Object Storage plug-in version 2.2.2 is available.
: For more information, see the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog).





 7 November 2022 

Worker node fix pack 4.11.12_1530_openshift, 4.10.39_1543_openshift, 4.9.51_1563_openshift, 4.8.52_1579_openshift, 4.7.59_1588_openshift, 4.6.61_1603_openshift
* Master fix pack 4.7.59_1589_openshift, 4.8.52_1580_openshift, 4.9.51_1565_openshift, 4.10.39_1545_openshift, and 4.11.12_1532_openshift.



* [15 November 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-nov1522)



* New Ingress status messages
* IBM Cloud Object Storage plug-in version 2.2.3 is available.



* [11 November 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-nov1122)



* Block Storage for VPC add-on version 4.3.8_1705
* Worker node fix pack 4.11.12_1531_openshift, 4.10.39_1544_openshift, 4.9.51_1564_openshift



* [10 November 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-nov1022)



* Istio add-on version 1.15.3



* [9 November 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-nov0922)



* Block Storage for VPC add-on version 4.4.12_1700 and 5.0.1_1695



* [8 November 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-nov0822)



* IBM Cloud Object Storage plug-in version 2.2.2 is available.
Deploying an app on OpenShift Data Foundation 

After you install the OpenShift Data Foundation add-on for your Red Hat® OpenShift® on IBM Cloud® cluster, you can use the ODF storage classes to create a persistent volume claim (PVC). Then, refer to the PVC in your deployment so that your app can save and use data from the underlying ODF storage device.

Minimum required permissions
: Editor platform access role and the Writer service access role for the cluster in IBM Cloud Kubernetes Service.

[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. List the ODF storage classes. For more information about ODF storage classes, see the [Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-sc-refocs-sc-ref).

oc get sc | grep openshift

Example output

NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
Immediate true 9m19s
ocs-storagecluster-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate false 9m19s
ocs-storagecluster-ceph-rgw openshift-storage.ceph.rook.io/bucket Delete Immediate false 18m
ocs-storagecluster-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 10m
openshift-storage.noobaa.io openshift-storage.noobaa.io/obc Delete Immediate false 6m32s
2. Create a PVC that refers to the storage class that you want to use. Save and edit the following PVC configuration file to refer to the storage class that you want to use. If you enabled encryption with Hyper Protect Crypto Services, you can use the storage class ocs-storagecluster-ceph-rbd-encrypted which supports encryption.
* [Ordering and configuring IBM Cloud Object Storage with Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-icos_ordering)
* [Veeam Backup and Replication](https://www.ibm.com/cloud/architecture/architectures/virtualization_backup_veeam)
* [Veeam website](https://www.veeam.com/)
* [Veeam Help Center](https://www.veeam.com/documentation-guides-datasheets.html)
* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginibm-object-storage-plugin-parameter-reference)



* [2.2 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginibm-object-storage-plugin-2.2-parameters)



* [Storage class reference for IBM Cloud Object Storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginconfig-storage-cos-sc-ref)
* [Getting help and support for IBM Cloud Object Storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-object-storage-pluginsat-storage-cos-support)



[Block Storage for VPC Container Storage Interface (CSI) Driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driverstorage-ibm-vpc-block-csi-driver)



* [Prerequisites for Block Storage for VPC](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driversat-storage-vpc-csi-prereq)
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driveribm-vpc-block-csi-driver-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-ibm-vpc-block-csi-driveribm-vpc-block-csi-driver-config-create-cli)
: The [CLI change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog) is updated for version 1.0.415.





 25 May 2022 

IBM Cloud Object Storage plug-in
: Version 2.1.16 of the IBM Cloud Object Storage plug-in [is available](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog).

Block Storage for VPC add-on.
: [Version 4.3.0_1163](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog) is available.

Block Storage for VPC add-on.
: [Version 4.2.6_1161](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog) is available.





 20 May 2022 

Worker node fix pack
: Kubernetes [1.20.15_1581](https://cloud.ibm.com/docs/containers?topic=containers-changelog_120), [1.21.12_1560](https://cloud.ibm.com/docs/containers?topic=containers-changelog_121), [1.22.9_1552](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), [1.23.6_1530](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123).





 19 May 2022 

Istio add-on
: Version [1.12.7](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1127) is available.

Ingress ALB change log updates
* [Managing Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_managing_licenses)
* [Ordering and configuring IBM Cloud Object Storage with Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-icos_ordering)
* [FAQ](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
* [Veeam Backup and Replication](https://www.ibm.com/cloud/architecture/architectures/virtualization_backup_veeam)
* [Veeam website](https://www.veeam.com/)
* [Veeam Help Center (Technical Documentation)](https://www.veeam.com/documentation-guides-datasheets.html)