docs: add critical note for same-subnet requirement in MetalLB underlay#630
docs: add critical note for same-subnet requirement in MetalLB underlay#630
Conversation
VIP and backend Pod IPs must be in the same Underlay subnet, otherwise ARP and DNAT routing will fail.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughA documentation update adding a critical warning to MetalLB Underlay configuration guidance, stating MetalLB LoadBalancer VIPs and backend Pod IPs must be in the same underlay subnet for ARP advertisement and Kube-OVN DNAT to function. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying alauda-container-platform with
|
| Latest commit: |
830e664
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7cac2a46.alauda-container-platform.pages.dev |
| Branch Preview URL: | https://docs-add-same-subnet-warning.alauda-container-platform.pages.dev |
VIP and backend Pod IPs must be in the same Underlay subnet, otherwise ARP and DNAT routing will fail.
Summary by CodeRabbit