Merge pull request #174254 from nshankar13/nshankar/OSM_AKS_Addon_CLI_config_single_mesh

Update OSM AKS addon documentation

Author: v-albemi

articles/aks/TOC.yml

@@ -388,6 +388,8 @@
                   href: open-service-mesh-nginx-ingress.md
                 - name: Configure observability using Prometheus, Grafana, and Jaeger
                   href: open-service-mesh-open-source-observability.md
+                - name: Customize OSM CLI experience
+                  href: open-service-mesh-customize-add-on-experience.md
             - name: Configure Azure Monitor
               href: open-service-mesh-azure-monitor.md
             - name: Troubleshoot OSM

articles/aks/open-service-mesh-binary.md

@@ -33,4 +33,7 @@ This article will discuss how to download the OSM client library to be used to o
 ::: zone-end
 
 > [!WARNING]
-> Do not attempt to install OSM from the binary using `osm install`. This will result in a installation of OSM that is not integrated as an add-on for AKS.
+> Do not attempt to install OSM from the binary using `osm install`. This will result in a installation of OSM that is not integrated as an add-on for AKS.
+
+> [!NOTE]
+> It is recommended to configure the OSM CLI to [customize the OSM AKS addon experience](/open-service-mesh-customize-addon-experience.md) after installing the binary, before using the OSM CLI. 

articles/aks/open-service-mesh-customize-add-on-experience.md

@@ -0,0 +1,36 @@
+---
+title: Customize OSM CLI experience
+description: Customize OSM CLI experience with an osmconfig file. 
+services: container-service
+ms.topic: article
+ms.date: 9/30/2021
+ms.custom: mvc, devx-track-azurecli
+ms.author: nshankar
+zone_pivot_groups: client-operating-system
+---
+
+# Configure OSM CLI variables with an OSM_CONFIG file
+
+Users can override the default OSM CLI configuration to enhance the add-on experience. This can be done by creating a config file, similar to `kubeconfig`. The config file can be either created at `$HOME/.osm/config.yaml`, or at a different path that is exported using the `OSM_CONFIG` environment variable.
+
+The file must contain the following YAML formatted content:
+
+```yaml
+install:
+  kind: managed
+  distribution: AKS
+  namespace: kube-system
+```
+
+If the file is not created at `$HOME/.osm/config.yaml`, remember to set the `OSM_CONFIG` environment variable to point to the path where the config file is created.
+
+After setting OSM_CONFIG, the output of the `osm env` command should be the following: 
+
+```console
+$ osm env
+--- 
+install:
+  kind: managed
+  distribution: AKS
+  namespace: kube-system
+```

articles/aks/open-service-mesh-deploy-new-application.md

@@ -415,4 +415,4 @@ trafficsplit.split.smi-spec.io/bookstore-split created
 
 Set up a port forward tunnel to the `bookbuyer` pod and you should now see books being purchased from the `bookstore` v2 service. If you continue to watch the increment of purchases, you should notice a faster increment of purchases happening through the `bookstore` v2 service.
 
-![OSM bookbuyer books boough UI](./media/aks-osm-addon/osm-bookbuyer-traffic-split-ui.png)
+![OSM bookbuyer books bought UI](./media/aks-osm-addon/osm-bookbuyer-traffic-split-ui.png)

articles/aks/open-service-mesh-troubleshoot.md

@@ -447,4 +447,8 @@ kubectl apply -f https://raw.githubusercontent.com/openservicemesh/osm/v0.8.2/ch
 
 ### Certificate management
 
-Information on how to issue and manage certificates to Envoy proxy via the OSM control plane can be found on the [OpenServiceMesh docs site](https://docs.openservicemesh.io/docs/guides/certificates/).
+Information on how OSM issues and manages certificates to Envoy proxies running on application pods can be found on the [OpenServiceMesh docs site](https://docs.openservicemesh.io/docs/guides/certificates/).
+
+### Upgrading Envoy
+
+When a new pod is created in a namespace monitored by the add-on, OSM will inject an [envoy proxy sidecar](https://docs.openservicemesh.io/docs/guides/app_onboarding/sidecar_injection/) in that pod. Information regarding how to update the envoy version can be found in the [Upgrade Guide](https://docs.openservicemesh.io/docs/getting_started/upgrade/#envoy) on the OpenServiceMesh docs site.