Hello everyone,
I wrote 2 minimalist step by step guides to set up EventStore on Kubernetes on Aws:
http://www.dinuzzo.co.uk/2018/08/12/set-up-a-kubernetes-cluster/
http://www.dinuzzo.co.uk/2018/08/13/set-up-an-eventstore-cluster-on-kubernetes/
I’ve been inspired by a (proper) article from Tomas Jansson so thanks to start early on this.
An official guide in under way so any feedback at this point is welcome.
Hope this helps,
Riccardo
Thank you very much for this content as I’m currently learning to set up EventStore cluster using kubernetes.
Very cool! I just went through the same exercise myself (except on Azure AKS vs EKS). Was neat to be able to double check what I had come up with against what you had done (though I suppose it would have been better if I had seen yours first!). We independently ended up with almost identical configurations, so I suppose that’s good. FWIW, if anyone would find a helm chart that deploys these services helpful, let me know and I’ll publish it somewhere.
One thing I am curious about is liveness and readiness checks. I wonder whether anyone may have any good ideas about whether to set either kind of check for the ES database nodes and what to set for them. For liveness, is there a particular executable or http endpoint that could be hit that would act as an appropriate canary in the mine indicating a node may actually be dead enough that it needs to be restarted? What about readiness? I’m less certain readiness has the same implication in ES given that it may handle this appropriately at the application layer.
Any suggestions are welcome.
Thank you!
Hi Matt,
in case it could be of some help, in my “Setup kubernetes on Aws” guide at #5 I also set a monitoring add-on that show nice monitoring graphs on the Kube UI and also offer the possibility to set thresholds to be triggered when cpu/memory/disk is under pressure. That part of the guide need more settings in order to do proper autoscaling but it’s a start.
Regards
Riccardo