Merge pull request #176959 from nshankar13/nshankar/OSM_AKS_add_on_observability_single_mesh

Fix OSM add-on docs for observability, single mesh

Author: PRMerger10

articles/aks/open-service-mesh-deploy-addon-az-cli.md

@@ -93,6 +93,9 @@ For an existing AKS cluster scenario, you will enable the OSM add-on to an exist
 
 To enable the AKS OSM add-on, you will need to run the `az aks enable-addons --addons` command passing the parameter `open-service-mesh`
 
+> [!NOTE]
+> For the OSM add-on deployment to succeed, only one OSM mesh instance should be deployed on your cluster. If you have other OSM mesh instances on your cluster, please uninstall them before running the `enable-addons` command. 
+
 ```azurecli-interactive
 az aks enable-addons --addons open-service-mesh -g <my-osm-aks-cluster-rg> -n <my-osm-aks-cluster-name>
 ```

articles/aks/open-service-mesh-open-source-observability.md

@@ -459,7 +459,7 @@ On the **Configure your Prometheus data source below** page, enter the Kubernete
 
 OSM Dashboards are available both through:
 
-- [Our repository](https://github.com/grafana/grafana), and are importable as json blobs through the web admin portal
+- [Our repository](https://github.com/openservicemesh/osm/tree/release-v0.11/charts/osm/grafana/dashboards), and are importable as json blobs through the web admin portal
 - or [online at Grafana.com](https://grafana.com/grafana/dashboards/14145)
 
 To import a dashboard, look for the `+` sign on the left menu and select `import`.
@@ -477,6 +477,12 @@ As soon as you select import, it will bring you automatically to your imported d
 
 ### Deploy Jaeger to the AKS cluster
 
+First, create a jaeger namespace:
+
+```azurecli-interactive
+kubectl create namespace jaeger
+```
+
 Apply the following manifest to install Jaeger:
 
 ```azurecli-interactive
@@ -538,14 +544,50 @@ deployment.apps/jaeger created
 service/jaeger created
 ```
 
+### Add RBAC for Jaeger SA
+
+Apply the following RBAC to grant the Jaeger Service Account the specified Cluster Role:
+
+```yaml
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  labels:
+    app: jaeger
+  name: jaeger
+  namespace: jaeger
+---
+kind: ClusterRole
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  labels:
+    app: jaeger
+  name: jaeger
+---
+kind: ClusterRoleBinding
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  name: jaeger
+  labels:
+    app: jaeger
+subjects:
+  - kind: ServiceAccount
+    name: jaeger
+    namespace: jaeger
+roleRef:
+  kind: ClusterRole
+  name: jaeger
+  apiGroup: rbac.authorization.k8s.io
+```
+
 ### Enable Tracing for the OSM add-on
 
 Next we will need to enable tracing for the OSM add-on.
 
 Run the following command to enable tracing for the OSM add-on:
 
 ```azurecli-interactive
-kubectl patch meshconfig osm-mesh-config -n kube-system -p '{"spec":{"observability":{"tracing":{"enable":true}}}}' --type=merge
+kubectl patch meshconfig osm-mesh-config -n kube-system -p '{"spec":{"observability":{"tracing":{"enable":true, "address": "jaeger.jaeger.svc.cluster.local"}}}}' --type=merge
 ```
 
 ```Output