5 ms·

Anyone else lament fleetd and the promise of a simple tool based container orchestration? Yet another complex framework. sigh

• felixgallo 10y ago
  not particularly! Sometimes problems really are difficult and demand thoughtfully designed solutions, and sometimes complexity in those solutions is both tolerable and worth it.
• puzzle 10y ago
  fleetd doesn't even support rolling updates. It just barely got support for in-place updates. There's a reason why CoreOS folks themselves don't dedicate many cycles to it anymore.
  • vidarh 10y ago
    It has plenty of flaws, but it also solves problems that aren't well handled with Kubernetes unless I'm missing something, such as being able to schedule arbitrary systemd units, including things like timers, across a cluster. As a low level building block it is/was more flexible in some ways. Of course it is solving only a tiny part of what Kubernetes tries to solve.
• ownagefool 10y ago
  Yeah, sure. Fleet for dnyamic scheduling Consul for k/v service discovery Registrator to actually populate consul Confd to talk to consul so you can configure your containers ... Oh wait I seem to be building a crappy more involved version of kubernetes. p.s. I actually did the above. kubernetes is a better solution.
  • invisible 10y ago
    Can confirm; did similar and kubernetes is a better solution.