Skip to content

Commit 59a9a79

Browse files
authored
Merge pull request #12657 from openshift-cherrypick-robot/cherry-pick-4648-to-enterprise-3.10
[enterprise-3.10] Added hostnetwork to the ways to get traffic in
2 parents 2777aaa + aa55022 commit 59a9a79

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

452452

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

0 commit comments

Comments
 (0)