NGINX Gateway Fabric is Kubernetes policy, so a title count is a weak ownership signal
NGINX Gateway Fabric implements the Kubernetes Gateway API with a control plane and one or more NGINX data planes. Most of its authority comes from Kubernetes resources and the controller configuration, not from a distinctive public home page. A title search can find a small amount of product text while missing a busy gateway deployment.
What ZoomEye returned
The count-only probe ran on 2026-11-18 at 22:44 UTC with sub_type=all, page 1, and pagesize 1. It returned:
-
app="NGINX Gateway Fabric": 0 matches. -
title="NGINX Gateway Fabric": 1 match. -
http.body="NGINX Gateway Fabric": 121 matches.
The body result is the only observation large enough to form a useful research list, and it remains an ambiguous phrase. A page can mention the project in documentation, a status page, or an internal portal. The single title match is not enough to establish a deployment population. The exact query and scope are recorded below.
The control plane and data plane
The official architecture separates a control plane that watches Kubernetes resources from data plane pods that run NGINX and the NGINX Agent. When a Gateway resource is created, the control plane provisions a corresponding data plane deployment and service. The control plane translates Gateway API objects into configuration and sends it to the agent over gRPC. The documentation describes TLS on that channel, with self-signed certificates by default and optional cert-manager integration.
Review who can create GatewayClasses, Gateways, HTTPRoutes, and Secrets. A subject that can modify routes may expose a service or change a hostname even if the public interface never reveals the controller name. Review service types and ingress paths, and confirm that the management namespace cannot be reached from application workloads.
Validate the split-plane model
Check the control plane's RBAC, the data plane's service account, and the certificate rotation process. Test that a new Gateway creates the expected data plane and that an invalid route is rejected or reported. Verify that data plane pods do not have broad Kubernetes API access and that the control plane does not receive client traffic.
Monitor configuration drift in Gateways and HTTPRoutes and record the relevant Kubernetes resource versions. The ZoomEye result can tell an analyst that a search phrase is uncommon, but it cannot establish the route policy, certificate trust, or separation of duties. Use it as one source in an asset record that links external names to the controller and the team that owns them.