feat(kube-vip)!: Use auto detection of kube-vip interface (#331)
* Remove kube-vip interface config setting * Remove kube-vip interface Ansible variable * Remove kube-vip interface from cluster manifest * Remove kube-vip interface from Ansible deployment * Delete checks for consistent kube-vip interface names * Remove checks task from Ansible role
This commit is contained in:
1 parent
1fa16287e8
commit
63e29a7257
6 files changed
-33
No files matched your search
@@ -36,12 +36,6 @@ export BOOTSTRAP_METALLB_TRAEFIK_ADDR=""
|
||||
# e.g. age15uzrw396e67z9wdzsxzdk7ka0g2gr3l460e0slaea563zll3hdfqwqxdta
|
||||
export BOOTSTRAP_AGE_PUBLIC_KEY=""
|
||||
|
||||
# The network interface on the host kube-vip should attach to
|
||||
# Look this up on your nodes to verify what NIC to use
|
||||
# This name should be the same across your nodes, see:
|
||||
# https://github.com/k8s-at-home/template-cluster-k3s/issues/310
|
||||
# e.g. eno1
|
||||
export BOOTSTRAP_KUBE_VIP_INTERFACE=""
|
||||
# The IP Address to use with KubeVIP
|
||||
# Pick a unused IP that is on the same network as your nodes
|
||||
# and outside the ${BOOTSTRAP_METALLB_LB_RANGE} range
|
||||
|
||||
Reference in new issue
Block a user