jakman85andClaude Opus 4.8
d57c9cbf12
- ansible hosts.ini: node ansible_host -> 192.168.1.50/.51/.52, with a clear note that the PM may need to swap these for the pfSense NAT-forwarded address:port once that NAT rule exists (not guessed here). k3s_api_host derives from the inventory, so it follows automatically. - Cilium CiliumLoadBalancerIPPool -> 192.168.1.53-.60 (matches the tofu cilium_l2_vip reservation on the new LAN). - CiliumL2AnnouncementPolicy: broaden interface selector to ^e(n|th) so the Proxmox NIC name (ens18/eth0) need not be pinned; flagged verify-at-bringup. Co-Authored-By: Claude Opus 4.8 <[email protected]>
17 lines
737 B
YAML
17 lines
737 B
YAML
---
|
|
# CiliumLoadBalancerIPPool — reserved VIP range for LoadBalancer Services. Gateway API listeners
|
|
# (gatewayClassName: cilium) get their address from here. Range matches the tofu reservation
|
|
# (cilium_l2_vip_range 192.168.1.53-.60) on the Proxmox LAN 192.168.1.0/24. These addresses sit
|
|
# OUTSIDE the node IPs (.50/.51/.52) and any DHCP scope, so nothing else claims them.
|
|
#
|
|
# NOTE (dev): the range is hardcoded to the dev LAN reservation. A prod overlay must supply the
|
|
# prod LAN range (parameterize via cluster-vars when prod hardware is built). See DECISIONS-LOG.
|
|
apiVersion: cilium.io/v2alpha1
|
|
kind: CiliumLoadBalancerIPPool
|
|
metadata:
|
|
name: default-pool
|
|
spec:
|
|
blocks:
|
|
- start: "192.168.1.53"
|
|
stop: "192.168.1.60"
|