Sounds very cool, and I’m going to be a huge ass and say that could have easily been done with k3s and either flux or argo image watcher.

+1 for terraform at home tho, I do the same and people look at me like I’ve curb stomped their child

For cloudflare tunnels no, it does a nat punch through I think it’s called, where it connects from inside your network out to 2 edge locations to cloudlfare, where it then can send traffic back and forwards.

​

If I wanted to expose by port forwarding, then yes you are correct, I could configure ddns.

Personally, I would configure my own version of DDNS where it’s just a cron job once every 5 minutes to run terraform and check if my public IP has changed, and if it has run an apply.

​

Does that answer the question?

I use it within my Kubernetes to expose services outsides my house, and then I use Azure AD to manage access.

I know this isn’t very self hosted, but for me where I have a dynamic IP and don’t want to play with port forwarding, it’s really good. Nice and easy especially with Kubernetes and the helm chart I wrote

That’s impressive.

I’m crying in .35p/kwh ($0.43)

Am I allowed to answer both?

A simple docker-compose stack would probably do everything you need

My view is skewed as I run k8’s at work, but I have a single node k3s cluster and have all my things on there, and honestly I forgot about it until now