v0.14.0
gardener-robot-ci-3
released this
04 Nov 08:45
·
272 commits
to master
since this release
[etcd-druid]
⚠️ Breaking Changes
- [OPERATOR] Claim logic for
PodDisruptionBudget
s have been removed. Already existingPodDisruptionBudget
objects cannot be adopted anymore (gardener/etcd-druid#430, @aaronfern) - [OPERATOR] Logic for deleting any leftover
CronJob
s created byetcd-druid:v0.6.0
has been removed. Please deploy a lower version ofetcd-druid
before upgrading if you still have any leftoverCronJob
s or manually delete them (gardener/etcd-druid#430, @aaronfern)
✨ New Features
- [OPERATOR] Applying the annotation
druid.gardener.cloud/ignore-reconciliation
on the ETCD CR will stop etcd-druid from reconciling it. (gardener/etcd-druid#446, @abdasgupta)- This is helpful for operators to apply any manual fixes to the ETCD components, such as manually fixing permanent quorum loss as per the playbook.
🐛 Bug Fixes
- [OPERATOR] Updated condition used to decide when the
gardener.cloud/scaled-to-multi-node
annotation is added (gardener/etcd-druid#455, @aaronfern) - [OPERATOR] A bug has been fixed that caused the wrong
minAvailable
configuration being calculated for multi-node etcdPodDisruptionBudget
. (gardener/etcd-druid#441, @timuthy)
🏃 Others
- [OPERATOR] Enables etcd-druid to trigger restarts of the etcd pods when peer URL is TLS enabled. (gardener/etcd-druid#421, @unmarshall)
- [OPERATOR] Etcd druid will now use
policy/v1
forPodDisruptionBudget
s for kubernetes >= 1.21. However, for kubernetes < 1.21,PodDisruptionBudget
s will still default topolicy/v1beta1
(gardener/etcd-druid#430, @aaronfern) - [OPERATOR] Golang version used upgraded to
1.18.6
(gardener/etcd-druid#431, @aaronfern) - [OPERATOR] etcd-custom-image upgraded to
v3.4.13-bootstrap-8
(gardener/etcd-druid#432, @aaronfern) - [OPERATOR] Added new field to the etcd CRD
etcd.Spec.Etcd.clientService
(gardener/etcd-druid#438, @aaronfern)- Users can now add annotations to the client service by specifying them in the above field of the etcd resource
- [OPERATOR] The
BackupReady
condition is not considered anymore when thePodDisruptionBudget
configuration is calculated. This earlier blocked rolling out fixes that potentially solved problems with backup procedures. (gardener/etcd-druid#441, @timuthy) - [OPERATOR] Enhance
BackupReady
condition to take into account statefulset being scaled down and the backup section not being defined (gardener/etcd-druid#415, @aaronfern)
[etcd-backup-restore]
🐛 Bug Fixes
- [OPERATOR] To avoid potential race-condition between go-routines updated
probeEtcd func()
to use shorter timeout. (gardener/etcd-backup-restore#532, @ishan16696)
🏃 Others
- [OPERATOR] Always update member peer URL, changed the way scale-up of etcd cluster is identified. (gardener/etcd-backup-restore#534, @unmarshall)
- [OPERATOR] Decreases the likelihood of potential race condition between the go-routines while closing the snapshotter. (gardener/etcd-backup-restore#537, @ishan16696)
- [OPERATOR] [bug-fix] backup-restore does not return error when it fails to update PeerURL of member. (gardener/etcd-backup-restore#540, @aaronfern)
📰 Noteworthy
- [OPERATOR] Updated golang version used to build images to 1.18.6 (gardener/etcd-backup-restore#535, @aaronfern)
- [OPERATOR] Updated golang version to 1.18 (gardener/etcd-backup-restore#535, @aaronfern)
[etcd-custom-image]
🏃 Others
- [OPERATOR]
Etcd-custom-image
will now retry fetching etcd configuration in case of any error (gardener/etcd-custom-image#26, @aaronfern)