docs/release_notes/v1.11.0.md
We're happy to announce the release of Dapr 1.11!
We would like to extend our thanks to all the new and existing contributors who helped make this release happen.
If you're new to Dapr, visit the getting started page and familiarize yourself with Dapr.
Docs have been updated with all the new features and changes of this release. To get started with new capabilities introduced in this release, go to the Concepts and the Developing applications pages.
Note: This release contains a few breaking changes.
See the upgrading section for instructions on upgrading Dapr to version 1.11.
If upgrading to v1.11.0 with the Dapr CLI, make sure you're using the latest v1.11.0 version of the CLI. Older versions of the CLI cannot upgrade to the v1.11.0 runtime version.
Thanks to everyone who made this release possible!
@AaronCrawfis, @abhi314e, @abossard, @AdamKorcz, @addjuarez, @alicejgibbons, @artursouza, @ASHIQUEMD, @berndverst, @binnn6, @bruth, @cciobanu98, @cgillum, @champel, @cmoulliard, @codefromthecrypt, @DeepanshuA, @dmutterSF, @drewby, @ehalsey, @fernandosmither, @filintod, @Flern, @gaofeihang, @greenie-msft, @handlerww, @hhunter-ms, @HiltonGiesenow, @hunter007, @iamnicoj, @ItalyPaleAle, @jackycsl, @JaimeStill, @JaydipGabani, @jjcollinge, @JoshVanL, @Juneezee, @k0da, @KarlisAG, @kayayarai, @kubemq, @kushalnl7, @LaurenceLiZhixin, @leepa, @letmerecall, @liu-song, @louisquach, @macel94, @MatejNedic, @matzew, @mcandeia, @mdarii, @MregXN, @msfussell, @mukundansundar, @naah69, @NickLarsenNZ, @nponraj, @nyemade-uversky, @obenarchid, @owainow, @owenchenxy, @ParrySMS, @paulyuk, @philliphoff, @pimmerks, @pravinpushkar, @riverar, @robertojrojas, @rosdi, @RyanLettieri, @ryou90, @sab-codes, @salmankhan-prs, @sarsharma, @serpentfabric, @shivamkm07, @shivanisinghnitp, @shubham1172, @sicoyle, @SoTrx, @SpikeWong, @stuartleeks, @sunzhaochang, @Taction, @taenyang, @tanopanta, @tharun634, @thombrn, @ThorstenHans, @tianyax, @timcallaghan, @tmacam, @tomkerkhove,@tottoto, @Vishal07051999, @wolvever, @worming004, @wralith, @XavierGeerinck, @xclayl, @yaron2, @yash-nisar, @ZhangSetSail
These are the v1.11 release highlights:
instanceID is now supplied as a query parameter when starting a workflow You can read more on the workflow APIs herestablecomponents tag.The Dapr dashboard is no longer installed by default with the Dapr control plane when installing via Helm. To install the dashboard, use the new dapr-dashboard chart:
helm repo add dapr https://dapr.github.io/helm-charts/
helm repo update
kubectl create namespace dapr-system
helm install dapr dapr/dapr-dashboard --namespace dapr-system
When using dapr init or dapr init -k with Dapr CLI, the Dapr Dashboard is still installed. On Kubernetes, it will automatically use the new dapr-dashboard Helm chart.
Dapr 1.11 offers container images for Windows Server 2022, using the windows-ltsc2022 tag. This is in addition to the images based on Windows Server 1809.
In Dapr 1.11, the CLI flag --app-protocol can now assume 3 more values in addition to http and grpc:
https and grpcs use HTTP and gRPC, respectively, but enable TLS.
Note: With Dapr 1.11, using
--app-protocol=httpsand--app-protocol=grpcsis preferred to the previous option of setting--app-ssl=true(which is still supported but considered deprecated).
h2c is a new value that configures Dapr to connect to your app using HTTP/2 Cleartext.
Using HTTP/2 (including HTTP/2 Cleartext) can offer noticeable performance benefits when Dapr communicates with your app. It requires your app to expose a HTTP/2-capable server.
dapr run -f .A new preview feature enables a TTL on actor state which enables you to have the state automatically removed after a certain time
The following features are now stable, having been in preview for at least 2 releases.
/healthz 6217There are now over 100+ components in Dapr (115 in total). New components added in this release:
Starting with Dapr 1.11, support for authenticating with Azure AD has been added to these components:
Additionally, all Azure components that support Azure AD now support authentication using:
This release focused on preparing more components for beta and stable designation. This means certification tests are added and quality issues are addressed. Read component certification lifecycle for details.
The following components are now stable
The following components that were deprecated in a previous version of Dapr have been removed from Dapr 1.11:
dapr-ext-workflow 559--app-channel-address flag, you can instruct Dapr to send all events to the configured addressdapr run --resources-path ./mycomponents --resources-path ./mysubscriptionsThe following new Quickstarts have been added
If you're new to Dapr, visit the getting started page and familiarize yourself with Dapr.
Docs have been updated with all the new features and changes of this release. To get started with new capabilities introduced in this release, go to the Concepts and the Developing applications.
Note: This release contains a few breaking changes.
See this section on upgrading Dapr to version 1.11.0.
stablecomponents and allcomponents 3168 6465dapr.io/sidecar-injected and dapr.io/app-id when Dapr sidecar is injected 4366 6275dapr Helm chart to a new dapr-dashboard chart 4724--resources-path flags on daprd 5909seccompProfile in Dapr sidecar via injector 5916# character (Workflows not working with Cosmos DB) 6156 6294OTEL_EXPORTER_OTLP_ENDPOINT env var 6176https and h2c to app-protocol for better HTTP/2 support, and deprecate app-ssl 6205actorStateStore and keyPrefix 6206/healthz) 6217dapr_http_server_response_count metric 6312dapr-http-max-request-size now applies to gRPC proxying too 6349 6353reinvocationPolicy: IfNeeded to Dapr Sidecar injector 6350name property to run file 1204DAPR_CONTAINER_RUNTIME env in addition to --container-runtime arg. 1210--resources-path flags 1216dapr run -f 1238~ does not resolve to home folder in in dapr run -f 1245app-protocol, including HTTP/2 Cleartext, and deprecate app-ssl 1267httpendpoint resource on dapr init -k 1285WorkflowEngineClient to DaprWorkflowClient and added additional APIs. 1053NewService 400dapr.aio.clients.DaprClient) 90dapr-ext-workflow 559createHTTPMetadataQueryParam in favor of createHTTPQueryParam 479To upgrade to this release of Dapr, follow the steps here to ensure a smooth upgrade. You know, the one where you don't get red errors on the terminal.. we all hate that, right?
Uninstall Dapr using the CLI you currently have installed. Note that this will remove the default $HOME/.dapr directory, binaries and all containers dapr_redis, dapr_placement and dapr_zipkin. Linux users need to run sudo if docker command needs sudo:
dapr uninstall --all
For RC releases like this, download the latest and greatest release from here and put the dapr binary in your PATH.
Once you have installed the CLI, run:
dapr init --runtime-version=1.11
Wait for the update to finish, ensure you are using the latest version of Dapr(1.11) with:
$ dapr --version
CLI version: 1.11
Runtime version: 1.11
You can perform zero-downtime upgrades using both Helm 3 and the Dapr CLI.
Download the latest RC release from here and put the dapr binary in your PATH.
To upgrade Dapr, run:
dapr upgrade --runtime-version 1.11 -k
To upgrade with high availability mode:
dapr upgrade --runtime-version 1.11 --enable-ha=true -k
Wait until the operation is finished and check your status with dapr status -k.
All done!
Note: Make sure your deployments are restarted to pick the latest version of the Dapr sidecar
To upgrade Dapr using Helm, run:
helm repo add dapr https://dapr.github.io/helm-charts/
helm repo update
helm upgrade dapr dapr/dapr --version 1.11 --namespace=dapr-system --wait
Wait until the operation is finished and check your status with dapr status -k.
All done!
Note: Make sure your deployments are restarted to pick the latest version of the Dapr sidecar
Please see how to deploy Dapr on a Kubernetes cluster for a complete guide to installing Dapr on Kubernetes
You can use Helm 3 to install Dapr:
helm repo add dapr https://dapr.github.io/helm-charts/
helm repo update
kubectl create namespace dapr-system
helm install dapr dapr/dapr --version 1.11 --namespace dapr-system --wait
Alternatively, you can use the latest version of CLI:
dapr init --runtime-version=1.11 -k
Verify the control plane pods are running and are healthy:
$ dapr status -k
NAME NAMESPACE HEALTHY STATUS REPLICAS VERSION AGE CREATED
dapr-sidecar-injector dapr-system True Running 1 1.11 15s 2023-06-02 13:07.39
dapr-sentry dapr-system True Running 1 1.11 15s 2023-06-02 13:07.39
dapr-operator dapr-system True Running 1 1.11 15s 2023-06-02 13:07.39
dapr-placement dapr-system True Running 1 1.11 15s 2023-06-02 13:07.39
After Dapr 1.11 has been installed, perform a rolling restart for your deployments to pick up the new version of the sidecar. This can be done with:
kubectl rollout restart deploy/<deployment-name>
/healthz. The old path /health can still be used if configured explicitly. 6225The following components have been removed from Dapr 1.11 (2597):
WorkflowEngineClient to DaprWorkflowClient and added additional APIs. 1053--app-ssl (in both the Dapr CLI and daprd) has been deprecated in favor of using --app-protocol with values https or grpcs. daprd:6158 cli:1267