Skip to content

[release-1.3] Should not use loopback addresses #5044

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

Merged
frankbu merged 3 commits into from
Sep 24, 2019
Merged

[release-1.3] Should not use loopback addresses #5044

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f7d6659
fix multi cluster dns docs
hzxuzhonghu Sep 21, 2019
839374f
fix multi cluster dns docs
hzxuzhonghu Sep 21, 2019
fe96c36
ignore multicast spelling check
hzxuzhonghu Sep 23, 2019
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
1 change: 1 addition & 0 deletions .spelling
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -345,6 +345,7 @@ misordered
Mitigations
MongoDB
mongodb
multicast
Multicloud
multicloud
Multicluster
Expand Down
7 changes: 4 additions & 3 deletions content/en/blog/2019/multicluster-version-routing/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,7 +299,7 @@ spec:
protocol: http
resolution: DNS
addresses:
- 127.255.0.3
- 224.0.0.3
endpoints:
- address: ${CLUSTER2_GW_ADDR}
labels:
Expand All @@ -326,8 +326,9 @@ spec:
EOF
{{< /text >}}

The address `127.255.0.3` of the service entry can be any arbitrary unallocated IP.
Using an IP from the loopback range 127.0.0.0/8 is a good choice.
The address `224.0.0.3` of the service entry can be any arbitrary unallocated IP.
Note that loopback range `127.0.0.0/8` should not be used, as it will influence outbound traffic.
Using an IP from the multicast range 224.0.0.0/4 is a good choice.
Check out the
[gateway-connected multicluster example](/docs/setup/install/multicluster/gateways/#configure-the-example-services)
for more details.
Expand Down
14 changes: 6 additions & 8 deletions content/en/docs/setup/install/multicluster/gateways/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,10 +264,8 @@ running in a second cluster. Before you begin:
{{< /tip >}}

If the global services have actual VIPs, you can use those, but otherwise we suggest
using IPs from the loopback range `127.0.0.0/8` that are not already allocated.
These IPs are non-routable outside of a pod.
In this example we'll use IPs in `127.255.0.0/16` which avoids conflicting with
well known IPs such as `127.0.0.1` (`localhost`).
using IPs from the multicast range `224.0.0.0/4` that are not already allocated.
These IPs are not loopback addresses and are non-routable outside of a pod.
Application traffic for these IPs will be captured by the sidecar and routed to the
appropriate remote service.

Expand All @@ -294,7 +292,7 @@ running in a second cluster. Before you begin:
# must be unique for each remote service, within a given cluster.
# This address need not be routable. Traffic for this IP will be captured
# by the sidecar and routed appropriately.
- 127.255.0.2
- 224.0.0.2
endpoints:
# This is the routable address of the ingress gateway in cluster2 that
# sits in front of sleep.foo service. Traffic from the sidecar will be
Expand Down Expand Up @@ -365,7 +363,7 @@ spec:
protocol: http
resolution: STATIC
addresses:
- 127.255.0.2
- 224.0.0.2
endpoints:
- address: ${CLUSTER2_GW_ADDR}
network: external
Expand Down Expand Up @@ -399,7 +397,7 @@ spec:
protocol: http
resolution: DNS
addresses:
- 127.255.0.2
- 224.0.0.2
endpoints:
- address: ${CLUSTER2_GW_ADDR}
network: external
Expand Down Expand Up @@ -459,7 +457,7 @@ spec:
addresses:
# the IP address to which httpbin.bar.global will resolve to
# must be unique for each service.
- 127.255.0.2
- 224.0.0.2
endpoints:
- address: ${CLUSTER2_GW_ADDR}
labels:
Expand Down