|
1 | 1 | # Design Principles
|
2 | 2 |
|
3 | 3 | The aim of the NGINX Kubernetes Gateway is to become a fundamental infrastructure component within a Kubernetes cluster,
|
4 |
| -serving as both an ingress and egress point for traffic directed towards the services (applications) running |
5 |
| -within or outside the cluster. Leveraging NGINX as a data plane technology, it harnesses the well-established reputation |
6 |
| -of NGINX as an open-source project widely recognized for its role as a web server, proxy, load balancer, and content |
7 |
| -cache. NGINX is renowned for its stability, high performance, security, and rich feature set, positioning it as a |
8 |
| -critical infrastructure tool. Notably, once properly configured and operational, NGINX requires minimal attention, |
9 |
| -making it reliable and "boring" software. |
| 4 | +serving as both an ingress and egress point for traffic directed towards the services (applications) running within or |
| 5 | +outside the cluster. Leveraging NGINX as a data plane technology, it harnesses the well-established reputation of NGINX |
| 6 | +as an open-source project widely recognized for its role as a web server, proxy, load balancer, and content cache. NGINX |
| 7 | +is renowned for its stability, high performance, security, and rich feature set, positioning it as a critical |
| 8 | +infrastructure tool. Notably, once properly configured and operational, NGINX requires minimal attention, making it |
| 9 | +reliable and steady software. |
10 | 10 |
|
11 | 11 | The NGINX Kubernetes Gateway aims to embody the same qualities as NGINX and become familiar, trustworthy and reliable
|
12 | 12 | software. The principles outlined below serve as a guide for engineering the NGINX Kubernetes Gateway with the intention
|
@@ -41,9 +41,9 @@ policies.
|
41 | 41 |
|
42 | 42 | ## Observability
|
43 | 43 |
|
44 |
| -We provide comprehensive logging, metrics, and tracing capabilities to gain insights into our behavior and |
45 |
| -performance. We prioritize Kubernetes-native observability tools like Prometheus, Grafana, and distributed |
46 |
| -tracing systems to help users monitor the health of NGINX Kubernetes Gateway and to assist in diagnosing issues. |
| 44 | +We provide comprehensive logging, metrics, and tracing capabilities to gain insights into our behavior and performance. |
| 45 | +We prioritize Kubernetes-native observability tools like Prometheus, Grafana, and distributed tracing systems to help |
| 46 | +users monitor the health of NGINX Kubernetes Gateway and to assist in diagnosing issues. |
47 | 47 |
|
48 | 48 | ## Ease of Use
|
49 | 49 |
|
|
0 commit comments