feat(infra): kube-vip control-plane HA VIP (192.168.1.49) + API tls-san
Add an HA control-plane API VIP for the k3s cluster with kube-vip, and add the VIP + all node IPs to the kube-apiserver serving-cert SANs so TLS via the VIP validates. Prepares the stable failover endpoint the operator fronts with a pfSense port-forward to 192.168.1.49:6443. roles/kube_vip + playbooks/kube-vip.yml: - Templates a single manifest (RBAC + DaemonSet kube-vip-ds) into each server's k3s auto-deploy dir (/var/lib/rancher/k3s/server/manifests) so it is reproducible and independent of Flux; k3s auto-applies it. - Control-plane ONLY (cp_enable=true, svc_enable=false): Cilium keeps ownership of Service LoadBalancing (L2 pool .53-.60) — no ARP conflict. - Runs on control-plane nodes (nodeSelector node-role.kubernetes.io/control-plane), hostNetwork, NET_ADMIN/NET_RAW, image pinned ghcr.io/kube-vip/kube-vip:v0.8.9. - vip_interface auto-detected per node (the iface holding 192.168.1.5x = eth0). - Leader election (plndr-cp-lock) with 15/10/2s lease timings. - This cluster runs without kube-proxy (Cilium replacement), so a hostNetwork pod cannot reach the kubernetes ClusterIP; kube-vip is pointed at the node-local apiserver (KUBERNETES_SERVICE_HOST=127.0.0.1:6443) so leader election works. roles/k3s_server tls-san: - New k3s_tls_sans (VIP + all three node IPs + 127.0.0.1, deduped); install args now emit one --tls-san per entry. - Persist the SAN list to /etc/rancher/k3s/config.yaml (read by a running k3s) and Restart k3s handler so an existing cluster regenerates its serving cert. - k3s.yml secondaries run serial:1 so a SAN change rolls one node at a time, keeping etcd quorum (kube-vip keeps the API reachable during each restart). Verified live: DS 3/3 ready, VIP answers on 192.168.1.49:6443, all 3 certs and an s_client against the VIP carry 192.168.1.49 + .50/.51/.52 + 127.0.0.1, all nodes Ready throughout the rolling restart. Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
1 parent
d99d171468
commit
60a58f01ad
9 files changed
+276
-1
No files matched your search
@@ -20,9 +20,30 @@
|
||||
--disable-network-policy
|
||||
--disable={{ k3s_disable }}
|
||||
--write-kubeconfig-mode=644
|
||||
--tls-san={{ k3s_api_host }}
|
||||
{% for san in k3s_tls_sans %}--tls-san={{ san }} {% endfor %}
|
||||
--node-ip={{ k3s_node_ip }}
|
||||
|
||||
# On an ALREADY-installed cluster the install task above is idempotent (creates:
|
||||
# k3s.yaml) and won't re-apply new --tls-san flags. Persist the SAN list in
|
||||
# /etc/rancher/k3s/config.yaml, which a running k3s reads on the next restart —
|
||||
# it then regenerates the serving cert when the SAN set changes. Apply the
|
||||
# restart ROLLING, one node at a time (kube-vip keeps the API reachable; etcd
|
||||
# quorum holds at 2/3). See playbooks note: run with `serial: 1`.
|
||||
- name: Write /etc/rancher/k3s/config.yaml with the tls-san list
|
||||
ansible.builtin.copy:
|
||||
dest: /etc/rancher/k3s/config.yaml
|
||||
owner: root
|
||||
group: root
|
||||
mode: "0600"
|
||||
content: |
|
||||
# Managed by Ansible (roles/k3s_server). Read by k3s in addition to the
|
||||
# systemd unit flags; tls-san entries are merged into the serving cert.
|
||||
tls-san:
|
||||
{% for san in k3s_tls_sans %}
|
||||
- "{{ san }}"
|
||||
{% endfor %}
|
||||
notify: Restart k3s
|
||||
|
||||
# --- primary: found the cluster --------------------------------------------
|
||||
- name: Install k3s primary (cluster-init, embedded etcd)
|
||||
ansible.builtin.command:
|
||||
|
||||
Reference in new issue
Block a user