-
Bug
-
Resolution: Done
-
Major
-
None
-
1.11.1
-
8
-
False
-
None
-
False
-
-
-
GitOps Scarlet - Sprint 3257, GitOps Scarlet - Sprint 3258, GitOps Scarlet - Sprint 3259, GitOps Scarlet - Sprint 3260, GitOps Scarlet - Sprint 3261
Issue :
I have a customer, Who wants to schedule GitOps pods to a dedicated nodes.
In order to achieve that we tried below steps :
1] Added label to the node :
$ oc label node <Node-Name> <Key>=<Value>
Then added "nodePlacement" ArgoCD CR as below :
$ oc get argocd openshift-gitops -n openshift-gitops -o yaml | grep -i nodeplacement -A3
nodePlacement: <----------
nodeSelector: <----------
key: value <----------
With this, We are able to schedule the GitOps pods to respective node.
But after few hours this changes gets reverted back.
Environment:
OCP Version: 4.12.29
GitOps Operator Version: 1.11.1
Actual results:
Unable to schedule pods to specific nodes.
Expected results:
Able to schedule pods to specific nodes.
Additional Info :
I see similar issue reported on Thread
Where it is advised to update the "gitopsservice" for the same and not ArgoCd instance.
I could also see a RFE around the same > GITOPS-2164
Which has a fix version Openshift GitOps 1.7.0
This RFE introduced a feature that enable users to set custom nodeSelectors in their operator workloads by editing their GitopsService CR like so:
spec:
nodeSelector:
key1: value1
But we are not able to patch a "gitopservice" with this.
- mentioned on
