mirrors/k3s-ansible
1
0
Fork 1
mirror of https://github.com/k3s-io/k3s-ansible.git synced 2025-12-25 00:12:37 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add ability to move kubeconfig to control node on demand (#467)

Browse Source 
Signed-off-by: Phillip Thurston <phil@goinvictus.com>
This commit is contained in:
Phillip Thurston
2025-12-04 13:14:04 -07:00
committed by GitHub
parent c23ef774e4
commit 11e99b0b7f
2 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@@ -167,7 +167,7 @@ It is assumed that the control node has access to the internet. The playbook wil
## Kubeconfig ## Kubeconfig
After successful bringup, the kubeconfig of the cluster is copied to the control node and merged with `~/.kube/config` under the `k3s-ansible` context. After successful bringup, the kubeconfig of the cluster is copied to the control node and merged with `~/.kube/config` under the `k3s-ansible` context unless overwritten by the `cluster_context` variable.
Assuming you have [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) installed, you can confirm access to your **Kubernetes** cluster with the following: Assuming you have [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) installed, you can confirm access to your **Kubernetes** cluster with the following:
```bash ```bash
@@ -177,6 +177,19 @@ kubectl get nodes
If you wish for your kubeconfig to be copied elsewhere and not merged, you can set the `kubeconfig` variable in `inventory.yml` to the desired path. If you wish for your kubeconfig to be copied elsewhere and not merged, you can set the `kubeconfig` variable in `inventory.yml` to the desired path.
If you wish to get a new copy of the kubeconfig after installation you can run the site playbook again using the `kubeconfig` tag.
*Installed with ansible-galaxy*
```bash
ansible-playbook k3s.orchestration.site -i inventory.yml --tags kubeconfig
```
*Running the playbook from inside the repository*
```bash
ansible-playbook playbooks/site.yml -i inventory.yml --tags kubeconfig
```
## Local Testing ## Local Testing
A Vagrantfile is provided that provision a 5 nodes cluster using Vagrant (LibVirt or Virtualbox as provider). To use it: A Vagrantfile is provided that provision a 5 nodes cluster using Vagrant (LibVirt or Virtualbox as provider). To use it:
@@ -185,7 +198,7 @@ A Vagrantfile is provided that provision a 5 nodes cluster using Vagrant (LibVir
vagrant up vagrant up
``` ```
By default, each node is given 2 cores and 2GB of RAM and runs Ubuntu 20.04. You can customize these settings by editing the `Vagrantfile`. By default, each node is given 2 cores and 2GB of RAM and runs Ubuntu 24.04. You can customize these settings by editing the `Vagrantfile`.
## Need More Features? ## Need More Features?

5
roles/k3s_server/tasks/main.yml
View File

@@ -171,6 +171,7 @@
# noqa var-naming[no-role-prefix] # noqa var-naming[no-role-prefix]
ansible.builtin.command: 'kubectl' ansible.builtin.command: 'kubectl'
register: kubectl_installed register: kubectl_installed
tags: kubeconfig
ignore_errors: true ignore_errors: true
delegate_to: 127.0.0.1 delegate_to: 127.0.0.1
become: false become: false
@@ -185,11 +186,11 @@
mode: "0600" mode: "0600"
remote_src: true remote_src: true
register: k3s_server_copy_yaml register: k3s_server_copy_yaml
tags: kubeconfig
- name: Apply K3S kubeconfig to control node - name: Apply K3S kubeconfig to control node
when: when:
- kubectl_installed.rc == 0 - kubectl_installed.rc == 0 and (k3s_server_copy_yaml.changed or 'kubeconfig' in ansible_run_tags)
- k3s_server_copy_yaml.changed
block: block:
- name: Copy kubeconfig to control node - name: Copy kubeconfig to control node
ansible.builtin.fetch: ansible.builtin.fetch: