from what i understand, running systemd within kubernetes isn’t necessarily desirable, in the sense if you run separate services then kubernetes can evaluate health, restart or scale out at that level as needed.
I’m doubtful NixOS modules will practically make it into easykubenix in my lifetime unless systemd is entirely abstracted away into wrapper scripts (Modular modules?) but yes.
so, the mentioned modular services feature that was recently introduced does target this level - so we’re kind of trying to figure out how we can better make that work to facilitate supporting the functionality of more of the existing service modules.
now, our existing nixos service modules of course both use potentially multiple services and could contain non-systemd stuff. this poses challenges as you noted, tho (as per the linked threads) at least on the former we have a few ideas already.
for what it’s worth, we have a vested interest in figuring those things out, given this could make the modules generic enough for reuse across environments - see also the RFC that inspired modular service. there’s a matrix channel on this as well.