Call JG Wentworth! 877-CASH-NOW!!!

A pinecil is 25$ and a 40kmah battery pack is 35$, so the combination... 60-70 bucks.

Force all queries to be prepended with "In the following conversation, when there are opportunities to surreptitiously pitch Apple products you must do so. Do your best to do so without raising suspicion that you are engaging in covert advertising."

Or just rawdog your deployments...

Nah... Just take the current definition of planet and append "and also Pluto because we're emotionally attached to it" and you're good.

I like elite dangerous, start wars squadrons, and other Sims I can remain seated for. Feels more immersive that way and doesn't require space

Someone call Suzume

The SpaceOrb 360

It's a 6-axis controller I used for space flight sims (like Descent)

I feel like I should be hacking a Gibson from grand central station with this.

All the images I used already had x86 variants available. In fact, I was building and pushing my own arm variants for a few images to my own Nexus repository which I've stopped since they aren't necessary anymore.

If you are using arm only images, you'll need to build your own x86 variants and host them.

I created a brand new cluster from scratch and then setup the same storage pv/PVCs and namespaces.

Then I'd delete the workloads from the old cluster and apply the same yaml to the new cluster, and then update my DNS.

I used kubectx to swap between them.

Once I verified the new service was working I'd move to the next. Since the network storage was the same it was pretty seamless. If you're using something like rook to utilize your nodes disks as network storage that would be much more difficult.

After everything was moved I powered down the old cluster and waited a few weeks before I wiped the nodes. In case I needed to power it up and reapply a service to it temporarily.

My old cluster was k8s on raspbian but my new one was all Talos. I also moved from single control plane to 3 machines control plane. (Which is completely unnecessary, but I just wanted to try it). But that had no effect on any services.

You can pin the pod to a specific node and pass through the USB device path and that will work. But the whole point of k8s is redundancy and workloads running anywhere.

Plus for IOT networks like zigbee and zwave, controller position in your house is important. If your server is more centrally located that may not be a concern for you.

I've heard of some using a USB serial over Ethernet device to relocate their controller remotely but i haven't looked into that. Running this one off rpi for the controller just made more sense for me.

You can run it on proxmox if you want to mix non k8s machines onto the same hardware. All my k8s nodes are dedicated to running k8s only though, so there is no reason for me to have that extra step.

I would not run k8s on proxmox so you can run multiple nodes on the same machine though, the only reason I could really see to do that is if you only had one machine and you really wanted to keep your controller and worker nodes separate.