Add a kube_vip_endpoint variable so the address kube-vip binds and listens on can differ from the announced apiserver_endpoint. This is useful for complex routing and site-to-site tunnels where the VIP kube-vip advertises over ARP differs from the address it listens on internally. - roles/k3s_server/templates/vip.yaml.j2: use kube_vip_endpoint (defaulting to apiserver_endpoint) for the `address` env and for deriving `vip_subnet` - roles/k3s_server/defaults/main.yml: add kube_vip_endpoint default (null) - roles/k3s_server/meta/main.yml: add kube_vip_endpoint argument_spec - inventory/sample/group_vars/all.yml: document the new sample variable - README.md: document the kube_vip_endpoint option - .github/scripts/test-kube-vip-manifest.py: extend regression test to cover the default (apiserver_endpoint) and the override case Closes #221 |
||
|---|---|---|
| .. | ||
| download | ||
| k3s/node/defaults | ||
| k3s_agent | ||
| k3s_custom_registries | ||
| k3s_server | ||
| k3s_server_post | ||
| lxc | ||
| prereq | ||
| proxmox_lxc | ||
| raspberrypi | ||
| reset | ||
| reset_proxmox_lxc | ||