From 1f6fa967b5c39cd90ead94c353afdaf3bae86484 Mon Sep 17 00:00:00 2001
From: Saylor Berman <s.berman@f5.com>
Date: Mon, 22 Dec 2025 11:59:06 -0700
Subject: [PATCH 1/2] docs: Update N1 NGF installation doc

The N1 doc for NGF integration was missing the step to deploy a Gateway. Without this, nothing can be seen on the console.
---
 content/nginx-one-console/k8s/add-ngf-helm.md | 21 +++++++++++++++++++
 .../k8s/add-ngf-manifests.md                  | 21 +++++++++++++++++++
 2 files changed, 42 insertions(+)

diff --git a/content/nginx-one-console/k8s/add-ngf-helm.md b/content/nginx-one-console/k8s/add-ngf-helm.md
index 10685d94a..0c063e944 100644
--- a/content/nginx-one-console/k8s/add-ngf-helm.md
+++ b/content/nginx-one-console/k8s/add-ngf-helm.md
@@ -137,6 +137,27 @@ To wait for the Deployment to be ready, you can either add the `--wait` flag to
 kubectl wait --timeout=5m -n nginx-gateway deployment/ngf-nginx-gateway-fabric --for=condition=Available
 ```
 
+## Deploy a Gateway
+
+Now that the control plane is installed, you need to create a Gateway, which will provision NGINX and NGINX Agent. For example:
+
+```yaml
+kubectl apply -f - <<EOF
+apiVersion: gateway.networking.k8s.io/v1
+kind: Gateway
+metadata:
+  name: gateway
+spec:
+  gatewayClassName: nginx
+  listeners:
+  - name: http
+    port: 80
+    protocol: HTTP
+EOF
+```
+
+An NGINX Deployment will be created in the `default` namespace (same namespace as the Gateway). Once Running, it should report to the NGINX One Console.
+
 ## Verify a connection to NGINX One Console
 
 {{< include "/nginx-one-console/how-to/verify-connection.md" >}}
diff --git a/content/nginx-one-console/k8s/add-ngf-manifests.md b/content/nginx-one-console/k8s/add-ngf-manifests.md
index e9c798f84..d261f4db6 100644
--- a/content/nginx-one-console/k8s/add-ngf-manifests.md
+++ b/content/nginx-one-console/k8s/add-ngf-manifests.md
@@ -43,6 +43,27 @@ Specify the data plane key Secret name in the `--nginx-one-dataplane-key-secret`
 
 {{< include "/ngf/installation/deploy-ngf-manifests.md" >}}
 
+## Deploy a Gateway
+
+Now that the control plane is installed, you need to create a Gateway, which will provision NGINX and NGINX Agent. For example:
+
+```yaml
+kubectl apply -f - <<EOF
+apiVersion: gateway.networking.k8s.io/v1
+kind: Gateway
+metadata:
+  name: gateway
+spec:
+  gatewayClassName: nginx
+  listeners:
+  - name: http
+    port: 80
+    protocol: HTTP
+EOF
+```
+
+An NGINX Deployment will be created in the `default` namespace (same namespace as the Gateway). Once Running, it should report to the NGINX One Console.
+
 ## Verify a connection to NGINX One Console
 
 {{< include "/nginx-one-console/how-to/verify-connection.md" >}}

From 24e9a2a571670dcda364f80bfaa60c069a5aff75 Mon Sep 17 00:00:00 2001
From: Saylor Berman <s.berman@f5.com>
Date: Mon, 22 Dec 2025 12:08:54 -0700
Subject: [PATCH 2/2] Encase in quotes

---
 content/nginx-one-console/k8s/add-ngf-helm.md      | 2 +-
 content/nginx-one-console/k8s/add-ngf-manifests.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/nginx-one-console/k8s/add-ngf-helm.md b/content/nginx-one-console/k8s/add-ngf-helm.md
index 0c063e944..fc81a97af 100644
--- a/content/nginx-one-console/k8s/add-ngf-helm.md
+++ b/content/nginx-one-console/k8s/add-ngf-helm.md
@@ -156,7 +156,7 @@ spec:
 EOF
 ```
 
-An NGINX Deployment will be created in the `default` namespace (same namespace as the Gateway). Once Running, it should report to the NGINX One Console.
+An NGINX Deployment will be created in the `default` namespace (same namespace as the Gateway). Once `Running`, it should report to the NGINX One Console.
 
 ## Verify a connection to NGINX One Console
 
diff --git a/content/nginx-one-console/k8s/add-ngf-manifests.md b/content/nginx-one-console/k8s/add-ngf-manifests.md
index d261f4db6..0ff5ba455 100644
--- a/content/nginx-one-console/k8s/add-ngf-manifests.md
+++ b/content/nginx-one-console/k8s/add-ngf-manifests.md
@@ -62,7 +62,7 @@ spec:
 EOF
 ```
 
-An NGINX Deployment will be created in the `default` namespace (same namespace as the Gateway). Once Running, it should report to the NGINX One Console.
+An NGINX Deployment will be created in the `default` namespace (same namespace as the Gateway). Once `Running`, it should report to the NGINX One Console.
 
 ## Verify a connection to NGINX One Console