fix(cilium): update LB pool API from v2alpha1 to v2

cluster/platform/cilium-config/manifests/lb-pool.yaml

@@ -1,16 +1,5 @@
-# ------------------------------------------------------------------------------
-# Cilium LB IPAM — IP Address Pools
-#
-# Pool 1: ingress-nginx pool  — 10.1.71.80 - 10.1.71.89
-# Pool 2: cilium-gateway pool — 10.1.71.90 - 10.1.71.99
-#
-# Pools are separated so ingress-nginx and Gateway API services never
-# compete for the same IPs. Each pool uses a serviceSelector to ensure
-# IPs are only assigned to the right controller.
-# ------------------------------------------------------------------------------
-
-# Pool for ingress-nginx LoadBalancer service
-apiVersion: cilium.io/v2alpha1
+# Pool for ingress-nginx
+apiVersion: cilium.io/v2
 kind: CiliumLoadBalancerIPPool
 metadata:
   name: ingress-nginx-pool
@@ -24,9 +13,8 @@ spec:
       app.kubernetes.io/name: ingress-nginx
 
 ---
-# Pool for Cilium Gateway API — only assigned to Gateway-owned services
-# Cilium automatically labels Gateway services with io.cilium.gateway/owning-gateway
-apiVersion: cilium.io/v2alpha1
+# Pool for Cilium Gateway API
+apiVersion: cilium.io/v2
 kind: CiliumLoadBalancerIPPool
 metadata:
   name: cilium-gateway-pool
@@ -41,7 +29,7 @@ spec:
         operator: Exists
 
 ---
-# L2 Announcement Policy — ARP on server VLAN for both pools
+# L2 Announcement Policy
 apiVersion: cilium.io/v2alpha1
 kind: CiliumL2AnnouncementPolicy
 metadata:
@@ -49,6 +37,5 @@ metadata:
   namespace: kube-system
 spec:
   loadBalancerIPs: true
-  # All nodes participate — Cilium handles failover automatically
   interfaces:
     - ^eth[0-9]+