docs: add host network security#1034
Open
Yu-Jack wants to merge 2 commits into
Open
Conversation
|
Yu-Jack
force-pushed
the
HARV-5681
branch
4 times, most recently
from
0cd7a79 to
8c6d767
Compare
Yu-Jack
requested review from
a team,
Copilot,
ibrokethecloud,
rrajendran17 and
starbops
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds new documentation for hardening Harvester host inbound traffic using iptables, and updates the installation “Network Requirements” page to provide a more structured, role-specific port matrix (including addon port tables).
Changes:
- Added a new “Host Network Security” page describing an iptables chain approach, CloudInit persistence, and troubleshooting/upgrade considerations.
- Refactored “Network Requirements” to list inbound ports per node role, including bind-address context and an addon-specific port section (kubeovn-operator).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
docs/networking/host-network-security.md |
New page documenting iptables-based host inbound filtering, CloudInit persistence, and debugging guidance. |
docs/install/requirements.md |
Replaces the legacy port list with role-specific port tables and adds addon port requirements tables. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
pohanhuang
reviewed
May 15, 2026
pohanhuang
left a comment
pohanhuang
left a comment
There was a problem hiding this comment.
LGTM from a documentation structure perspective.
I'm not familiar with the iptables/networking area, so I'll defer to the networking folks for a deeper review.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem:
Solution:
Related Issue(s):
harvester/harvester#5681
Test plan:
Technical writer can skip this section.
All tests are tested on two nodes cluster (default role). Although sometimes the logs appear, those are false positives and harmless. We can ignore it.
upgrade (false positive traffic)
I tested the upgrade from v1.7.0 -> v1.7.1 -> v1.8.0 with iptables rules. It works well, but I still put on dropping the rules as the final solution during the upgrade.
v1.7.0 -> v1.7.1
v1.7.1 -> v1.8.0
After the upgrade, these logs will show up. But, these are false positives.
storage network (no missing traffic)
kubeovn
VM communication
Before:
After:
node1:
node2:
e2e api test
Guest Cluster
Additional documentation or context