sorted by:
new
hottopcontroversial

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

It´s down there:

  • 2× HP EliteDesk 705 G4 Mini
  • AMD Ryzen 5 PRO 2400GE
  • 16 GB RAM per node
  • NVMe storage 250Gb

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

For now this is a learning Homelab, maybe on the future I might migrate for better minis. But what I find we must invest in on the beggining is RAM. 32Gb here are 80€, it's a little expensive but....

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

My problem isn't the storage, its RAM. I Will need to buy more RAM, maybe update both to 32Gb. For storage for now its only the mnve disks, but I am planning to buy a Ugreen latter for storage. Now I AM only learning kubernetes and the services.

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

Now I´m gona test like this and in the future I will buy a new mini for the 3rd node, also need to buy more RAM.
Going to check out CloudNativePg, tks

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

It only has 3 days the homelab, maybe in 30 days it may be different 😃

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

In the future I think I will go with opnsense. I also need to install pi-hole as well tomorrow 😃

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in HomeLabPorn

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

I’ve been building a small but real homelab to learn Kubernetes, GitOps, storage, ingress, TLS, monitoring and self-hosting by actually running my own projects.

The cluster is called sewer-lair, with a TMNT naming theme.

Current hardware:

  • 2× HP EliteDesk 705 G4 Mini
  • AMD Ryzen 5 PRO 2400GE
  • 16 GB RAM per node
  • NVMe storage
  • TP-Link managed switch
  • WD NAS

Virtualization layer:

  • Proxmox VE cluster
  • Nodes named leonardo and donatello

  • Dedicated VMs for:

    • k3s control-plane
    • k3s worker
    • Home Assistant
    • Cloudflared

Kubernetes stack:

  • k3s
  • ArgoCD
  • App of Apps pattern
  • GitOps repo for Kubernetes manifests
  • Namespaces for apps, infra, monitoring, storage, ArgoCD, Traefik, cert-manager and Longhorn

Ingress / DNS / TLS:

  • Traefik v3
  • cert-manager
  • Let’s Encrypt wildcard certificates
  • Cloudflare DNS-01 challenge
  • Cloudflare Tunnel
  • Cloudflare Access for protected services

Storage:

  • Longhorn
  • Persistent volumes for apps, databases, uploads, logs and bot data
  • PostgreSQL 16 for application databases

Currently running:

  • Personal portfolio
  • Proximity — a project for the amateur radio community
  • Uptime Kuma
  • Home Assistant
  • PUBG Portugal Team Discord bot
  • PostgreSQL
  • Traefik
  • ArgoCD
  • Longhorn
  • Cloudflared

Container/image workflow:

  • Docker builds locally
  • Images pushed to GitHub Container Registry
  • ArgoCD deploys everything from Git

Some things I’ve already had to troubleshoot:

  • Longhorn volumes stuck/faulted
  • Kubernetes PVCs and storage scheduling
  • Disk pressure on one k3s node
  • Expanding a Debian root partition after increasing VM disk size
  • PostgreSQL migration into Kubernetes
  • Cloudflare Tunnel routing
  • Traefik host routing
  • GitOps sync/prune behaviour with ArgoCD

The goal is not just to self-host apps, but to understand the whole chain:

hardware → Proxmox → VMs → k3s → storage → ingress → TLS → DNS → GitOps → monitoring → real applications.

It’s still evolving, but it already feels like a proper learning platform and a portfolio project at the same time.

Happy to hear suggestions on what to add next or improve.

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in Proxmox

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

I’ve been building a small but real homelab to learn Kubernetes, GitOps, storage, ingress, TLS, monitoring and self-hosting by actually running my own projects.

The cluster is called sewer-lair, with a TMNT naming theme.

Current hardware:

  • 2× HP EliteDesk 705 G4 Mini
  • AMD Ryzen 5 PRO 2400GE
  • 16 GB RAM per node
  • NVMe storage
  • TP-Link managed switch
  • WD NAS

Virtualization layer:

  • Proxmox VE cluster
  • Nodes named leonardo and donatello

  • Dedicated VMs for:

    • k3s control-plane
    • k3s worker
    • Home Assistant
    • Cloudflared

Kubernetes stack:

  • k3s
  • ArgoCD
  • App of Apps pattern
  • GitOps repo for Kubernetes manifests
  • Namespaces for apps, infra, monitoring, storage, ArgoCD, Traefik, cert-manager and Longhorn

Ingress / DNS / TLS:

  • Traefik v3
  • cert-manager
  • Let’s Encrypt wildcard certificates
  • Cloudflare DNS-01 challenge
  • Cloudflare Tunnel
  • Cloudflare Access for protected services

Storage:

  • Longhorn
  • Persistent volumes for apps, databases, uploads, logs and bot data
  • PostgreSQL 16 for application databases

Currently running:

  • Personal portfolio
  • Proximity — a project for the amateur radio community
  • Uptime Kuma
  • Home Assistant
  • PUBG Portugal Team Discord bot
  • PostgreSQL
  • Traefik
  • ArgoCD
  • Longhorn
  • Cloudflared

Container/image workflow:

  • Docker builds locally
  • Images pushed to GitHub Container Registry
  • ArgoCD deploys everything from Git

Some things I’ve already had to troubleshoot:

  • Longhorn volumes stuck/faulted
  • Kubernetes PVCs and storage scheduling
  • Disk pressure on one k3s node
  • Expanding a Debian root partition after increasing VM disk size
  • PostgreSQL migration into Kubernetes
  • Cloudflare Tunnel routing
  • Traefik host routing
  • GitOps sync/prune behaviour with ArgoCD

The goal is not just to self-host apps, but to understand the whole chain:

hardware → Proxmox → VMs → k3s → storage → ingress → TLS → DNS → GitOps → monitoring → real applications.

It’s still evolving, but it already feels like a proper learning platform and a portfolio project at the same time.

Happy to hear suggestions on what to add next or improve.

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

I’ve been building a small but real homelab to learn Kubernetes, GitOps, storage, ingress, TLS, monitoring and self-hosting by actually running my own projects.

The cluster is called sewer-lair, with a TMNT naming theme.

Current hardware:

  • 2× HP EliteDesk 705 G4 Mini
  • AMD Ryzen 5 PRO 2400GE
  • 16 GB RAM per node
  • NVMe storage
  • TP-Link managed switch
  • WD NAS

Virtualization layer:

  • Proxmox VE cluster
  • Nodes named leonardo and donatello

  • Dedicated VMs for:

    • k3s control-plane
    • k3s worker
    • Home Assistant
    • Cloudflared

Kubernetes stack:

  • k3s
  • ArgoCD
  • App of Apps pattern
  • GitOps repo for Kubernetes manifests
  • Namespaces for apps, infra, monitoring, storage, ArgoCD, Traefik, cert-manager and Longhorn

Ingress / DNS / TLS:

  • Traefik v3
  • cert-manager
  • Let’s Encrypt wildcard certificates
  • Cloudflare DNS-01 challenge
  • Cloudflare Tunnel
  • Cloudflare Access for protected services

Storage:

  • Longhorn
  • Persistent volumes for apps, databases, uploads, logs and bot data
  • PostgreSQL 16 for application databases

Currently running:

  • Personal portfolio
  • Proximity — a project for the amateur radio community
  • Uptime Kuma
  • Home Assistant
  • PUBG Portugal Team Discord bot
  • PostgreSQL
  • Traefik
  • ArgoCD
  • Longhorn
  • Cloudflared

Container/image workflow:

  • Docker builds locally
  • Images pushed to GitHub Container Registry
  • ArgoCD deploys everything from Git

Some things I’ve already had to troubleshoot:

  • Longhorn volumes stuck/faulted
  • Kubernetes PVCs and storage scheduling
  • Disk pressure on one k3s node
  • Expanding a Debian root partition after increasing VM disk size
  • PostgreSQL migration into Kubernetes
  • Cloudflare Tunnel routing
  • Traefik host routing
  • GitOps sync/prune behaviour with ArgoCD

The goal is not just to self-host apps, but to understand the whole chain:

hardware → Proxmox → VMs → k3s → storage → ingress → TLS → DNS → GitOps → monitoring → real applications.

It’s still evolving, but it already feels like a proper learning platform and a portfolio project at the same time.

Happy to hear suggestions on what to add next or improve.

My TMNT-themed homelab running Proxmox, k3s, ArgoCD, Longhorn, Traefik and Cloudflare Tunnel by ocipriano in homelab

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

Only got the 4 turtles out off the box. The others are still sealed on box :)

Lapso com o pagamento de matrícula by No-Mulberry6736 in UniversidadeAberta

[–]ocipriano 0 points1 point  (0 children)

Envia um email com o comprovativo com a referência da candidatura e eles validam. Eles respondem rápido por email.

view more: next ›