CORE#12191: Adds clarity on Maglev doc, surrounding NodePorts and type:LoadBalancer #2455
Conversation
❌ Deploy Preview for calico-docs-preview-next failed. Why did it fail? →
|
❌ Deploy Preview for tigera failed. Why did it fail? →Built without sensitive environment variables
|
There was a problem hiding this comment.
Pull request overview
This PR improves the Maglev load balancing documentation by clarifying NodePort limitations and adding guidance on using Maglev with LoadBalancer IPAM. The changes address confusion around when Maglev functionality is useful and how to properly configure services to leverage it.
Changes:
- Clarified that Maglev doesn't work with NodePorts specifically (not just NodePort-type services)
- Added new section explaining how to use Maglev with LoadBalancer IPAM and BGP advertisement
- Updated prerequisites to emphasize the need for external IP routing capability
| ## Use Maglev Alongside $[prodname] LoadBalancer IPAM | ||
|
|
||
| Maglev can be enabled on services with `type: LoadBalancer`, and $[prodname] can be configured to allocate | ||
| load balancer VIPs. See the guide to [enable LoadBalancer IPAM](networking/ipam/service-loadbalancer). |
There was a problem hiding this comment.
The relative link path is incorrect. Based on the file's location in calico-enterprise/networking/configuring/, this link should start with ../../ to navigate up to the root, or use an absolute path starting with /calico-enterprise/. The current path networking/ipam/service-loadbalancer will not resolve correctly from this file's location.
| load balancer VIPs. See the guide to [enable LoadBalancer IPAM](networking/ipam/service-loadbalancer). | |
| load balancer VIPs. See the guide to [enable LoadBalancer IPAM](../../networking/ipam/service-loadbalancer). |
| ## Prerequisites | ||
|
|
||
| * Your cluster uses the eBPF data plane with [direct server return mode](../../operations/ebpf/enabling-ebpf.mdx#try-out-direct-server-return-mode). | ||
| * Your cluster uses the eBPF data plane with [direct server return mode](../../../operations/ebpf/enabling-ebpf#try-out-direct-server-return-mode). |
There was a problem hiding this comment.
The relative link path appears incorrect. The file is in calico-enterprise/networking/configuring/, so the path ../../../operations/ebpf/enabling-ebpf would navigate too far up (3 levels up would go above the calico-enterprise directory). This should be ../../operations/ebpf/enabling-ebpf.mdx#try-out-direct-server-return-mode to correctly reference the file.
| * Your cluster uses the eBPF data plane with [direct server return mode](../../../operations/ebpf/enabling-ebpf#try-out-direct-server-return-mode). | |
| * Your cluster uses the eBPF data plane with [direct server return mode](../../operations/ebpf/enabling-ebpf.mdx#try-out-direct-server-return-mode). |
There was a problem hiding this comment.
@ctauchen based on our chat, I think Copilot is wrong here, right?
calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx
Outdated
Show resolved
Hide resolved
calico-enterprise/networking/configuring/add-maglev-load-balancing.mdx
Outdated
Show resolved
Hide resolved
aaaaaaaalex
changed the title
aaaaaaaalex
force-pushed
the
maglev-doc-lb-support
branch
from
ffea0db to
9674b88
Compare
aaaaaaaalex
force-pushed
the
maglev-doc-lb-support
branch
from
9674b88 to
13edc4f
Compare
aaaaaaaalex
changed the title
| Note Maglev load balancing cannot be used with the following: | ||
| * In-cluster pod-to-service traffic. | ||
| * NodePort-type services. | ||
| * NodePorts. |
There was a problem hiding this comment.
I broadened this line - since it also won't work with type:LoadBalancer services if you try to use those services' "node ports"
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 participant
Product Version(s):
OSS and EE next
Issue
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: