Skip to content

Commit 427eb66

Browse files
authored
Merge pull request #12661 from ahardin-rh/4648-followup
Follow-up edits to PR#4648
2 parents 91a220b + edefd37 commit 427eb66

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

dev_guide/getting_traffic_into_cluster.adoc

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -520,25 +520,23 @@ virtual IP address to the host in a configured pool of hosts. If the host goes
520520
down, the virtual IP address is automatically transferred to another host in the
521521
pool.
522522

523-
524523
[[host-network]]
525524
== Using Host Networking
526525

527-
You can choose to let the pods use the networking of the host that
528-
they are on rather than containerizing the networking and using
529-
the SDN. This is how the router works, and it can be a useful
530-
technique when you have to proxy a Layer 7 protocol that is not
531-
http/https/or TLS with SNI. You can look at the way the router is
532-
configured to see how to set it up, but basically you need to set
533-
`hostNetwork: true` in the pod definition, and then run the router
534-
with a service account that has the `hostnetwork` permission. You can
535-
grant the permission with `oc adm policy add-scc-to-user hostnetwork
526+
You can choose to let the pods use the networking of the host that they are on
527+
rather than containerizing the networking and using the SDN. This is how the
528+
router works, and it can be a useful technique when you have to proxy a Layer 7
529+
protocol that is not http/https/ or TLS with SNI. You can look at the way the
530+
router is configured to see how to set it up, but basically you must set
531+
`hostNetwork: true` in the pod definition, and then run the router with a
532+
service account that has the `hostnetwork` permission. You can grant the
533+
permission with `oc adm policy add-scc-to-user hostnetwork
536534
system:serviceaccount:default:someserviceaccountname`.
537535

538-
Once configured, the pod can access all of the network interfaces on
539-
the node that it is running on, including the host's SDN interface.
540-
This allows you to make your own proxy, or allows you to run a program
541-
directly on the host interfaces directly.
536+
Once configured, the pod can access all of the network interfaces on the node
537+
that it is running on, including the host's SDN interface. This allows you to
538+
make your own proxy, or allows you to run a program directly on the host
539+
interfaces directly.
542540

543541
[[ingress-load-balancer]]
544542
== Non-Cloud Edge Router Load Balancer

0 commit comments

Comments
 (0)