Hacker News Reader

Someone is building a systemd based kublet replacement.

Why? Because Kubernetes has some great ideas on self-healing and resiliency.

But if you are small, and can work with a single instance for availability, then probably should stick with systemd. You could also use podman to get a small bit of the kubernetes ideas for working with containers.

The next level of scale wouldn’t be the full k8s but more like k0s, or k3s.

View on HN

> Someone is building a systemd based kublet replacement.

I'm working on a product that uses something like this internally, basically, we provide multiple preview-environments in the same big server, these are managed by systemd.

This is the first time I get to think that this may be a project by itself, ping me if you have any ideas or want to get into a discussion on this topic.

I forgot who built it, but it isn’t a strict replacement. One of the rationale for doing so was identifying daemonsets as an anti-pattern.

Reply on news.ycombinator.com