Hot-reloading of resiliency policies #5435
Labels
Comments
|
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
|
This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In what area(s)?
/area runtime
/area operator
Describe the feature
Resiliency policies are defined in Resiliency CRDs and are loaded by
daprdas soon as it starts up, requesting the list of policies from the Dapr Operator service. For self-hosted, they are loaded from disk whendaprdstarts.Because they are only loaded once, if the resiliency policies change, pods need to be restarted to pick up the updated policies.
We should implement a way for
daprdto "hot-reload" resiliency policies when they are changed. In K8s, this would happen by periodically polling the Dapr Operator to get updated policies (the polling interval will be configurable, but it should not require a persistent gRPC streaming connection, which is expensive).Release Note
RELEASE NOTE: ADD Hot-reloading for Dapr resiliency policies
The text was updated successfully, but these errors were encountered: