Dapr v1.0.0-rc.1 is now available
In a recent blog post , we shared that Dapr is on the path towards a v1.0 release and today we are excited to announce that the first release candidate for v1.0 is available. This release candidate marks a significant milestone for Dapr as it has matured to be a solution for developers building distributed applications in a variety of scenarios.
We invite the Dapr community to install and start using this release and help us find and fix issues so we can get Dapr further closer to a production ready release. As issues are identified and fixed, we expect to continue and release additional release candidate versions until the official v1.0.0 release.
We are proud of the community that has grown around Dapr since it was first released and of the significant contributions the project has seen from community members along the way. This important step in the maturity of Dapr is an achievement for the entire community and we are thankful for each and every community member who has tried out Dapr, opened issues, submitted pull requests and engaged with us to make it better.
Installing and using v1.0.0-rc.1
Since this is a release candidate, if you would like to try it out you will have to explicitly opt-in and install it. The instructions to upgrade to the v1.0.0-rc.1 can be found in the release notes as well as in the v1.0.0-rc.1 docs.
These are some highlights for this release:
The actor placement service now has a high availability (HA) configuration to improve resilience and enable upgrades on production system that use actors to minimize downtime on actor instance availability.
Substantial work has been done on improving the scale and performance of actors.
Starting with this release you can configure the Open Telemetry collector exporters to export metrics and traces to telemetry backends instead of using the Dapr exporter components. Until now, Dapr exporter components were necessary to emit traces. From the next release, we will remove the Dapr exporter components and instead leverage Open Telemetry collector to emit traces to telemetry backend monitoring tools. Additionally, you will be able to configure metric exporters as well as trace exporters.
All Dapr APIs can now be called on the Dapr sidecar before the app has responded on the app-port. For example, this enables the app to retrieve secrets before the app starts, enabling setting up JWT validation in an auth pipeline/middleware.
HTTP endpoints in your app can now be HTTPS endpoints, which previously were blocked. If your app is listening on HTTPS or has a gRPC TLS configuration enabled, use the
app-sslflag like this. This will have Dapr invoke the app over an insecure SSL channel.
dapr run --app-id nodeapp --app-port 3000 node app.js --app-ssl
Published service invocation API performance numbers for the v0.11.3 release which will be updated with each future release.
The CLI component command
dapr components -know shows version information.
See a detailed description of changes, fixes and new features in the Dapr v1.0.0-rc.1 release notes. As with every release, please pay careful attention to the breaking changes section.
We hope you try out this release candidate and raise issues on GitHub as well as reach out to us to ask questions on Gitter or via Twitter - just give us your thoughts, we’d love to hear from you!