MichaelFisher1997 4726db2b5b Add Tailscale IPs to k3s TLS SANs for secure tailnet access ...

Changes:
- Add tailscale_control_plane_ips list to k3s-server defaults
- Include all 3 control plane Tailscale IPs (100.120.55.97, 100.108.90.123, 100.92.149.85)
- Update primary k3s install to add Tailscale IPs to TLS certificates
- Enables kubectl access via Tailscale without certificate errors

After next deploy, cluster will be accessible via:
- kubectl --server=https://100.120.55.97:6443 (or any CP tailscale IP)
- kubectl --server=https://k8s-cluster-cp-1:6443 (via tailscale DNS)

2026-03-23 23:04:00 +00:00

..

addon-secrets-bootstrap/tasks

fix: bootstrap tailscale namespace before secret

2026-03-20 09:24:35 +00:00

ccm-deploy/tasks

Install helm binary in ccm-deploy role before using it

2026-03-23 00:07:39 +00:00

common

fix: avoid server replacement; install tailscale via Ansible

2026-03-01 04:51:19 +00:00

doppler-bootstrap/tasks

fix: defer doppler store until eso is installed

2026-03-20 09:30:17 +00:00

k3s-agent

Enable Hetzner CCM and CSI for cloud provider integration

2026-03-22 22:26:21 +00:00

k3s-server

Add Tailscale IPs to k3s TLS SANs for secure tailnet access

2026-03-23 23:04:00 +00:00

observability

fix: clear stale helm pending revisions before kube-prometheus upgrade

2026-03-04 18:35:55 +00:00

observability-content

fix: fail fast when loki datasource has no labels

2026-03-04 21:00:01 +00:00

private-access

feat: automate private tailnet access on cp1

2026-03-08 04:16:06 +00:00