use fsgroup and remove chowning initContainers
The ownership of mounted volumes gets automatically chowned by default to fsGroup (although this may not be the case for some multi-writer volumes: link but the volumes in question are local to each pod e.g. /var/log/eos and /var/eos, not shared by multiple writers).
By default, Kubernetes recursively changes ownership and permissions for the contents
of each volume to match the fsGroup specified in a Pod's securityContext when that volume is mounted.
I believe this has been the case for as long as fsGroup has existed. So removing the chowning containers should be possible. There is a further possible optimization fsGroupChangePolicy
to avoid doing a recursive chown if the root dir of the volume already matches.
This will require setting fsGroup. Actually the original need to chown the volumes to daemon could have been because the container init process runs as UID 0 but EOS runs as UID 2 and the securityContext does not set fsGroup to 2 (or it pre-dated the existence of fsGroup).