You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit updates tables across the NGINX documentation set by
removing the old bootstrap shortcode or replacing it with the new table
one. Mainframe has better sensible defaults, so the scaffolding provided
by the bootstrap shortcode is no longer necessary.
Copy file name to clipboardExpand all lines: content/agent/about.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,6 @@ For NGINX Agent to work properly with an NGINX Plus instance, the API needs to b
46
46
NGINX Agent allows a gRPC connected control system to register a listener for a specific event. The control mechanism is then invoked when NGINX Agent sends an associated system signal. The source of a notification can be either the NGINX instance or NGINX Agent itself. Here's a list of currently supported events:
|`--api-cert`|`NGINX_AGENT_API_CERT`| Specifies the certificate used by the Agent API. |
@@ -214,9 +214,7 @@ If you are upgrading from an older version, update your configuration accordingl
214
214
|`--tls-enable`|`NGINX_AGENT_TLS_ENABLE`| Enables TLS for secure communications. |
215
215
|`--tls-key`|`NGINX_AGENT_TLS_KEY`| Specifies the path to the certificate key file for TLS. |
216
216
|`--tls-skip-verify`|`NGINX_AGENT_TLS_SKIP_VERIFY`| Insecurely skips verification for gRPC TLS credentials. |
217
-
{{</bootstrap-table>}}
218
-
219
-
<br>
217
+
{{< /table >}}
220
218
221
219
{{< call-out "note" >}}
222
220
Use the `--config-dirs` command-line option, or the `config_dirs` key in the `nginx-agent.conf` file, to identify the directories NGINX Agent can read from or write to. This setting also defines the location to which you can upload config files when using a control plane.
Copy file name to clipboardExpand all lines: content/agent/technical-specifications.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,33 +11,28 @@ This document describes the requirements for NGINX Agent version 2.
11
11
This document provides technical specifications for NGINX Agent. It includes information on supported distributions, deployment environments, NGINX versions, sizing recommendations, and logging.
Copy file name to clipboardExpand all lines: content/ngf/overview/custom-policies.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,16 +15,13 @@ These custom policies follow the Gateway API [Policy Attachment](https://gateway
15
15
Policies are a Kubernetes object that augments the behavior of an object in a standard way. Policies can be attached to one object ([Direct Policy Attachment](#direct-policy-attachment)) or objects in a hierarchy ([Inherited Policy Attachment](#inherited-policy-attachment)).
16
16
The following table summarizes NGINX Gateway Fabric custom policies:
|[ClientSettingsPolicy]({{< ref "/ngf/traffic-management/client-settings.md" >}}) | Configure connection behavior between client and NGINX | Inherited | Gateway, HTTPRoute, GRPCRoute | No | Yes | v1alpha1 |
23
22
|[ObservabilityPolicy]({{< ref "/ngf/monitoring/tracing.md" >}}) | Define settings related to tracing, metrics, or logging | Direct | HTTPRoute, GRPCRoute | Yes | No | v1alpha2 |
24
23
|[UpstreamSettingsPolicy]({{< ref "/ngf/traffic-management/upstream-settings.md" >}}) | Configure connection behavior between NGINX and backend | Direct | Service | Yes | Yes | v1alpha1 |
25
24
26
-
{{< /bootstrap-table >}}
27
-
28
25
{{< call-out "important" >}}
29
26
If attaching a Policy to a Route, that Route must not share a hostname:port/path combination with any other Route that is not referenced by the same Policy. If it does, the Policy will be rejected. This is because the Policy would end up affecting other Routes that it is not attached to.
| GatewayClass | Supported | Not supported | Supported | v1 | Standard |
57
-
58
-
{{< /bootstrap-table >}}
54
+
{{< /table >}}
59
55
60
56
NGINX Gateway Fabric supports a single GatewayClass resource configured with the `--gatewayclass` flag of the [controller]({{< ref "/ngf/reference/cli-help.md#controller">}}) command.
61
57
@@ -77,13 +73,11 @@ NGINX Gateway Fabric supports a single GatewayClass resource configured with the
Custom policies are NGINX Gateway Fabric-specific CRDs (Custom Resource Definitions) that support features such as tracing, and client connection settings. These important data-plane features are not part of the Gateway API specifications.
371
348
While these CRDs are not part of the Gateway API, the mechanism to attach them to Gateway API resources is part of the Gateway API. See the [Policy Attachment documentation](https://gateway-api.sigs.k8s.io/references/policy-attachment/).
0 commit comments