RATATOSK
← 전체 릴리스

Daprv1.17.11

중요 수정 2기타 2

Dapr 알림 받기

확인할 변경이 있을 때만 주 1회, critical 보안 공지는 즉시 발송

중요 수정2

  • 액터 리마인더 목록의 메타데이터 수정
    영향 대상ID에 ||가 포함된 액터
    Listing reminders for actors whose IDs contain `||` now also reports the correct actor metadata.
    github.com/dapr/dapr/releases/tag/v1.17.11
  • Scheduler에서 Dapr 유효 리마인더 이름, 작업 이름 및 액터 ID 허용
    영향 대상Scheduler 기반 액터 리마인더 및 예약 작업

    이전에는 리마인더 이름이나 액터 ID에 | 또는 @ 같은 문자가 포함되면 리마인더 등록이 실패했고, 엄격한 DNS-1123 문자 집합을 벗어나는 예약 작업 이름도 영향을 받았습니다. 이제 이름과 액터 ID에 대문자, |, @, ||를 사용할 수 있습니다. /, \, #, ?, 제어 문자와 경로 시퀀스가 정확히 . 또는 ..인 경우는 여전히 허용되지 않습니다.

    ## Actor reminders and jobs fail to register when their name or actor ID contains characters such as `|` or `@`
    ### Problem
    Registering an actor reminder through the Scheduler service failed when the reminder name, or the actor ID it belongs to, contained certain characters such as the pipe `|` or at sign `@`.
    The same characters are accepted when invoking actors and when saving actor state, so an actor that worked everywhere else could not have a reminder created for it.
    The error returned in this case was also misleading:
    a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
    It claimed only lowercase names were allowed even though uppercase names are in fact accepted, and it did not describe which characters were actually rejected.
    ### Impact
    You were affected if you used Scheduler-backed actor reminders (the default since 1.15) and your reminder names, actor IDs, or scheduled job names contained characters outside the strict DNS-1123 set, for example `|`, `@`, or uppercase letters.
    ### Root Cause
    The Scheduler composes each reminder or job into a single name of the form `actorreminder||<namespace>||<type>||<id>||<name>` (or `app||<namespace>||<appID>||<name>` for jobs), using `||` as an internal delimiter.
    Each `||`-delimited segment was then validated against Kubernetes' DNS-1123 subdomain rules, which only permit lowercase alphanumeric characters, `-`, and `.`.
    This was far stricter than the character set Dapr already accepts at its API edge, producing the inconsistency between actor invocation and reminder registration.
    Because the validator lowercased each segment before checking it, uppercase names passed in practice while the surfaced error still referred to lowercase-only RFC 1123 subdomains.
    ### Solution
    The Scheduler now validates names using the same policy Dapr applies at its API edge, so anything accepted for actor invocation can also be used for a reminder or job.
    Reminder names, job names, and actor identifiers may now contain any character except `/`, `\`, `#`, `?`, control characters (including the NUL byte), and the exact path sequences `.` and `..`.
    Uppercase letters and characters such as `|` and `@` are allowed, and `||` continues to be accepted within actor IDs and names.
    - [Actor reminders and jobs fail to register when their name or actor ID contains characters such as `|` or `@`](#actor-reminders-and-jobs-fail-to-register-when-their-name-or-actor-id-contains-characters-such-as--or-)
    github.com/dapr/dapr/releases/tag/v1.17.11
기타2

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