Custom config on the operator

[woot3d]

Describe the bug I'm trying to change the loglevel on all components ( sts + the 2 deploy) and saw that its managed by the CR ArgoCD, so i tried to add a new flag on the ArgoCD CR to change the loglevel but it did not work, i tried to update that directly on the sts and the Deploy ( it accepts the syntax) but it do not persist, so my question is how to make that custom change ( loglevel) persist .

To Reproduce Steps to reproduce the behavior:

1. Go to 'ArgoCD CR'
2. Click on 'Edit'
3. Scroll down to 'Any resource'
4. Try to update the loglevel

Expected behavior I expect the change on the ArgoCD CR with the new loglevel to be reflected on my ArgoCD components and to persist

Additional context GitOps v1.5.6

[okanarabaci]

I am experiencing the same issue, but I'm able to update all components except openshift-gitops-applicationset-controller.

Copy pasting my issue I was going to create:

Describe the bug I'm trying to reduce the loggin of my ArgoCD instance in OpenShift. I'm unable to set a logLevel that changes the behaviour of the applicationSet controller. I have set warn, error and I still get all DEBUG messages logged in my applicationSet controller pod in OpenShift.

To Reproduce Steps to reproduce the behavior:

1. Go to the GitOps operator
2. Click on ArgoCD tab
3. Click on the ArgoCD instance deployed
4. Edit yaml to add:

  applicationSet:
    logLevel: error
    resources:
      limits:
        cpu: '2'
        memory: 1Gi
      requests:
        cpu: 250m
        memory: 512Mi

6. Check the openshift-gitops-applicationset-controller pod logs, no changes are made and DEBUG logs still showing.

Expected behavior When changing logLevel to e.g. error, the DEBUG logs should not get logged.

Additional context OCP v4.10 GitOps operator v1.5.7