This message was deleted.

Not sure what you're trying to achieve exactly here and if a plan is the best way forward 🤔 You know about https://github.com/rancher-sandbox/elemental-example-plan ?

@silly-airline-38945 local plans for

elemental-system-agent

are disabled by default since elemental-operator v1.4.0 (done in https://github.com/rancher/elemental-operator/pull/534), which is the version of elemental-operator version you are using? We do not expect

elemental-system-agent

to be used for customizations. Do you have further insights of what this plan is actually doing? is there anything special with it that you want to use a plan? You could already add commands to execute at boot in MachineRegistration directly, without the need of wrapping it in a system-agent plan.

Hi, ok. Operator is "latest and greatest" so now I know why it is not fiering. I was investigating if I could run a k0s worker initialize (or kubeadm join) as a run once instruction. Running command I guess is runcmd? Im provisioning customized elementals (and kamaji) with terraform so i can also add necessary files as write_files. Still working out the best way for provisioning (without cluster API at the moment) 😃