4 ms·

This made me remember Fleet[0], which I used in the past on CoreOS. It was a very good abstraction for my simple cluster. It felt as robust as a managed cloud s

• mdaniel 2y ago
  > (and also what happened to CoreOS) Arguably worse, IMHO, is that the name lives on but does something wholly different, polluting search results Anyway, I wanted to plug Flatcar which forked CoreOS back when the nonsense started and have been pretty pleasant to work with. They are still misguided about user-data management, and have since been acquired by Microsoft(!), but the code lives on https://github.com/flatcar/Flatcar#readme https://github.com/flatcar/Flatcar#readme and https://www.flatcar.org/docs/latest#upgrading-from-coreos-container-linux https://www.flatcar.org/docs/latest#upgrading-from-coreos-co...
  • ldmosquera 2y ago
    Small note - https://github.com/flatcar/Flatcar https://github.com/flatcar/Flatcar has no code in any branches: > Flatcar project repository for issue tracking, project documentation, etc. Per the building page https://www.flatcar.org/docs/latest/reference/developer-guides/sdk-modifying-flatcar/ https://www.flatcar.org/docs/latest/reference/developer-guid... the actual code seems to be at https://github.com/flatcar/scripts.git https://github.com/flatcar/scripts.git
    • mdaniel 2y ago
      Yes, apologies, that was poor wording on my part. The "lives on" was meant in the "continuation" sense but I can see how "lives on https:" implied it was in that specific repo. Sorry about that
• esseph 1y ago
  Hm. I'm actually deploying some CoreOS systems this weekend as a test.