Swapnil Mhamane

Restoration time is dependent on DB/backup size and network speed. And since restoration is ongoing process, etcd-backup-restore health status will be false. For etcd container the liveness probe check the...

@amshuman-kr May be you guys had detailed discussion around this. And if my comment above don't address the issue then probably i didn't understood the core issue. Probably, the description...

Thanks Amshu for triggering discussion again. That help me found out a correction to above explanation. `livenessProbe` is on etcd i.e. `etcdctl get foo`. So, by design , in all...

Currently we use multi-chunk upload logic with store-and-forward. So, currently expected disk size is twice the supported DB size. With encryption, i assume we will go for block cipher mostly...

@amshuman-kr > An alternative to avoid 3 times db size, could be if we encrypt on the fly while writing the snapshot to the disk in the first place. Then...

@vlerenc > I don't know whether I can follow. I assume, we can and will hold a chunk in memory (encrypt + upload and download + decrypt). We anyways limit...

> So at any given time, on the disk we'll have the actual etcd data + all encrypted chunks associated with the current snapshot (full or delta). Please check comment:...

Just to clarify further on terminology, here onwards i'll use __chunk__ : chunk in multi-part upload of chunk; chunk size is dynamic w.r.t. backup size and cloud provider support. __block__...

As per discussion, in the context of Gardener or to be precise etcd backing kubernetes we make use of [k8s secret encryption](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/) feature, so basically critical data is encrypted. But...

Sorry merging proposal closed issue automatically. Reopening, since the issue still persists. And need to be resolved in future.