Open ishan16696 opened 2 years ago
/assign
Any progress to this? Did we find which ETCD version to use?
no update from my side as I'm busy with refactoring. Anybody can this over. /unassign
This issue of moving the custom-etcd image: https://github.com/gardener/etcd-custom-image/issues/16 to golang app requires latest etcd v3.5.x
, Hence this is dependent on etcd version upgrade to take advantage of various functionality like EtcdServer.leaderChangedNotify
. IMO, we have to increase the priority of this issue.
In an out-of-band discussion with @ishan16696 @unmarshall @ashwani2k @abdasgupta , we decided that this change cannot be clubbed with the release of etcd-steward (as previously thought of). This change requires a dedicated release of etcdbr+druid, so that the change is deterministic, and no other changes are clubbed with it.
This is also important for Kubernetes 1.31: see https://github.com/gardener/etcd-wrapper/issues/28
We've decided to move to the latest patch, v3.4.34
. I've started work on this.
Work will be tracked here https://github.com/gardener/etcd-backup-restore/issues/792.
Feature (What you would like to be added): Upgrade the etcd from
v3.4.26
tov3.5.x
.Motivation (Why is this needed?): We are missing many fixes which comes only in latest version of etcd
3.5.x
. eg:The upgrade will be completed stepwise:
v3.4.34
in etcd-wrapper.v3.4.34
in etcd-druid.v3.5.x
in etcd-backup-restore.v3.5.x
in etcd-wrapper.v3.5.x
in etcd-druid.Approach/Hint to the implement solution (optional): We haven't decided to which exact version we want to move. We have to find the stable version of
etcd v3.5.x
which is good for production use with very less or none severe issues reported on upstream.