Update the known limitation of global ip pool selection - #1101
Conversation
2a8558b to
5d02b61
Compare
|
5d02b61 to
0b33c6d
Compare
There was a problem hiding this comment.
Pull request overview
Updates Harvester documentation to describe and surface a known limitation where guest-cluster LoadBalancer IP allocation may fall back to a global IP pool even when the requested network differs, and links the limitation from the IP pool selection policy docs.
Changes:
- Adds a troubleshooting entry describing the “unexpected global IP pool selection” behavior and suggested workarounds.
- Adds notes in IP pool documentation explaining global pool behavior and linking to the troubleshooting entry.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/troubleshooting/rancher.md | Adds a troubleshooting section documenting the global IP pool fallback limitation and workarounds. |
| docs/networking/ippool.md | Adds notes about global IP pools and links to the new troubleshooting section. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
0b33c6d to
f0c0c6d
Compare
f0c0c6d to
018d8de
Compare
Signed-off-by: Jian Wang <jian.wang@suse.com>
Signed-off-by: Jian Wang <jian.wang@suse.com>
abddc9a to
8e6dd6a
Compare
|
All comments were addressed and synced to versioned_v1.*, the PR was also rebased with main head, thanks. |
martindekov
left a comment
martindekov
left a comment
There was a problem hiding this comment.
LGTM Jian, only 1 question regarding Issue reference, thanks.
|
Tick the box to add this pull request to the merge queue (same as
|
Problem:
Global IP pool might be mis-selected.
Solution:
Update it as a known limitation.
Related Issue(s):
harvester/harvester#10592
Test plan:
Additional documentation or context
Original doc PR #1056 was reverted. We re-update the document with this PR #1101 to book the known limitation and workaround.