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
Set Service address in Gateway Status (nginx#1141)
Problem: NGF would only set the Gateway Status to the IP address of the NGF Pod. However, a Service will generally be the entrypoint, so we need to set that address in the status for application developers.
Solution: Using a CLI argument to identify the Service that is linked to this NGF Pod, we will get the Service and set the Addresses accordingly. LoadBalancer Service will set to the ingress IP and/or Hostname. If no Service exists or there is an error, then the Pod IP is used.
We also shouldn't deploy a Service for conformance tests now, since they could be run in an environment where NodePort doesn't work (like kind). These tests will use the Pod IP.
Copy file name to clipboardExpand all lines: docs/cli-help.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ Flags:
20
20
|`gatewayclass`|`string`| The name of the GatewayClass resource. Every NGINX Gateway Fabric must have a unique corresponding GatewayClass resource. |
21
21
|`gateway`|`string`| The namespaced name of the Gateway resource to use. Must be of the form: `NAMESPACE/NAME`. If not specified, the control plane will process all Gateways for the configured GatewayClass. However, among them, it will choose the oldest resource by creation timestamp. If the timestamps are equal, it will choose the resource that appears first in alphabetical order by {namespace}/{name}. |
22
22
|`config`|`string`| The name of the NginxGateway resource to be used for this controller's dynamic configuration. Lives in the same Namespace as the controller. |
23
+
|`service`|`string`| The name of the Service that fronts this NGINX Gateway Fabric Pod. Lives in the same Namespace as the controller. |
23
24
|`metrics-disable`|`bool`| Disable exposing metrics in the Prometheus format. (default false) |
24
25
|`metrics-listen-port`|`int`| Sets the port where the Prometheus metrics are exposed. Format: `[1024 - 65535]` (default `9113`) |
25
26
|`metrics-secure-serving`|`bool`| Configures if the metrics endpoint should be secured using https. Please note that this endpoint will be secured with a self-signed certificate. (default false) |
0 commit comments