remove refs to agc preview in appgw docs

greg-lindsay · greg-lindsay · commit c3991f7fb2fc · 2024-01-31T13:19:19.000-08:00
diff --git a/articles/application-gateway/ingress-controller-expose-service-over-http-https.md b/articles/application-gateway/ingress-controller-expose-service-over-http-https.md
@@ -15,7 +15,7 @@ ms.author: greglin
 These tutorials help illustrate the usage of [Kubernetes Ingress Resources](https://kubernetes.io/docs/concepts/services-networking/ingress/) to expose an example Kubernetes service through the [Azure Application Gateway](https://azure.microsoft.com/services/application-gateway/) over HTTP or HTTPS.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Prerequisites
 
diff --git a/articles/application-gateway/ingress-controller-expose-websocket-server.md b/articles/application-gateway/ingress-controller-expose-websocket-server.md
@@ -14,7 +14,7 @@ ms.author: greglin
 As outlined in the Application Gateway v2 documentation - it [provides native support for the WebSocket and HTTP/2 protocols](features.md#websocket-and-http2-traffic). Both Application Gateway and the Kubernetes Ingress don't have a user-configurable setting to selectively enable or disable WebSocket support.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 The following Kubernetes deployment YAML shows the minimum configuration used to deploy a WebSocket server, which is the same as deploying a regular web server:
 ```yaml
diff --git a/articles/application-gateway/ingress-controller-install-existing.md b/articles/application-gateway/ingress-controller-install-existing.md
@@ -17,7 +17,7 @@ AGIC monitors the Kubernetes [Ingress](https://kubernetes.io/docs/concepts/servi
 resources, and creates and applies Application Gateway config based on the status of the Kubernetes cluster.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Outline
 
diff --git a/articles/application-gateway/ingress-controller-install-new.md b/articles/application-gateway/ingress-controller-install-new.md
@@ -16,7 +16,7 @@ The instructions below assume Application Gateway Ingress Controller (AGIC) will
 installed in an environment with no pre-existing components.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Required Command Line Tools
 
diff --git a/articles/application-gateway/ingress-controller-letsencrypt-certificate-application-gateway.md b/articles/application-gateway/ingress-controller-letsencrypt-certificate-application-gateway.md
@@ -15,7 +15,7 @@ ms.author: greglin
 This section configures your AKS to use [LetsEncrypt.org](https://letsencrypt.org/) and automatically obtain a TLS/SSL certificate for your domain. The certificate is installed on Application Gateway, which performs SSL/TLS termination for your AKS cluster. The setup described here uses the [cert-manager](https://github.com/jetstack/cert-manager) Kubernetes add-on, which automates the creation and management of certificates.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 Use the following steps to install [cert-manager](https://docs.cert-manager.io) on your existing AKS cluster.
 
diff --git a/articles/application-gateway/ingress-controller-migration.md b/articles/application-gateway/ingress-controller-migration.md
@@ -14,7 +14,7 @@ ms.author: greglin
 If you already have AGIC deployed through Helm but want to migrate to AGIC deployed as an AKS add-on, the following steps help to guide you through the migration process. 
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Prerequisites 
 Before you start the migration process, there are a few things to check. 
diff --git a/articles/application-gateway/ingress-controller-multiple-namespace-support.md b/articles/application-gateway/ingress-controller-multiple-namespace-support.md
@@ -20,7 +20,7 @@ As of version 0.7 [Azure Application Gateway Kubernetes IngressController](https
 Version 0.7 of AGIC continues to exclusively observe the `default` namespace, unless this is explicitly changed to one or more different namespaces in the Helm configuration. See the following section.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Enable multiple namespace support
 
diff --git a/articles/application-gateway/ingress-controller-overview.md b/articles/application-gateway/ingress-controller-overview.md
@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: article
-ms.date: 07/28/2023
+ms.date: 01/31/2024
 ms.author: greglin
 ---
 
@@ -15,7 +15,7 @@ The Application Gateway Ingress Controller (AGIC) is a Kubernetes application, w
 The Ingress Controller runs in its own pod on the customer’s AKS. AGIC monitors a subset of Kubernetes Resources for changes. The state of the AKS cluster is translated to Application Gateway specific configuration and applied to the [Azure Resource Manager (ARM)](../azure-resource-manager/management/overview.md).
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Benefits of Application Gateway Ingress Controller
 AGIC helps eliminate the need to have another load balancer/public IP address in front of the AKS cluster and avoids multiple hops in your datapath before requests reach the AKS cluster. Application Gateway talks to pods using their private IP address directly and doesn't require NodePort or KubeProxy services. This capability also brings better performance to your deployments.
diff --git a/articles/application-gateway/ingress-controller-private-ip.md b/articles/application-gateway/ingress-controller-private-ip.md
@@ -15,7 +15,7 @@ ms.author: greglin
 This feature exposes the ingress endpoint within the `Virtual Network` using a private IP.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 ## Prerequisites
 Application Gateway with a [Private IP configuration](./configure-application-gateway-with-private-frontend-ip.md)
diff --git a/articles/application-gateway/ingress-controller-update-ingress-controller.md b/articles/application-gateway/ingress-controller-update-ingress-controller.md
@@ -16,7 +16,7 @@ The Azure Application Gateway Ingress Controller for Kubernetes (AGIC) can be up
 using a Helm repository hosted on Azure Storage.
 
 > [!TIP]
-> Also see [What is Application Gateway for Containers?](for-containers/overview.md) currently in public preview.
+> Also see [What is Application Gateway for Containers?](for-containers/overview.md).
 
 Before beginning the upgrade procedure, ensure that you've added the required repository:
 
