# After an upgrade to Argo CD 3.6, the repo-server stops sending custom OTLP headers to the trace collector. What is the likely cause?

Argo CD, Hard (Expert), Troubleshooting & Debugging. https://k8wiz.com/uquiz/after-an-upgrade-to-argo-cd-36-the-repo-server-stops-sending-custom-otlp-headers-to-the-trace-collector-what-is-the-likely-cause

- A. It now reads ARGOCD_REPO_SERVER_OTLP_HEADERS, not ARGOCD_REPO_OTLP_HEADERS
- B. It now reads headers only from the --otlp-headers command-line flag
- C. It now rejects every header value that contains an = character
- D. It now sends headers only when otlp.insecure is set to "false"

**Answer:** It now reads ARGOCD_REPO_SERVER_OTLP_HEADERS, not ARGOCD_REPO_OTLP_HEADERS

**Explanation:** Argo CD 3.6 renamed the repo-server variable to match the ARGOCD_<COMPONENT>_OTLP_HEADERS pattern used by the other components, and the old name is no longer read. The default manifests already set the new name, so only custom patches or Helm values break. Values containing = actually work better in 3.6, since each pair is split on its first =.