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 by etcd-backup-restore v0.18.0 (gardener/etcd-backup-restore#435, @ishan16696)
• [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 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)