Reading the Docs, it seems like PodMan is the replacement for docker. You could try containerd/nerdctl, but podman is likely the best way for you. RHEL10 docs even say it supports the older docker config options

Tailscale/headscale/wire guard is different from a normal vpn setup.

VPN: you tunnel into a remote network and all your connections flow through as if you’re on that remote network.

Tailscale: your devices each run the daemon and basically create a separate, encrypted, dedicated overlay network between them no matter where they are or what network they are on. You can make an exit node where network traffic can exit the overlay network to the local network for a specific cidr, but without that, you’re only devices on the network are the devices connected to the overlay. I can setup a set of severs to be on the Tailscale overlay and only on that network, and it will only serve data with the devices also on the overlay network, and they can be distributed anywhere without any crazy router configuration or port forwarding or NAT or whatever.

Honestly, that sounds like a keepalived replacement or equivalent. I went with keepalived because I’m also using the IP for the proxmox cluster itself so it had to be outside kube, but the idea is the same. If all you’re using the IP for is kube, go with kube-vip! But let us know how it works!

You’ll want to look into “keepalived” to setup a shared IP across all worker nodes in the cluster and either directly forward, or setup haproxy on each to do the forwarding from that keepalived IP to the ingresses.

I’m running 6 kube nodes (running Talos) running in a 3node proxmox cluster. Both haproxy and keepalived run on the 3 nodes to manage the IP and route traffic to the appropriate backend. Haproxy just allows me to migrate nodes and still have traffic hit an ingress kube node.

Keepalived manages which node is the active node and therefore listens to the IP based on backend communication and a simple local script to catch when nodes can’t serve traffic.

Have it sync the backup files from the -2- part. You can then copy them out of the syncthing folder to a local one with a cron to rotate them. That way you get the sync offsite and you can keep them out of the rotation as long as you want.

There’s a normal docker image, If this is all you want. However in all honesty, kubernetes is so nice to work with compared to running multiple docker compose things on the same host or the nightmare of a multi-host docker only lab. Just depends on how much homelab/selfhosting you’re doing. I know I’m grateful they included a helm chart here and I wish more self hosted software projects did as well. Options are always nice to have.

Current homelab+desktop+laptop host count here is 22. All anime characters or references. It’s a fairly large pool to pull from, so it’s worked for me for 20+ years now. Mobile devices (phones, tablets, etc) and game consoles aren’t really as clever though.

All of them are in a piHole DNS though so no host files keeps it easy to track. Services have names that mostly are just what they are though and cnames to the matching host that hosts them (or load balancer, whatever)

Got a plex lifetime sub like 7 years ago… As soon as Jellyfin allows downloads for offline viewing, I’m jumping ship. I know I’ll have to figure out TV listing data for OTA recordings, but that seems like a small price to pay. I’ve already got Jellyfin setup and running in my Kubernetes cluster for my video backups, but plex thus far “just works”.

I just tell it to back up my laptops every hour anyway. If it’s not on, it just doesn’t happen, but it’s generally on enough to capture what I need.

Nice, we’ll all look out for an update in a year!

I try to mix brands and lots (buy a few from one retailer and some from another). I used to work for a storage/NAS company and we had many incidents when we’d fill a 12 or 24 drive raid with drives right from the same order and had multiple drives die within hours of each other. Which isn’t usually enough for replacement/resilvering.

Mine are 3x 27k and 1x 47k. I just started replacing them… not because they’re old or have any issues, just because they’re becoming too small. Going from 4 to 8 tb disks and transferring the old ones to an external raid enclosure for backups.

Actually brings up a question I had… what do people think about refurbished drives for a NAS?

Finish my migration to my local Kubernetes cluster. Tired of running a mix of vms, docker, and bare metal. I got it setup and a few things, just have to power through.

I also need to bump the drive size in my NAS as I’m running low and want to leverage it more, not less. (Pods use PVs hosted on the NAS over NFS or iSCSI).

And get my offsite backups going again, I had to move this last year and it put a real damper on my goals for last year so there’s a lot of “got the stuff just have to make it work”.

Edit: the UDM Pro is pretty nice. That, a rack and a 2.5G enterprise switch were last year’s acquisitions.

We used turbo pascal in school in the early 90’s. And it had assembly blocks… which I used copious amounts of because it was the only way to make the IBM PS/1’s do useful graphics.

Ironically, ChatGPT is trained from the online communities.

And without fresh data on the communities, CharGPT will soon lack the answers people seek.

Don’t forget, Kubernetes is totally happy with json input and output instead. Use json, be the change you want to see in the world!

Even if you use a data cable, it might not have the pins/wires for usb 1.1 fallback meaning a keyboard or mouse won’t work with it. Or it might support low power only. I had to buy a usbc cable tester to validate which ones might actually work with what.

My favorite is that not all chargers support all voltages. I have a few that do 5v, 9v, and 20v, but if your device asks for 12v, you’re out of luck, you either don’t get anything, or it fails back to 9v which isn’t enough to accomplish what the device wants to do (like charge). Still, it’s standards compliant!

The standard explicitly allows but doesn’t require support of any subset of standards so you never REALLY know what that cable or charger in your hand or the devices you’re holding can actually do without finding specs in docs… It’s really infuriating. The idea of USB-C is better than the reality, which makes the push to standardize on the connector not nearly as cool as it could be.

True, but TCP will just resend them, you won’t lose anything but some latency. Meaning it’s something to look into, but not something to panic about.