![]() ![]() The following features are now stable, having been in preview for at least 2 releases. Metrics for resiliency policies are now reported.Metrics for actor reminders and timers are now reported.Ī new preview feature enables a TTL on actor state which enables you to have the state automatically removed after a certain time Metrics You can now write app logs to the console as well as to a local log file with multi-app run command dapr run -f.It requires your app to expose a HTTP/2-capable server. Using HTTP/2 (including HTTP/2 Cleartext) can offer noticeable performance benefits when Dapr communicates with your app. H2c is a new value that configures Dapr to connect to your app using HTTP/2 Cleartext. Note: With Dapr 1.11, using -app-protocol=https and -app-protocol=grpcs is preferred to the previous option of setting -app-ssl=true (which is still supported but considered deprecated). Https and grpcs use HTTP and gRPC, respectively, but enable TLS. In Dapr 1.11, the CLI flag -app-protocol can now assume 3 more values in addition to http and grpc: App channel supports HTTP/2 and HTTP/2 Cleartext This is in addition to the images based on Windows Server 1809. On Kubernetes, it will automatically use the new dapr-dashboard Helm chart.ĭapr 1.11 offers container images for Windows Server 2022, using the windows-ltsc2022 tag. ![]() When using dapr init or dapr init -k with Dapr CLI, the Dapr Dashboard is still installed. Helm install dapr dapr/dapr-dashboard -namespace dapr-system To install the dashboard, use the new dapr-dashboard chart: The Dapr dashboard is no longer installed by default with the Dapr control plane when installing via Helm.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |