Skip to content

Release 0.17.4

This patch release fixes a bug where a restore job failed immediately when it hit a transient storage error while resolving the snapshot, and a bug where resumed restores reported -1 as the last restored offset.

For new installations, see the Installation guide.

For upgrading existing installations, see the associated Upgrading to 0.17.x guide.

  • Restore: transient storage errors while resolving the snapshot, such as an S3 connect timeout, are now retried instead of failing the restore.

  • Restore: resumed restores now report the last restored offset from previous attempts, and the console renders a missing offset as ’-’ instead of -1.

  • Restore: loosened the editing restrictions for performance and pod settings. They can now be changed from the Restore Settings tab in the console when a restore is not running.

For a full list of changes, see the Changelog.