# Dapr v1.16.5

2025-12-19 · [릴리스 노트 원문](https://github.com/dapr/dapr/releases/tag/v1.16.5) · [전체 정리](https://ratatosk.io/ko/releases/dapr/v1.16.5)

중요 수정 2

## 중요 수정 (2)

### Pubsub 트레이스 컨텍스트 전파 수정

- 영향 대상: gRPC로 메시지를 전달하는 pubsub 컴포넌트

이번 릴리스 전에는 분산 트레이스가 불완전하거나 퍼블리셔와 서브스크라이버 간 연결 정보가 누락될 수 있었습니다. 이제 아웃고잉 gRPC 메타데이터에 트레이스 컨텍스트가 포함되어 다운스트림 서비스가 메시지 흐름 전반의 스팬을 연결해 확인할 수 있습니다.

> ## Trace information not populated in pubsub component using GPRC as transport
> ### Problem
> The pubsub component did not correctly propagate tracing information when delivering messages over gRPC.
> ### Impact
> Distributed traces were incomplete or missing links between publishers and subscribers. This prevented users from reliably correlating pubsub messages with their originating requests and spans.
> ### Root Cause
> The gRPC metadata used for pubsub calls did not include the tracing headers expected by downstream services and OpenTelemetry tooling. In particular, the trace context was not consistently attached to outgoing gRPC calls.
> ### Solution
> The trace context is now explicitly added to the outgoing gRPC metadata for pubsub calls. This ensures that downstream services receive the necessary tracing information and that spans can be correctly correlated across pubsub message flows.
> - [Trace information not populated in pubsub component using GPRC as transport](#trace-information-not-populated-in-pubsub-component-using-gprc-as-transport)

### Pulsar 컴포넌트의 파일 기반 클라이언트 시크릿 지원

- 영향 대상: 파일을 통한 OAuth2 클라이언트 시크릿 로테이션을 사용하는 Dapr Pulsar PubSub 설정 (추정)

`clientSecret` 파일이 업데이트되면 토큰을 갱신할 때 이전 시크릿을 계속 사용할 수 있습니다. 이로 인해 인증 오류가 발생하고 메시지 흐름이 중단될 수도 있습니다.

> ## Allow for OIDC clientSecret to be rotated when token is refreshed in the Pulsar PubSub component
> ### Problem
> The Pulsar OAuth2 client in the Go SDK only loads the client secret once at startup, and the Dapr Pulsar component only supports providing the clientSecret as a static value.
> This combination prevents rotating the OAuth2 client secret via a file path and breaks authentication when the clientSecret is changed.
> ### Impact
> Environments with strict security policies that require periodic rotation of the Pulsar OAuth2 client secret cannot safely rotate secrets.
> Once the clientSecret file is updated, token refresh operations may fail because the running client continues using the old secret, leading to authentication errors and potential message flow interruption.
> ### Root Cause
> The Dapr Pulsar component exposes clientSecret only as a literal value in metadata, not as a file path, so it cannot take advantage of secret rotation mechanisms based on files.
> ### Solution
> The Dapr Pulsar component will add support for specifying clientSecret (privateKey) via a file path in its metadata.
> - [Allow for OIDC clientSecret to be rotated when token is refreshed](#allow-for-oidc-clientsecret-to-be-rotated-when-token-is-refreshed-in-the-pulsar-pubsub-component)

---

정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.
