Merge pull request #249300 from JnHs/jh-arc-tocdn0823

displayName in TOC and small cleanup

Author: AnnaMHuff

articles/azure-arc/kubernetes/conceptual-agent-overview.md

@@ -1,6 +1,6 @@
 ---
 title: "Azure Arc-enabled Kubernetes agent overview"
-ms.date: 12/07/2022
+ms.date: 08/24/2023
 ms.topic: conceptual
 description: "Learn about the Azure Arc agents deployed on the Kubernetes clusters when connecting them to Azure Arc."
 ---
@@ -9,12 +9,14 @@ description: "Learn about the Azure Arc agents deployed on the Kubernetes cluste
 
 [Azure Arc-enabled Kubernetes](overview.md) provides a centralized, consistent control plane to manage policy, governance, and security across Kubernetes clusters in different environments.
 
-Azure Arc agents are deployed on Kubernetes clusters when you [connect them to Azure Arc](quickstart-connect-cluster.md),  This article provides an overview of these agents.
+Azure Arc agents are deployed on Kubernetes clusters when you [connect them to Azure Arc](quickstart-connect-cluster.md). This article provides an overview of these agents.
 
 ## Deploy agents to your cluster
 
 Most on-premises datacenters enforce strict network rules that prevent inbound communication on the network boundary firewall. Azure Arc-enabled Kubernetes works with these restrictions by not requiring inbound ports on the firewall. Azure Arc agents require outbound communication to a [set list of network endpoints](network-requirements.md).
 
+This diagram provides a high-level view of Azure Arc components. Kubernetes clusters in on-premises datacenters or different clouds are connected to Azure through the Azure Arc agents. This allows the clusters to be managed in Azure using management tools and Azure services. The clusters can also be accessed through offline management tools.
+
 :::image type="content" source="media/architectural-overview.png" alt-text="Diagram showing an architectural overview of the Azure Arc-enabled Kubernetes agents." lightbox="media/architectural-overview.png":::
 
 The following high-level steps are involved in [connecting a Kubernetes cluster to Azure Arc](quickstart-connect-cluster.md):
@@ -48,5 +50,6 @@ The following high-level steps are involved in [connecting a Kubernetes cluster
 ## Next steps
 
 * Walk through our quickstart to [connect a Kubernetes cluster to Azure Arc](./quickstart-connect-cluster.md).
+* View release notes to see [details about the latest agent versions](release-notes.md).
 * Learn about [upgrading Azure Arc-enabled Kubernetes agents](agent-upgrade.md).
 * Learn more about the creating connections between your cluster and a Git repository as a [configuration resource with Azure Arc-enabled Kubernetes](./conceptual-configurations.md).

articles/azure-arc/kubernetes/toc.yml

@@ -5,49 +5,55 @@
   - name: About Azure Arc-enabled Kubernetes
     href: overview.md
   - name: What's new with Arc-enabled Kubernetes
+    displayName: release, notes, version, latest
     href: release-notes.md
   - name: Azure Arc validated partners
     displayName: distributions, validation
     href: validation-program.md
 - name: Quickstarts
   items:
   - name: Connect a cluster to Azure Arc
-    displayName: enable, Arc-enable, deploy
+    displayName: enable, Arc-enable, deploy, quickstart
     href: quickstart-connect-cluster.md
 - name: Tutorials
   items:
   - name: Deploy configurations using GitOps
-    displayName: flux
+    displayName: flux, tutorial, controller
     href: tutorial-use-gitops-flux2.md
   - name: Implement CI/CD with GitOps
-    displayName: flux
+    displayName: flux, pipeline
     href: tutorial-gitops-flux2-ci-cd.md
 - name: Samples
   items:
   - name: Azure Resource Graph queries
+    displayName: arg
     href: ./resource-graph-samples.md
 - name: Concepts
   items:
   - name: Agent overview
     href: conceptual-agent-overview.md
   - name: System requirements
+    displayName: memory, compute, prerequisites
     href: system-requirements.md
   - name: Network requirements
+    displayName: endpoint, url, connection, connectivity, proxy
     href: network-requirements.md
   - name: Connectivity modes
+    displayName: disconnected, semi-connected
     href: conceptual-connectivity-modes.md
   - name: Data exchange between cluster and Azure
+    displayName: metadata
     href: conceptual-data-exchange.md
   - name: Identity and access management
     items:
       - name: Identity and access overview
-        displayName: connect, rbac
+        displayName: connect, rbac, authentication, authorization
         href: identity-access-overview.md
       - name: Cluster connect access
         displayName: identity
         href: conceptual-cluster-connect.md
       - name: Azure RBAC integration
-        displayName: azure ad, azure active directory, identity, access
+        displayName: azure ad, azure active directory, identity, access, role
         href: conceptual-azure-rbac.md
   - name: Extend Azure capabilities to clusters anywhere
     items:
@@ -57,14 +63,15 @@
         displayName: gitops, flux, version
         href: extensions-release.md
       - name: Custom locations
+        displayName: target
         href: conceptual-custom-locations.md
   - name: Deploy applications to cluster
     items:
       - name: Configurations and GitOps
         displayName: flux, deploy, applications
         href: conceptual-gitops-flux2.md
       - name: CI/CD workflow using GitOps
-        displayName: flux
+        displayName: flux, pipeline
         href: conceptual-gitops-flux2-ci-cd.md
       - name: Multi-cluster workload management with GitOps
         displayName: multicluster
@@ -90,24 +97,28 @@
     - name: Security baseline
       href: /security/benchmark/azure/baselines/azure-arc-enabled-kubernetes-security-baseline?toc=/azure/azure-arc/kubernetes/toc.json
   - name: Frequently Asked Questions
+    displayName: FAQ
     href: faq.md
 - name: How-to guides
   items:
   - name: Upgrade agents
+    displayName: update, automatic
     href: agent-upgrade.md
   - name: Use Private Link Scope
     href: private-link.md
   - name: View resources in Azure portal
-    displayName: kubernetes, yaml, workload
+    displayName: workload
     href: kubernetes-resource-view.md
   - name: Deploy applications consistently
-    displayName: GitOps, flux, configuration, policy
+    displayName: GitOps, flux, configuration, policy, scale
     href: use-azure-policy-flux-2.md
   - name: Explore multi-cluster workload management
+    displayName: gitops, application
     href: workload-management.md
   - name: Manage identity and access
     items:
     - name: Securely connect to cluster from anywhere
+      displayName: cluster connect, authentication, access
       href: cluster-connect.md
     - name: Use Azure RBAC for authorization checks
       displayName: azure active directory, identity, access
@@ -119,26 +130,32 @@
     - name: Monitor using Azure Monitor Container Insights
       href: ../../azure-monitor/containers/container-insights-enable-arc-enabled-clusters.md?toc=/azure/azure-arc/kubernetes/toc.json&bc=/azure/azure-arc/kubernetes/breadcrumb/toc.json
     - name: Monitor GitOps (Flux v2) activity
+      displayName: dashboard, prometheus, compliance, status, reconciliation, activity
       href: monitor-gitops-flux-2.md
     - name: Enforce threat protection using Microsoft Defender for Cloud
       displayName: security
       href: ../../defender-for-cloud/defender-for-kubernetes-azure-arc.md?toc=/azure/azure-arc/kubernetes/toc.json&bc=/azure/azure-arc/kubernetes/breadcrumb/toc.json
     - name: In-cluster policy enforcements using Azure Policy
+      displayName: compliance
       href: ../../governance/policy/concepts/policy-for-kubernetes.md?toc=/azure/azure-arc/kubernetes/toc.json&bc=/azure/azure-arc/kubernetes/breadcrumb/toc.json#install-azure-policy-extension-for-azure-arc-enabled-kubernetes
     - name: Deploy Azure Arc-enabled Open Service Mesh
+      displayName: osm, microservice
       href: tutorial-arc-enabled-open-service-mesh.md
     - name: Access secrets from Azure Key Vault
+      displayName: akv, cert
       href: tutorial-akv-secrets-provider.md
   - name: Deploy Arc-enabled services
     items:
       - name: Create custom locations
+        displayName: target
         href: custom-locations.md
       - name: Azure Arc-enabled Machine Learning
+        displayName: ML, AzureML, compute
         href: ../../machine-learning/how-to-attach-kubernetes-anywhere.md?toc=/azure/azure-arc/kubernetes/toc.json&bc=/azure/azure-arc/kubernetes/breadcrumb/toc.json
   - name: Move between regions
     href: move-regions.md
   - name: Diagnose connection issues
-    displayName: troubleshoot, problem, proxy
+    displayName: troubleshoot, problem, proxy, network
     href: diagnose-connection-issues.md
   - name: Troubleshooting
     displayName: problem, issue, resolve

articles/azure-arc/resource-bridge/network-requirements.md

@@ -2,7 +2,7 @@
 title: Azure Arc resource bridge (preview) network requirements
 description: Learn about network requirements for Azure Arc resource bridge (preview) including URLs that must be allowlisted.
 ms.topic: conceptual
-ms.date: 01/30/2023
+ms.date: 08/24/2023
 ---
 
 # Azure Arc resource bridge (preview) network requirements
@@ -17,32 +17,32 @@ This article describes the networking requirements for deploying Azure Arc resou
 
 ## Additional network requirements
 
-In addition, resource bridge (preview) requires connectivity to the [Arc-enabled Kubernetes endpoints](../network-requirements-consolidated.md?tabs=azure-cloud).
+In addition, Arc resource bridge (preview) requires connectivity to the [Arc-enabled Kubernetes endpoints](../network-requirements-consolidated.md?tabs=azure-cloud).
 
 > [!NOTE]
 > The URLs listed here are required for Arc resource bridge only. Other Arc products (such as Arc-enabled VMware vSphere) may have additional required URLs. For details, see [Azure Arc network requirements](../network-requirements-consolidated.md).
 
 ## SSL proxy configuration
 
-If using a proxy, Arc resource bridge must be configured for proxy so that it can connect to the Azure services. 
+If using a proxy, Arc resource bridge must be configured for proxy so that it can connect to the Azure services.
 
-- To configure the Arc resource bridge with proxy, provide the proxy certificate file path during creation of the configuration files. 
+- To configure the Arc resource bridge with proxy, provide the proxy certificate file path during creation of the configuration files.
 
-- The format of the certificate file is *Base-64 encoded X.509 (.CER)*. 
+- The format of the certificate file is *Base-64 encoded X.509 (.CER)*.
 
-- Only pass the single proxy certificate. If a certificate bundle is passed then the deployment will fail. 
+- Only pass the single proxy certificate. If a certificate bundle is passed, the deployment will fail.
 
-- The proxy server endpoint can't be a .local domain. 
+- The proxy server endpoint can't be a `.local` domain.
 
-- The proxy server has to be reachable from all IPs within the IP address prefix, including the control plane and appliance VM IPs. 
+- The proxy server has to be reachable from all IPs within the IP address prefix, including the control plane and appliance VM IPs.
 
-There are only two certificates that should be relevant when deploying the Arc resource bridge behind an SSL proxy: 
+There are only two certificates that should be relevant when deploying the Arc resource bridge behind an SSL proxy:
 
 - SSL certificate for your SSL proxy (so that the management machine and appliance VM trust your proxy FQDN and can establish an SSL connection to it)
 
 - SSL certificate of the Microsoft download servers. This certificate must be trusted by your proxy server itself, as the proxy is the one establishing the final connection and needs to trust the endpoint. Non-Windows machines may not trust this second certificate by default, so you may need to ensure that it's trusted.
 
-In order to deploy Arc resource bridge, images need to be downloaded to the management machine and then uploaded to the on-premises private cloud gallery. If your proxy server throttles download speed, this may impact your ability to download the required images (~3.5 GB) within the allotted time (90 min). 
+In order to deploy Arc resource bridge, images need to be downloaded to the management machine and then uploaded to the on-premises private cloud gallery. If your proxy server throttles download speed, you may not be able to download the required images (~3.5 GB) within the allotted time (90 min).
 
 ## Exclusion list for no proxy
 
@@ -51,7 +51,7 @@ If a proxy server is being used, the following table contains the list of addres
 |      **IP Address**       |    **Reason for exclusion**    |  
 | ----------------------- | ------------------------------------ |
 | localhost, 127.0.0.1  | Localhost traffic  |
-| .svc | Internal Kubernetes service traffic (.svc) where _.svc_ represents a wildcard name. This is similar to saying \*.svc, but none is used in this schema. |
+| .svc | Internal Kubernetes service traffic (.svc) where *.svc* represents a wildcard name. This is similar to saying \*.svc, but none is used in this schema. |
 | 10.0.0.0/8 | private network address space |
 | 172.16.0.0/12 |Private network address space - Kubernetes Service CIDR |
 | 192.168.0.0/16 | Private network address space - Kubernetes Pod CIDR |
@@ -60,13 +60,10 @@ If a proxy server is being used, the following table contains the list of addres
 The default value for `noProxy` is `localhost,127.0.0.1,.svc,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16`. While these default values will work for many networks, you may need to add more subnet ranges and/or names to the exemption list. For example, you may want to exempt your enterprise namespace (.contoso.com) from being directed through the proxy. You can achieve that by specifying the values in the `noProxy` list.
 
 > [!IMPORTANT]
-> When listing multiple addresses for the noproxy settings, do not add a space after the commas to separate the addresses. The addresses must immediately follow the comma.
+> When listing multiple addresses for the `noProxy` settings, don't add a space after each comma to separate the addresses. The addresses must immediately follow the commas.
+
 ## Next steps
 
 - Review the [Azure Arc resource bridge (preview) overview](overview.md) to understand more about requirements and technical details.
 - Learn about [security configuration and considerations for Azure Arc resource bridge (preview)](security-overview.md).
-
-
-
-
-
+- View [troubleshooting tips for networking issues](troubleshoot-resource-bridge.md#networking-issues).

articles/azure-arc/toc.yml

@@ -11,22 +11,30 @@
 - name: Samples
   items:
   - name: Azure Resource Graph queries
+    displayName: arg, query
     href: ./resource-graph-samples.md
 - name: Azure Arc resource bridge
   items:
   - name: About Azure Arc resource bridge
+    displayName: appliance
     href: ./resource-bridge/overview.md
   - name: System requirements
+    displayName: resource bridge
     href: ./resource-bridge/system-requirements.md
   - name: Network requirements
+    displayName: resource bridge
     href: ./resource-bridge/network-requirements.md
   - name: Security overview
+    displayName: resource bridge
     href: ./resource-bridge/security-overview.md
   - name: Deployment overview
+    displayName: resource bridge, arcappliance
     href: ./resource-bridge/deploy-cli.md
   - name: Maintenance
+    displayName: resource bridge, appliance
     href: ./resource-bridge/maintenance.md
   - name: Troubleshoot
+    displayName: resource bridge
     href: ./resource-bridge/troubleshoot-resource-bridge.md
 - name: Azure Arc-enabled servers >
   href: ./servers/overview.md
@@ -45,10 +53,13 @@
 - name: Arc validation program
   items:
    - name: Program overview
+     displayName: validation
      href: validation-program/overview.md
    - name: Validated Kubernetes partners
+     displayName: validation
      href: kubernetes/validation-program.md?toc=/azure/azure-arc/toc.json&bc=/azure/azure-arc/breadcrumb/toc.json
    - name: Validated data services partners
+     displayName: validation
      href: data/validation-program.md?toc=/azure/azure-arc/toc.json&bc=/azure/azure-arc/breadcrumb/toc.json
 - name: Reference
   items: