luxolus/open-consul
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

docs: remove note on ingress gateway hosts field needing a port number (#10827)

Browse source 
This was necessary in older versions of Consul, but was obsoleted by
making Consul add the port number itself when constructing the Envoy
configuration.
This commit is contained in:
Chris Piraino 2021-08-11 16:36:57 -05:00 committed by GitHub
parent db59597cac
commit b302a926c6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
website/content/docs/connect/config-entries/ingress-gateway.mdx
View file

@ -205,11 +205,11 @@ Listeners = [
Services = [ Services = [
{ {
Name = "api" Name = "api"
Hosts = ["foo.example.com", "foo.example.com:4567"] Hosts = ["foo.example.com"]
}, },
{ {
Name = "web" Name = "web"
Hosts = ["website.example.com", "website.example.com:4567"] Hosts = ["website.example.com"]
} }
] ]
} }
@ -233,9 +233,9 @@ spec:
protocol: http protocol: http
services: services:
- name: api - name: api
hosts: ['foo.example.com', 'foo.example.com:4567'] hosts: ['foo.example.com']
- name: web - name: web
hosts: ['website.example.com', 'website.example.com:4567'] hosts: ['website.example.com']
``` ```
```json ```json
@ -261,11 +261,11 @@ spec:
"Services": [ "Services": [
{ {
"Name": "api", "Name": "api",
"Hosts": ["foo.example.com", "foo.example.com:4567"] "Hosts": ["foo.example.com"]
}, },
{ {
"Name": "web", "Name": "web",
"Hosts": ["website.example.com", "website.example.com:4567"] "Hosts": ["website.example.com"]
} }
] ]
} }
@ -310,12 +310,12 @@ Listeners = [
{ {
Namespace = "frontend" Namespace = "frontend"
Name = "api" Name = "api"
Hosts = ["foo.example.com", "foo.example.com:4567"] Hosts = ["foo.example.com"]
}, },
{ {
Namespace = "frontend" Namespace = "frontend"
Name = "web" Name = "web"
Hosts = ["website.example.com", "website.example.com:4567"] Hosts = ["website.example.com"]
} }
] ]
} }
@ -342,10 +342,10 @@ spec:
services: services:
- name: api - name: api
namespace: frontend namespace: frontend
hosts: ['foo.example.com', 'foo.example.com:4567'] hosts: ['foo.example.com']
- name: web - name: web
namespace: frontend namespace: frontend
hosts: ['website.example.com', 'website.example.com:4567'] hosts: ['website.example.com']
``` ```
```json ```json
@ -374,12 +374,12 @@ spec:
{ {
"Namespace": "frontend", "Namespace": "frontend",
"Name": "api", "Name": "api",
"Hosts": ["foo.example.com", "foo.example.com:4567"] "Hosts": ["foo.example.com"]
}, },
{ {
"Namespace": "frontend", "Namespace": "frontend",
"Name": "web", "Name": "web",
"Hosts": ["website.example.com", "website.example.com:4567"] "Hosts": ["website.example.com"]
} }
] ]
} }
@ -830,13 +830,7 @@ spec:
be used as part of the host to match multiple hosts, but only in the be used as part of the host to match multiple hosts, but only in the
leftmost DNS label. This ensures that all defined hosts are valid DNS leftmost DNS label. This ensures that all defined hosts are valid DNS
records. For example, \`*.example.com\` is valid, while \`example.*\` and records. For example, \`*.example.com\` is valid, while \`example.*\` and
\`*-suffix.example.com\` are not.<br><br> \`*-suffix.example.com\` are not.`,
<b>Note:</b> If a well-known port is not used, i.e. a port other than 80
(http) or 443 (https), then the port must be appended to the host to
correctly match traffic. This is defined in the [HTTP/1.1 RFC](https://tools.ietf.org/html/rfc2616#section-14.23). If TLS is
enabled, then the host <b>without</b> the port must be added to the \`Hosts\`
field as well. TLS verification only matches against the hostname of the
incoming connection, and thus does not take into account the port.`,
}, },
], ],
}, },