You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OCPBUGS-64771: Force Global IP forwarding for DPU host mode
Ensure DPU host nodes always use Global IP forwarding mode regardless
of cluster-wide configuration.
- Force ip_forwarding_mode="Global" for dpu-host mode
- Add comprehensive test cases for IP forwarding behavior
- Document DPU host IP forwarding requirements and rationale
DPU hosts require IP forwarding enabled to allow traffic flow between
management and data plane interfaces. This change ensures proper DPU
operation even when cluster-wide IPForwarding is set to Restricted.
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,7 +167,9 @@ OVN-Kubernetes supports specialized hardware deployments such as DPU (Data Proce
167
167
- Multi-network policies and admin network policies
168
168
- Network segmentation features
169
169
170
-
This per-node feature enforcement is implemented through conditional logic in the startup scripts, allowing the same cluster configuration to work across heterogeneous node types. For detailed information about node modes and the technical implementation, see `docs/ovn_node_mode.md`.
170
+
Additionally, **IP forwarding is always forced to Global mode** on DPU host nodes, regardless of the cluster-wide `IPForwarding` setting in `gatewayConfig`. This is required for DPU hosts to properly forward traffic across management and data plane interfaces.
171
+
172
+
This per-node feature enforcement is implemented through conditional logic in the startup scripts, allowing the same cluster configuration to work across heterogeneous node types. For detailed information about node modes, IP forwarding behavior, and the technical implementation, see `docs/ovn_node_mode.md`.
171
173
172
174
These configuration flags are only in the Operator configuration object.
-`ip_forwarding_mode="Global"` (forced to Global to allow traffic forwarding across interfaces)
27
28
- Multi-network, network segmentation, and multi-network policy/admin network policy are gated and not enabled in this mode.
28
29
29
30
### Manifests
@@ -87,6 +88,24 @@ The following table shows how cluster-wide configuration translates to per-node
87
88
- Correct multi-network enablement logic (OVN_MULTI_NETWORK_ENABLE or OVN_NETWORK_SEGMENTATION_ENABLE)
88
89
- Tests verify both positive cases (features enabled in full mode) and negative cases (features disabled in DPU host mode).
89
90
91
+
### IP Forwarding Mode Behavior
92
+
93
+
IP forwarding configuration is handled differently based on the node mode:
94
+
95
+
#### Full Mode (default)
96
+
- Respects the cluster-wide `IPForwarding` configuration from `gatewayConfig`
97
+
- When set to `Global`: enables IP forwarding (`net.ipv4.ip_forward=1`, `net.ipv6.conf.all.forwarding=1`)
98
+
- When set to `Restricted` or empty (default): disables IP forwarding and passes `--disable-forwarding` flag to ovnkube
99
+
100
+
#### DPU Host Mode
101
+
-**Always forces IP forwarding to `Global` mode**, regardless of cluster-wide configuration
102
+
- This is required for DPU hosts to properly forward traffic across management and data plane interfaces
103
+
- The script automatically overrides `ip_forwarding_mode="Global"` when `OVN_NODE_MODE="dpu-host"`
104
+
- System-level IP forwarding is enabled: `net.ipv4.ip_forward=1` and `net.ipv6.conf.all.forwarding=1`
105
+
- The `--disable-forwarding` flag is never passed to ovnkube on DPU host nodes
106
+
107
+
**Rationale**: DPU hosts require IP forwarding to be enabled at all times to allow proper traffic flow between the host management interface and the DPU's data plane interfaces. Disabling IP forwarding on these nodes would break connectivity and prevent proper operation of the DPU hardware offload.
108
+
90
109
### Migration Notes
91
110
92
111
When upgrading clusters that previously relied on ConfigMap-based feature control:
@@ -95,6 +114,7 @@ When upgrading clusters that previously relied on ConfigMap-based feature contro
95
114
2. The startup scripts (both node and control-plane) now contain the authoritative feature enablement logic
96
115
3. Control-plane components automatically enable all features (always run in "full" mode)
97
116
4. DPU host nodes will automatically have incompatible features disabled regardless of previous ConfigMap settings
98
-
5. No manual intervention is required - the migration is handled automatically during the upgrade process
117
+
5. DPU host nodes will have IP forwarding forced to Global mode regardless of the cluster-wide `IPForwarding` setting
118
+
6. No manual intervention is required - the migration is handled automatically during the upgrade process
0 commit comments