0 Fork 0

Files

T

jakman85andClaude Opus 4.8 d8101bca38 chore(ansible): set private_key_file for k3s node connectivity

The k3s nodes authorize ~/.ssh/home_network for the `k3s` user, but ansible.cfg
set no private_key_file and there's no ssh_config entry for the SSH-NAT host, so
node-config plays (e.g. the rolling k3s config.yaml + Restart handler) failed
with Permission denied (publickey). Pin the key so those plays connect without a
per-run --private-key.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

2026-08-26 15:27:29 -05:00

ansible

chore(ansible): set private_key_file for k3s node connectivity

2026-08-26 15:27:29 -05:00

cloud-init

tofu(proxmox): API-only native cloud-init; move node baseline to Ansible node_baseline role

2026-08-25 10:55:48 -05:00

devcontainer

infra: direct kube-API access via kube-vip VIP + NAT (retire SSH tunnel)

2026-08-25 22:10:27 -05:00

tofu

tofu(proxmox): use debian generic image + serial console to fix first-boot kernel panic (bpg#1639)

2026-08-25 11:45:29 -05:00

cluster.sh

Phase 1 checkpoint: status/resume doc + cluster helper + toolchain note

2026-08-16 02:18:39 -05:00

PHASE1-SCOPE.md

Phase 1: host Gitea as the bootstrap GitOps source (resolves source-URL)

2026-08-16 01:26:47 -05:00

PHASE1-STATUS.md

Phase 1 checkpoint: status/resume doc + cluster helper + toolchain note

2026-08-16 02:18:39 -05:00

README.md

Scope Phase 1: dev/test cluster bring-up on local KVM

2026-08-16 00:48:48 -05:00

README.md

infra/ — Phase 1 node provisioning (local KVM)

OpenTofu (libvirt) + cloud-init + Ansible bring up the 3-node k3s/Cilium cluster. See PHASE1-SCOPE.md. Spec: ../home-network-k3s/docs/02-environments-and-provisioning.md.