infra(net): repoint ansible inventory + Cilium VIPs to the Proxmox LAN
- 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]>
This commit is contained in:
1 parent
4bb9c8fcbd
commit
d57c9cbf12
3 files changed
+21
-12
No files matched your search
@@ -1,10 +1,10 @@
|
||||
---
|
||||
# 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 10.73.0.240-.250) on the k3s-dev NAT 10.73.0.0/24; DHCP is OFF on that
|
||||
# network so the range can never be leased elsewhere.
|
||||
# (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 NAT reservation. A prod overlay must supply the
|
||||
# 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
|
||||
@@ -12,5 +12,5 @@ metadata:
|
||||
name: default-pool
|
||||
spec:
|
||||
blocks:
|
||||
- start: "10.73.0.240"
|
||||
stop: "10.73.0.250"
|
||||
- start: "192.168.1.53"
|
||||
stop: "192.168.1.60"
|
||||
Reference in new issue
Block a user