Support zarf-init when cluster is comprised of nodes that are all tainted

[jacobbmay]

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

Currently zarf-init doesn't work if all nodes are tainted. Example scenario, you have a cluster that currently only contains control-plane nodes and you have a reason to do a zarf deploy before any worker nodes are added to the cluster. There is currently no way to zarf-init the cluster without removing taints from 1 or more control-plane nodes.

Steps to replicate unsupported scenario

• Create a new k0s cluster with sudo k0s install controller --enable-worker
• Start k0s cluster with sudo k0s start
• Attempt to perform a zarf-init

You will see the error ERROR: failed to deploy bundle: unable to deploy component "zarf-seed-registry": no suitable injector image or node exists even if you have configured the REGISTRY_TOLERATIONS and PROXY_TOLERATIONS zarf vars to tolerate the control-plane taint.

If you remove the taints from the single control-plane node and try again, the zarf init will successfully create the injector pod.

Describe the behavior you'd like

• Given a cluster with all nodes tainted
• When a zarf init package is deployed and tolerations are configured
• Then the zarf init successfully creates the injector and stands up all of the zarf components on the tainted node(s)

[a1994sc]

A "hack" is add an .actions.onDeploy.after[] something like this:

components:
  - name: zarf-injector
    actions:
      onDeploy:
        before:
          - description: Permit Inject and socat on all nodes
            cmd: |-
              ./zarf tools kubectl -n zarf patch ds zarf-injector -p '{"spec": { "template": { "spec": {"tolerations": [ {"operator": "Exists"} ]}}}}'
              ./zarf tools kubectl -n zarf patch ds zarf-registry-proxy -p '{"spec": { "template": { "spec": {"tolerations": [ {"operator": "Exists"} ]}}}}'