0.4.0

[etcd-backup-restore]

Most notable changes

• [USER] Now, snapshot upload happens in chunk. One can configure the number of parallel chunk uploads by setting command line argument max-parallel-chunk-uploads. Default is set to 5. (#68, @swapnilgm)
• [OPERATOR] Dynamic profiling support is added. Now we expose the debug/pprof/* endpoint to dynamically profile cpu, heap consumption. To enable profiling one has to explicitly set enable-profiling on server sub-command. (#60, @swapnilgm)
• [USER] At the time of restoration, the etcd data directory will be restored to temporary directory with suffix .part i.e.<path-to-etcd-data-dir>.part. On successful restoration we will replace actual etcd data directory with this. This brings standard and more cleaner approach to restoration. (#58, @georgekuruvillak)
• [USER] Restoration time optimised by parallelising the fetching of delta snapshots. Added the --max-fetchers flag to the etcdbrctl command to specify the maximum number of fetcher threads that are allowed to run in parallel. (#57, @shreyas-s-rao)
• [USER] Etcd-backup-restore utility when started in server mode will start defragmenting etcd member data directory periodically, so that db size will be under control. You can set defragmentation period in number of hours by setting defragmentation-period-in-hours flag on etcdbrctl server command. (#55, @swapnilgm)

Improvements

• [OPERATOR] Updated the azure sdk as per the recommendation in doc to use package github.com/Azure/azure-storage-blob-go as azure storage SDK, (#76, @swapnilgm)
• [OPERATOR] Added mock test for Openstack Swift snapstore. (#75, @swapnilgm)
• [OPERATOR] Snapshot are now uploaded in chunks, considering only erroneous chunk upload in case of failure. (#53, @swapnilgm)

0.3.1

Fixed the issue where in case of failed delta snapshot, data directory was marked as valid even though there is data loss due to further delta snapshots in queue which weren't getting applied.

0.3.0

Docker Image: eu.gcr.io/gardener-project/gardener/etcdbrctl:0.3.0

Added

• Incremental backups.
• Condensed backups.

0.2.3

Docker Image: eu.gcr.io/gardener-project/gardener/etcdbrctl:0.2.3

Fixed

• Etcd made unready in case backup container fails to take periodic backups.
• Backup container made to retry exponentially rather than crash out.

Changed

• Readiness probe renamed to /healthz.

0.2.2

Docker Image: eu.gcr.io/gardener-project/gardener/etcdbrctl:0.2.2

Added

• TLS support for etcd endpoints.

Changed

• Delete contents of data directory instead of the directory.

0.2.1

release notes

0.2.0

release notes

0.1.0

Initial release

Etcd-backup-restore is collection of components to backup and restore the etcd. It takes periodic backups of etcd to the configured cloud object store. It also, provides the ability to validate the data directory against data corruptions. In the event of data corruption, the data directory is restored from the latest backup available in the cloud object store.

Supported Object Stores:

• Amazon S3
• Azure Blob Storage
• Google Cloud Storage
• Openstack Swift

For more information, please refer the design document.

Docker Images

etcd-backup-restore: eu.gcr.io/gardener-project/gardener/etcdbrctl:0.1.0