We have a series of customers who I want to move away from Kubernetes, simply because the management of the Kubernetes cluster out weights the cost of managing the application, compared to running it on a few virtual machines.
I wouldn't even set the limit a three service, but perhaps closer to 10, depending on the type of services and the development flow.
Getting a late night alarm on a virtual machine is still much easier to deal with, that an error on a container platform.
One solution that seems to be somewhat simpler, but still managing to retain many of the advantages of having a containerized infrastructure is Nomad, but I still haven't tested it on anything large scale.
Have you tried fixing Docker Swarm when it randomly decides that one worker is missing and it spins up the "missing" containers on the remaining worker while reporting that your missing a worker, but at the same time your containers are somehow also over-replicated?
But that's the operational headache of using Kubernetes specially when you are dealing with a small number of services. There are other simple and/or managed platforms that will give the same usage experience hiding the complexity.
I wouldn't even set the limit a three service, but perhaps closer to 10, depending on the type of services and the development flow.
Getting a late night alarm on a virtual machine is still much easier to deal with, that an error on a container platform.
One solution that seems to be somewhat simpler, but still managing to retain many of the advantages of having a containerized infrastructure is Nomad, but I still haven't tested it on anything large scale.