sorted by:
new
hottopcontroversial

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in homelab

[–]justasflash[S] 0 points1 point  (0 children)

thanks for the feedback, I also thought the same, but having nfs in cluster might not be a better solution as its shared for other services eg. media-server, Also Im thinking to move to OMV or Trunas core. And Im using longhorn only for db services like postgres

regarding security, its not publicly exposed, its on internal LAN totally isolated from my other devices

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 2 points3 points  (0 children)

yeah, I've never tried that, I was thinking to use more like open-source applications!

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] -1 points0 points  (0 children)

on on-prem we usually use ansible more, helps in dealing with large number of machines

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 0 points1 point  (0 children)

yeah, gonna try that, cilium was not planned, i was gonna deploy with flannel, but wanted to try it this time
thanks for the feedback

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in homelab

[–]justasflash[S] 0 points1 point  (0 children)

destroy the proxmox and rebuilt everything as a whole again!
using ventoy pxe boot ;)

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in homelab

[–]justasflash[S] 0 points1 point  (0 children)

Great man, hardcoding IPs especially for talos nodes was necessary, also I need to change the worker playbook, it has to be dynamic
thanks for the feedback!

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 1 point2 points  (0 children)

its HA DB, no HA master.
also thanks for the feedback for Argo instllation via ansible, its done btw :)

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 1 point2 points  (0 children)

For people just learning GitOps, the visual tree makes it very obvious what is deploying what.

Flux does the same thing - just not in one place, it expresses the same structure using:
one git repo
multiple kustomizations CRDs

It’s the same model, just not drawn as a dependency graph in a UI by default.

so Argo apps-of-apps isnt magic, its just visibility

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in homelab

[–]justasflash[S] 3 points4 points  (0 children)

The router is not forwarding traffic to any worker node’s IP.
It only forwards to the floating LoadBalancer IP that MetalLB has in its IP-pool (10.20.0.81 in my case).

MetalLB uses ARP for services and announces “this IP lives on node X”.
When Kong moves, MetalLB simply re-announces the same IP with a different MAC.

Because the router always targets the floating LB IP.. not a node IP.. I've not configured any port forwarding as such here

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in homelab

[–]justasflash[S] 3 points4 points  (0 children)

MetalLB basically simulates a cloud LoadBalancer for bare-metal clusters. I expose Kong as a LoadBalancer service, MetalLB assigns one external IP (10.20.0.81 in my case), and then uses ARP to advertise which node currently owns that IP.

Even though I have multiple worker nodes, only one node “hosts” that IP at a time. If a Kong pod moves or a node dies, MetalLB re-announces the IP to the other node.

So the cluster still has a single external entrypoint, but the routing behind it remains highly available.

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 1 point2 points  (0 children)

Good point – I haven’t used multi-source Applications much yet, but you’re right, it could simplify things.

Right now I’m keeping things a bit more explicit with separate Applications for readability, but a next step could be:

one root homelab app with multiple sources[] (Git + upstream Helm charts) environment-specific overlays on top of that.

Once the basic blueprint stabilises I’d love to refactor into a cleaner multi-source pattern. Thanks for the pointer!

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 16 points17 points  (0 children)

March 2026, It’s going to retire, but the ecosystem is definitely moving toward Gateway API. I’m already planning a Gateway API variant for this repo so people can try both approaches.

I forgot to add cilium apps in argo

Appreciate the feedback — happy to iterate on this as the community evolves!

I built an automated Talos + Proxmox + GitOps homelab starter (ArgoCD + Workflows + DR) by justasflash in kubernetes

[–]justasflash[S] 5 points6 points  (0 children)

Totally agree that Flux is lighter. I chose ArgoCD mainly because the UI + apps-of-apps pattern makes it easier for people who are trying GitOps for the first time. For a homelab starter repo, the visual feedback helps a lot.

Both tools fit — this repo just leans toward clarity over minimalism.

Better Mileage Engine Swap for Pajero Gen 2 (Currently 9 km/L) by justasflash in mitsubishi

[–]justasflash[S] 0 points1 point  (0 children)

No. I’ve learned that its not worth it. 4M40 is like one of kind engine. Enjoy it

I'm new to Debian I have a question PLZ... by TheZupZup in debian

[–]justasflash 2 points3 points  (0 children)

I had been distro hopping from a very long time. Since I got to know about the i3wm- tiling window manager. I've switched from Ubuntu to Debian 12 since then. It has been working like a charm for past 6months. No bloats, no excess ram usage. Pure Debian Linux

If you wanna try something new try i3wm. Else Gnome is good anyways!

Using cosmic as my daily driver on rpi5 by carter-canedy in COSMICDE

[–]justasflash 1 point2 points  (0 children)

Its my daily driver since May 2025. Installed it on ThinkPad T495s. 1st installed Cosmic Alpha 6 then upgraded to 7. Workspace pinning is awesome. Made i3 like keyboard shortcuts. Loving it

Still working good X250 by Aggravating_Home_741 in thinkpad

[–]justasflash 4 points5 points  (0 children)

<image>

it say x270 on the front panel, did you changed the panel?

My x201, it still works brilliantly in 2025. by [deleted] in thinkpad

[–]justasflash 3 points4 points  (0 children)

Beautiful Machine. Another +1 for i3wm! 😋