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
If the default server TLS secret is not configured via
-default-server-tls-secret cli arg or it is not present on the filesystem
at /etc/nginx/secrets/default, the Ingress Controller will configure
NGINX to reject TLS connections to the default server.
Note: The default server is used in NGINX configuration to handle HTTP
and HTTPS request to hosts that are not configured by any Ingress,
VirtualServer or TransportServer resources. The default server simply
returns 404 responses.
Copy file name to clipboardExpand all lines: docs-web/configuration/global-configuration/command-line-arguments.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ Below we describe the available command-line arguments:
15
15
Secret with a TLS certificate and key for TLS termination of the default server.
16
16
17
17
- If not set, certificate and key in the file "/etc/nginx/secrets/default" are used.
18
-
- If a secret is set, but the Ingress controller is not able to fetch it from Kubernetes API, or if a secret is not set and the file "/etc/nginx/secrets/ default" does not exist, the Ingress controller will fail to start.
18
+
- If "/etc/nginx/secrets/default" doesn't exist, the Ingress Controller will configure NGINX to reject TLS connections to the default server.
19
+
- If a secret is set, but the Ingress controller is not able to fetch it from Kubernetes API, or it is not set and the Ingress Controller fails to read the file "/etc/nginx/secrets/default", the Ingress controller will fail to start.
0 commit comments