Yeah -- I think I was just reciting what I hear folks say a lot. Basically its IPC and a stable interface for clients that is the core of the concern. Thats really what the takeaway is.
But Systemd has IPC and a stable interface for clients, it's "the D-Bus interface of systemd"[1]. I would think that exposing that over http would be a little reckless, but I'm sure one can create a proxy that can do it in a "secure"-ish way.
[1] https://www.freedesktop.org/software/systemd/man/org.freedes...
Re:Why Fix Kubernetes and Systemd?
by mike_hearn on Sunday September 18, 2022 @01:44PM
(#32889604)
There is this:
systemctl --host=whatever.abc status apache2
It uses ssh and UNIX domain socket forwarding behind the scenes. There's a writeup of how to do this with minimal privs here:https://sleeplessbeastie.eu/2021/03/03/how-to-manage-systemd...
If you want to speak the protocol without the systemctl program then you can do the same trick. Use an SSH library, connect to the dbus socket and connect to systemd. You do need a dbus library though. They are less common than HTTP stacks.
TIL. I had no idea the systemd team implemented something like this already, it's great info, thank you. :)
Re:Why Fix Kubernetes and Systemd?
by customkitchen on Monday September 19, 2022 @06:11PM
(#32904811)
>They are less common than HTTP stacks.
libsystemd includes a d-bus library for exactly this reason.
Edit after further reflection: Alternatively, perhaps both of those complaints could be summarized as poor ability to interoperate with other tooling, in which case they really do fit together.