Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tls user guide --default-ssl-certificate clarification #4588

Merged
merged 1 commit into from
Sep 25, 2019
Merged

tls user guide --default-ssl-certificate clarification #4588

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
tls user guide --default-ssl-certificate clarification 
Evidently the `--default-ssl-certificate` option is used not only for the catch-all server, but also for all ingress `tls:` sections that don't have a `secretName` option. This doesn't seem to be documented anywhere, hence this change.
  • Loading branch information
@multi-io
multi-io authored Sep 23, 2019
commit 1a5e2d57a6eb197c403893ae98222ec2adba8f4a
3 changes: 3 additions & 0 deletions docs/user-guide/tls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,9 @@ 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,
add `--default-ssl-certificate=default/foo-tls` in the `nginx-controller` deployment.

The default certificate will also be used for ingress `tls:` sections that do not
have a `secretName` option.

## SSL Passthrough

The [`--enable-ssl-passthrough`](cli-arguments/) flag enables the SSL Passthrough feature, which is disabled by
Expand Down