feat: allow using secrets for header for grpc/http exports#1156
Open
basti1302 wants to merge 1 commit into
Open
feat: allow using secrets for header for grpc/http exports#1156basti1302 wants to merge 1 commit into
basti1302 wants to merge 1 commit into
Conversation
basti1302
force-pushed
the
ope-431-enable-grpchttp-headers-for-non-dash0-exports-via-kubernetes
branch
from
c9b8feb to
11f355a
Compare
basti1302
changed the title
basti1302
force-pushed
the
ope-431-enable-grpchttp-headers-for-non-dash0-exports-via-kubernetes
branch
7 times, most recently
from
172ed2f to
477e01b
Compare
Header values for non-Dash0 gRPC/HTTP exports can now also be sourced
from a Kubernetes secret, as an alternative to providing the value as a
literal.
Each header now takes exactly one of:
- value: the header value as a literal string (as before), or
- valueFrom.secretKeyRef: a reference to a key in a Kubernetes secret
holding the value, useful for sensitive data like
authorization tokens or API keys.
A validation rule enforces that exactly one of the two is set. When a
header is sourced from a secret, the operator injects a corresponding
environment variable (backed by the secret) into the collector pod and
renders the header value in the collector config as a ${env:...}
reference, so the sensitive value is never stored in plain text in the
custom resource.
The secret must exist in the operator's namespace.
basti1302
force-pushed
the
ope-431-enable-grpchttp-headers-for-non-dash0-exports-via-kubernetes
branch
from
477e01b to
188ae5b
Compare
Member
Author
|
/run-e2e |
Contributor
🚀 E2E tests triggered
Results will be posted here once the tests complete. You can also view the workflow runs directly. |
Contributor
✅ E2E tests passed
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.