docs/release_notes/v1.3.0.md
We're happy to announce the release of Dapr 1.3.0!
We would like to extend our thanks to all the new and existing contributors who helped make this release happen.
Highlights
If you’re new to Dapr, familiarize yourself by visiting the getting started page.
Note: This release contains breaking changes.
See this section on upgrading Dapr to version 1.3.0.
Thanks to everyone who made this release possible!
@1046102779, @AaronCrawfis, @akkie, @alvinhenrick, @amirmm11, @anhldbk, @artursouza, @Banchio, @beiwei30, @berndverst, @bjorkstromm, @caogj, @CodeMonkeyLeet, @CodingSinger, @daixiang0, @DanAbara, @DarqueWarrior, @delvh, @dmitsh, @emattiza, @eNeRGy164, @fabistb, @gogi2811, @greenie-msft, @halspang, @iamazy, @ItalyPaleAle, @jasonviviano, @jcdickinson, @jigargandhi, @Junnplus, @luckyxiaoqiang, @luiscantero, @marviniter, @msfussell, @mukundansundar, @orizohar, @pinxiong, @pkedy, @puzpuzpuz, @rovangju, @seeflood, @skyao, @stulzq, @Taction, @tanvigour, @tianjipeng, @tomkerkhove, @wcs1only, @withinboredom, @yaron2
--buildinfo 3341dapr buildinfo command to print commit id and other info 599dapr uninstall -k --all which also removes CRDs 656dapr init if Github API is unavailable 677dapr run --placement-host-address now supports specifying TCP port 705dapr list 728--enable-profiling and --app-ssl parameters not being properly passed to daprd768To 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.3.0
Wait for the update to finish, ensure you are using the latest version of Dapr(1.3.0) with:
$ dapr --version
CLI version: 1.3.0
Runtime version: 1.3.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.3.0 -k
To upgrade with high availability mode:
dapr upgrade --runtime-version 1.3.0 --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.3.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
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.3.0 --namespace dapr-system --wait
Alternatively, you can use the latest version of CLI:
dapr init --runtime-version=1.3.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.7.0 15s 2021-07-26 13:07.39
dapr-sidecar-injector dapr-system True Running 1 1.3.0 15s 2021-07-26 13:07.39
dapr-sentry dapr-system True Running 1 1.3.0 15s 2021-07-26 13:07.39
dapr-operator dapr-system True Running 1 1.3.0 15s 2021-07-26 13:07.39
dapr-placement dapr-system True Running 1 1.3.0 15s 2021-07-26 13:07.39
After Dapr 1.3.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>