Closed SuperSweatyYeti closed 1 year ago
Figured it out Guys.
# apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "192.168.30.222"
...
# metallb ip range for load balancer
metal_lb_ip_range: "192.168.30.80-192.168.30.90"
Neded to change the apiserver_endpoint
and metal_lb_ip_range
to some ips that actually exist in my local network.
Anyways,
Thanks again for this tool guys. Much appreciated 😄
First Off
Just wanna say thank you to everyone who contributes to this project. I love the idea as someone who is trying to learn these technologies, and greatly appreciate all the hard work that has been done so far 😄
The Issue
Everything Runs perfectly until I get to the task: TASK [k3s/node : Enable and check K3s service] And then the playbook hangs
Expected Behavior
The last task completes and the node joins the cluster
Current Behavior
That task hangs forever and the node never joins the cluster
Steps to Reproduce
ansible-playbook site.yml -i inventory/my-cluster/hosts.ini --ask-become-pass
BRANCH Used: v1.24.6+k3s1
Context (variables)
Operating system: The OS used to run the playbook was : WSL on windows 10 OS of VMs: Ubuntu 22.04 Same behavior when using Ubuntu 20.04
Hardware: My ProxMox host: intel i5 8 core, 32GB ram, 500GB ssd
Variables Used
all.yml
Hosts
host.ini
[master] 192.168.22.233
[node] 192.168.22.234
[k3s_cluster:children] master node
Possible Solution
here are the logs from the service on the node that the ansible task is trying to modify:
This is what the systemd service file looks like on the node: