Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

NodePlacement or Toleration/NodeSelector not working

Open
  • Is something wrong?
#572 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, kubernetes
Domain
devops, infrastructure

Research direction

Start by tracing how the ArgoCD resource template's NodePlacement and the GitOps Service resource's toleration are applied to generated resources. Compare the affected kam and cluster deployments with argocd-repo-server and application-controller, using the linked custom-resource documentation as context. Done means the configured node label and taint placement affect all intended ArgoCD resources.

Written by the indexing model from the issue text.

Description

triage:required

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.

Dominant language
Go
Stars
188
Forks
359
Avg merge
3d 12h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redhat-developer/gitops-operator

All issues in redhat-developer/gitops-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.