You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature (What you would like to be added):
Currently, the helm charts of etcd-backup-restore are not being updated or maintained. This is due to the need for the involvement of etcd-druid aka the etcd operator to make etcd HA gardener/etcd-druid#107 and facilitating features like scaling up from a single node etcd to a multi-node etcd etc.
The question now is whether we want to continue supporting and maintaining the helm charts of etcd-backup-restore.
If the answer is yes, then we have to upgrade the helm charts as right-now it's working with very old version of backup-restore.
Update the backup-restore version in the helm charts for single-node etcd.
Upgrade the helm charts to bootstrap of multi-node etcd (0 -> 3 replicas).
However, we should note that some features of HA etcd like scale-up feature cannot be supported in the helm charts without the involvement of etcd-druid.
If the answer is no, we should completely discontinue support for the helm charts.
Motivation (Why is this needed?):
Many of our community users consumes etcd-backup-restore via helm charts.
Approach/Hint to the implement solution (optional):
It is recommended to use druid to provision and maintain an etcd cluster. Having said that users in the community might be using backup-restore as well since we have not really positioned druid the way we are doing now. What is also not clear is how etcdBR is currently being used in the community.
The charts actually sets up an etcd cluster for which druid is recommended and i find these charts to be a misfit in etcd-backup-restore as that is not its intended purpose anyways.
Feature (What you would like to be added):
Currently, the helm charts of etcd-backup-restore are not being updated or maintained. This is due to the need for the involvement of etcd-druid aka the etcd operator to make etcd HA gardener/etcd-druid#107 and facilitating features like scaling up from a
single node etcd
to amulti-node etcd
etc.The question now is whether we want to continue supporting and maintaining the helm charts of etcd-backup-restore.
If the answer is yes, then we have to upgrade the helm charts as right-now it's working with very old version of backup-restore.
0 -> 3 replicas
).If the answer is no, we should completely discontinue support for the helm charts.
Motivation (Why is this needed?):
Many of our community users consumes etcd-backup-restore via helm charts.
Approach/Hint to the implement solution (optional):
/cc @shreyas-s-rao
The text was updated successfully, but these errors were encountered: