diff --git a/app/_how-tos/operator/operator-get-started-gateway-api-2-create-gateway.md b/app/_how-tos/operator/operator-get-started-gateway-api-2-create-gateway.md
index 2f20a1a5f53..4b0d8f8d88a 100644
--- a/app/_how-tos/operator/operator-get-started-gateway-api-2-create-gateway.md
+++ b/app/_how-tos/operator/operator-get-started-gateway-api-2-create-gateway.md
@@ -42,6 +42,10 @@ prereqs:
     konnect:
       auth: true
 
+related_resources:
+  - text: Enable static naming for Konnect control planes
+    url: /operator/konnect/how-to/static-naming/
+
 ---
 
 ## Create a `GatewayConfiguration` resource
@@ -176,7 +180,11 @@ spec:
 ```
 
 {% konnect %}
-content: {{site.operator_product_name}} will automatically create the `DataPlane` and `KonnectGatewayControlPlane` resources.
+content: |
+  {{site.operator_product_name}} will automatically create the `DataPlane` and `KonnectGatewayControlPlane` resources.
+
+  {:.info}
+  > By default, the generated `KonnectGatewayControlPlane` receives a dynamic name. Add the `gateway-operator.konghq.com/static-naming: "true"` annotation to your `Gateway` to use a predictable name based on the Gateway's namespace and name. Names can't be changed after creation.
 {% endkonnect %}
 
 {% on_prem %}
diff --git a/app/_how-tos/operator/operator-konnect-auth-cross-namespace-reference.md b/app/_how-tos/operator/operator-konnect-auth-cross-namespace-reference.md
index b32f31aaf17..88b6cb76fb6 100644
--- a/app/_how-tos/operator/operator-konnect-auth-cross-namespace-reference.md
+++ b/app/_how-tos/operator/operator-konnect-auth-cross-namespace-reference.md
@@ -22,6 +22,8 @@ tldr:
 related_resources:
   - text: Reference Secrets across multiple namespaces
     url: /operator/konnect/how-to/secret-cross-namespace-reference/
+  - text: Enable static naming for Konnect control planes
+    url: /operator/konnect/how-to/static-naming/
 
 min_version:
   operator: '2.1'
@@ -141,4 +143,7 @@ To validate, check that the `KonnectGatewayControlPlane` resource was automatica
 
 ```sh
 kubectl get konnectgatewaycontrolplane -n kong
-```
\ No newline at end of file
+```
+
+{:.info}
+> By default, the generated `KonnectGatewayControlPlane` receives a dynamic name. Add the `gateway-operator.konghq.com/static-naming: "true"` annotation to your `Gateway` to use a predictable name based on the Gateway's namespace and name. Names can't be changed after creation.
\ No newline at end of file
diff --git a/app/_how-tos/operator/operator-konnect-static-naming.md b/app/_how-tos/operator/operator-konnect-static-naming.md
index 6398102fe63..de7f50d4f9e 100644
--- a/app/_how-tos/operator/operator-konnect-static-naming.md
+++ b/app/_how-tos/operator/operator-konnect-static-naming.md
@@ -20,6 +20,12 @@ tldr:
   a: |
     Add the `gateway-operator.konghq.com/static-naming: "true"` annotation to your `Gateway` resource. 
 
+related_resources:
+  - text: Provision a Gateway
+    url: /operator/get-started/gateway-api/deploy-gateway/
+  - text: Reference Konnect authentication across multiple namespaces
+    url: /operator/konnect/how-to/auth-cross-namespace-reference/
+
 min_version:
   operator: '2.1'
 
@@ -33,6 +39,9 @@ By default, {{ site.operator_product_name }} generates unique, dynamic names for
 
 The `gateway-operator.konghq.com/static-naming: "true"` annotation instructs {{site.operator_product_name}} to use a static, predictable name for the generated control plane based on the Gateway's namespace and name (for example, `default-hybrid`). This enables you to configure references before the control plane is created.
 
+{:.warning}
+> Once a `KonnectGatewayControlPlane` name is created, it can't be modified. Plan your naming carefully before enabling this annotation.
+
 When static naming is enabled, {{site.operator_product_name}} derives the name for the `KonnectGatewayControlPlane` using the following logic:
 
 * If the Gateway is in the same namespace as {{site.operator_product_name}}, the name will be the same as the Gateway name.