its_me_gb

When my brother had his first child, we spent a Sunday cooking up a load of meals, portioning them up into those foil takeaway containers (cheap on eBay) and freezing them and then gave them those.

They said they were a god send, it meant that they didn’t have to think about preparing dinners whilst they were coping with the new born.

I have pretty much this exact setup.

• k3s cluster running on proxmox
• FluxCD for Deployment (not operator)
• NFS storage on truenas
• Longhorn with SSD storage for PVCs
• Traefik for ingress (recently switched from nginx ingress controller)
• cloud native Postgres for DB
• Prometheus/Loki for monitoring
• sops for secret encryption

That being said, all of the configs are stored in a private git repo that isn’t exposed to the internet, so I’m afraid I can share it all with you.

Like others, I don’t use a UI for Flux, just a combination of VSCode, Vim, kubectl, k9s and the flux cli.

Kubernetes is not for the faint hearted and is a massive step up/learning curve from Docker. I definitely wouldn’t recommend it for everyone, I’m ‘lucky’ that I also work with it most of the time in my day job.

I can share my immich helm release later, but I’d suggest looking into bjw-s-app template and having a look at https://kubesearch.dev/

I’m currently on book 5 of the Dungeon Crawler Carl series, I started book one In January.

After lots of button spamming, I eventually got my order placed.

Payment processor can’t keep up with the demand.

I’m glad it helped! As i said, it was all from memory and was a good few years ago, so hopefully it all still applies!

The biggest issue you’re going to have is that the Virgin hubs don’t allow you to change the DNS server that they hand out via DHCP.

By default, Virgin hubs are in ‘Router mode’, this means that they use DHCP to hand out IP addresses, a default gateway address (the hubs own IP address), and DNS server addresses. Typically the DNS server will be the Hub itself and any request sent to the hub will then be forwarded on to the DNS servers that the hub had defined for forward lookup.

Virgin have decided that they know best and don’t allow you to change the DNS servers that they forward your requests to, so you can’t modify the router to point to your PiHole.

There are a couple of options here (and forgive me, I’m doing this from memory as I no longer use virgin):

1. Disable DHCP (IP addresses management) on the Virgin hub and enable it on the PiHole, if possible. You can then configure the PiHole to hand out the IP addresses for the network, including the PiHole address as the DNS servers (and the Virgin hub as the gateway).

2. Put the Virgin Hub into ‘modem mode’. This requires you to buy an additional router that will allow you to change the DNS servers to point to your PiHole. Putting the Virgin hub in modem mode basically disables all Router functionality and tells it to only terminate the network connection of the virgin connection, you then connect you new router to the hub (and only your new router) to perform all of the functions required to handle your network. You’ll also need to disable WiFi on the Virgin hub (but I think it may do that automatically in modem mode).

In my opinion, if you can use the method in point 1, that’ll be your easiest and cheapest option, if not, you’re going to have to get a new router.

When I had Virgin (many, many years ago) I went down route 2, but mainly because I wanted more control over my network than Virgin would allow me than with their shitty virgin hubs.