Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Raspberry Pi Homelab with Kubernetes

amithm.ca

Post reply on HN
Print view View original

41–50 of 52 posts

Re: Raspberry Pi Homelab with Kubernetes

#41

Post by throwaway894345 »

wil421 wrote: post #24
anderspitman wrote: post #7

As has become my habit lately, I'll chime in and say if you're interested in accessing your self-hosted services from the internet, IMO tunneling is the way to go: https://github.com/anderspitman/awesome-tunneling

Most of my services are only available by using a vpn into my home network. I can understand why you might need a public facing service but I avoid it like the plague.

I have an EC2 instance running caddy that proxies through to my RPI cluster via VPN. It was pretty easy to set up. And Caddy handles HTTPS and HTTP->HTTPS redirection out of the box.

Re: Raspberry Pi Homelab with Kubernetes

#42

Post by erulabs »

anderspitman wrote: post #7

As has become my habit lately, I'll chime in and say if you're interested in accessing your self-hosted services from the internet, IMO tunneling is the way to go: https://github.com/anderspitman/awesome-tunneling

If you’re using Kube, I’m building a service to solve this for home hosting. Checkout https://KubeSail.com (YC S19) - we forward traffic to your ingress controller over a tunnel so that you can host public apps on the internet from home without dynamic DNS or port forwarding . Feedback welcome :)

Re: Raspberry Pi Homelab with Kubernetes

#43

Post by jlgaddis »

justinholmes wrote: post #35
gravypod wrote: post #34

Earlier quoted context omitted.

Because they have a lot of Raspberry Pis, they want to setup kubernetes, and they have fun doing it and what to share that with the rest of the internet?

It's been done since 2014 when K8s came out. Move on please. Still I guess it's better than AKS.

You are always free to simply not read the articles!

In fact, you'll not only save yourself time, you'll also save us time too (as then we won't have to read your useless comments).

Re: Raspberry Pi Homelab with Kubernetes

#44

Post by anderspitman »

jlgaddis wrote: post #38
anderspitman wrote: post #26

Earlier quoted context omitted.

I see it as an important step to a more decentralized future. For example, I know a few people who maintain Plex servers for their friends and family. This works quite well, but getting the server on the internet is the trickiest part. You can sink a lot of time into configuring routers, managing certs, NAT, DMZ, LMNOP. Or you can use a tunneling service that manages all of it for you.

The way to a more decentralized future is through yet another third-party service?

Huh? Are you referring to the VPS provider?

Re: Raspberry Pi Homelab with Kubernetes

#45

Post by sovreign »

anderspitman wrote: post #7

As has become my habit lately, I'll chime in and say if you're interested in accessing your self-hosted services from the internet, IMO tunneling is the way to go: https://github.com/anderspitman/awesome-tunneling

For my personal homelab Nginx Proxy Manager has been great (https://nginxproxymanager.com/). It provides a dead simple ui for configuring Nginx to expose internal services, even websocket servers, and integrates easy https cert managmenet (with Let's Encrypt wildcard subdomain support!).

Re: Raspberry Pi Homelab with Kubernetes

#46

Post by redis_mlc »

justinholmes wrote: post #33

Why are people still posting these Pi homelabs they have been done to death. I run microk8s on KVM running in Mesos with openvswitch and Mikrotik CRS/CCRs.

The parent has a valid point.

If you buy hardware for an experimental cluster, I recommend each node has 8+ GB RAM and a fairly current processor (no Atom.) Otherwise you're really buying e-waste. Cutting down modern software so it runs in a limited amount of RAM is really no fun.

Some of the most ridiculous have been "running" Cassandra on early Pi nodes, or really any Java software.

Re: Raspberry Pi Homelab with Kubernetes

#47

Post by huseyinkeles »

wil421 wrote: post #25
huseyinkeles wrote: post #13

Earlier quoted context omitted.

I really tried! But maybe because my setup was a bit demanding, rPi4 couldn't handle it well. (home-assistant, adguard home, nextcloud, plex, *arr apps, and many more on docker) I just had to switch to a SFF desktop PC with Ubuntu on it and never looked back. For toying around rPis can be fun but in real life applications, they were getting extremely hot. Had to add extra fans etc. I still use my rPi4s, one of them c…

Why kind of quality did you get running plex? I doubt a cluster of pi’s could keep up with the transcoding.

Very poorly. The cooling is a big problem as well.

Now I switched to x86, I’m even sharing my Plex library with a few more people (looking at the Tautulli stats, it’s been transcoding a lot) without any problems.

If it becomes an issue, I’d add a GPU but for now a 6 core AMD is doing a very good job.

Re: Raspberry Pi Homelab with Kubernetes

#48

Post by anaganisk »

justinholmes wrote: post #33

Why are people still posting these Pi homelabs they have been done to death. I run microk8s on KVM running in Mesos with openvswitch and Mikrotik CRS/CCRs.

So what, scroll to the next article, every article posted may be an improvement, may be there is something done in a new way. Every human has his own way od doing things.

Re: Raspberry Pi Homelab with Kubernetes

#49

Post by melenaos »

justinholmes wrote: post #33

Why are people still posting these Pi homelabs they have been done to death. I run microk8s on KVM running in Mesos with openvswitch and Mikrotik CRS/CCRs.

Is this on a single server? The reason is to learn or does it have any practical reason?

What hardware are you using?

Re: Raspberry Pi Homelab with Kubernetes

#50

Post by anderspitman »

sovreign wrote: post #45
anderspitman wrote: post #7

As has become my habit lately, I'll chime in and say if you're interested in accessing your self-hosted services from the internet, IMO tunneling is the way to go: https://github.com/anderspitman/awesome-tunneling

For my personal homelab Nginx Proxy Manager has been great ( https://nginxproxymanager.com/ ). It provides a dead simple ui for configuring Nginx to expose internal services, even websocket servers, and integrates easy https cert managmenet (with Let's Encrypt wildcard subdomain support!).

NPM looks solid, but it still requires you to set up port forwarding and hope your ISP doesn't block ports 80/443, right?
Post reply on HN