mirror of
https://github.com/khuedoan/homelab.git
synced 2025-02-02 04:14:28 +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
19 lines
516 B
YAML
19 lines
516 B
YAML
k3s_version: v1.28.3+k3s2
|
|
k3s_config_file: /etc/rancher/k3s/config.yaml
|
|
k3s_token_file: /etc/rancher/node/password
|
|
k3s_service_file: /etc/systemd/system/k3s.service
|
|
k3s_data_dir: /var/lib/rancher/k3s
|
|
k3s_kubeconfig_file: /etc/rancher/k3s/k3s.yaml
|
|
k3s_server_config:
|
|
tls-san:
|
|
- "{{ control_plane_endpoint }}"
|
|
disable:
|
|
- local-storage
|
|
- servicelb
|
|
- traefik
|
|
disable-helm-controller: true
|
|
disable-kube-proxy: true
|
|
disable-network-policy: true
|
|
flannel-backend: none
|
|
secrets-encryption: true
|