NiftyLogic

joined 10 months ago
[–] [email protected] 1 points 9 months ago

CoreDNS as my central DNS manager in my home(lab).

Currently two nodes are running CoreDNS with the same config for resilence. I really hate long DNS chains, because if something breaks in between, DNS is out ... wife and children scream ... me unhappy.

Current setup with five zones:

- .fritz.box - resolved to the provider-supplied router which also manages my network printer

- .home - forwarded to my UDM which runs DHCP in my home

- .lab.home - zone file which define s a wildcard to resolve all requests to my Traefik reverse proxy

- .consul - forwarded to Consul service catalog for service discovery

- . - everything else (internet) is either forwarded to AdGuard Home (and then to Cloudflare DNS) if the AdGuard service is running. If not, forward directly to the UDM. Nomad + Consul are amazing for this kind of templating and dynamic re-configuration.

Works quite well for me :-)

[–] [email protected] 1 points 9 months ago

Same here, had a deeper look at MicroK8s and decided to go the Nomad route...

Unfortunately, I'm just running a homelab setup. With two publicly exposed services, but noting enterprise like.

Does that count as "in producion"? If yes, what are your questions?

[–] [email protected] 1 points 10 months ago (2 children)

Nomad is totally fine to run on low-spec machines. On my homelab, I have the following running Nomad + Consul:

  • VM with 1GB as arbiter
  • 2 MFF PCs with 16GB and i5-6500T

Totally fine to run client and server on the same machine in a non-enterprise setup.

One stand-alone machine should also work, you just lose the failover capabilities.

[–] [email protected] 1 points 10 months ago

IMHO not really.

There is the slight chance that DBs get inconsistent with backing up hot DB files, but in a homelab with minimal load this is usually not an issue. Same for NFS.

Just make sure you have older backups, too. Just in case the last backup was not good.