Files
JimsGarage/Kubernetes
cyberops7 49313239f4 K3S-Deploy: join via the VIP, not master1; harden per k8s review
- join all nodes to --server-ip $vip (the readiness-gated VIP) so no single
  master is the registration SPOF; drop the dead --server-user on joins
  (a --node-token is already supplied, so k3sup doesn't SSH the server)
- add --tls-san=$vip to every server's args (not just master1's install) so
  master2/3 declare the VIP SAN uniformly
- pin --flannel-iface/--node-ip on workers too (correct on multi-NIC nodes)
- filter k3sup's repeated 'slicervm.com' promo tip on install/join (sed, so
  pipefail still surfaces a real failure)
- guard 'kubectl expose' with || true so a re-run doesn't abort on AlreadyExists

Re-validated on the 6-VM Multipass e2e: 5 nodes Ready, VIP serves the API,
MetalLB LoadBalancer reachable.
2026-07-07 22:55:48 -06:00
..
2023-11-07 17:00:07 +00:00
2023-12-06 01:02:07 +00:00
2024-04-25 11:24:09 +02:00
2024-01-16 12:55:53 +00:00
2024-03-17 21:22:19 +00:00
2023-11-22 16:26:43 +00:00
2025-09-02 21:48:48 +01:00
2024-03-14 22:02:50 +00:00