The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
This PR addresses the issue if the install user's home directory is not in /home/username. The Copy config file to user home directory task copies /etc/rancher/k3s/k3s.yaml to "{{ ansible_user_dir }}/.kube/config"
Without this change, when installing Cilium by a non-standard user, it will fail to set the KUBECONFIG correctly and the cilium installer will fail to fetch the k8s/k3s version with an error as described in https://github.com/techno-tim/k3s-ansible/issues/446.
Proposed Changes
This ensures the KUBECONFIG environment variable points to the user's directory and does not assume it is in /home/username/.kube/config
Checklist
[x] Tested locally
[x] Ran site.yml playbook
[x] Ran reset.yml playbook
[x] Did not add any unnecessary changes
[x] Ran pre-commit install at least once before committing
timothystewart6
commented
8 months ago
This PR addresses the issue if the install user's home directory is not in
/home/username. TheCopy config file to user home directorytask copies/etc/rancher/k3s/k3s.yamlto"{{ ansible_user_dir }}/.kube/config"Without this change, when installing Cilium by a non-standard user, it will fail to set the
KUBECONFIGcorrectly and the cilium installer will fail to fetch the k8s/k3s version with an error as described in https://github.com/techno-tim/k3s-ansible/issues/446.Proposed Changes
KUBECONFIGenvironment variable points to the user's directory and does not assume it is in/home/username/.kube/configChecklist
site.ymlplaybookreset.ymlplaybook