3 ms·

I sure have, but not for any of those reasons, and especially not that cowboy "just log in, change couple of lines and restart". The reason is always when the

I sure have, but not for any of those reasons, and especially not that cowboy "just log in, change couple of lines and restart". The reason is always when the time, cost and complexity of managing the control plane outweighs the benefits. You can still have a perfectly good, quickly executing, end-to-end CI/CD pipeline for which the deployment step is (gasp) put some files on a server and start a process. The inflexion point for this varies by organisation, but I've never seen an environment with less than three services where managing container scaffolding is a net positive.

mrweasel 6y ago
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.
- gonrial 6y ago
  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.
  - mrweasel 6y ago
    Absolutely, just plain Docker or Docker Compose are both wonderful and easy to use tools.
- bovermyer 6y ago
  This may sound like heresy, but Docker Swarm is perfectly viable for this kind of use case.
  - mrweasel 6y ago
    Viable yes, annoying, also yes. 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?
    - bovermyer 6y ago
      Yes, and I've also run into the networking issues more than once. However, both fail states are fairly rare, and Docker Swarm is far simpler to manage than K8s.
  - heavyset_go 6y ago
    I use K8s at work, but Docker Swarm at home because it is simple to set up and works well.

mrweasel 6y ago

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.

gonrial 6y ago
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.
- mrweasel 6y ago
  Absolutely, just plain Docker or Docker Compose are both wonderful and easy to use tools.
bovermyer 6y ago
This may sound like heresy, but Docker Swarm is perfectly viable for this kind of use case.
- mrweasel 6y ago
  Viable yes, annoying, also yes. 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?
  - bovermyer 6y ago
    Yes, and I've also run into the networking issues more than once. However, both fail states are fairly rare, and Docker Swarm is far simpler to manage than K8s.
- heavyset_go 6y ago
  I use K8s at work, but Docker Swarm at home because it is simple to set up and works well.