whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More consistent naming of services in Ingress docs (#15718)

Browse Source 
It switched from a naming scheme of service1/service2 to s1/s2. That can be confusing for new people, and I propose we stick to only one naming scheme.
This commit is contained in:
Andreas Lindhé
2019-08-08 00:33:18 +02:00
committed by Kubernetes Prow Robot
parent d3c216fedc
commit c02cf959b7
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/ingress.md
+8 -8
View File
@@ -215,7 +215,7 @@ Events:
``` ```
The Ingress controller provisions an implementation-specific load balancer The Ingress controller provisions an implementation-specific load balancer
that satisfies the Ingress, as long as the Services (`s1`, `s2`) exist. that satisfies the Ingress, as long as the Services (`service1`, `service2`) exist.
When it has done so, you can see the address of the load balancer at the When it has done so, you can see the address of the load balancer at the
Address field. Address field.
@@ -230,9 +230,9 @@ you are using, you may need to create a default-http-backend
Name-based virtual hosts support routing HTTP traffic to multiple host names at the same IP address. Name-based virtual hosts support routing HTTP traffic to multiple host names at the same IP address.
```none ```none
foo.bar.com --| |-> foo.bar.com s1:80 foo.bar.com --| |-> foo.bar.com service1:80
| 178.91.123.132 | | 178.91.123.132 |
bar.foo.com --| |-> bar.foo.com s2:80 bar.foo.com --| |-> bar.foo.com service2:80
``` ```
The following Ingress tells the backing load balancer to route requests based on The following Ingress tells the backing load balancer to route requests based on
@@ -384,7 +384,7 @@ Rules:
Host Path Backends Host Path Backends
---- ---- -------- ---- ---- --------
foo.bar.com foo.bar.com
/foo s1:80 (10.8.0.90:80) /foo service1:80 (10.8.0.90:80)
Annotations: Annotations:
nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/rewrite-target: /
Events: Events:
@@ -407,14 +407,14 @@ spec:
http: http:
paths: paths:
- backend: - backend:
serviceName: s1 serviceName: service1
servicePort: 80 servicePort: 80
path: /foo path: /foo
- host: bar.baz.com - host: bar.baz.com
http: http:
paths: paths:
- backend: - backend:
serviceName: s2 serviceName: service2
servicePort: 80 servicePort: 80
path: /foo path: /foo
.. ..
@@ -438,9 +438,9 @@ Rules:
Host Path Backends Host Path Backends
---- ---- -------- ---- ---- --------
foo.bar.com foo.bar.com
/foo s1:80 (10.8.0.90:80) /foo service1:80 (10.8.0.90:80)
bar.baz.com bar.baz.com
/foo s2:80 (10.8.0.91:80) /foo service2:80 (10.8.0.91:80)
Annotations: Annotations:
nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress.kubernetes.io/rewrite-target: /
Events: Events: