Preview features in Dapr are considered experimental when they are first released.
Runtime preview features require explicit opt-in in order to be used. The runtime opt-in is specified in a preview setting feature in Dapr’s application configuration. See How-To: Enable preview features for more information.
For CLI there is no explicit opt-in, just the version that this was first made available.
Current preview features
||In self hosted mode you can set this flag to specify any private registry to pull the container images required to install Dapr||N/A||CLI init command reference||v1.7|
|Resiliency||Allows configuring of fine-grained policies for retries, timeouts and circuitbreaking.||
||Configure Resiliency Policies||v1.7|
|App Middleware||Allow middleware components to be executed when making service-to-service calls||N/A||App Middleware||v1.9|
|App health checks||Allows configuring app health checks||
||App health checks||v1.9|
|Pluggable components||Allows creating self-hosted gRPC-based components written in any language that supports gRPC. The following component APIs are supported: State stores, Pub/sub, Bindings||N/A||Pluggable components concept||v1.9|
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.