1614027cd4
* clarify link * Add section headers * console blocks * grpc example json was not valid * multi-tls update text The preceding point 1 related to4f2cb51ef8/ingress/controllers/nginx/examples/ingress.yamland the deployments referenced in4f2cb51ef8/ingress/controllers/nginx/examples/README.mdThey are not relevant to the current instructions. * add whitespace around parens * grammar setup would be a proper noun, but it is not the intended concept, which is a state * grammar * is-only * via * Use bullets for choices * ingress-controller nginx is a distinct brand. generally this repo talks about ingress-controller, although it is quite inconsistent about how... * drop stray paren * OAuth is a brand and needs an article here also GitHub is a brand * Indent text under numbered lists * use e.g. * Document that customer header config maps changes do not trigger updates This should be removed if https://github.com/kubernetes/ingress-nginx/issues/5238 is fixed. * article * period * infinitive verb + period * clarify that the gRPC server is responsible for listening for TCP traffic and not some other part of the backend application * avoid using ; and reword * whitespace * brand: gRPC * only-does is the right form `for` adds nothing here * spelling: GitHub * punctuation `;` is generally not the right punctuation... * drop stray `to` * sentence * backticks * fix link * Improve readability of compare/vs * Renumber list * punctuation * Favor Ingress-NGINX and Ingress NGINX * Simplify custom header restart text * Undo typo damage Co-authored-by: Josh Soref <jsoref@users.noreply.github.com>
93 lines
2.6 KiB
Markdown
93 lines
2.6 KiB
Markdown
# Multi TLS certificate termination
|
|
|
|
This example uses 2 different certificates to terminate SSL for 2 hostnames.
|
|
|
|
1. Create tls secrets for foo.bar.com and bar.baz.com as indicated in the yaml
|
|
2. Create [multi-tls.yaml](multi-tls.yaml)
|
|
|
|
This should generate a segment like:
|
|
```console
|
|
$ kubectl exec -it ingress-nginx-controller-6vwd1 -- cat /etc/nginx/nginx.conf | grep "foo.bar.com" -B 7 -A 35
|
|
server {
|
|
listen 80;
|
|
listen 443 ssl http2;
|
|
ssl_certificate /etc/nginx-ssl/default-foobar.pem;
|
|
ssl_certificate_key /etc/nginx-ssl/default-foobar.pem;
|
|
|
|
|
|
server_name foo.bar.com;
|
|
|
|
|
|
if ($scheme = http) {
|
|
return 301 https://$host$request_uri;
|
|
}
|
|
|
|
|
|
|
|
location / {
|
|
proxy_set_header Host $host;
|
|
|
|
# Pass Real IP
|
|
proxy_set_header X-Real-IP $remote_addr;
|
|
|
|
# Allow websocket connections
|
|
proxy_set_header Upgrade $http_upgrade;
|
|
proxy_set_header Connection $connection_upgrade;
|
|
|
|
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
|
proxy_set_header X-Forwarded-Host $host;
|
|
proxy_set_header X-Forwarded-Proto $pass_access_scheme;
|
|
|
|
proxy_connect_timeout 5s;
|
|
proxy_send_timeout 60s;
|
|
proxy_read_timeout 60s;
|
|
|
|
proxy_redirect off;
|
|
proxy_buffering off;
|
|
|
|
proxy_http_version 1.1;
|
|
|
|
proxy_pass http://default-http-svc-80;
|
|
}
|
|
```
|
|
|
|
And you should be able to reach your nginx service or http-svc service using a hostname switch:
|
|
```console
|
|
$ kubectl get ing
|
|
NAME RULE BACKEND ADDRESS AGE
|
|
foo-tls - 104.154.30.67 13m
|
|
foo.bar.com
|
|
/ http-svc:80
|
|
bar.baz.com
|
|
/ nginx:80
|
|
|
|
$ curl https://104.154.30.67 -H 'Host:foo.bar.com' -k
|
|
CLIENT VALUES:
|
|
client_address=10.245.0.6
|
|
command=GET
|
|
real path=/
|
|
query=nil
|
|
request_version=1.1
|
|
request_uri=http://foo.bar.com:8080/
|
|
|
|
SERVER VALUES:
|
|
server_version=nginx: 1.9.11 - lua: 10001
|
|
|
|
HEADERS RECEIVED:
|
|
accept=*/*
|
|
connection=close
|
|
host=foo.bar.com
|
|
user-agent=curl/7.35.0
|
|
x-forwarded-for=10.245.0.1
|
|
x-forwarded-host=foo.bar.com
|
|
x-forwarded-proto=https
|
|
|
|
$ curl https://104.154.30.67 -H 'Host:bar.baz.com' -k
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>Welcome to nginx on Debian!</title>
|
|
|
|
$ curl 104.154.30.67
|
|
default backend - 404
|
|
```
|