docs/release_notes/v1.1.0.md
We're happy to announce the release of Dapr 1.1.0!
We would like to extend our thanks to all the new and existing contributors who helped make this release happen.
Highlights
shutdown API to stop sidecar from app 2689If 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.
See this section on upgrading Dapr to version 1.1.0.
Thanks to everyone who made this release possible!
@1046102779, @Betula-L, @Hugome, @PeterGerrard, @SamuelMcAravey, @Taction, @artursouza, @dinggh, @halspang, @hnlq715, @jigargandhi, @ksivamuthu, @liamgib, @luckyxiaoqiang, @lynn-orrell, @moonchanyong, @mukundansundar, @orizohar, @pkedy, @puzpuzpuz, @rynowak, @springe2004, @tcnghia, @trondhindenes, @wcs1only, @withinboredom, @yaron2
role-tokenreview-binding (used by Vault) cluster role binding 2651--wait flag for init and upgrade commands 597dapr upgrade 622eTag support for MongoDB state store 726byte[] value in CosmoDB state component 745To 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 releases like this, download the latest and greatest release from here and put the dapr binary in your PATH. Alternatively, follow these instructions to get the latest CLI.
Once you have installed the CLI, run:
dapr init --runtime-version=1.1.0
Wait for the update to finish, ensure you are using the latest version of Dapr(1.1.0) with:
$ dapr --version
CLI version: 1.1.0
Runtime version: 1.1.0
You can perform zero-downtime upgrades using both Helm 3 and the Dapr CLI.
Download the latest CLI release from here and put the dapr binary in your PATH.
Alternatively, follow these instructions to get the latest CLI.
To upgrade Dapr, run:
dapr upgrade --runtime-version 1.1.0 -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
There is a known issue running upgrades on clusters that may have previously had a version prior to 1.0.0-rc.2 installed on a cluster.
Most users should not encounter this issue, but there are a few upgrade path edge cases that may leave an incompatible CustomResourceDefinition installed on your cluster. The error message for this case looks like this:
❌ Failed to upgrade Dapr: Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
The CustomResourceDefinition "configurations.dapr.io" is invalid: spec.preserveUnknownFields: Invalid value: true: must be false in order to use defaults in the schema
To resolve this issue please run the follow command to upgrade the CustomResourceDefinition to a compatible version:
kubectl replace -f https://raw.githubusercontent.com/dapr/dapr/5a15b3e0f093d2d0938b12f144c7047474a290fe/charts/dapr/crds/configuration.yaml
Then proceed with the dapr upgrade --runtime-version 1.1.0 -k command as above.
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.1.0 --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
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.1.0 --namespace dapr-system --wait
Alternatively, you can use the latest version of CLI:
dapr init --runtime-version=1.1.0 -k
Verify the control plane pods are running and are healthy:
$ dapr status -k
NAME NAMESPACE HEALTHY STATUS REPLICAS VERSION AGE CREATED
dapr-dashboard dapr-system True Running 1 0.6.0 15s 2021-03-31 13:07.39
dapr-sidecar-injector dapr-system True Running 1 1.1.0 15s 2021-03-31 13:07.39
dapr-sentry dapr-system True Running 1 1.1.0 15s 2021-03-31 13:07.39
dapr-operator dapr-system True Running 1 1.1.0 15s 2021-03-31 13:07.39
dapr-placement dapr-system True Running 1 1.1.0 15s 2021-03-31 13:07.39
After Dapr 1.1.0 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>
None.