feat: Add Support page content

ADubhlaoich · ADubhlaoich · commit 901c42cad012 · 2025-08-15T14:30:37.000+01:00
diff --git a/_banners/waf-v4-warning.md b/_banners/waf-v4-warning.md
diff --git a/_banners/waf-v5-warning.md b/_banners/waf-v5-warning.md
diff --git a/content/waf/_index.md b/content/waf/_index.md
@@ -23,17 +23,17 @@ nd-product: NAP-WAF
 Defend your applications and APIs with a software security solution that seamlessly integrates into DevOps environments as a lightweight web application firewall (WAF), layer 7 denial-of-service (DoS) protection, bot protection, API security, and threat intelligence services.
 
 ## Featured content
-[//]: # "You can add a maximum of three cards: any extra will not display."
-[//]: # "One card will take full width page: two will take half width each. Three will stack like an inverse pyramid."
-[//]: # "Some examples of content could be the latest release note, the most common install path, and a popular new feature."
 
 {{<card-layout>}}
   {{<card-section showAsCards="true" isFeaturedSection="true">}}
-    {{<card title="Install NGINX App Protect WAF" titleUrl="/waf/install" >}}
-      Explore the methods available to deploy NGINX App Protect WAF in your environment.
+  {{<card title="Overview" titleUrl="/waf/fundamentals/overview">}}
+      Learn about how F5 WAF for NGINX works and how it can be used to protect your applications
     {{</card>}}
-    {{<card title="Changelog" titleUrl="/waf/changelog" icon="archive">}}
-      Review the latest changes and improvements to NGINX App Protect WAF.
+    {{<card title="Install F5 WAF for NGINX" titleUrl="/waf/install" >}}
+      Explore the methods available to deploy F5 WAF for NGINX in your environment
+    {{</card>}}
+    {{<card title="Changelog" titleUrl="/waf/changelog">}}
+      Review the latest changes and improvements to F5 WAF for NGINX
     {{</card>}}
   {{</card-section>}}
 {{</card-layout>}}
diff --git a/content/waf/fundamentals/overview.md b/content/waf/fundamentals/overview.md
@@ -31,7 +31,7 @@ It provides protection for the OWASP Top 10, with additional functionality:
 - Meta character checking
 - Disallowing file types
 
-For full details, see the [Supported Security Policy features]({{< ref "/waf/policies/configuration.md">}}).
+For more details, see the [Supported Security Policy features]({{< ref "/waf/fundamentals/technical-specifications.md#supported-security-policy-features">}}).
 
 F5 WAF for NGINX is part of the [NGINX One](https://www.f5.com/products/nginx/one) premium packages and runs natively on [NGINX Plus](https://www.f5.com/products/nginx/nginx-plus) and [NGINX Ingress Controller](https://www.f5.com/products/nginx/nginx-ingress-controller). 
 
diff --git a/content/waf/fundamentals/technical-specifications.md b/content/waf/fundamentals/technical-specifications.md
@@ -6,7 +6,7 @@ weight: 200
 # Creates a table of contents and sidebar, useful for large documents
 toc: false
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
-nd-content-type: how-to
+nd-content-type: reference
 # Intended for internal catalogue and search, case sensitive:
 # Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
 nd-product: NAP-WAF
@@ -24,4 +24,26 @@ It follows a design pattern set by other NGINX product sets, showing various com
 
 It is also where information about the [Supported Security Policy Features]({{< ref "/nap-waf/v4/configuration-guide/configuration.md#supported-security-policy-features" >}}) could be referenced, though most of that detail will instead be kept in the new top-level "Policies" section.
 
-{{</ call-out>}}
+{{</ call-out>}}
+
+This page outlines the technical specifications for F5 WAF for NGINX, which includes the minimum requirements and supported platforms.
+
+## Supported deployment environments
+
+You can deploy F5 WAF for NGINX in the following environments:
+
+- **Virtual environment** (or bare metal)
+- **Container** (Docker)
+- **Kubernetes**
+
+View the [Install section]({{< ref "/waf/install/" >}}) for information on deploying F5 WAF for NGINX.
+
+## Supported operating systems
+
+## Supported NGINX versions
+
+## Supported Security Policy features
+
+The following Security Policy features are available with F5 WAF for NGINX.
+
+For additional information on each feature, view the [Configuring Policies]({{< ref "/waf/policies/configuration.md" >}}) topic.
diff --git a/content/waf/install/_index.md b/content/waf/install/_index.md
@@ -2,4 +2,4 @@
 title: "Install"
 url: /app-protect-waf/install/
 weight: 200
----
+---
diff --git a/content/waf/install/disconnected-environment.md b/content/waf/install/disconnected-environment.md
@@ -1,8 +1,8 @@
 ---
 # We use sentence case and present imperative tone
-title: "Deploy NGINX App Protect WAF in a disconnected environment"
+title: "Deploy F5 WAF for NGINX in a disconnected environment"
 # Weights are assigned in increments of 100: determines sorting order
-weight: 200
+weight: 400
 # Creates a table of contents and sidebar, useful for large documents
 toc: false
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
@@ -23,10 +23,4 @@ The design intention for this page is as a standalone page for the operating sys
 
 Instead of having separate top level folders, differences between v4 and v5 will be denoted with whole page sections, tabs, or other unique signifiers.
 
-This reduces the amount of duplicate content, which makes maintainability much simpler and the text more uniform.
-
-With the full context of this section, the page is shorter, being concerned only with one specific method of installation.
-
-This makes it easier to link to specific instructions, and ensures that the customer sees only the critical information they need.
-
 {{</ call-out>}}
diff --git a/content/waf/install/docker.md b/content/waf/install/docker.md
@@ -1,8 +1,8 @@
 ---
 # We use sentence case and present imperative tone
-title: "Deploy NGINX App Protect WAF using Docker"
+title: "Deploy F5 WAF for NGINX using Docker"
 # Weights are assigned in increments of 100: determines sorting order
-weight: 300
+weight: 200
 # Creates a table of contents and sidebar, useful for large documents
 toc: false
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
diff --git a/content/waf/install/kubernetes.md b/content/waf/install/kubernetes.md
@@ -1,15 +1,10 @@
 ---
 # We use sentence case and present imperative tone
-title: "Deploy NGINX App Protect WAF using Kubernetes"
+title: "Deploy F5 WAF for NGINX using Kubernetes"
 # Weights are assigned in increments of 100: determines sorting order
-weight: 400
+weight: 300
 # Creates a table of contents and sidebar, useful for large documents
 toc: false
-nd-banner:
-    enabled: true
-    type: deprecation
-    start-date: 2025-07-07
-    md: /_banners/waf-v5-warning.md
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
 # Intended for internal catalogue and search, case sensitive:
diff --git a/content/waf/install/uninstall.md b/content/waf/install/uninstall.md
@@ -1,6 +1,6 @@
 ---
 # We use sentence case and present imperative tone
-title: "Uninstall NGINX App Protect WAF"
+title: "Uninstall F5 WAF for NGINX"
 # Weights are assigned in increments of 100: determines sorting order
 weight: 600
 # Creates a table of contents and sidebar, useful for large documents
diff --git a/content/waf/install/upgrade.md b/content/waf/install/upgrade.md
@@ -1,6 +1,6 @@
 ---
 # We use sentence case and present imperative tone
-title: "Upgrade NGINX App Protect WAF"
+title: "Upgrade F5 WAF for NGINX"
 # Weights are assigned in increments of 100: determines sorting order
 weight: 500
 # Creates a table of contents and sidebar, useful for large documents
diff --git a/content/waf/install/virtual-environment.md b/content/waf/install/virtual-environment.md
@@ -1,15 +1,10 @@
 ---
 # We use sentence case and present imperative tone
-title: "Deploy NGINX App Protect WAF in a virtual environment"
+title: "Deploy F5 WAF for NGINX in a virtual environment"
 # Weights are assigned in increments of 100: determines sorting order
 weight: 100
 # Creates a table of contents and sidebar, useful for large documents
 toc: false
-nd-banner:
-    enabled: true
-    type: deprecation
-    start-date: 2025-07-07
-    md: /_banners/waf-v4-warning.md
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
 # Intended for internal catalogue and search, case sensitive:
@@ -26,12 +21,12 @@ The design intention for this page is as a standalone page for the operating sys
 
 Instead of having separate top level folders, differences between v4 and v5 will be denoted with whole page sections, tabs, or other unique signifiers.  
 
-This reduces the amount of duplicate content, which makes maintainability much simpler and the text more uniform.
+{{</ call-out>}}
 
-**For an example of a unique signifier, look at the top of this page.**
+This page describes how to install F5 WAF for NGINX on a virtual machine or bare metal environment. To review supported operating systems, please read the [Technical specifications]({{< ref "/waf/fundamentals/technical-specifications.md" >}}) guide.
 
-With the full context of this section, the page is shorter, being concerned only with one specific method of installation.
+There are multiple alternative deployment methods available:
 
-This makes it easier to link to specific instructions, and ensures that the customer sees only the critical information they need.
-
-{{</ call-out>}}
+- [Deploy F5 WAF for NGINX using Docker]({{< ref "/waf/install/docker.md" >}})
+- [Deploy F5 WAF for NGINX using Kubernetes]({{< ref "/waf/install/kubernetes.md" >}})
+- [Deploy F5 WAF for NGINX in a disconnected environment]({{< ref "/waf/install/disconnected-environment.md" >}})
diff --git a/content/waf/support.md b/content/waf/support.md
@@ -4,7 +4,7 @@ title: "Support"
 # Weights are assigned in increments of 100: determines sorting order
 weight: 900
 # Creates a table of contents and sidebar, useful for large documents
-toc: false
+toc: true
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
 # Intended for internal catalogue and search, case sensitive:
@@ -24,4 +24,131 @@ There's lots of examples of existing support pages, some of which may have inclu
 - [NGINX Agent - Support]({{< ref "/agent/support.md" >}})
 - [NGINX Ingress Controller - Commercial support]({{< ref "/nic/troubleshooting/troubleshoot-support.md" >}})
 
-{{</ call-out>}}
+{{</ call-out>}}
+
+## Support policy
+
+F5 WAF for NGINX adheres to the support policy detailed in the following knowledge base article: [K000140156](https://my.f5.com/manage/s/article/K000140156).
+
+## Contact F5 Support
+
+For questions or assistance with installing, troubleshooting, or using F5 WAF for NGINX, contact support through the [MyF5 Customer Portal](https://account.f5.com/myf5).
+
+### Collecting log information
+
+As part of opening a support ticket, you will be asked to collect troubleshooting information for a customer support engineer.
+
+The steps involved depend on your deployment type.
+
+{{< tabs name="log-options" >}}
+
+{{% tab name="Virtual environment" %}}
+
+Get the operating system information:
+
+```shell
+cat /etc/os-release > system_version.txt && uname -r >> system_version.txt && cat /proc/version >> system_version.txt
+```
+
+Collect the package versions:
+
+```shell
+cat /opt/app_protect/VERSION /opt/app_protect/RELEASE > package_versions.txt
+```
+
+You may need a different command depending on the operating system.
+
+```shell
+# Alpine Linux
+apk info -vv | grep -E 'nginx|app-protect' > package_versions.txt
+# Debian / Ubuntu
+apt list --installed | grep -E 'nginx|app-protect' > package_versions.txt
+# RHEL / Amazon Linux / Oracle Linux
+rpm -qa nginx* app-protect* > package_versions.txt
+```
+
+Create a list of files called _tarball-targets.txt_:
+
+```text
+system_version.txt
+package_versions.txt
+/var/log/app_protect/*
+/var/log/nginx/*
+/etc/nginx.conf
+# Add any additional policy or log configuration files
+```
+
+Create a tarball using the list of files:
+
+```shell
+tar cvfz logs.tgz `cat tarball-targets.txt`
+```
+
+{{% /tab %}}
+
+{{% tab name="Docker" %}}
+
+Use _docker_compose_ to create log files:
+
+```shell
+sudo docker compose logs > docker_compose_logs.txt
+```
+
+If a centralized logging system such as the ELK stack is used, you should retrieve them in CSV format instead:
+
+```shell
+sudo docker compose logs > docker_compose_logs.csv
+```
+
+Add the log files to a tarball:
+
+```shell
+tar cvfz logs.tgz docker_compose_logs.txt
+```
+
+{{% /tab %}}
+
+{{% tab name="Kubernetes" %}}
+
+In the following steps, replace `<example-ns>` with the namespace you used to deploy F5 WAF for NGINX.
+
+Verify the pods in your deployment:
+
+```shell
+kubectl get pods -n <example-ns>
+```
+
+Use the following script to collect logs from every pod, which will create a timestamped directory with files after each pod and container:
+
+```shell
+#!/bin/bash
+
+set -x
+
+# Define the namespace variable
+NAMESPACE="<example-ns>"
+
+# Define a directory to store log files
+log_dir="k8s_logs_$(date +%Y%m%d_%H%M%S)"
+mkdir -p "$log_dir"
+
+# Loop through all pods and containers, saving logs to timestamped directories
+for pod in $(kubectl get pods -n $NAMESPACE -o=name | sed 's|pod/||g'); do
+    for container in $(kubectl get pod/$pod -n $NAMESPACE -o=jsonpath='{.spec.containers[*].name}'); do
+        kubectl logs $pod -c $container -n $NAMESPACE > "${log_dir}/${pod}_${container}_logs.txt"
+    done
+done
+```
+
+Once the log files have been saved, run the following command to create a tarball:
+
+```shell
+tar cvfz logs.tgz .
+```
+
+
+{{% /tab %}}
+
+{{< /tabs >}}
+
+Attach the tarball named _logs.tgz_ to your support ticket.
