| 28 Jul 2025 |
 magic_rb | So i gave up, went to istio | 16:27:48 |
| magic_rb | But istio is insanely slow, envoy has huge overheads | 16:29:01 |
| magic_rb | I can see envoy burning cpu time when im copying from my nix cache, so im throwing the whole thing out | 16:29:55 |
 Zhaofeng Li | hmm, that doesn't sound too good... basically https://spot.rackspace.com provides cheap compute but their control plane is garbage, so I want to just shove a daemonset up there and run my k3s 🙃 | 16:31:24 |
| magic_rb | Yeah i wouldnt, pain | 16:33:01 |
| magic_rb | What you save on hardware cost youll spend double on your sanity because kubernetes and istio/cilium | 16:33:20 |
| Zhaofeng Li | (with a bit of wireguard and bird magic maybe I can make them join my existing cluster, but yeah, extremely cursedness) | 16:33:29 |
| magic_rb | I went into it enthusiastically trying to make it work, but the whole thing is rotten from the core. | 16:33:42 |
| Zhaofeng Li | * (with a bit of wireguard and bird magic maybe I can make them join my existing cluster, but yeah, extreme cursedness) | 16:34:39 |
| magic_rb | etcd fucking sucks, its slow as hell. The manifests gets huge very quickly, i can never remember all of the obscure options, networking is a mess, if you want to use the new gateway api youll end up reading issues trying to figure what is or isnt supported, eventually reading tests and source code like me. | 16:34:44 |
| Zhaofeng Li | can't say much about the gateway api, but etcd basically just works for me though my setup is far from complex | 16:37:22 |
 emily | it should almost certainly be a systemd daemon, I think | 17:31:58 |
| emily | (it can be a oneshot or similar though) | 17:32:10 |
| emily | we don't want to add new activation scripts unless it's completely unavoidable | 17:32:13 |
| emily | (and moving stuff out of activation scripts is being worked on) | 17:32:36 |
| emily | (this doesn't necessarily determine where in the options hierarchy to put it though) | 17:34:06 |
 ElvishJerricco | It'll have to support systemd initrd if it's going to be upstreamed. The plan is to phase out scripted initrd over the next year or so, which means scripted-initrd-only things are not acceptable, though systemd-initrd-only things are acceptable. | 17:41:18 |
| magic_rb | Should be fine for ifstate, i run it not in the initrd but on systemd initrd | 17:44:03 |
| emily | ah I see it's already systemd.services.ifstate | 17:44:10 |
| emily | so never mind me about activation scripts | 17:44:16 |
| emily | I would personally probably go for services.ifstate.* IMO, it's comparable to services.network-manager.* in that you have a systemd service managing the config, but I'm ambivalent | 17:44:54 |
| emily | networkd is under systemd.network.* which is its own kind of weird :P | 17:45:01 |
| emily | well,
message = "ifstate.nix does not currently implement a systemd unit for initrd. Please continue to use the scripted stage one for the time being.";
| 17:45:11 |
| emily | so yeah we'd want to drop the initrd support for upstreaming or else implement systemd initrd support (and probably only systemd initrd support) | 17:45:27 |
| magic_rb | In reply to @emilazy:matrix.org
well,
message = "ifstate.nix does not currently implement a systemd unit for initrd. Please continue to use the scripted stage one for the time being.";
I dont see why it couldnt, at least v1, i havent used v2 | 17:45:37 |
| emily | (we are hoping to flip the default to systemd initrd within the month) | 17:45:38 |
| emily | I didn't say couldn't :P I'm just talking about what the module actually says, in the context of upstreaming it | 17:45:52 |
| magic_rb | In reply to @emilazy:matrix.org
(we are hoping to flip the default to systemd initrd within the month) (Finally) | 17:45:55 |
| magic_rb | In reply to @emilazy:matrix.org
I didn't say couldn't :P I'm just talking about what the module actually says, in the context of upstreaming it Ah okay | 17:46:01 |
 Marcel | In reply to @emilazy:matrix.org
so yeah we'd want to drop the initrd support for upstreaming or else implement systemd initrd support (and probably only systemd initrd support) i've just never came to create a unit, because all my sytems still use scrypted stage 1 - allthough thats something, that i will definitely add | 17:47:14 |
