Merge pull request #114676 from MS-jgol/retire-istio

change toc to retire old kubernetes doc

Author: ttorble

articles/azure-monitor/app/kubernetes.md

@@ -8,12 +8,11 @@ ms.date: 04/25/2019
 
 ---
 
-# Zero instrumentation application monitoring for Kubernetes hosted applications
+# Zero instrumentation application monitoring for Kubernetes hosted applications with Istio - DEPRECATED
 
 > [!IMPORTANT]
-> This functionality is currently in public preview.
-> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
-> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+> This functionality is currently being deprecated and will no longer be supported after August 1st, 2020.
+> The currently recommended version works only for [Java through standalone agent](https://docs.microsoft.com/azure/azure-monitor/app/java-in-process-agent).
 
 Azure Monitor now leverages service mesh tech on your Kubernetes cluster to provide out of the box application monitoring for any Kubernetes hosted app. With default Application Insight features like [Application Map](../../azure-monitor/app/app-map.md) to model your dependencies, [Live Metrics Stream](../../azure-monitor/app/live-stream.md) for real-time monitoring, powerful visualizations with the [default dashboard](../../azure-monitor/app/overview-dashboard.md), [Metric Explorer](../../azure-monitor/platform/metrics-getting-started.md), and [Workbooks](../../azure-monitor/app/usage-workbooks.md). This feature will help users spot performance bottlenecks and failure hotspots across all of their Kubernetes workloads within a selected Kubernetes namespace. By capitalizing on your existing service mesh investments with technologies like Istio, Azure Monitor enables auto-instrumented app monitoring without any modification to your application's code.
 
@@ -108,7 +107,7 @@ Below is the troubleshooting flow to use when telemetry doesn't appear in the Az
    ```
    Verify that there is a container named *istio-proxy* running on the pod.
 
-5. View the Application Insights adapter’s traces.
+5. View the Application Insights adapter's traces.
 
    ```console
    kubectl get pods -n istio-system -l "app=application-insights-istio-mixer-adapter"

articles/azure-monitor/toc.yml

@@ -239,9 +239,11 @@
       - name: Azure Functions
         displayname: functions, monitor functions, automation
         href: ../azure-functions/functions-monitoring.md
-      - name: Kubernetes applications
-        displayname: aks, microservice, istio, service mesh, application monitoring, monitor kubernetes, monitor aks
-        href: app/kubernetes.md
+      - name: Azure Kubernetes Service
+        items:
+        - name: Kubernetes (Deprecated)
+          displayname: aks, microservice, istio, service mesh, application monitoring, monitor kubernetes, monitor aks
+          href: app/kubernetes.md
       - name: Standalone - any environment
         items:  
           - name: Java (preview)
@@ -282,7 +284,7 @@
       href: app/app-map.md
     - name: Transaction diagnostics
       href: app/transaction-diagnostics.md
-      displayname: e2e, end-to-end, component, dependency, cross-compoent transaction, operation ID, dependencies
+      displayname: e2e, end-to-end, component, dependency, cross-component transaction, operation ID, dependencies
     - name: Availability
       items:
       - name: URL tests