New Features

Stork has introduced an enhanced workflow for creating a ClusterPair, enabling you to create a ClusterPair using a single storkctl command in both synchronous and asynchronous Disaster Recovery (DR) scenarios. See Create a synchronous DR ClusterPair and Create an asynchronous DR ClusterPair for more information. #1467 , #1466, #1461, #1455, #1450
Note: You need to update the storkctl binary for this change to take effect.

Improvements

Updated golang, aws-iam-authenticator and google-cloud-sdk versions to resolve 20 Critical and 105 High vulnerabilities reported by the JFrog scanner. #1458
Added kubelogin utility in Stork container. #1448

Issue: Due to occasional delays in bound pod deletion, the current timeout setting of 30 seconds proves insufficient, resulting in backup failures.
User Impact: At times, the backup process for a volume, which is bound with the "WaitForFirstConsumer" mode, encounters timeout errors and fails.
Resolution: The timeout value has been extended to five minutes to ensure that the deletion of the bound pod, created for binding the volume with "WaitForFirstConsumer," will not encounter timeout errors. #1454
Issue: During the cleanup process, when the KDMP/Localsnapshot backup fails, the volumesnapshot/volumesnapshotcontent were not being removed.
User Impact: Unnecessary accumulation of the stale volumesnapshot/volumesnapshotcontent was occurring.
Resolution: Volumesnapshot/volumensnapshotcontent cleanup is now performed, even in the case of failed KDMP/localshapshot backups. #295
Issue: When the native CSI backup fails with a timeout error, the volumesnapshotcontent is not being deleted.
User Impact: In the event of native CSI backup failures, the volumesnapshotcontent will accumulate.
Resolution: Proper handling includes deleting the volumesnapshotcontent in case of failure as well. #1460