ctrox
Why not adding s3ql
I have seen in the history that s3ql was removed, for me it sounded like the perfect fit feature wise.
any reason why it flew out?
It has been quite a while since I made that choice but the commit message explains it (although briefly). The main issue I can remember was that on every unclean shutdown (which can happen regularly on a Kubernetes cluster), it required manual intervention to get it to mount a volume again. This, coupled with the fact that it dramatically increased the docker image size because of all the dependencies lead me to remove it. I'm not completely ruling out the possibility of introducing it again but it would require quite some effort to get it into a reliable state.
