Warn when registry wont work without node affinity

[phillebaba]

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

By default the registry deployed by Zarf will have a node affinity configured to always run on the same node. It is also configured to deploy only a single instance. It is possible to disable this affinity and deploy multiple instances if one wants to run the registry in HA mode. This does however require that the PVC used by the registry supports ReadWriteMany as stated in the documentation.

https://docs.zarf.dev/ref/init-package/#making-the-registry-highly-available

While it may not work it is possible to deploy the registry with the affinity disabled while using a PVC which would not support the pod scheduling. To help the end user we could give them a warning the the configuration is not possible, to avoid future questions.

Describe the solution you'd like

• Given a Kubernetes cluster with PVC that is configured ReadWriteOnce
• When Zarf is instantiated with zarf init --set=REGISTRY_AFFINITY_ENABLE=false
• Then Zarf should warn about the potential problems

Describe alternatives you've considered

N/A

Additional context

N/A