From d8101bca38043b7a0a7669156bc2ee699cd3326a Mon Sep 17 00:00:00 2001 From: Keith Jackson Date: Wed, 26 Aug 2026 15:27:29 -0500 Subject: [PATCH] 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 --- infra/ansible/ansible.cfg | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/infra/ansible/ansible.cfg b/infra/ansible/ansible.cfg index 60fc2a3..3667681 100644 --- a/infra/ansible/ansible.cfg +++ b/infra/ansible/ansible.cfg @@ -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