Amshuman K R

> Does that mean kube-apiserver might also suffer memory spike in case of large updates? Potentially, yes. They would be using the same client library.

I can think of only three options. 1. Document this and do nothing for now. 1. Contribute throttling to etcd client. 1. Try a polling-based approach (with parallel download of...

> Instead of running a TLS server for the initialization/status and initialization/start, use unix domain socket (UDS) to connect from etcd -> bacup sidecar. The socked can be created in...

Thanks @brumhard and @breuerfelix for showing interest and going through the proposal. And also for offering to help with implementing parts of it. Unfortunately, there are some sequencing issues due...

It is also a goal to try and reproduce https://github.com/gardener/etcd-druid/issues/99

How about introducing a new RestartPolicy value such as **AlwaysPod** which means always restart the pod whenever any container dies? I.e. the whenever any (non-init) container of the pod dies...

The AlwaysPod RestartPolicy can also be used to make a stateful apps/services more self-managed using init-containers and side-car containers for some of the simpler management tasks such as backups while...

@majgis AFAIK, the only possible work-around is to bake in some co-ordination between the containers of the pod. I am working on a PR for implementing the AlwaysPod restartPolicy which...