-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Ocpbugs 25129: metallb should make sure that secondary nics are forwarding traffic #83087
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
:_mod-docs-content-type: PROCEDURE | ||
[id="nw-metallb-configure-secondary-interface_{context}"] | ||
= Configuring MetalLB with secondary networks | ||
|
||
From {product-title} 4.14 the default network behavior is to not allow forwarding of IP packets between network interfaces. Therefore, when MetalLB is configured on a secondary interface, you need to add a machine configuration to enable IP forwarding for only the required interfaces. | ||
[NOTE] | ||
==== | ||
{product-title} clusters upgraded from 4.13 are not affected because a global parameter is set during upgrade to enable global IP forwarding. | ||
==== | ||
|
||
To enable IP forwarding for the secondary interface, you have two options: | ||
|
||
* Enable IP forwarding for all interfaces. | ||
* Enable IP forwarding for a specific interface. | ||
+ | ||
[NOTE] | ||
==== | ||
Enabling IP forwarding for a specific interface provides more granular control, while enabling it for all interfaces applies a global setting. | ||
==== | ||
|
||
.Procedure | ||
|
||
. Enable forwarding for a specific secondary interface, such as `bridge-net` by creating and applying a `MachineConfig` CR. | ||
|
||
.. Create the `MachineConfig` CR to enable IP forwarding for the specified secondary interface named `bridge-net`. | ||
|
||
.. Save the following YAML in the `enable-ip-forward.yaml` file: | ||
+ | ||
[source,yaml] | ||
---- | ||
apiVersion: machineconfiguration.openshift.io/v1 | ||
kind: MachineConfig | ||
metadata: | ||
labels: | ||
machineconfiguration.openshift.io/role: <node_role> <1> | ||
name: 81-enable-global-forwarding | ||
spec: | ||
config: | ||
ignition: | ||
version: 3.2.0 | ||
storage: | ||
files: | ||
- contents: | ||
source: data:text/plain;charset=utf-8;base64,`echo -e "net.ipv4.conf.bridge-net.forwarding = 1\nnet.ipv6.conf.bridge-net.forwarding = 1\nnet.ipv4.conf.bridge-net.rp_filter = 0\nnet.ipv6.conf.bridge-net.rp_filter = 0" | base64 -w0` | ||
verification: {} | ||
filesystem: root | ||
mode: 644 | ||
path: /etc/sysctl.d/enable-global-forwarding.conf | ||
osImageURL: "" | ||
---- | ||
+ | ||
<1> Node role where you want to enable IP forwarding, for example, `worker` | ||
|
||
.. Apply the configuration by running the following command: | ||
+ | ||
[source,terminal] | ||
---- | ||
$ oc apply -f enable-ip-forward.yaml | ||
---- | ||
|
||
. Alternatively, you can enable IP forwarding globally by running the following command: | ||
+ | ||
[source,terminal] | ||
---- | ||
$ oc patch network.operator cluster -p '{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"gatewayConfig":{"ipForwarding": "Global"}}}}} | ||
---- |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renders OK on the docs.openshift.com preview, but you'll want to check the docs.redhat.com preview after merge; hard to say if the lack of the line space breaks anything there.