feat!: Drop Metallb in favor of Cilium L2Announcements (#821)

.config.sample.env

@@ -45,22 +45,11 @@ export BOOTSTRAP_CLOUDFLARE_ACCOUNT_TAG=""
 export BOOTSTRAP_CLOUDFLARE_TUNNEL_SECRET=""
 export BOOTSTRAP_CLOUDFLARE_TUNNEL_ID=""
 
-# Pick a range of unused IPs that are on the same network as your nodes
-# You don't need many IPs, just choose 10 IPs to start with
-# e.g. 192.168.1.220-192.168.1.230
-export BOOTSTRAP_METALLB_LB_RANGE=""
-# The load balancer IP for k8s_gateway, choose from one of the available IPs above
-# e.g. 192.168.1.220
-export BOOTSTRAP_METALLB_K8S_GATEWAY_ADDR=""
-# The load balancer IP for the ingress controller, choose from one of the available IPs above
-# that doesn't conflict with any other IP addresses here
-# e.g. 192.168.1.221
-export BOOTSTRAP_METALLB_INGRESS_ADDR=""
-# The IP Address to use with kube-vip
-# Pick a unused IP that is on the same network as your nodes
-# and outside the ${BOOTSTRAP_METALLB_LB_RANGE} range
-# and doesn't conflict with any other IP addresses here
-# e.g. 192.168.1.254
+# The load balancer IP for k8s_gateway, choose a available IP in your nodes network that is not being used
+export BOOTSTRAP_K8S_GATEWAY_ADDR=""
+# The load balancer IP for ingress-nginx, choose a available IP in your nodes network that is not being used
+export BOOTSTRAP_INGRESS_NGINX_ADDR=""
+# The IP address to use with kube-vip, choose a available IP in your nodes network that is not being used
 export BOOTSTRAP_KUBE_VIP_ADDR=""
 # Choose your cluster or service cidrs
 # Leave this unchanged unless you know what you are doing
@@ -84,7 +73,7 @@ export BOOTSTRAP_ANSIBLE_DEFAULT_NODE_HOSTNAME_PREFIX="k8s-" # NOTE: Must only c
 # incrementing the last digit on the variable name for each node
 #
 
-# Host IP Address to the control plane node
+# IP Address to the node
 # That doesn't conflict with any other IP addresses here
 # e.g. 192.168.1.200
 export BOOTSTRAP_ANSIBLE_HOST_ADDR_0=""