docs/release_notes/v1.2.0.md
We're happy to announce the release of Dapr 1.2.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, visit the getting started page and familiarize yourself with Dapr.
For more information on the features listed above watch the Dapr Community Call #38 and the upcoming Community call #39
See this section on upgrading Dapr to version 1.2.0.
The GET /v1.0/shutdown HTTP API is deprecated and scheduled for removal in 1.4. All users who have directly integrated with this API should use the POST /v1.0/shutdown API instead. If you are using one of the supported Dapr SDKs you do not need to take any action.
See https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-job/ for an example usage of this API.
Thanks to everyone who made this release possible!
@0to1, @1046102779, @AaronCrawfis, @DarqueWarrior, @EdwinVW, @Hugome, @JoeMayo, @Junnplus, @Taction, @TomorJM, @a-elsheikh, @abogdanov37, @akkie, @apuzyrevsky, @artursouza, @beiwei30, @berndverst, @cinience, @fjvela, @halspang, @jigargandhi, @jjcollinge, @jony4, @luckyxiaoqiang, @marviniter, @msfussell, @mukundansundar, @newbe36524, @pkedy, @readefries, @wcs1only, @withinboredom, @xiazuojie, @yanjianlong, @yaron2, @zhongfox
daprd process on error when dapr run is called 645run detects shutdown API call and exits as expected 654dapr upgrade on a cluster with MTLS disabled 664--dapr-http-max-request-size parameter to CLI 699go mod tidy before make 799--data-file flags for invoke and publish 1391--dapr-http-max-request-size flags for run 1481dapr/dapr to dapr/kit 1To 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 stable 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.2.0
Wait for the update to finish, ensure you are using the latest version of Dapr(1.2.0) with:
$ dapr --version
CLI version: 1.2.0
Runtime version: 1.2.0
You can perform zero-downtime upgrades using both Helm 3 and the Dapr CLI.
Download the latest stable release from here and put the dapr binary in your PATH.
To upgrade Dapr, run:
dapr upgrade --runtime-version 1.2.0 -k
To upgrade with high availability mode:
dapr upgrade --runtime-version 1.2.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.2.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 Deploying 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.2.0 --namespace dapr-system --wait
Alternatively, you can use the latest version of CLI:
dapr init --runtime-version=1.2.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-05-20 13:07.39
dapr-sidecar-injector dapr-system True Running 1 1.2.0 15s 2021-05-20 13:07.39
dapr-sentry dapr-system True Running 1 1.2.0 15s 2021-05-20 13:07.39
dapr-operator dapr-system True Running 1 1.2.0 15s 2021-05-20 13:07.39
dapr-placement dapr-system True Running 1 1.2.0 15s 2021-05-20 13:07.39
After Dapr 1.2.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.