docs/release_notes/v1.0.0.md
We're excited to announce the release of Dapr 1.0.0! ππππ ππππ
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.
See this section on installing/upgrading Dapr to version 1.0.0.
For a list of all changes since 0.11 release, refer to the release notes from the release candidates:
For Java applications using Dapr Java SDK, use SDK version 1.0.0. See upgrade instructions for the Java SDK.
For .Net applications using Dapr .Net SDK, use SDK version 1.0.0. See upgrade instructions for the .Net SDK.
Thanks to everyone who made this release possible!
@AaronCrawfis, @1046102779, @abserari, @alpha-baby, @alydersen, @ajaysingh77, @arghya88, @artursouza, @beiwei30, @Betula-L, @bvwells, @cilerler, @cmendible, @cvictory, @DarqueWarrior, @darren-wang, @davidkarlsen, @discostu105, @dylandee, @eibrunorodrigues, @eNeRGy164, @fjvela, @gaoxinge, @georgestevens99, @halspang, @harrykimpel, @hepin1989, @IroNEDR, @issacg, @jdubois, @jigargandhi, @jjcollinge, @juazasan, @karishma-chawla, @karoldeland, @kendallroden, @kevgo, @ksivamuthu, @kzmake, @Li-Yanzhi, @mchmarny, @mfcollins3, @msfussell, @mrchypark, @mukundansundar, @newbe36524, @orizohar, @PeterGerrard, @Phiph, @pkedy, @ProfessorMc, @Qalifah, @rrylee, @rynowak, @sau-lanvy, @shubham1172, @skyao, @soiboxauxi, @tcnghia, @TenSt, @tianvan, @tomkerkhove, @trondhindenes, @tylermurry, @vinayada1, @wcs1only, @withinboredom, @wjayesh, @XavierGeerinck, @xiazuojie, @yaron2, @Yggdrasill-7C9, @youngbupark, @wwulfric, @ZeyadYasser, @zzxwill
https or has a gRPC TLS configuration enabled, use the app-ssl flag 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-ssldapr components -k now shows version information for each component.ignoreErrors field.{uuid} markerdata_base64 attribute when wrapping pubsub payload as CloudEvent. 2612To 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
Next, follow these instructions to install the latest CLI version, or alternatively 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
Wait for the update to finish, ensure you are using the latest version of Dapr(1.0.0) with:
$ dapr --version
CLI version: 1.0.0
Runtime version: 1.0.0
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.0.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
Note: If upgrading from Dapr 0.11.x, use the CLI to upgrade
To upgrade Dapr using Helm, run:
helm repo add dapr https://dapr.github.io/helm-charts/
helm repo update
helm upgrade dapr dapr/dapr --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
helm install dapr dapr/dapr --create-namespace=true --namespace dapr-system --wait
Alternatively, you can use the latest version of CLI:
dapr init -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-02-14 13:07.39
dapr-sidecar-injector dapr-system True Running 1 1.0.0 15s 2021-02-14 13:07.39
dapr-sentry dapr-system True Running 1 1.0.0 15s 2021-02-14 13:07.39
dapr-operator dapr-system True Running 1 1.0.0 15s 2021-02-14 13:07.39
dapr-placement dapr-system True Running 1 1.0.0 15s 2021-02-14 13:07.39
After Dapr 1.0.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>