Did you try the Kubernetes Operator: https://github.com/arangodb/kube-arangodb? Should at least help with the k8s part... Also would be curious about your sharding challenges, feel free to ping me on the ArangoDB slack
Yes, I struggled with the operator, to the point where it would not install at all. I even fixed some of the documentation, but later my database was not responsive.
IMO these are a great improvement but one still needs to be aware of the underlying container limits. E.g., understanding why setting MaxRAMFraction=1 might not be a good idea as the container might get killed...
One of the authors here: First of all thanks for the great disucssion here, it really motivated to write another follow-up article.
There were some comments asking for more practical advice which is totally fair as this was supposed to be more informational and creating problem awareness.
What else would you like to see covered in a follow-up?
A base Java image and a set of recommendations. Most of us here (I assume) are running containers in K8s or Swarm. Our issue is - there is no base docker image which the java community can embrace. I have pods which restarted 35 times in the last one month.
