Declaring backup as code (Kubernetes, Terraform or Ansible), curious if this matters outside enterprise use cases?

A lot of home lab setups hit the same issue production clusters do, which is that backup config lives in someone's head or a UI, not in a repo. Or if it's in a repo, it's not usually automatically going to work if you or someone else adds a new workload (PVC, etc.) into the cluster. I'm curious, does any of that matter for your home labs or is this really only a corporate problem? One of the reasons I ask is, I've been looking around for solutions to this problem and see Plakar has a Kubernetes operator and a Terraform / Ansible provider to help declare what's protected and schedule backups. The free tier also looks reasonable with 500 GB. Has anyone tried it? One of their blog posts is at plakar.io/posts/2026-09-23/resilience-as-code-kubernetes-operator .