Elements missing in Decision Records.

[MozeBaltyk]

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 :

• Rkub

• Okub

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,

[khuedoan]

Thanks for creating the issue. The doc needs some more love. I'll go back and update it after some upcoming major refactor (I've been playing around with some ideas over my offsite setup https://github.com/khuedoan/cloudlab, and once that's "feels good" to use, I’ll start implementing them here)

For RKE2, I didn't know that they have Cilium built in. That’s worth trying out, thanks!

[MozeBaltyk]

So you are already preparing the next generation of homelab ? and I see no ansible indeed... I guess ansible is to incremental and almost impossible to parallelize.

Correct me if I am wrong but what I see in cloudlab, is much more flexible for multi-environments and can apply on local, metal, and cloud ?

May I ask why temporal instead of woodpeeker ? I do not understand all the purpose of the controller ? what does it accomplish ?

For platform and apps, may I suggest to use this pattern : https://github.com/hivenetes/k8s-bootstrapper/tree/main/argocd
( an helm charts of apps-of-apps). Argocd stay the CD but you will get DRY code and values.yaml with the compoments that you want to enable or disable and customized values...

But I see a big progress, I assume that cloudlab is much faster to deploy than homelab ?

thanks for this shared project!

[MozeBaltyk]

How do you pxeboot on baremetal with cloudlab ? or have you quit this option ?

[khuedoan]

Cloudlab is my offsite setup, and they will continue to be separate projects. I'll port features between them where it makes sense (and when I have some more free time 😛)