Releases: gardener/etcd-backup-restore
Releases · gardener/etcd-backup-restore
v0.15.3
[etcd-backup-restore]
🏃 Others
- [OPERATOR] Fixed retrieval of credentials during copy operation for backups stored in Swift snapstore. (gardener/etcd-backup-restore#477, @ishan16696)
v0.15.2
[etcd-backup-restore]
🐛 Bug Fixes
- [OPERATOR] Throw Fatal error to avoid edge case potential deadlocks. (gardener/etcd-backup-restore#467, @ishan16696)
🏃 Others
- [OPERATOR] ETCD won't restart from the PVC if it is wrongly mounted to the pod (gardener/etcd-backup-restore#470, @abdasgupta)
v0.16.0
[etcd-backup-restore]
📰 Noteworthy
- [OPERATOR] Multi-node etcd bootstrapping is now supported. This is an alpha feature intended for initial use and evaluation. Please do not enable this feature for your productive workloads (gardener/etcd-backup-restore#419, @abdasgupta)
- Multi-node etcd restoration from backup buckets is not supported
- Intended to work only with etcd-druid v0.9.x and beyond
- Intended to work only with etcd-custom-image v3.4.13-bootstrap-4 and beyond
v0.15.1
[etcd-backup-restore]
🐛 Bug Fixes
- [OPERATOR] Fix defragmentation fail issue which occurs due to x509: failed to validate certificate for 0.0.0.0 because it doesn't contain any IP SANs. (gardener/etcd-backup-restore#459, @ishan16696)
v0.15.0
[etcd-backup-restore]
📰 Noteworthy
- [OPERATOR] To Dynamically load Iaas credentials, added support to pass the credentials through file mount. (gardener/etcd-backup-restore#435, @ishan16696)
- [OPERATOR]
⚠️ The support to pass the credentials through environment variables will get deprecated byetcd-backup-restore
v0.18.0 (gardener/etcd-backup-restore#435, @ishan16696)
- [OPERATOR]
- [OPERATOR] Failed backups won't fail the readinessProbe thus etcd is allowed to keep serving the incoming traffic. (gardener/etcd-backup-restore#411, @ishan16696)
- [OPERATOR] Added CLI flags
--backoff-multiplier
,--backoff-attempt-limit
and--backoff-threshold-time
to configure the exponential-backoff mechanism. (gardener/etcd-backup-restore#411, @ishan16696)
- [OPERATOR] Added CLI flags
- [OPERATOR] Added the leader-election to the backup-restore. Added support to allow only backup-restore Leader to take/upload the snapshots and trigger the defragmentation. (gardener/etcd-backup-restore#353, @ishan16696)
🏃 Others
- [OPERATOR] The used Golang version was updated to
1.17
. (gardener/etcd-backup-restore#445, @timuthy) - [OPERATOR] Fixed etcd-backup-restore exiting immediately on SIGTERM without proper context cancellation (gardener/etcd-backup-restore#440, @sibucan)
- [OPERATOR] Added support for non-AWS S3-compatible providers by specifying a custom endpoint. (gardener/etcd-backup-restore#431, @sibucan)
- [OPERATOR] Upgrade the Go from v1.14 to v1.16 (gardener/etcd-backup-restore#405, @ishan16696)
🐛 Bug Fixes
- [OPERATOR] Took care of a bug where contexts were created multiple times without being cancelled (gardener/etcd-backup-restore#408, @aaronfern)
v0.14.1
[etcd-backup-restore]
🐛 Bug Fixes
- [OPERATOR] Took care of a bug where contexts were created multiple times without being cancelled. This caused a significant higher memory and CPU footprint. (gardener/etcd-backup-restore#409, @aaronfern)
v0.14.0
[etcd-backup-restore]
🏃 Others
- [OPERATOR] The backup-restore sidecar will now check if the owner domain name resolves to the specified owner ID and if not, take a final full snapshot and disable the cluster. (gardener/etcd-backup-restore#383, @stoyanr)
📰 Noteworthy
- [OPERATOR] Added
health
package to allow backup-restore to renew member leases to indicate member health and snapshot leases to indicate snapshots being taken successfully (gardener/etcd-backup-restore#382, @aaronfern)- Added flags to the
server
andcompact
subcommand.--enable-snapshot-lease-renewal
to enable snapshot lease renewal,--enable-member-lease-renewal
to enable member lease updates,full-snapshot-lease-name
to specify the full snapshot lease name, anddelta-snapshot-lease-name
to specify the delta snapshot lease name - Pod name and namespace has to be passed via environment variables (
POD_NAME
andPOD_NAMESPACE
) when running the server subcommand when--enable-member-lease-renewal
flag is set to true - Pod namespace needs to be passed via an environment variable (
POD_NAMESPACE
) when running the server subcommand when--enable-snapshot-lease-renewal
flag is set to true - Pod namespace needs to be passed via an environment variable (
POD_NAMESPACE
) when running the compact subcommand when--enable-snapshot-lease-renewal
flag is set to true
- Added flags to the
v0.13.0
[etcd-backup-restore]
🏃 Others
- [USER] Compaction job will now throw warning instead of error if revisions are already compacted (#358, @shreyas-s-rao)
- [OPERATOR] Added '--etcd-snapshot-timeout' and '--etcd-defrag-timeout' CLI flags in 'server' and 'compact' subcommands (#361, @ishan16696)
- [OPERATOR] Updated number of chunks while uploading to never exceed the cloud provider limits. (#334, @abdasgupta)
📰 Noteworthy
- [OPERATOR] Added compaction command support to ETCD Backup Restore. Users can now use compaction sub command with
etcdbrctl
tool to compact basesnapshot and all it's subsequent deltasnapshot to one single compacted snapshot. (#301, @abdasgupta) - [OPERATOR] Snapshots are not stored under separate prefix (Backup-XXX) in backup storage. Instead, all of the snapshots are stored under
v2
backup version prefix in a flat structure. (#301, @abdasgupta) - [OPERATOR] Support for
v1
backup version is still there but only for restoration and snapshot garbage collection. So backup storages that hadv1
backup version and where snapshots were stored under separate prefix (Backup-XXX), can still be used with compaction sub command (as well as for restoration). However, the new snapshots will be stored underv2
backup version prefix. (#301, @abdasgupta) - [OPERATOR] The support for the
v1
backup structure with separate prefix (Backup-XXX) will be dropped in a subsequent release. (#301, @abdasgupta)
v0.12.1
[etcd-backup-restore]
🏃 Others
- [OPERATOR] Updated number of chunks while uploading to never exceed the cloud provider limits. (#335, @amshuman-kr)
v0.12.0
[etcd-backup-restore]
🏃 Others
- [USER] Added CLI flags
--auto-compaction-mode
and--auto-compaction-retention
to configure auto-compaction for embedded etcd. Default values: auto-compaction-mode="periodic" and auto-compaction-retention="30m" (#315, @ishan16696) - [OPERATOR] Added a new metric
etcdbr_snapshotter_failure
used as a blanket metric to capture any snapshotter error. (#326, @aaronfern) - [OPERATOR] etcdbr-compression specification can be configured through helm-charts. (#307, @ishan16696)
- [OPERATOR] Added CLI-flags (
max-call-send-message-size
,max-request-bytes
andmax-txn-ops
) to enable restoration for delta snapshots with large amount of data (large number of events or events with large data). (#282, @abdasgupta)
📰 Noteworthy
- [USER] Move bootstrap script out of the helm chart, as it will now be part of the
etcd-custom-image
. (#327, @shreyas-s-rao) - [USER] Add support for snapshot compression/decompression. Compression and compression policy can be configured through flags:
--compress-snapshots
and--compression-policy
respectively. Supported compression policies currently aregzip
(default),lzw
andzlib
. Snapshot compression is disabled by default. (#293, @ishan16696)