openshift · kalexand-rh · Oct 30, 2018 · Oct 23, 2018
diff --git a/servicemesh-release-notes/servicemesh-release-notes.adoc b/servicemesh-release-notes/servicemesh-release-notes.adoc
@@ -29,12 +29,11 @@ include::servicemesh-release-notes/topics/rn-technology-preview.adoc[leveloffset
 ////
 
 [[RN_resolved_issues]]
-== Resolved Issues
+== Resolved issues
 
 include::servicemesh-release-notes/topics/rn-fixed-issues.adoc[leveloffset=+2]
 
 [[RN_known_issues]]
 == Known issues
 
 include::servicemesh-release-notes/topics/rn-known-issues.adoc[leveloffset=+2]
-
diff --git a/servicemesh-release-notes/topics/document-attributes.adoc b/servicemesh-release-notes/topics/document-attributes.adoc
@@ -13,7 +13,7 @@
 :ProductName: Red Hat OpenShift Service Mesh
 :ProductShortName: the Service Mesh
 :ProductRelease:
-:ProductVersion: 0.2.TechPreview
+:ProductVersion: 0.3.TechPreview
 :product-build:
 :DownloadURL: registry.access.redhat.com
 //
@@ -34,4 +34,3 @@
 :Install_BookName: Installing Red Hat OpenShift Service Mesh
 :Using_BookName: Using Red Hat OpenShift Service Mesh
 :RN_BookName: Red Hat OpenShift Service Mesh  Release Notes
-
diff --git a/servicemesh-release-notes/topics/rn-fixed-issues.adoc b/servicemesh-release-notes/topics/rn-fixed-issues.adoc
@@ -9,3 +9,13 @@ Result - How has the behavior changed as a result?  Try to avoid “It is fixed
 ////
 
 https://github.com/Maistra/openshift-ansible/pull/19/[MASITRA-21] -  The default in the installer of 512Mi was too low for tracing.  Increased default Elasticsearch memory from 512 MB to 1GB.
+
+https://issues.jboss.org/browse/MAISTRA-4[MAISTRA-4] - The uninstall does not remove all the files, and as a result, when you re-install the istio-operator installation fails because `customresourcedefinitions.apiextensions.k8s.io "installations.istio.openshift.com"` already exists.
+
+https://issues.jboss.org/browse/MAISTRA-5[MAISTRA-5] - `openshift-ansible-istio-installer-job` pod tries to start but with errors.
+Graph layout - The layout for the Kiali graph can render differently, depending on your application architecture and the data to display (number of graph nodes and their interactions).  Because it is difficult if not impossible to create a single layout that renders nicely for every situation, Kiali offers a choice of several different layouts.  To choose a different layout, you can choose a different *Layout Schema* from the *Graph Settings* menu.
+
+https://issues.jboss.org/browse/MAISTRA-13[MAISTRA-13] - Installer should determine release version from installed components.  At present, the installer queries the yaml file, however if the yaml has been modified, the installer is not able to remove an older version.
+
+https://issues.jboss.org/browse/KIALI-1572[KIALI-1572]
+If you see this ERROR message when you view the Kiali logs, you can ignore it: `Failed to determine console version from file [/opt/kiali/console/version.txt]. error=open /opt/kiali/console/version.txt: no such file or directory Kiali: Console version: unknown`
diff --git a/servicemesh-release-notes/topics/rn-known-issues.adoc b/servicemesh-release-notes/topics/rn-known-issues.adoc
@@ -28,50 +28,14 @@ https://github.com/istio/old_issues_repo/issues/115
 ////
 * The istio-init container requires a privileged security context or at least to run as root and to have the NET_ADMIN capability.  The istio-init container needs to be privileged because it needs to properly configure the iptables rules in the pod in order to intercept network connections.  The team is currently investigating ideas for ways to reduce the privileges required by Istio.
 
-https://issues.jboss.org/browse/MAISTRA-4[MAISTRA-4] - The uninstall does not remove all the files, and as a result, when you re-install the istio-operator installation fails because `customresourcedefinitions.apiextensions.k8s.io "installations.istio.openshift.com"` already exists.
+https://issues.jboss.org/browse/MAISTRA-62[MAISTRA-62] After a successful Istio installation, when upgrading an OCP cluster from 3.10 to 3.11, the storage upgrade task fails causing the entire upgrade process to fail.
 
-*Workaround* - In order to cleanly remove the operator execute the following command:
-```
-oc process -f istio_product_operator_template.yaml | oc delete -f -
-```
-
-https://issues.jboss.org/browse/MAISTRA-5[MAISTRA-5] - `openshift-ansible-istio-installer-job` pod tries to start but with errors.
-
-Graph layout - The layout for the Kiali graph can render differently, depending on your application architecture and the data to display (number of graph nodes and their interactions).  Because it is difficult if not impossible to create a single layout that renders nicely for every situation, Kiali offers a choice of several different layouts.  To choose a different layout, you can choose a different *Layout Schema* from the *Graph Settings* menu.
-
-https://issues.jboss.org/browse/MAISTRA-13[MAISTRA-13] - Installer should determine release version from installed components.  At present, the installer queries the yaml file, however if the yaml has been modified, the installer is not able to remove an older version.
-
-*Workaround* - If the installation fails because of a previous, older installation, then use the following workaround:
-
-```
-$ oc delete namespace devex istio-operator istio-system bookinfo logging foo bar
-
-$ oc delete csr istio-sidecar-injector.istio-system
-
-$ oc get crd  | grep istio | awk '{print $1}' | xargs oc delete crd
-
-$ oc get mutatingwebhookconfigurations  | grep istio | awk '{print $1}' | xargs oc delete mutatingwebhookconfigurations
-
-$ oc get validatingwebhookconfiguration  | grep istio | awk '{print $1}' | xargs oc delete validatingwebhookconfiguration
-
-$ oc get clusterroles  | grep istio | awk '{print $1}' | xargs oc delete clusterroles
-
-$ oc get clusterroles  | grep kiali | awk '{print $1}' | xargs oc delete clusterroles
-
-$ oc get clusterrolebindings  | grep istio | awk '{print $1}' | xargs oc delete clusterrolebindings
-
-$ oc get clusterrolebindings  | grep kiali | awk '{print $1}' | xargs oc delete clusterrolebindings
-```
-
-https://github.com/kiali/kiali/issues/507[Kiali-507] Kiali does not support Internet Explorer 11.  This is because the underlying frameworks do not support Internet Explorer.  In order to access the Kiali console, use one of the two most recent versions of the Chrome, Edge, Firefox or Safari browser.
+https://github.com/kiali/kiali/issues/507[KIALI-507] Kiali does not support Internet Explorer 11.  This is because the underlying frameworks do not support Internet Explorer.  In order to access the Kiali console, use one of the two most recent versions of the Chrome, Edge, Firefox or Safari browser.
 
 https://issues.jboss.org/browse/KIALI-1284[KIALI-1284] In Istio, a Workload can be any pod or group of pods, regardless where they originate from. They may come from Kubernetes Deployments, Replica Sets or even as a single "orphan" pod. In Kiali the current assumption is that a Workload comes from a Deployment. This should represent the vast majority of the cases.
 
 https://issues.jboss.org/browse/KIALI-1570[KIALI-1570]
 When a graph is loading in the Kiali console, a message that the graph is empty is displayed instead of a message that the graph is loading.
 
-https://issues.jboss.org/browse/KIALI-1572[KIALI-1572]
-If you see this ERROR message when you view the Kiali logs, you can ignore it: `Failed to determine console version from file [/opt/kiali/console/version.txt]. error=open /opt/kiali/console/version.txt: no such file or directory Kiali: Console version: unknown`
-
 https://issues.jboss.org/browse/KIALI-1609[KIALI-1609]
 When dealing with very small values (for example, less than 0.0.1 rps) you might encounter some inconsistencies in the graph. We are working on making changes to have this function better when dealing with very small values.
diff --git a/servicemesh-release-notes/topics/rn-new-features.adoc b/servicemesh-release-notes/topics/rn-new-features.adoc
@@ -5,6 +5,10 @@ Feature – Describe the new functionality available to the customer.  For enhan
 Reason – If known, include why has the enhancement been implemented (use case, performance, technology, etc.).   For example, showcases integration of X with Y, demonstrates Z API feature, includes latest framework bug fixes.  There may not have been a 'problem' previously, but system behaviour may have changed.
 Result – If changed, describe the current user experience
 ////
+= New features Technology Preview 3
+
+The release of {ProductName} adds support for OpenShift 3.11, support for Kiali 0.8.x, and an updated base Ansible installer (3.11.16-3).
+
 = New features Technology Preview 2
 
 The release adds the  Kiali observability console to  {ProductName}.  Kiali provides a number of graphs that you can use to view the topography and health of the microservices that make up your service mesh.   You can view predefined dashboards that provide detailed request and response metrics (volume, duration, size, TCP traffic) per inbound and outbound traffic.  You can also browse your service mesh by application, workloads, and services to view the health of each element.
@@ -16,4 +20,3 @@ The release adds the  Kiali observability console to  {ProductName}.  Kiali prov
 * *Service Identity and Security* - Provide services in the mesh with a verifiable identity and provide the ability to protect service traffic as it flows over networks of varying degrees of trustworthiness.
 * *Policy Enforcement* - Apply organizational policy to the interaction between services, ensure access policies are enforced and resources are fairly distributed among consumers. Policy changes are made by configuring the mesh, not by changing application code.
 * *Telemetry* -  Gain understanding of the dependencies between services and the nature and flow of traffic between them, providing the ability to quickly identify issues.
-