khuedoan-homelab/metal/roles/k3s
Khue Doan 0ceb426cd5 fix(k3s): re-enable cloud controller manager
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
2024-01-18 17:48:31 +07:00
..
defaults fix(k3s): re-enable cloud controller manager 2024-01-18 17:48:31 +07:00
files/bin fix(metal): ignore cached k3s binary 2021-11-25 18:30:30 +07:00
tasks feat(k3s): install kube-vip for HA control plane 2024-01-16 12:34:22 +07:00
templates feat(k3s): install kube-vip for HA control plane 2024-01-16 12:34:22 +07:00