zarf-agent custom tolerations

[fingermustache]

Is your feature request related to a problem? Please describe.

It seems the zarf-registry package supports setting custom tolerations, but there's no such ability with the zarf-agent, especially because it's a set of manifests instead of a Helm chart. I'm currently trying to deploy Zarf to a boostrapping node that has a taint on it to only allow the pods necessary to get the cluster started. I intended to deploy Karpenter after zarf-init, but if non-tainted nodes need to exist for zarf-agent to work, I'm a bit stuck.

Is there a reason zarf-agent is a bunch of manifests instead of a Helm chart? If it was a chart, I could set an override.

Describe the behavior you'd like

zarf-agent configurable tolerations (helm charts)

• Given deploying zarf-init to a bootstrapping node.
• When I try to deploy karpenter after a zarf-init, there are non-tainted nodes needed for zarf-agent to work. I am trying to deploy zarf to a bootstrapping node that has a taint to only allow pods neccesary to get the cluster started.
• Then zarf-agent won't deploy.

Describe alternatives you've considered

custom init package