Skip to content
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

Disable iptables bridge forwarding on initialization (backport #83) #120

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 19, 2024

Problem:

In the Harvester cluster whose management network has a VLAN ID, the VM will be unable to access the host port or node port with the host IP where the VM is running.

Solution:

Disable net.bridge.bridge-nf-call-iptables to avoid iptables rules affecting bridge forwarding on vlan.init().

We could not disable net.bridge.bridge-nf-call-iptables in the harvester-installer because RKE2 will enable it after harvester-installer.

Related Issue: harvester/harvester#3960

Test plan:

  • Spin up a Harvester whose management network has a VLAN ID
  • Create a VM with VLAN network whose VLAN ID is same with the management network.
  • Curl nodeIP:443 in the VM.

This is an automatic backport of pull request #83 done by [Mergify](https://mergify.com).

@bk201 bk201 requested a review from starbops September 19, 2024 07:42
@starbops starbops merged commit d817431 into v0.5.x Sep 19, 2024
4 checks passed
@mergify mergify bot deleted the mergify/bp/v0.5.x/pr-83 branch September 19, 2024 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants