From 0ceb426cd53e75d73cb6de9c5f5ee4bdf0810ed4 Mon Sep 17 00:00:00 2001 From: Khue Doan Date: Thu, 18 Jan 2024 17:48:31 +0700 Subject: [PATCH] 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 --- metal/roles/k3s/defaults/main.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/metal/roles/k3s/defaults/main.yml b/metal/roles/k3s/defaults/main.yml index d7acdec2..37ca151b 100644 --- a/metal/roles/k3s/defaults/main.yml +++ b/metal/roles/k3s/defaults/main.yml @@ -11,7 +11,6 @@ k3s_server_config: - local-storage - servicelb - traefik - disable-cloud-controller: true disable-helm-controller: true disable-kube-proxy: true disable-network-policy: true