We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I want to deploy my argocd pods on a specific node role using nodeAffinity like this :
global: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: role operator: In values: - <MY_NODE_ROLE>
But this is not replicated inside the manifests and the applications are deployed wherever they can
argo-cd
7.3.11
Deploy the helm release with this kind of helm values
argo-cd to be deployed on the good set of nodes
No response
The text was updated successfully, but these errors were encountered:
Hi @afreyermuth98 , According to the values.yaml, you need to define like below ?
global: affinity: nodeAffinity: # -- Default node affinity rules. Either: `none`, `soft` or `hard` type: hard # -- Default match expressions for node affinity matchExpressions: - key: role operator: In values: - <MY_NODE_ROLE>
You can also read the list of types in README. https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd#global-configs
Sorry, something went wrong.
No branches or pull requests
Describe the bug
I want to deploy my argocd pods on a specific node role using nodeAffinity like this :
But this is not replicated inside the manifests and the applications are deployed wherever they can
Related helm chart
argo-cd
Helm chart version
7.3.11
To Reproduce
Deploy the helm release with this kind of helm values
Expected behavior
argo-cd to be deployed on the good set of nodes
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: