Skip to content

Commit 19f6441

Browse files
authored
Merge pull request #12658 from openshift-cherrypick-robot/cherry-pick-4648-to-enterprise-3.9
[enterprise-3.9] Added hostnetwork to the ways to get traffic in
2 parents 4415f52 + 385a39c commit 19f6441

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
@@ -445,6 +445,25 @@ down, the virtual IP address is automatically transferred to another host in the
445445
pool.
446446

447447

448+
[[host-network]]
449+
== Using Host Networking
450+
451+
You can choose to let the pods use the networking of the host that
452+
they are on rather than containerizing the networking and using
453+
the SDN. This is how the router works, and it can be a useful
454+
technique when you have to proxy a Layer 7 protocol that is not
455+
http/https/or TLS with SNI. You can look at the way the router is
456+
configured to see how to set it up, but basically you need to set
457+
`hostNetwork: true` in the pod definition, and then run the router
458+
with a service account that has the `hostnetwork` permission. You can
459+
grant the permission with `oc adm policy add-scc-to-user hostnetwork
460+
system:serviceaccount:default:someserviceaccountname`.
461+
462+
Once configured, the pod can access all of the network interfaces on
463+
the node that it is running on, including the host's SDN interface.
464+
This allows you to make your own proxy, or allows you to run a program
465+
directly on the host interfaces directly.
466+
448467
[[ingress-load-balancer]]
449468
== Non-Cloud Edge Router Load Balancer
450469

0 commit comments

Comments
 (0)