So many `rejected connection error` in ETCD logs 🔍

Describe the bug: There are lot of logs of rejected connection in etcd but clusters(kube-apiserver) is running fine without any issues, I haven't noticed/experienced any problems so far. Logs:

2023-02-06 05:58:46 {"log":"rejected connection from \"127.0.0.1:50234\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
2023-02-06 05:56:56 {"log":"rejected connection from \"127.0.0.1:60860\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
.
.
2023-02-06 05:53:56 {"log":"rejected connection from \"127.0.0.1:42208\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
2023-02-06 05:53:46 {"log":"rejected connection from \"127.0.0.1:49266\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
2023-02-06 05:52:20 {"log":"rejected connection from \"127.0.0.1:33918\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
.
.
2023-02-06 05:48:45 {"log":"rejected connection from \"127.0.0.1:46070\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
.
.
2023-02-06 05:40:49 {"log":"rejected connection from \"127.0.0.1:46676\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
.
.
2023-02-06 05:39:09 {"log":"rejected connection from \"127.0.0.1:53230\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
2023-02-06 05:36:23 {"log":"rejected connection from \"127.0.0.1:52298\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}
2023-02-06 05:35:58 {"log":"rejected connection from \"127.0.0.1:37942\" (error \"EOF\", ServerName \"etcd-main-local\")","severity":"INFO","source":"embed"}

These logs give DoDs a false impression that etcd is not running fine and they usually ping @gardener/etcd-druid-maintainers by seeing these logs of rejected connection but when we take a look most of the time etcds are running fine.

Expected behavior: These logs of connection rejected in ETCD logs shouldn’t be there, so that it is easy to debug any etcd related issue as well as it shouldn’t give DoD a false information.

Environment (please complete the following information):

Etcd version/commit ID : 3.4.13
Etcd-backup-restore version/commit ID:
Cloud Provider [All/AWS/GCS/ABS/Swift/OSS]: All

Anything else we need to know?:

gardener / etcd-backup-restore

So many `rejected connection error` in ETCD logs 🔍 #585