Home-Network/home-network-k3s-impl
2
0 Fork 0
Code Issues 2 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore(ansible): set private_key_file for k3s node connectivity

Browse Source 
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]>
This commit is contained in:
jakman85andClaude Opus 4.8 committed 2026-08-26 15:27:29 -05:00
1 parent df5979fceb
commit d8101bca38
1 file changed
+4
Download Patch File Download Diff File Expand all files Collapse all files
infra/ansible/ansible.cfg
+4
View File
@@ -3,6 +3,10 @@ inventory = inventory/hosts.ini
roles_path = roles
host_key_checking = False
retry_files_enabled = False
# SSH key the k3s nodes authorize for the `k3s` user (see inventory ansible_user).
# Set here so node config plays (e.g. the rolling k3s config.yaml + Restart handler) connect
# without a per-run --private-key. Path is on the operator workstation / dev container ~/.ssh.
private_key_file = ~/.ssh/home_network
# ansible-core 2.20 removed community.general.yaml; use the builtin default with YAML result format.
stdout_callback = default
result_format = yaml