mirror of
https://github.com/khuedoan/homelab.git
synced 2025-01-05 13:08:52 +07:00
0ceb426cd5
Otherwise the first node will use kube-vip's IP as its InternalIP, causing issues with Kube API certificate due to an incorrect IP. K3s's CCM does more than I thought, it not only handles Klipper LB but also sets node InternalIP/ExternalIP and clears the uninitialized taint. https://github.com/k3s-io/docs/blob/main/docs/networking.md#deploying-an-external-cloud-controller-manager |
||
---|---|---|
.. | ||
defaults | ||
files/bin | ||
tasks | ||
templates |