Adding @yissachar's concerns in a new PR

docs/releases/1.6.0-alpha.1.md

@@ -6,8 +6,6 @@ made before release of kops 1.6.0.
 
 This is not a full set of release notes, but rather a summary of the highest impact changes in the 1.6 release:
 
-* kops is not yet recommending etcd3, pending issues such as HA upgrade support.
-
 * RBAC can be enabled by passing the `--authorization=rbac` parameter to `kops create cluster`,
 or via `kops edit cluster` and change `authorization` from `alwaysAllow: {}` to `rbac: {}`
 
@@ -16,7 +14,7 @@ service account method will be denied.
 
 * The taints & tolerations have changed as part of their graduation from alpha.  The taint is now a field on the node:
 
-```
+```yaml
 spec:
   taints:
   - effect: NoSchedule
@@ -25,7 +23,7 @@ spec:
 
 An example toleration (as used in dns-controller) is:
 
-```
+```yaml
 spec:
   tolerations:
   - effect: NoSchedule
@@ -40,7 +38,15 @@ and moved from an annotation to the field.
 the `node-role.kubernetes.io/<role>=` form is preferred.  `kubernetes.io/role=node` and `node-role.kubernetes.io/node=`
 are also present.
 
-* Rolling update to 1.6 does not succeed because new kube-dns pods mount a configmap with an optional volume map,
+Workaround: create the configmap with `kubectl create configmap -n kube-system kube-dns` before updating.
+
+## Known Issues
+
+##### Rolling updates
+
+Rolling update to 1.6 does not succeed because new kube-dns pods mount a configmap with an optional volume map,
 but that is enforced by the kubelets, which are upgraded after the master.
 
-Workaround: create the configmap with `kubectl create configmap -n kube-system kube-dns` before updating.
+##### etcd3
+
+`kops` is not yet recommending etcd3. We do however support a **run at your own risk** option. Right now we are working on resolving issues such as HA upgrade support.