Can't make it work with helm installation

[phgeraldeli]

Can we have a docs or an example using the helm chart github.com/argoproj/argo-helm?

[phgeraldeli]

I`ve edited manually, and still got the problem below

Changed source in configmap manifests to use my prometheus at:

When trying to access got No metrics to display and accessing the url:

"Invalid headers: header "Argocd-Application-Name" must be provided"

Followed all instruction on readme. Someone can help me?

[phgeraldeli]

It would be great something like this:

https://github.com/argoproj-labs/rollout-extension/pull/72/files

[yalattas]

this is great. Yet, I think it misses to deploy argocd-metrics-server at the first place, I've been trying to find it in the helm values but I found the extension without the actual deployment
https://github.com/argoproj/argo-helm/blob/main/charts/argo-cd/values.yaml

As a workaround, I guess I can use extraObjects to deploy the metrics-server.

Currently stuck at the final step

Finally Argo CD needs to be configured so it knows how to reach the metrics server. In order to do so, add the following section in the argocd-cd.

extension.config: |-
  extensions:
    - name: metrics
      backend:
        services:
          - url: <METRICS_SERVER_URL>

README stating I should put above snippet in argocd-cd which I don't have in my cluster. Even though, I thought its typo and should be argocd-cm but it doesn't make sense with the mentioned syntax. argocd-cm takes a different input

  cm:
    create: true
    admin.enabled: true
    server.rbac.log.enforce.enable: true
  params:
    create: true
    server.insecure: true
    server.enable.proxy.extension: "true"

[antodoms]

still trying to figure out why i am getting empty dashboard in the argocd metrics extension tab. the issue seems to be similar to this.

i am using the below for metrics-server-configmap

{
...
...
"provider":
      {
        "Name": "default",
        "default": true,
        "address": "http://prometheus-server.prometheus.svc.cluster.local"
      }

and then for argocd helm chart values.txt i got the below values

configs:
    cm:
        create: true
        server.rbac.log.enforce.enable: true
        extension.config: |-
           extensions:
             - name: metrics
               backend:
                  services:
                     - url: http://argocd-metrics-server:9003
    params:
        create: true
        server.insecure: true
        server.enable.proxy.extension: "true"

[yalattas]

still trying to figure out why i am getting empty dashboard in the argocd metrics extension tab. the issue seems to be similar to this.

i am using the below for metrics-server-configmap

{
...
...
"provider":
      {
        "Name": "default",
        "default": true,
        "address": "http://prometheus-server.prometheus.svc.cluster.local"
      }

and then for argocd helm chart values.txt i got the below values

configs:
    cm:
        create: true
        server.rbac.log.enforce.enable: true
        extension.config: |-
           extensions:
             - name: metrics
               backend:
                  services:
                     - url: http://argocd-metrics-server:9003
    params:
        create: true
        server.insecure: true
        server.enable.proxy.extension: "true"

how did deploy argocd-metrics-server ? via helm with the official ArgoCD values ?

In my case I don't see any metrics

Should I use extraObjects to deploy the metrics server ?

[mcanevet]

Have you tried to escape the curly braces in the ConfigMap. i.e, using:

"queryExpression": "sum(rate(container_cpu_usage_seconds_total{pod=~\"{{`{{.name}}`}}\", image!=\"\", container!=\"POD\", container!=\"\", container_name!=\"POD\"}[5m])) by (pod)"

instead of:

"queryExpression": "sum(rate(container_cpu_usage_seconds_total{pod=~\"{{.name}}\", image!=\"\", container!=\"POD\", container!=\"\", container_name!=\"POD\"}[5m])) by (pod)"

[vikramalmosafer]

yalattas
try this....

"provider":
{
"Name": "default",
"default": true,
"address": "http://prometheus-operated.monitoring.svc.cluster.local:9090"
}
}
}