Argo CD
Hard
Troubleshooting & Debugging
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?
Select your answer:
Show answer and explanation
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 =.
More hard Argo CD questions
- In Argo CD 3.6, you run argocd app diff --local --server-side-generate with a single --local-include "*.yaml". Which files are sent?
- A proxy in front of argocd-server sends a traceparent header marked not sampled. With --otlp-sample-ratio=1.0 in Argo CD 3.6, what happens to that request's trace?
- What is a Sync Wave in Argo CD?
- How does Argo CD handle Kubernetes secrets?
- Which of the following is NOT a valid sync strategy in Argo CD?
- What is the purpose of resource hooks in Argo CD?