Adds Etcdv2

daprdocs/content/en/reference/api/actors_api.md

@@ -77,7 +77,7 @@ Persists the change to the state for an actor as a multi-item transaction.
 
 #### TTL
 
-With the [`ActorStateTTL` feature enabled]]({{< ref
+With the [`ActorStateTTL` feature enabled]({{< ref
 "support-preview-features.md" >}}), actor clients can set the `ttlInSeconds`
 field in the transaction metadata to have the state expire after that many
 seconds. If the `ttlInSeconds` field is not set, the state will not expire.

daprdocs/content/en/reference/components-reference/supported-state-stores/setup-etcd.md

@@ -18,7 +18,9 @@ metadata:
   name: <NAME>
 spec:
   type: state.etcd
-  version: v1
+  # Supports v1 and v2. Users should always use v2 by default. There is no
+  # migration path from v1 to v2, see `versioning` below.
+  version: v2
   metadata:
   - name: endpoints
     value: <CONNECTION STRING> # Required. Example: 192.168.0.1:2379,192.168.0.2:2379,192.168.0.3:2379
@@ -38,6 +40,15 @@ spec:
 The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described [here]({{< ref component-secrets.md >}}).
 {{% /alert %}}
 
+
+### Versioning
+
+Dapr has 2 versions of the Etcd state store component: `v1` and `v2`. It is recommended to use `v2`, as `v1` is deprecated.
+
+While `v1` and `v2` have the same metadata fields, `v1` causes data inconsistencies in apps when using [Actor TTLs]({{< ref "actors_api.md#ttl" >}}) from Dapr v1.12.
+`v1` and `v2` are incompatible with no data migration path for `v1` to `v2` on an existing active Etcd cluster and `keyPrefixPath`.
+If you are using `v1`, you should continue to use `v1` until you create a new Etcd cluster or use a different `keyPrefixPath`.
+
 ## Spec metadata fields
 
 | Field              | Required | Details | Example |