Skip to content

Commit 91a220b

Browse files
authored
Merge pull request #4648 from knobunc/fix/explain-host-network
Added hostnetwork to the ways to get traffic in
2 parents d9b04b3 + 37384f2 commit 91a220b

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

dev_guide/getting_traffic_into_cluster.adoc

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -521,6 +521,25 @@ down, the virtual IP address is automatically transferred to another host in the
521521
pool.
522522

523523

524+
[[host-network]]
525+
== Using Host Networking
526+
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
536+
system:serviceaccount:default:someserviceaccountname`.
537+
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.
542+
524543
[[ingress-load-balancer]]
525544
== Non-Cloud Edge Router Load Balancer
526545

0 commit comments

Comments
 (0)