techno-tim / k3s-ansible

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.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k stars 1.05k forks source link

readme, troubleshooting, or play should ensure metal_lb_ip_range and apiserver_endpoint have valid ips in flannel_iface #377

Closed edoziw closed 3 months ago

edoziw commented 1 year ago

RE: closed issue

Expected Behavior

Document and or assert metal_lb_ip_range and apiserver_endpoint have valid ips in flannel_iface

Current Behavior

If the master and or node hosts flannel_iface eg eth0 has a netmask of 255.255.255.0 and an ip of 192.168.0.* vars of

are invalid

Steps to Reproduce

given

docs, but use invalid ips like above

when

ansible-playbook site.yml

then

docs and or trouble shooting or assert should explain the problem

Possible Solution

Thanks

edoziw commented 1 year ago

Tim, if you find this reasonable I'd be happy to give a PR or PRs a go.. possible PRs:

timothystewart6 commented 1 year ago

This would be awesome! If you are going to do that work, another thing to assert is that the apiserver_endpoint does not fall into the range of the metal_lb_ip_range . That seems to be another common pitfall.

edoziw commented 1 year ago

PR pushed thanks Tim!

timothystewart6 commented 3 months ago

The PR was closed because it was never updated, closing this issue too. If you would like this change, please feel free to reopen the PR with updated code. Thanks!