Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose client CA TLS certificate in receiver gRPC options #963

Closed
pavolloffay opened this issue May 13, 2020 · 0 comments · Fixed by #1185
Closed

Expose client CA TLS certificate in receiver gRPC options #963

pavolloffay opened this issue May 13, 2020 · 0 comments · Fixed by #1185

Comments

@pavolloffay
Copy link
Member

TLSCredentials struct should expose client's CA certificate option

opentelemetry-collector/receiver/securereceiverconfig.go

Line 33 in dc6b290

type TLSCredentials struct {

Here is an example from Jaeger:
https://github.com/jaegertracing/jaeger/blob/e1248014988b7cde207d45f73f4e402c21dd6eae/pkg/config/tlscfg/options.go#L67
This was referenced May 13, 2020
Closed
Merged
@ccaraman ccaraman mentioned this issue May 22, 2020
Merged
@bogdandrutu bogdandrutu mentioned this issue Jun 24, 2020
Merged
MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this issue Nov 11, 2021
@MrAlias
Make the stdout exporter a package (open-telemetry#963)
3b01a85 
* Make the stdout exporter its own package

Follow the pattern of the other exporters.

* Update dependabot with stdout exporter

* Add replace directives for stdout exporter

* Remove outdated example test from metric SDK

* go mod tidy

* Update othttp example test

Remove unused stdout exporter.

* Remove tests in API that depend on stdout exporter

The global package does not need to be validated with the SDK. A more
properly constructed end-to-end integration test should be built if this
is actually needed.

* Add replace clause for otel in stdout go.mod
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this issue Apr 27, 2023
@dependabot
Bump lycheeverse/lychee-action from 1.1.0 to 1.1.1 (open-telemetry#963)
bab053d 
Bumps [lycheeverse/lychee-action](https://github.com/lycheeverse/lychee-action) from 1.1.0 to 1.1.1.
- [Release notes](https://github.com/lycheeverse/lychee-action/releases)
- [Commits](lycheeverse/lychee-action@v1.1.0...v1.1.1)

---
updated-dependencies:
- dependency-name: lycheeverse/lychee-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this issue Jul 5, 2024
@lalitb
Separate baggage<->Context api from Baggage Propagator (open-telemetr…
7b1842b 
…y#963)
swiatekm pushed a commit to swiatekm/opentelemetry-collector that referenced this issue Oct 9, 2024
@Allex1
[BUMP] Operator v0.89.0/kube-rbac-proxy v0.15.0 (open-telemetry#963)
44ebd75 
* [BUMP] Operator v0.89.0/kube-rbac-proxy v0.15.0

* fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

mTLS: Add support to configure client CA and enforce ClientAuth bogdandrutu/opentelemetry-collector
1 participant
@pavolloffay