Merge pull request #247403 from JackStromberg/JackStromberg-patch-190

Naming conventions for managed resources

Author: Stacyrch140

articles/application-gateway/for-containers/how-to-backend-mtls-gateway-api.md

@@ -73,6 +73,7 @@ spec:
 EOF
 ```
 
+[!INCLUDE [application-gateway-for-containers-frontend-naming](../../../includes/application-gateway-for-containers-frontend-naming.md)]
 
 # [Bring your own (BYO) deployment](#tab/byo)
 1. Set the following environment variables

articles/application-gateway/for-containers/how-to-multiple-site-hosting-gateway-api.md

@@ -62,6 +62,7 @@ spec:
 EOF
 ```
 
+[!INCLUDE [application-gateway-for-containers-frontend-naming](../../../includes/application-gateway-for-containers-frontend-naming.md)]
 
 # [Bring your own (BYO) deployment](#tab/byo)
 

articles/application-gateway/for-containers/how-to-path-header-query-string-routing-gateway-api.md

@@ -64,6 +64,7 @@ spec:
 EOF
 ```
 
+[!INCLUDE [application-gateway-for-containers-frontend-naming](../../../includes/application-gateway-for-containers-frontend-naming.md)]
 
 # [Bring your own (BYO) deployment](#tab/byo)
 1. Set the following environment variables

articles/application-gateway/for-containers/how-to-ssl-offloading-gateway-api.md

@@ -71,6 +71,7 @@ This document helps set up an example application that uses the following resour
     EOF
     ```
 
+[!INCLUDE [application-gateway-for-containers-frontend-naming](../../../includes/application-gateway-for-containers-frontend-naming.md)]
 
 # [Bring your own (BYO) deployment](#tab/byo)
 

articles/application-gateway/for-containers/how-to-ssl-offloading-ingress-api.md

@@ -71,6 +71,7 @@ spec:
 EOF
 ```
 
+[!INCLUDE [application-gateway-for-containers-frontend-naming](../../../includes/application-gateway-for-containers-frontend-naming.md)]
 
 # [Bring your own (BYO) deployment](#tab/byo)
 

articles/application-gateway/for-containers/how-to-traffic-splitting-gateway-api.md

@@ -64,6 +64,7 @@ spec:
 EOF
 ```
 
+[!INCLUDE [application-gateway-for-containers-frontend-naming](../../../includes/application-gateway-for-containers-frontend-naming.md)]
 
 # [Bring your own (BYO) deployment](#tab/byo)
 

articles/application-gateway/for-containers/quickstart-create-application-gateway-for-containers-managed-by-alb-controller.md

@@ -102,6 +102,15 @@ EOF
 
 2. Define the _ApplicationLoadBalancer_ resource, specifying the subnet ID the Application Gateway for Containers association resource should deploy into.  The association establishes connectivity from Application Gateway for Containers to the defined subnet (and connected networks where applicable) to be able to proxy traffic to a defined backend.
 
+> [!Note]
+> When the ALB Controller creates the Application Gateway for Containers resources in ARM, it'll use the following naming conventions for its resources:
+> - alb-\<8 randomly generated characters\> to define the Application Gateway for Containers resource
+> - as-\<8 randomly generated characters\> to define the association resource
+>
+> If you would like to change the name of the resources created in Azure, consider following the [bring your own deployment strategy](quickstart-create-application-gateway-for-containers-byo-deployment.md).
+
+Run the following command to create the Application Gateway for Containers resource and association.
+
 ```bash
 kubectl apply -f - <<EOF
 apiVersion: alb.networking.azure.io/v1

includes/application-gateway-for-containers-frontend-naming.md

@@ -0,0 +1,12 @@
+---
+author: greg-lindsay
+ms.service: application-gateway
+ms.subservice: appgw-for-containers
+ms.topic: include
+ms.date: 08/14/2023
+ms.author: greglin
+---
+> [!Note]
+> When the ALB Controller creates the Application Gateway for Containers resources in ARM, it'll use the following naming convention for a frontend resource: fe-\<8 randomly generated characters\>
+>
+> If you would like to change the name of the frontend created in Azure, consider following the [bring your own deployment strategy](../articles/application-gateway/for-containers/overview.md#deployment-strategies).