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

Persist the bridge-nf-call-iptables across rke2 restart (backport #884) #914

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Dec 26, 2024

The bridge-nf-call-iptables should be disabled by network-controller. But rke2 will toggle it back to enable. Need to make sure it stays at disabled.

Problem:
harvester/harvester#7041

Solution:
persist the bridge-nf-call-iptables across rke2 restart

Related Issue:
harvester/harvester#3960

Test plan:

  1. Install Harvester on any Node
  2. Make sure the value is 0 of command sysctl -a | grep net.bridge.bridge-nf-call-iptables
  3. do systemctl restart rke2-server on management node
  4. do systemctl restart rke2-agent on worker node
  5. verify the value of step 2 and make sure it's still zero

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

The bridge-nf-call-iptables should be disabled by network-controller.
But rke2 will toggle it back to enable. Need to make sure it stays
at disabled.

Signed-off-by: Chris Chiu <[email protected]>
(cherry picked from commit 8ff5515)
@mingshuoqiu mingshuoqiu merged commit 94f0055 into v1.3 Dec 27, 2024
7 checks passed
@mingshuoqiu mingshuoqiu deleted the mergify/bp/v1.3/pr-884 branch December 27, 2024 03:04
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