Category: Kubernetes, Infrastructure, yaml

Bit of Erento’s background We went with one of the very first stable releases 1.0.5, we had no resources limits control, no affinity, even simple deployment resource was far distant.

Everything was running smoothly but the maintenance of such setup absorbed quite a lot of time and our ops resources were quite limited (it was me only).

We have decided not to host on Kubernetes for a few reasons:- with our solution, multiple Kubernetes clusters can access GlusterFS cluster, which brings us high availability and failover- separation of applications and static hosting layer allows us to maintain and upgrade Kubernetes clusters without any risk of impacting GlusterFS- solution with separated GlusterFS is simpler to maintain

It is seriously pushing us forward and we are hoping to spread this kind of spirit all over the world.

Related Articles