This message was deleted.

Try messing with the list of commands in

/oem/90_custom.yaml

(see e.g. https://docs.harvesterhci.io/v1.2/install/update-harvester-configuration#configuration-persistence)

thanks! I wonder if the commands I put in afterinstallchroot get thrown into here if I install the system with them?

> I wonder if the commands I put in afterinstallchroot get thrown into here if I install the system with them? I think so, but haven't tested

Hrm. Doesn’t seem to work, but it may be because I’m running iptables rules and some other process runs and flushes the tables afterwards. Are you familiar with what that might be? I need to have some persistent rules aside from all the K8s/Calico rules that automatically get added. They apply specific to an interface.

hrm... no, sorry, I haven't really looked in detail into the nitty gritty of the networking stuff yet

AYe. Yeah, the commands works. It’s gotta be an iptables flush

no problem! (sorry I can't advise further ATM 😕 )

no worries. everything helps

you can create a new file under /oem/your-file.yaml and it will be executed on boot it just needs to follow elemental-toolkit cloud-init format

I got this to work, but something does na iptables flush later on within the harvester/calico machinery