Closed kenorb closed 3 years ago
https://asciinema.org/a/cwHkB4NvpOCK1smgwQano1rqO
Perhaps try this for a playbook?
---
- hosts: vm01
become: true
roles:
- role: xanmanning.k3s
vars:
k3s_become_for_all: true
k3s_server:
write-kubeconfig-mode: '0640'
k3s_state: installed
Your config seems to work fine.
After adding k3s_become_for_all: true
to my config, it works fine.
But after re-running it with:
k3s_become_for_directory_creation: true
k3s_become_for_install_dir: true
k3s_become_for_systemd: true
k3s_become_for_uninstall: true
k3s_become_for_usr_local_bin: true
instead of k3s_become_for_all
, it generates the same error.
If I want to split become, which param is missing in above list, or it's a bug?
k3s_become_for_kubectl: true
was missing, I assume it's expected behaviour.
Summary
When I run playbook on the existing configured cluster, I've got the fatal error:
Issue Type
Controller Environment and Configuration
Steps to Reproduce
Expected Result
Should run without errors.
Actual Result