Removes IC info from networking overview

Author: chasewilson

articles/aks/concepts-network.md

@@ -2,7 +2,7 @@
 title: Concepts - Networking in Azure Kubernetes Services (AKS)
 description: Learn about networking in Azure Kubernetes Service (AKS), including kubenet and Azure CNI networking, ingress controllers, load balancers, and static IP addresses.
 ms.topic: conceptual
-ms.date: 05/14/2024
+ms.date: 06/03/2024
 author: schaffererin
 ms.author: schaffererin
 ms.custom: fasttrack-edit
@@ -20,7 +20,6 @@ In a container-based, microservices approach to application development, applica
 This article introduces the core concepts that provide networking to your applications in AKS:
 
 - [Azure virtual networks](#azure-virtual-networks)
-- [Ingress controllers](#ingress-controllers)
 - [Network policies](#network-policies)
 
 ## Kubernetes networking basics
@@ -54,61 +53,6 @@ In AKS, you can deploy a cluster that uses one of the following network models:
 
 For more information on networking models in AKS, see [CNI Networking in AKS][network-cni-overview].
 
-## Ingress controllers
-
-When you create a LoadBalancer-type Service, you also create an underlying Azure load balancer resource. The load balancer is configured to distribute traffic to the pods in your Service on a given port.
-
-The *LoadBalancer* only works at layer 4. At layer 4, the Service is unaware of the actual applications, and can't make any more routing considerations.
-
-*Ingress controllers* work at layer 7 and can use more intelligent rules to distribute application traffic. Ingress controllers typically route HTTP traffic to different applications based on the inbound URL.
-
-![Diagram showing Ingress traffic flow in an AKS cluster][aks-ingress]
-
-### Compare ingress options
-
-The following table lists the feature differences between the different ingress controller options:
-
-| Feature | Application Routing addon | Application Gateway for Containers | Azure Service Mesh/Istio-based service mesh |
-|---------|---------------------------|---------------------------------------------|-------|
-| **Ingress/Gateway controller** | NGINX ingress controller | Azure Application Gateway for Containers | Istio Ingress Gateway |
-| **API** | Ingress API | Ingress API and Gateway API | Gateway API |
-| **Hosting** | In-cluster | Azure hosted | In-cluster |
-| **Scaling** | Autoscaling | Autoscaling | Autoscaling |
-| **Load balancing** | Internal/External | External | Internal/External |
-| **SSL termination** | In-cluster | Yes: Offloading and E2E SSL | In-cluster |
-| **mTLS** | N/A | Yes to backend | N/A |
-| **Static IP Address** | N/A | FQDN | N/A |
-| **Azure Key Vault stored SSL certificates** | Yes | Yes | N/A |
-| **Azure DNS integration for DNS zone management** | Yes | Yes | N/A |
-
-The following table lists the different scenarios where you might use each ingress controller:
-
-| Ingress option | When to use |
-|----------------|-------------|
-| **Managed NGINX - Application Routing addon** | • In-cluster hosted, customizable, and scalable NGINX ingress controllers. </br> • Basic load balancing and routing capabilities. </br> • Internal and external load balancer configuration. </br> • Static IP address configuration. </br> • Integration with Azure Key Vault for certificate management. </br> • Integration with Azure DNS Zones for public and private DNS management. </br> • Supports the Ingress API. |
-| **Application Gateway for Containers** | • Azure hosted ingress gateway. </br> • Flexible deployment strategies managed by the controller or bring your own Application Gateway for Containers. </br> • Advanced traffic management features such as automatic retries, availability zone resiliency, mutual authentication (mTLS) to backend target, traffic splitting / weighted round robin, and autoscaling. </br> • Integration with Azure Key Vault for certificate management. </br> • Integration with Azure DNS Zones for public and private DNS management. </br> • Supports the Ingress and Gateway APIs. |
-| **Istio Ingress Gateway** | • Based on Envoy, when using with Istio for a service mesh. </br> • Advanced traffic management features such as rate limiting and circuit breaking. </br> • Support for mTLS </br> • Supports the Gateway API. |
-
-### Create an Ingress resource
-
-The application routing addon is the recommended way to configure an Ingress controller in AKS. The application routing addon is a fully managed ingress controller for Azure Kubernetes Service (AKS) that provides the following features:
-
-- Easy configuration of managed NGINX Ingress controllers based on Kubernetes NGINX Ingress controller.
-
-- Integration with Azure DNS for public and private zone management.
-
-- SSL termination with certificates stored in Azure Key Vault.
-
-For more information about the application routing addon, see [Managed NGINX ingress with the application routing add-on](app-routing.md).
-
-### Client source IP preservation
-
-Configure your ingress controller to preserve the client source IP on requests to containers in your AKS cluster. When your ingress controller routes a client's request to a container in your AKS cluster, the original source IP of that request is unavailable to the target container. When you enable *client source IP preservation*, the source IP for the client is available in the request header under *X-Forwarded-For*.
-
-If you're using client source IP preservation on your ingress controller, you can't use TLS pass-through. Client source IP preservation and TLS pass-through can be used with other services, such as the *LoadBalancer* type.
-
-To learn more about client source IP preservation, see [How client source IP preservation works for LoadBalancer Services in AKS][ip-preservation].
-
 ## Control outbound (egress) traffic
 
 AKS clusters are deployed on a virtual network and have outbound dependencies on services outside of that virtual network. These outbound dependencies are almost entirely defined with fully qualified domain names (FQDNs). By default, AKS clusters have unrestricted outbound (egress) Internet access, which allows the nodes and services you run to access external resources as needed. If desired, you can restrict outbound traffic.
@@ -138,7 +82,7 @@ For more information, see [Secure traffic between pods using network policies in
 
 ## Next steps
 
-To get started with AKS networking, create and configure an AKS cluster with your own IP address ranges using [kubenet][aks-configure-kubenet-networking] or [Azure CNI][aks-configure-advanced-networking].
+To get started with AKS networking, create and configure an AKS cluster with your own IP address ranges using [Azure CNI Overlay][azure-cni-overlay] or [Azure CNI][aks-configure-advanced-networking].
 
 For associated best practices, see [Best practices for network connectivity and security in AKS][operator-best-practices-network].