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
This commit is contained in:
Khue Doan 2024-01-18 17:48:31 +07:00
parent 376f0e1b92
commit 0ceb426cd5

View File

@ -11,7 +11,6 @@ k3s_server_config:
- local-storage - local-storage
- servicelb - servicelb
- traefik - traefik
disable-cloud-controller: true
disable-helm-controller: true disable-helm-controller: true
disable-kube-proxy: true disable-kube-proxy: true
disable-network-policy: true disable-network-policy: true