Disabling kustomize or Jsonnet isn't restarting argocd

[adrianmoisey]

I've done the following in my Values file:

configs:
  cm:
    jsonnet.enable: false
    kustomize.enable: false

But after applying it, it seems like argocd isn't restarted, making me assume that the config wasn't loaded.

Am I incorrect in this assumption?

[yu-croco]

Hi @adrianmoisey ,

But after applying it, it seems like argocd isn't restarted

The values at .configs.cm will be set to argocd-cm ConfigMap and it does not change any configurations against deployment of Argo CD server.
So, in your case, I think you need to restart ArgoCD server by yourself to read updated argocd-cm ConfigMap... 🤔

Maybe you can consider using https://github.com/stakater/Reloader to restart deployment when ConfigMap/Secret is updated.

[yu-croco]

Thank you for the info!
I didn't know that... 👀 I thought that in order for argocd-server to read updated argocd-cm, argocd-server needs to be restarted.

[adrianmoisey]

The argocd-server pod reads config directly via kube-api from the ConfigMap (argocd-cm) and therefore does not require a manual restart.

Thanks, that's useful to know.
Do you know how often it does this?

[pdrastil]

K8s controllers use either watchers or reconciliation loops with queues. As soon as you change the resource watcher will create event or item is queued for processing.

[adrianmoisey]

Is that what ArgoCD does?

[pdrastil]

Here is code that watches configs in Argo CD.

Ref: https://github.com/argoproj/argo-cd/blob/052a5d2f69aa6bcc61a9a744d1e46e99490fda59/server/server.go#L555