Gave kube-vip entire cidr range and fix traefik static ip

clusters/titan.lan.huizinga.dev/infrastructure.yaml

@@ -23,15 +23,6 @@ spec:
   path: ./infrastructure/controllers
   prune: true
   wait: true
-  patches:
-    - patch: |
-        - op: add
-          path: /spec/values/service/spec/loadBalancerIP
-          value: 10.0.2.2
-      target:
-        kind: HelmRelease
-        name: traefik
-        namespace: traefik
 ---
 apiVersion: kustomize.toolkit.fluxcd.io/v1
 kind: Kustomization

infra/kube-vip/config-map-kubevip.yaml

@@ -3,6 +3,5 @@ kind: ConfigMap
 metadata:
   name: kubevip
 data:
-  # 10.0.2.1 is reserved for control plane
-  # 10.0.2.2 is reserved for traefik
-  range-global: 10.0.2.3-10.0.2.254
+  # Can't use cidr-range as 10.0.2.1 is reserved for the control plane
+  range-global: 10.0.2.2-10.0.2.254

infra/traefik/helm-release.yaml

@@ -50,14 +50,8 @@ spec:
         tls:
           secretName: ${domain//./-}-tls
 
-    # This is needed in order to properly forward the real ip to each service
-    # There are likely better ways of handling that, but for now this works
-    # TODO(Tim): Figure out how to properly forward the IP
-    # hostNetwork: true
     service:
+      annotations:
+        kube-vip.io/loadbalancerIPs: 10.0.2.2
       spec:
         externalTrafficPolicy: Local
-    # updateStrategy:
-    #   rollingUpdate:
-    #     maxUnavailable: 2
-    #     maxSurge: 0