Skip to content

Commit

Permalink
Arch note
Browse files Browse the repository at this point in the history
  • Loading branch information
sjberman committed Jan 22, 2024
1 parent db4e671 commit 2a8ba19
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions site/content/overview/gateway-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,12 @@ The following list describes the connections, preceeded by their types in parent
1. (HTTP, HTTPS) A _client_ sends traffic to and receives traffic from any of the _NGINX workers_ on ports 80 and 443.
1. (HTTP, HTTPS) An _NGINX worker_ sends traffic to and receives traffic from the _backends_.

### Differences with NGINX Plus

The previous diagram depicts NGINX Gateway Fabric using NGINX Open Source. NGINX Gateway Fabric with NGINX Plus has the following difference:

- An _admin_ can connect to the NGINX Plus API using port 8765. NGINX only allows connections from localhost.

## Pod readiness

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.
Expand Down

0 comments on commit 2a8ba19

Please sign in to comment.