Argo CD monitor
A CDK8s chart that adds what the Pulumi-installed Argo CD lacks: metrics Services for VMAgent to scrape and a trusted TLS certificate. Adding them here avoids changing the platform stack.
| Namespace | argocd |
| Source | argocd_monitor.go |
| Exposure | — |
| Storage | — |
| Auth | — |
Configuration
Section titled “Configuration”Each component gets a <name>-metrics Service and a ServiceMonitor scraping /metrics every 30s.
| Component | Metrics port |
|---|---|
argocd-application-controller | 8082 |
argocd-server | 8083 |
argocd-repo-server | 8084 |
argocd-applicationset-controller | 8085 |
The cert-manager Certificate argocd-server-tls (issuer letsencrypt-prod, argocd.madhan.app) writes the Secret Argo CD looks for by name, replacing its self-signed certificate.
Troubleshooting
Section titled “Troubleshooting”Argo CD metrics missing
Section titled “Argo CD metrics missing”Empty endpoints mean the Service selector matches no pod; compare with the pod labels.
kubectl get servicemonitor,endpoints -n argocd | grep metricskubectl get pods -n argocd --show-labels