Skip to content

Commit 2a8ba19

Browse files
committed
Arch note
1 parent db4e671 commit 2a8ba19

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

site/content/overview/gateway-architecture.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,12 @@ The following list describes the connections, preceeded by their types in parent
9292
1. (HTTP, HTTPS) A _client_ sends traffic to and receives traffic from any of the _NGINX workers_ on ports 80 and 443.
9393
1. (HTTP, HTTPS) An _NGINX worker_ sends traffic to and receives traffic from the _backends_.
9494

95+
### Differences with NGINX Plus
96+
97+
The previous diagram depicts NGINX Gateway Fabric using NGINX Open Source. NGINX Gateway Fabric with NGINX Plus has the following difference:
98+
99+
- An _admin_ can connect to the NGINX Plus API using port 8765. NGINX only allows connections from localhost.
100+
95101
## Pod readiness
96102

97103
The `nginx-gateway` container includes a readiness endpoint available through the path `/readyz`. A [readiness probe](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-readiness-probes) periodically checks the endpoint on startup, returning a `200 OK` response when the pod can accept traffic for the data plane. Once the control plane successfully starts, the pod becomes ready.

0 commit comments

Comments
 (0)