apiserver-runtime
apiserver-runtime copied to clipboard
kubernetes-sigs
build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.35.0 to 0.46.0
Bumps go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.35.0 to 0.46.0.
Release notes
Sourced from go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc's releases.
Release v1.21.0/v0.46.0/v0.15.0/v0.1.0
Added
- Add the new
go.opentelemetry.io/contrib/instrgenpackage to provide auto-generated source code instrumentation. (#3068, #3108)- Add
"go.opentelemetry.io/contrib/samplers/jaegerremote".WithSamplingStrategyFetcherwhich sets custom fetcher implementation. (#4045)- Add
"go.opentelemetry.io/contrib/config"package that includes configuration models generated via go-jsonschema. (#4376)- Add
NewSDKfunction to"go.opentelemetry.io/contrib/config". The initial implementation only returns noop providers. (#4414)- Add metrics support (No-op, OTLP and Prometheus) to
go.opentelemetry.io/contrib/exporters/autoexport. (#4229, #4479)- Add support for
consolespan exporter and metrics exporter ingo.opentelemetry.io/contrib/exporters/autoexport. (#4486)- Set unit and description on all instruments in
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp. (#4500)- Add metric support for
grpc.StatsHandleringo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#4356)- Expose the name of the scopes in all instrumentation libraries as
ScopeName. (#4448)Changed
- Dropped compatibility testing for [Go 1.19]. The project no longer guarantees support for this version of Go. (#4352)
- Upgrade dependencies of OpenTelemetry Go to use the new
v1.20.0/v0.43.0release. (#4546)- In
go.opentelemetry.io/contrib/exporters/autoexport,Optionwas renamed toSpanOption. The old name is deprecated but continues to be supported as an alias. (#4229)Deprecated
- The interceptors (
UnaryClientInterceptor,StreamClientInterceptor,UnaryServerInterceptor,StreamServerInterceptor,WithInterceptorFilter) are deprecated. Use stats handlers (NewClientHandler,NewServerHandler) instead. (#4534)Fixed
- The
go.opentelemetry.io/contrib/samplers/jaegerremotesampler does not panic when the default HTTP round-tripper (http.DefaultTransport) is not*http.Transport. (#4045)- The
UnaryServerInterceptoringo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcnow sets gRPC status code correctly for therpc.server.durationmetric. (#4481)- The
NewClientHandler,NewServerHandleringo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcnow honorotelgrpc.WithMessageEventsoptions. (#4536)Release v1.20.0/v0.45.0/v0.14.0
Added
- Set the description for the
rpc.server.durationmetric ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#4302)- Add
NewServerHandlerandNewClientHandlerthat return agrpc.StatsHandlerused for gRPC instrumentation ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#3002)- Add new Prometheus bridge module in
go.opentelemetry.io/contrib/bridges/prometheus. (#4227)Changed
- Upgrade dependencies of OpenTelemetry Go to use the new
v1.19.0/v0.42.0/v0.0.7release.- Use
grpc.StatsHandlerfor gRPC instrumentation ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc/example. (#4325)New Contributors
@puckpuckmade their first contribution in open-telemetry/opentelemetry-go-contrib#4302Full Changelog: https://github.com/open-telemetry/opentelemetry-go-contrib/compare/v1.19.0...v1.20.0
Release v1.19.0/v0.44.0/v0.13.0
Added
... (truncated)
Changelog
Sourced from go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc's changelog.
[1.21.0/0.46.0/0.15.0/0.1.0] - 2023-11-10
Added
- Add
"go.opentelemetry.io/contrib/samplers/jaegerremote".WithSamplingStrategyFetcherwhich sets custom fetcher implementation. (#4045)- Add
"go.opentelemetry.io/contrib/config"package that includes configuration models generated via go-jsonschema. (#4376)- Add
NewSDKfunction to"go.opentelemetry.io/contrib/config". The initial implementation only returns noop providers. (#4414)- Add metrics support (No-op, OTLP and Prometheus) to
go.opentelemetry.io/contrib/exporters/autoexport. (#4229, #4479)- Add support for
consolespan exporter and metrics exporter ingo.opentelemetry.io/contrib/exporters/autoexport. (#4486)- Set unit and description on all instruments in
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp. (#4500)- Add metric support for
grpc.StatsHandleringo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#4356)- Expose the name of the scopes in all instrumentation libraries as
ScopeName. (#4448)Changed
- Dropped compatibility testing for [Go 1.19]. The project no longer guarantees support for this version of Go. (#4352)
- Upgrade dependencies of OpenTelemetry Go to use the new
v1.20.0/v0.43.0release. (#4546)- In
go.opentelemetry.io/contrib/exporters/autoexport,Optionwas renamed toSpanOption. The old name is deprecated but continues to be supported as an alias. (#4229)Deprecated
- The interceptors (
UnaryClientInterceptor,StreamClientInterceptor,UnaryServerInterceptor,StreamServerInterceptor,WithInterceptorFilter) are deprecated. Use stats handlers (NewClientHandler,NewServerHandler) instead. (#4534)Fixed
- The
go.opentelemetry.io/contrib/samplers/jaegerremotesampler does not panic when the default HTTP round-tripper (http.DefaultTransport) is not*http.Transport. (#4045)- The
UnaryServerInterceptoringo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcnow sets gRPC status code correctly for therpc.server.durationmetric. (#4481)- The
NewClientHandler,NewServerHandleringo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcnow honorotelgrpc.WithMessageEventsoptions. (#4536)[1.20.0/0.45.0/0.14.0] - 2023-09-28
Added
- Set the description for the
rpc.server.durationmetric ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#4302)- Add
NewServerHandlerandNewClientHandlerthat return agrpc.StatsHandlerused for gRPC instrumentation ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#3002)- Add new Prometheus bridge module in
go.opentelemetry.io/contrib/bridges/prometheus. (#4227)Changed
- Upgrade dependencies of OpenTelemetry Go to use the new
v1.19.0/v0.42.0/v0.0.7release.- Use
grpc.StatsHandlerfor gRPC instrumentation ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc/example. (#4325)Removed
- The
net.sock.peer.*andnet.peer.*high cardinality attributes are removed from the metrics generated bygo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#4322)[1.19.0/0.44.0/0.13.0] - 2023-09-12
Added
... (truncated)
Commits
b4b06bcRelease v1.21.0/v0.46.0/v0.15.0/v0.1.0 (#4546)c1ac303config: Prepare module for release (#4541)fe68fe9host: fix typo (#4540)016b46fotelgrpc: Use net.Listen in TestStatsHandler (#4538)23bd4edotelgrpc: Deprecate interceptors in favor of stats handlers (#4534)a3b16aeExpose instrumentation scope name (#4448)2b69029otelgrpc: Fix stats handlers to honor WithMessageEvents option (#4536)f6aeb0dotelgrpc: Stablize TestInterceptors (#4535)b44dfc9otelgrpc: Remove high cardinality metric attributes (#4322)2a5fe23otelgrpc: Refine tests to use a net socket instead of a buffer (#4503)- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign yue9944882 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.