mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
18 lines
1.4 KiB
Plaintext
18 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * networking/nw-osp-loadbalancer-limitations.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="nw-osp-loadbalancer-etp-local_{context}"]
|
|
= Local external traffic policies
|
|
|
|
[role="_abstract"]
|
|
You can set the external traffic policy (ETP) parameter, `.spec.externalTrafficPolicy`, on a load balancer service to preserve the source IP address of incoming traffic when it reaches service endpoint pods.
|
|
|
|
If your cluster uses the Amphora Octavia provider, the source IP of the traffic is replaced with the IP address of the Amphora VM. This behavior does not occur if your cluster uses the OVN Octavia provider.
|
|
|
|
Having the `ETP` option set to `Local` requires creating health monitors for the load balancer. Without health monitors, traffic can be routed to a node that does not have a functional endpoint, which causes the connection to drop. To force Cloud Provider OpenStack to create health monitors, you must set the value of the `create-monitor` option in the cloud provider configuration to `true`.
|
|
|
|
In {rh-openstack} 16.2, the OVN Octavia provider does not support health monitors. Therefore, setting the ETP to `Local` is unsupported.
|
|
|
|
In {rh-openstack} 16.2, the Amphora Octavia provider does not support HTTP monitors on UDP pools. As a result, UDP load balancer services have `UDP-CONNECT` monitors created instead. Due to implementation details, this configuration only functions properly with the OVN-Kubernetes CNI plugin.
|