Carlos M.

+1

I also notice the same issue without using helm. For example: ```yaml apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: gitops namespace: argocd finalizers: - resources-finalizer.argocd.argoproj.io spec: project: cluster-admin sources: - repoURL:...

> We have https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/deployment/helm/node-feature-discovery/values.yaml#L96 > > Commented and with a low request/limit. moving forward should be the opposite, it should be uncommented and users can comment out if they feel...

I can contribute with a PR if that helps.

> We always welcome PR :) > > Argo CD has same kind of condition for ServiceMonitor, so it sounds reasonable to adopt the same style. https://github.com/argoproj/argo-helm/blob/main/charts/argo-cd/templates/argocd-server/servicemonitor.yaml#L1 Perfect! Here it...

There's still an open pr associated to this issue. Removing the stale label.

Also confirmed that adding `redis.compression: none` in ConfigMap `argocd-cmd-params-cm` solves the issue. I'm also using ArgoCD v2.8.4.

I still can reproduce this issue with version v23.9.0. In our case the NVIDIA drivers come pre-installed, and I can see devices `/dev/nvidia*`

> - name: DISABLE_DEV_CHAR_SYMLINK_CREATION > value: "true" This what we have in our `values.yaml`: ```yaml validator: driver: env: - name: DISABLE_DEV_CHAR_SYMLINK_CREATION value: "true" ```

I can submit a PR to fix this if it is ok.