fix(envoyproxy): replace telemetry header by env var for envoy gateway#4051
Conversation
Signed-off-by: Eliott Bouhana <[email protected]>
BenchmarksBenchmark execution time: 2025-10-17 09:16:24 Comparing candidate commit b72c9f6 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics. |
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
devflow unqueued this merge request: It did not become mergeable within the expected time |
|
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|
What does this PR do?
This PR changes the way we get telemetry out of envoy gateway instances because we cannot add the usual custom header using EnvoyExtensionPolicy CRD. Therefore we fall back to only look if we run in kubernetes if we have not found another header we know of
Motivation
Better telemetry
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!