fixed merge blocking issues

Author: Phill Gibson

.openpublishing.redirection.json

@@ -46503,6 +46503,16 @@
       "redirect_url": "/azure/aks/open-service-mesh-deploy-addon-az-cli",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "articles/aks/open-service-mesh-customize-add-on-experience.md",
+      "redirect_url": "/azure/aks/open-service-mesh-deploy-binary",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/aks/open-service-mesh-disable-add-on.md",
+      "redirect_url": "/azure/aks/open-service-mesh-deploy-addon-az-cli",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/iot-dps/quick-create-device-symmetric-key-csharp.md",
       "redirect_url": "/azure/iot-dps/quick-create-simulated-device-symm-key",

articles/aks/TOC.yml

@@ -386,6 +386,8 @@
                   href: open-service-mesh-deploy-new-application.md
                 - name: Manage an existing application deployment
                   href: open-service-mesh-deploy-existing-application.md
+                - name: Using Azure Application Gateway Ingress
+                  href: open-service-mesh-azure-application-gateway-ingress.md
                 - name: Using Kubernetes Nginx Ingress Controller
                   href: open-service-mesh-nginx-ingress.md
                 - name: Configure observability using Prometheus, Grafana, and Jaeger

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

@@ -57,7 +57,7 @@ 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. 
+> 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>
@@ -162,6 +162,14 @@ Notice the **enablePermissiveTrafficPolicyMode** is configured to **true**. Perm
 kubectl patch meshconfig osm-mesh-config -n kube-system -p '{"spec":{"traffic":{"enablePermissiveTrafficPolicyMode":true}}}' --type=merge
 ```
 
+## Disable Open Service Mesh (OSM) add-on for your AKS cluster
+
+To disable the OSM add-on, run the following command:
+
+```azurecli-interactive
+az aks disable-addons -n <AKS-cluster-name> -g <AKS-resource-group-name> -a open-service-mesh
+```
+
 <!-- Links -->
 <!-- Internal -->
 

articles/aks/open-service-mesh-nginx-ingress.md

@@ -169,7 +169,7 @@ service/bookwarehouse created
 deployment.apps/bookwarehouse created
 ```
 
-## Update the Bookbuyer Service
+## Update the Bookbuyer service
 
 Update the `bookbuyer` service to the correct inbound port configuration with the following service manifest.