Skip to content

Commit 2ffcc46

Browse files
authored
Merge pull request #37407 from jboxman/gh-36979
An egress router pod macvlan is created by cluster
2 parents e250ac0 + 9e315fd commit 2ffcc46

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/nw-egress-router-pod.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ spec:
9595
- name: egress-router-wait
9696
image: {egress-pod-image-url}
9797
----
98-
<1> Before starting the `egress-router` container, create a macvlan network interface on the primary network interface and move that interface into the pod network namespace. You must include the quotation marks around the `"true"` value. To create the macvlan interface on a network interface other than the primary one, set the annotation value to the name of that interface. For example, `eth1`.
98+
<1> The annotation tells {product-title} to create a macvlan network interface on the primary network interface controller (NIC) and move that macvlan interface into the pod's network namespace. You must include the quotation marks around the `"true"` value. To have {product-title} create the macvlan interface on a different NIC interface, set the annotation value to the name of that interface. For example, `eth1`.
9999
<2> IP address from the physical network that the node is on that is reserved for use by the egress router pod. Optional: You can include the subnet length, the `/24` suffix, so that a proper route to the local subnet is set. If you do not specify a subnet length, then the egress router can access only the host specified with the `EGRESS_GATEWAY` variable and no other hosts on the subnet.
100100
<3> Same value as the default gateway used by the node.
101101
<4> External server to direct traffic to. Using this example, connections to the pod are redirected to `203.0.113.25`, with a source IP address of `192.168.12.99`.
@@ -192,7 +192,7 @@ ifdef::dns[]
192192
endif::dns[]
193193
...
194194
----
195-
<1> Before starting the `egress-router` container, create a macvlan network interface on the primary network interface and move that interface into the pod network namespace. You must include the quotation marks around the `"true"` value. To create the macvlan interface on a network interface other than the primary one, set the annotation value to the name of that interface. For example, `eth1`.
195+
<1> The annotation tells {product-title} to create a macvlan network interface on the primary network interface controller (NIC) and move that macvlan interface into the pod's network namespace. You must include the quotation marks around the `"true"` value. To have {product-title} create the macvlan interface on a different NIC interface, set the annotation value to the name of that interface. For example, `eth1`.
196196
<2> IP address from the physical network that the node is on that is reserved for use by the egress router pod. Optional: You can include the subnet length, the `/24` suffix, so that a proper route to the local subnet is set. If you do not specify a subnet length, then the egress router can access only the host specified with the `EGRESS_GATEWAY` variable and no other hosts on the subnet.
197197
<3> Same value as the default gateway used by the node.
198198
ifdef::http[]

0 commit comments

Comments
 (0)