I've started using iscsi volumes for kubernetes storage, and it seems to be working fine. I have volumes automatically created under Data/k8s/scsi/v for each PV.

As a backup strategy I have periodic snapshots of every volume set up and I am also replicating the entire k8s dataset to a different pool.

I've done this kind of thing for other "normal" filesystem datasets and restoring from snapshots or replications usually just entails copying files. However I'm new to iscsi and "volume" datasets, so if something went wrong with one of my iscsi volume datasets, and I have snapshots and/or replicated them, how do I go about restoring them?

I'm not sure if I'm even asking the right question :) Is the "right" thing to do here to do application-level backups, ie. run sidecars for my k8s workloads that back up the files inside the volumes rather than rely on backups at the TrueNAS level?

Picture of the setup for reference:

I just installed the Kia Uvo integration via HACS but am concerned with settings causing 12v battery drain on the car. Anyone else have this set up and willing to share their experience with it?

Came across this tool on HackerNews last week and gave it a try and thought it was a really comprehensive (in my experience) tool for doing long term financial planning yourself.

It costs money, but you can even self host it for a certain price tier.

About a year ago I hired a financial planner to manage assets in my retirement accounts but am starting to think about doing it myself.

I don't disagree with the general approach they're taking, but it seems like it should be simple enough for me to do myself every 6 months or whatever.

The gist of the strategy is a balance across large/mid/small cap and sectors at certain percents along with some % of bond funds and some real estate funds.

I think my main questions are how do I identify and compare various funds that fall into these broad categories to try and pick the ones I want to actually invest in.

Developers are operating and building in more and more heterogeneous and complex systems. This article offers some thoughts on how to think about "developer experience" in this world that's increasingly more like a "rainforest" than a "well tended garden".

I'd love to hear some stories about how you or your organization is using Kubernetes for development! My team is experimenting with using it because our "platform" is getting into the territory of too large to run or manage on a single developer machine. We've previously used Docker Compose to enable starting things up locally, but that started getting complicated.

The approach we're trying now is to have a Helm chart to deploy the entire platform to a k8s namespace unique to each developer and then using Telepresence to connect a developer's laptop to the cluster and allow them to run specific services they're working on locally.

This seems to be working well, but now I'm finding myself concerned with resource utilization in the cluster as devs don't remember to uninstall or scale down their workloads when they're not active any more, leading to inflation of the cluster size.

Would love to hear some stories from others!