v0.19.0

[etcd-backup-restore]

⚠️ Breaking Changes

• [OPERATOR] Dropping the feature of passing storage container credentials through ENV for the following storage provider: S3, Swift, OCS, ABS, OSS. Please switch to pass the storage container credentials through volume file mount. (gardener/etcd-backup-restore#493, @ishan16696)

🏃 Others

• [OPERATOR] A new flag --service-endpoints has been added to the etcdbrctl server command. These (Kubernetes) service URLs ensure that etcd-backup-restore only connects to etcd member which are ready to server traffic. Especially the MemberAdd and Init steps require this. (gardener/etcd-backup-restore#513, @timuthy)
• [OPERATOR] Fixed a bug where etcd calls related to multi node operation were used in single node operation (gardener/etcd-backup-restore#504, @aaronfern)
• [OPERATOR] Assigned the correct Peer address to the Etcd after it restores from backup-bucket. (gardener/etcd-backup-restore#505, @ishan16696)
• [OPERATOR] No attempt is made to update member Peer URL when trying to promote a member (gardener/etcd-backup-restore#506, @aaronfern)
• [OPERATOR] An issue has been fixed that caused the Backup-Restore component to connect to the wrong etcd cluster for initializing and member-add procedures. (gardener/etcd-backup-restore#510, @timuthy)

📰 Noteworthy

• [USER] For multi-node etcd: Added a feature of single member etcd restoration in case of data/data-dir of etcd member found to be corrupted or invalid. (gardener/etcd-backup-restore#509, @ishan16696)