NodePlacement or Toleration/NodeSelector not working

[cristian98149]

Describe the bug NodePlacement or Toleration/NodeSelector don't affect argocd resources.

Expected behavior I've already deployed ArgoCD using GitOps operator on default nodes.

Now I need to move ArgoCD resources on dedicated nodes that have a taint and a label.

I've tried to use NodePlacement field in ArgoCD resource template adding the toleration (as indicated here). It takes the toleration but nothing happens and resources remain on default nodes.

Also, I've tried to set toleration inside GitOps Service resource and it works but just for 2 deployment resources: kam and cluster. Others resources (argocd-repo-server, application-controller, etc..) are not affected by this change. This is indicated here.

How can I reach my goal?

Thank you.

[dverbeek84]

Same issue here, and i also found the problem. There is a default nodeselector in place:

nodeSelector: kubernetes.io/os: linux machine.openshift.io/cluster-api-machineset: cl01-worker-0

but our infra nodes are a different machine set called cl01-infra-0