Now you know that the problem is not your DNS.

It is either your routing or firewalling.

I tell it to point docmost.example.com to 192.168.1.80, […] but actually nothing happens. I get a connection timed out error.

I suggest to collect more info about this “nothing”.

ping from your PC on the inside to the name docmost.example.com

ping from your PC on the inside to the number 192.168.1.80

traceroute from your PC on the inside to the name docmost.example.com

traceroute from your PC on the inside to the number 192.168.1.80

Then do the same in the reverse direction: from that docker container to your PC.

Maybe traceroute shows you some stations on the route. Then do the same from this station.

Write down the results thoroughly.

You do not let your k8s control instance look “live” at your git server during the start (or reformation) of the whole cluster. It needs the (repo and) files checked out somewhere locally, and this local “somewhere” must exist at start time.

Later, when your git is alive, you do a regular git pull for keeping it up to date.

chicken and egg situation, since I plan to store my Kubernetes manifests in my git repo

Not really.

K8s would use a “checked-out” visible representation, not the repo database itself.

git is file system based.

Git is also a database.

deleted by creator

This is the way

RasPi 4B with the dedicated HassOS distro.

Installation was easy. Upgrades run regularly and very stable.

No. Never would I self-host a search engine.

The crawler would eat up so much more ressources than I am ever willing to spend.

No testing environment in my home lab so far.

But on the other hand, no planned builds either. Just fiddling around til it works.

I am currently planning for new hardware, and then doing it all with build scripts there, as fully automated as possible. The whole setup, from scratch. But for that I need to do some learning first.

So the new hardware is going to be it’s own test environment for a good while, until it turns into production.