DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update tls.md

Browse source 
Believe this nginx runtime flag was updated to `default-server-tls-secret`
This commit is contained in:
Conrad J 2023-06-02 22:35:52 -04:00 committed by GitHub
parent 179aa898f4
commit 074cbd0305
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/user-guide/tls.md
View file

@ -33,13 +33,13 @@ for requests that do not match any of the configured server names.
This configuration works out-of-the-box for HTTP traffic. This configuration works out-of-the-box for HTTP traffic.
For HTTPS, a certificate is naturally required. For HTTPS, a certificate is naturally required.
For this reason the Ingress controller provides the flag `--default-ssl-certificate`. For this reason the Ingress controller provides the flag `--default-ssl-certificate-secret`.
The secret referred to by this flag contains the default certificate to be used when The secret referred to by this flag contains the default certificate to be used when
accessing the catch-all server. accessing the catch-all server.
If this flag is not provided NGINX will use a self-signed certificate. If this flag is not provided NGINX will use a self-signed certificate.
For instance, if you have a TLS secret `foo-tls` in the `default` namespace, For instance, if you have a TLS secret `foo-tls` in the `default` namespace,
add `--default-ssl-certificate=default/foo-tls` in the `nginx-controller` deployment. add `--default-server-tls-secret=default/foo-tls` in the `nginx-controller` deployment.
The default certificate will also be used for ingress `tls:` sections that do not The default certificate will also be used for ingress `tls:` sections that do not
have a `secretName` option. have a `secretName` option.