Elements missing in Decision Records.
Describe the bug
Hello guys, first of all congrats and thanks for this interesting projects. Just opening this issues since I have trouble to understand some of your technical choices. So it just to discuss and see if I could help on this project since I am working personally on similar topics....
- I have read the documentation
- I have searched open issues
To reproduce
In your Decision records some elements are missing to understand your technological stack.
k3s with cilium + traefik replaced by nginx-ingress => why not to choose rke2 which include by default Cilium and nginx-ingress + etcd db ?
You are deploying a container with dnsmasq for dhcp/tftp/dns why not use KVM ? It could ease dev and test, deploying with a terrafom locally 3 vms with dhcp, dns, tftp set in the KVM dnsmasq... for me the advantage is that I have a button to destroy and rebuild as I want.
Cloud-init instead of Kickstart, if I am not mistaken, Kickstart is gonna to end and for me cloud-init is much more agnostic also it can trigger ansible pull. Also in a Metal as a service approach, we can build our own iso with user-data but on this one I am a newbee.
I have two projects where I played around if you are interested :
By the way, did you check justfile as a replacement of makefile ? Open topics, just want to discuss ... I can provides example about the point listed above.
cheers,
Source: khuedoan/homelab