Skip to content

v0.12.0

Compare
Choose a tag to compare
@gardener-robot-ci-1 gardener-robot-ci-1 released this 08 Aug 15:59
· 294 commits to master since this release

[etcd-druid]

⚠️ Breaking Changes

  • [OPERATOR] etcd Statefulsets are not claimed anymore based on labels. Instead, the statefulsets are fetched using Name and Namespace combination. Thus, etcd.spec.selector does not have an effect on statefulsets anymore. (gardener/etcd-druid#365, @abdasgupta)
  • [OPERATOR] The entrypoint for etcd-druid in its container image has been modified. (gardener/etcd-druid#360, @dimityrmirchev)

✨ New Features

🐛 Bug Fixes

  • [OPERATOR] A bug has been fixed that caused the etcd-backup-restore side-car to connect to the etcd cluster via the peer-service URL. The side-car is supposed to use the client-service instead since it a) exposes client port 2379 and b) redirects traffic only to members which are ready to service traffic. (gardener/etcd-druid#388, @timuthy)
  • [OPERATOR] An issue has been fixed that caused the liveness and readiness probes of etcd to always succeed even though an error was reported. This prevented defective etcd pods from being restarted automatically and caused unready candidates being considered as ready to serve traffic via the etcd service. (gardener/etcd-druid#396, @timuthy)
  • [OPERATOR] A startup probe has been added to etcd to allow 2 minutes of initialization time before checking for etcd liveness. (gardener/etcd-druid#396, @timuthy)

🏃 Others

  • [OPERATOR] The definition of the etcd.status.ready field was defined more precisely due to changed semantics of multi-node etcd clusters. etcd.status.ready is true whenever all underlying etcd replicas are ready. Please note, that the implementation for this check was not changed. (gardener/etcd-druid#389, @timuthy)
  • [OPERATOR] Fixed an issue in the release job needed to add the correct image version config/default/manager_image_patch.yaml. (gardener/etcd-druid#397, @aaronfern)
  • [OPERATOR] Added pod permission in etcd_role that now enable etcd-backup-restore to get/list/watch pods (gardener/etcd-druid#372, @aaronfern)
  • [OPERATOR] Etcd-Druid's Golang version has been update to 1.18.4.. (gardener/etcd-druid#375, @timuthy)
  • [OPERATOR] The correct image version has been set in config/default/manager_image_patch.yaml to match the current release. (gardener/etcd-druid#377, @timuthy)

[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#512, @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)
  • [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)

📰 Noteworthy