Update ingress-controller-expose-websocket-server.md

Author: JackStromberg

articles/application-gateway/ingress-controller-expose-websocket-server.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 08/01/2023
+ms.date: 2/28/2025
 ms.author: greglin
 ---
 
@@ -14,7 +14,7 @@ ms.author: greglin
 Azure Application Gateway v2 [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]
-> Consider [Application Gateway for Containers](for-containers/overview.md) for your Kubernetes ingress solution.
+> Consider [Application Gateway for Containers](for-containers/overview.md) for your Kubernetes ingress solution. For more information, see [Quickstart: Deploy Application Gateway for Containers ALB Controller](for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md).
 
 ## YAML for WebSocket server deployment
 
@@ -102,3 +102,4 @@ To avoid the `502 Bad Gateway` error, you might need to add an HTTP `GET` handle
 ## Related content
 
 - [Application Gateway for Containers](for-containers/overview.md)
+- [Application Gateway for Containers - WebSocket support](for-containers/websockets.md)