←back to thread

180 points teleforce | 2 comments | | HN request time: 0.414s | source
Show context
haolez ◴[] No.43688905[source]
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 service. It's a shame it didn't catch on (and also what happened to CoreOS).

[0] https://github.com/coreos/fleet

replies(2): >>43693761 #>>43725360 #
mdaniel ◴[] No.43693761[source]
> (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 and https://www.flatcar.org/docs/latest#upgrading-from-coreos-co...

replies(1): >>43695647 #
1. ldmosquera ◴[] No.43695647[source]
Small note - 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-guid...

the actual code seems to be at https://github.com/flatcar/scripts.git

replies(1): >>43700384 #
2. mdaniel ◴[] No.43700384[source]
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