Tolerations/NodeSelector for Zarf registry

[docandrew]

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

We'd like to be able to add a NodeSelector and tolerations to the Zarf registry via deployment variables for the zarf init command with --set. The immediate need driving this request is to work around #2104, but I think other users would benefit by being able to fine-tune their registry placement or enable the use of Zarf on nodes already tainted for different reasons.

Describe the solution you'd like

• Modify the Zarf registry charts to allow templating of the nodeSelector and tolerations keys in the spec.
• Add Zarf variables the Zarf registry zarf.yaml to enable setting these w/ --set during zarf init.

Describe alternatives you've considered

Manual modification and/or deployment of custom zarf init package with these set, or patching the registry manifests post-deployment.

[Racer159]

Adding good first issue - this would be relatively simple to add as another Zarf variable in the registry zarf.yaml file. It would just need to be passed down to the deployment.yaml in the chart which we also control.

https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/zarf.yaml#L60
https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/registry-values.yaml#L46
https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/chart/templates/deployment.yaml#L28

https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

[lemonprogis]

Hello 👋, @docandrew. I would like to pick this issue up if it's available.

[lemonprogis]

Nevermind, I see @waveywaves got it, thanks!