From 2e3f32891be1521af1f9ad51049804a365b17bf0 Mon Sep 17 00:00:00 2001 From: Manuel de Brito Fontes Date: Mon, 21 Aug 2017 19:38:22 -0300 Subject: [PATCH] Update ssl-passthrough docs --- controllers/nginx/configuration.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/controllers/nginx/configuration.md b/controllers/nginx/configuration.md index 6ffa79f3e..90c1fbc53 100644 --- a/controllers/nginx/configuration.md +++ b/controllers/nginx/configuration.md @@ -220,9 +220,10 @@ To configure this setting globally for all Ingress rules, the `limit-rate-after` ### SSL Passthrough The annotation `ingress.kubernetes.io/ssl-passthrough` allows to configure TLS termination in the pod and not in NGINX. -This is possible thanks to the [ngx_stream_ssl_preread_module](https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html) that enables the extraction of the server name information requested through SNI from the ClientHello message at the preread phase. -**Important:** using the annotation `ingress.kubernetes.io/ssl-passthrough` invalidates all the other available annotations. This is because SSL Passthrough works in L4 (TCP). +**Important:** +- Using the annotation `ingress.kubernetes.io/ssl-passthrough` invalidates all the other available annotations. This is because SSL Passthrough works in L4 (TCP). +- The use of this annotation requires the flag `--enable-ssl-passthrough` (By default it is disabled) ### Secure backends