restoring Related content sections

ShawnJackson · ShawnJackson · commit 7d7b3653d908 · 2024-10-16T13:07:50.000-05:00
diff --git a/articles/application-gateway/ingress-controller-add-health-probes.md b/articles/application-gateway/ingress-controller-add-health-probes.md
@@ -68,3 +68,7 @@ Any property that the readiness or liveness probe can't infer uses the following
 | `Timeout` | `30` |
 | `Interval` | `30` |
 | `UnhealthyThreshold` | `3` |
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-autoscale-pods.md b/articles/application-gateway/ingress-controller-autoscale-pods.md
@@ -129,3 +129,4 @@ ab -n10000 http://<applicaiton-gateway-ip-address>/
 ## Related content
 
 - [Troubleshoot Application Gateway Ingress Controller issues](ingress-controller-troubleshoot.md)
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-cookie-affinity.md b/articles/application-gateway/ingress-controller-cookie-affinity.md
@@ -34,3 +34,7 @@ spec:
           serviceName: frontend
           servicePort: 80
 ```
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-disable-addon.md b/articles/application-gateway/ingress-controller-disable-addon.md
@@ -50,3 +50,4 @@ az aks enable-addons -n <AKS-cluster-name> -g <AKS-cluster-resource-group> -a in
 ## Related content
 
 - For more information on how to enable the AGIC add-on by using an existing Application Gateway deployment and AKS cluster, see [this tutorial](tutorial-ingress-controller-add-on-existing.md).
+- For information about Application Gateway for Containers, see [this overview article](for-containers/overview.md).
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
@@ -177,3 +177,7 @@ spec:
           serviceName: frontend
           servicePort: 80
 ```
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-expose-websocket-server.md b/articles/application-gateway/ingress-controller-expose-websocket-server.md
@@ -98,3 +98,7 @@ Depending on the server implementation (such as [this example](https://github.co
 Because Application Gateway doesn't add WebSocket headers, the Application Gateway health probe response from your WebSocket server is most likely `400 Bad Request`. Application Gateway then marks your pods as unhealthy. This status eventually results in a `502 Bad Gateway` error for the consumers of the WebSocket server.
 
 To avoid the `502 Bad Gateway` error, you might need to add an HTTP `GET` handler for a health check to your server. For example, `/health` returns `200 OK`.
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-install-existing.md b/articles/application-gateway/ingress-controller-install-existing.md
@@ -414,3 +414,7 @@ You can prohibit AGIC from making changes to a subset of the configuration:
 
 3. Modify the Application Gateway configuration from the Azure portal. For example, add listeners, routing rules, and backends. The new object that you created (`manually-configured-staging-environment`) prohibits AGIC from overwriting the Application Gateway configuration related to
 `staging.contoso.com`.
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-install-new.md b/articles/application-gateway/ingress-controller-install-new.md
@@ -366,3 +366,4 @@ Alternatively, you can:
 ## Related content
 
 - For more examples on how to expose an AKS service to the internet via HTTP or HTTPS by using Application Gateway, see [this how-to guide](ingress-controller-expose-service-over-http-https.md).
+- For information about Application Gateway for Containers, see [this overview article](for-containers/overview.md).
diff --git a/articles/application-gateway/ingress-controller-letsencrypt-certificate-application-gateway.md b/articles/application-gateway/ingress-controller-letsencrypt-certificate-application-gateway.md
@@ -140,3 +140,7 @@ Use the following steps to install [cert-manager](https://docs.cert-manager.io)
     1. Delete the existing staging `ClusterIssuer` resource that you created earlier. Create a new staging resource by replacing the ACME server from the previous `ClusterIssuer` YAML with `https://acme-v02.api.letsencrypt.org/directory`.
 
 Before the Let's Encrypt certificate expires, `cert-manager` automatically updates the certificate in the Kubernetes secret store. At that point, the Application Gateway Ingress Controller applies the updated secret referenced in the ingress resources that it's using to configure Application Gateway.
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-multiple-namespace-support.md b/articles/application-gateway/ingress-controller-multiple-namespace-support.md
@@ -158,3 +158,7 @@ By default, AGIC configures Application Gateway based on annotated ingress withi
     aksClusterConfiguration:
         apiServerAddress: <aks-api-server-address>
 ```
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-private-ip.md b/articles/application-gateway/ingress-controller-private-ip.md
@@ -65,3 +65,7 @@ This code makes the ingress controller filter the IP address configurations for
 
 > [!NOTE]
 > Application Gateway v2 requires a public IP. If you require Application Gateway to be private, attach a [network security group](../virtual-network/network-security-groups-overview.md) to the Application Gateway deployment's subnet to restrict traffic.
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)
diff --git a/articles/application-gateway/ingress-controller-update-ingress-controller.md b/articles/application-gateway/ingress-controller-update-ingress-controller.md
@@ -108,3 +108,7 @@ If the Helm deployment fails, you can roll back to a previous release:
     ```bash
     helm rollback odd-billygoat 1
     ```
+
+## Related content
+
+- [Application Gateway for Containers](for-containers/overview.md)

Original file line number	Diff line number	Diff line change
`@@ -129,3 +129,4 @@ ab -n10000 http://<applicaiton-gateway-ip-address>/`
`129`	`129`	`## Related content`
`130`	`130`
`131`	`131`	`- [Troubleshoot Application Gateway Ingress Controller issues](ingress-controller-troubleshoot.md)`
	`132`	`+- [Application Gateway for Containers](for-containers/overview.md)`
Original file line number	Diff line number	Diff line change
`@@ -50,3 +50,4 @@ az aks enable-addons -n <AKS-cluster-name> -g <AKS-cluster-resource-group> -a in`
`50`	`50`	`## Related content`
`51`	`51`
`52`	`52`	`- For more information on how to enable the AGIC add-on by using an existing Application Gateway deployment and AKS cluster, see [this tutorial](tutorial-ingress-controller-add-on-existing.md).`
	`53`	`+- For information about Application Gateway for Containers, see [this overview article](for-containers/overview.md).`
Original file line number	Diff line number	Diff line change
`@@ -366,3 +366,4 @@ Alternatively, you can:`
`366`	`366`	`## Related content`
`367`	`367`
`368`	`368`	`- For more examples on how to expose an AKS service to the internet via HTTP or HTTPS by using Application Gateway, see [this how-to guide](ingress-controller-expose-service-over-http-https.md).`
	`369`	`+- For information about Application Gateway for Containers, see [this overview article](for-containers/overview.md).`