Problem
vipLink is a single value, so the preset can pin at most one VIP. A node that needs a VIP on two links — e.g. a control-plane VIP on the primary link (192.0.2.254) and a separate VIP on a storage/secondary link (203.0.113.254) — cannot express the second and must hand-edit the rendered config.
Related to #226 (full multi-link topology).
Proposal
Accept a list of VIPs, each bound to a link:
vips:
- { link: bond0, ip: 192.0.2.254 }
- { link: bond1, ip: 203.0.113.254 }mapping to one Layer2VIPConfig (Talos 1.12+) or an inline vip block (legacy) per link. Keep vipLink/floatingIP as the single-VIP shorthand for back-compat.
Problem
vipLinkis a single value, so the preset can pin at most one VIP. A node that needs a VIP on two links — e.g. a control-plane VIP on the primary link (192.0.2.254) and a separate VIP on a storage/secondary link (203.0.113.254) — cannot express the second and must hand-edit the rendered config.Related to #226 (full multi-link topology).
Proposal
Accept a list of VIPs, each bound to a link:
mapping to one
Layer2VIPConfig(Talos 1.12+) or an inlinevipblock (legacy) per link. KeepvipLink/floatingIPas the single-VIP shorthand for back-compat.