Aaron Francis Fernandes
Aaron Francis Fernandes
I tried running the restoration scenario for single node etcd's as well as multi node etcd's, with both TLS enables as well as disabled. Running fine in all cases
I noticed that there was a regression with compaction with the changes from this PR The issue is [here](https://github.com/gardener/etcd-backup-restore/blob/722eea3155e604fe222150819c601840f34619e0/pkg/types/restorer.go#L163). Since this PR changes the peer port used by the embedded...
> case 2: disabling the encryption on the fly. > ``` > I think we can use this ` { "enabled"}` as an of indication of encryption turn on/off on...
With this PR, is #456 still needed?
Since restoration is being moved to the etcd container, the member addition logic (member remove, member add as learner, and member promote) will be moved into the etcd container, and...
Member restoration in the multi node case requires these member management operations where we need to remove the member from the cluster member list, add it back as a learner,...
This PR is quite old, and a lot of changes have been made since this PR was initially filed. This PR is also not vital to etcd-br operations Hence I'm...
On further testing we saw that although this change is fine if `MCM` runs standalone, there is a scenario that when `CA` runs alongside this change can cause `CA`s backoff...
@Kumm-Kai We have some questions 1. How would MCM proceed with rolling updated for this machine deployment? would these annotated machines be ignored? 2. When the annotation is eventually removed...