3 ms·

This is roughly correct. The README says it best: https://github.com/coreos/fleet#current-status https://github.com/coreos/fleet#current-status Also, as you me

by philips 10y ago

This is roughly correct. The README says it best: https://github.com/coreos/fleet#current-status https://github.com/coreos/fleet#current-status Also, as you mention there are very compelling reasons that when Kubernetes came on the scene 2 years ago we started contributing heavily instead of trying to compete. We started to say something with fleet and Kubernetes completed our sentence: https://github.com/coreos/fleet/blob/master/Documentation/fleet-k8s-compared.md https://github.com/coreos/fleet/blob/master/Documentation/fl... Overall, we recommend everyone use Kubernetes as the way to orchestrate containers.

vidarh 10y ago
Personally I feel it's a shame - Kubernetes is way overkill for most of the deployments I do. At the same time fleet has a number of annoying problems even on (or even particularly on) small clusters. I see Kubernetes deployments where more of the containers running are there to provide infrastructure than actual workloads, which gets just silly. For small deployments like that, something as simpl as Fleet but with a better scheduling story would be preferable to me. But I get that those kind of deployments won't pay the bills as they're certainly much less likely to pay for CoreOS services.
- dankohn1 10y ago
  But Kubernetes is the future [0]. [0] https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/
- untoreh 10y ago
  Indeed if you have just a handful of hosts, spending gigas of ram for kubernetes is not really exciting.