feat: NGINX One Console for NIC with Agent 3 with F5 WAF

[AlexFenlon]

Proposed changes

Adds documentation for NGINX Ingress Controller images that include NGINX Agent 3, available starting with NIC 5.5.0. These images use the -agent suffix and are required for connecting WAF-enabled deployments to NGINX One Console.

What changed and why:

• registry-download.md: Added pull and push entries for WAF v4 (nginx-ic-nap) and WAF v5 (nginx-ic-nap-v5) images with the -agent suffix. Added missing -ubi8 tag for nginx-ic-nap, confirmed against the release pipeline config.

• technical-specifications.md: Added rows for all new -agent image variants across WAF v4 and v5, including alpine-fips-agent, agent (Debian), ubi-agent, ubi8, and ubi8-agent. Added missing ubi8 non-agent row for WAF v4.

• security-monitoring.md: Restructured from a single NIM-only guide into tabbed NIM | NGINX One Console sections. The NGINX One Console tab covers NGINX Agent 3 deployment steps (Helm and Manifests), including the Agent 3 nginx-agent.conf with logs-nap and allowed_directories for WAF. Added upgrade path from NIM to NGINX One Console. Note: nested tabs were avoided due to a known CSS issue in the Hugo theme where descendant selectors bleed into nested .tab-contents containers, causing both inner tabs to render simultaneously. Bold headers are used instead.

• add-nic.md: Added "Choosing the right image" table, WAF v4/v5 Helm commands, inner ConfigMap tabs (Without WAF / With WAF), two additional volume mounts required by NGINX Agent 3 (agent-etc, agent-dynamic), a WAF security monitoring section linking to security-monitoring.md, and updated troubleshooting for Agent 2 vs Agent 3.

Implementation PR: nginx/kubernetes-ingress#9740

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/1897/

---