Fresh Install

[Shadpog]

Hello,
So I don't know anything about K3s and try to learn.
I try to do a fresh install to discover all the system but I am stuck at the install and don't understand the problem and saw some other people with same problem
.

My variables files

---
k3s_version: v1.25.12+k3s1
# this is the user that has ssh access to these machines
ansible_user: sysadmin
systemd_dir: /etc/systemd/system

# Set your timezone
system_timezone: "Africa/Libreville"

# interface which will be used for flannel
flannel_iface: "ens18"

# apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "10.0.50.16"

# k3s_token is required  masters can talk together securely
# this token should be alpha numeric only
k3s_token: "FPiy9rQi3A3QyR4maoEvZVzsJSU6fDn7FZWF6zN4kuo"

# The IP on which the node is reachable in the cluster.
# Here, a sensible default is provided, you can still override
# it for each of your hosts, though.
k3s_node_ip: '{{ ansible_facts[flannel_iface]["ipv4"]["address"] }}'

# Disable the taint manually by setting: k3s_master_taint = false
k3s_master_taint: "{{ true if groups['node'] | default([]) | length >= 1 else false }}"

# these arguments are recommended for servers as well as agents:
extra_args: >-
  --flannel-iface={{ flannel_iface }}
  --node-ip={{ k3s_node_ip }}

# change these to your liking, the only required are: --disable servicelb, --tls-san {{ apiserver_endpoint }}
extra_server_args: >-
  {{ extra_args }}
  {{ '--node-taint node-role.kubernetes.io/master=true:NoSchedule' if k3s_master_taint else '' }}
  --tls-san {{ apiserver_endpoint }}
  --disable servicelb
  --disable traefik
extra_agent_args: >-
  {{ extra_args }}

# image tag for kube-vip
kube_vip_tag_version: "v0.5.12"

# metallb type frr or native
metal_lb_type: "native"

# metallb mode layer2 or bgp
metal_lb_mode: "layer2"

# bgp options
# metal_lb_bgp_my_asn: "64513"
# metal_lb_bgp_peer_asn: "64512"
# metal_lb_bgp_peer_address: "192.168.30.1"

# image tag for metal lb
metal_lb_speaker_tag_version: "v0.13.9"
metal_lb_controller_tag_version: "v0.13.9"

# metallb ip range for load balancer
metal_lb_ip_range: "10.0.50.80-10.0.50.90"

# Only enable if your nodes are proxmox LXC nodes, make sure to configure your proxmox nodes
# in your hosts.ini file.
# Please read https://gist.github.com/triangletodd/02f595cd4c0dc9aac5f7763ca2264185 before using this.
# Most notably, your containers must be privileged, and must not have nesting set to true.
# Please note this script disables most of the security of lxc containers, with the trade off being that lxc
# containers are significantly more resource efficent compared to full VMs.
# Mixing and matching VMs and lxc containers is not supported, ymmv if you want to do this.
# I would only really recommend using this if you have partiularly low powered proxmox nodes where the overhead of
# VMs would use a significant portion of your available resources.
proxmox_lxc_configure: false
# the user that you would use to ssh into the host, for example if you run ssh some-user@my-proxmox-host,
# set this value to some-user
proxmox_lxc_ssh_user: root
# the unique proxmox ids for all of the containers in the cluster, both worker and master nodes
proxmox_lxc_ct_ids:
  - 200
  - 201
  - 202
  - 203
  - 204

Here my hosts file:

[master]
10.0.50.20
10.0.50.21
10.0.50.22

[node]
10.0.50.23
10.0.50.24
10.0.50.25

# only required if proxmox_lxc_configure: true
# must contain all proxmox instances that have a master or worker node
# [proxmox]
# 192.168.30.43

[k3s_cluster:children]
master
node

And thanks for all your job.

[Shadpog]

I try with a new intall of ubuntu with the cloud img.
But still same error.

Any help will be appreciate.

[bluevulpine]

What version of Ansible are you running?

#317 (comment)

[Shadpog]

I run ansible 2.10.8.
edit: Ok this version in not working ....

[bluevulpine]

See the issue I linked above. In addition, the project README file indicates the minimum version is 2.11. https://github.com/techno-tim/k3s-ansible#-system-requirements

[Shadpog]

Well thanks for the help, next time must read better.

[dcwestra]

I am having this exact same issue with ansible 2.14.3

root@DietPi:~/k3s-ansible# ansible --version
ansible [core 2.14.3]
  config file = /root/k3s-ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] (/usr/bin/python3)
  jinja version = 3.1.2
  libyaml = True

[dcwestra]

Ignore. My issue was my flannel interface. I assumed my VMs were on eth0, when they were, in fact, not. Always double check, never assume.