pvmigrate VS velero

All of the facts based queries I have asked so far have not been 100% correct on any LLM including this one.

Here are some examples of the worst performing:

"What platform front rack fits a Stromer ST2?": The answer is the Racktime ViewIt. Nothing, not even Google, seems to get this one. Discord gives the right answer.

"Is there a pre-existing controller or utility to migrate persistent volume claims from one storage class to another in the open source Kubernetes ecosystem?" It said no (wrong) and then provided another approach that partially used Velero that wasn't correct, if you know what Velero does in those particular commands. Discord communities give the right answer, such as `pvmigrate` (https://github.com/replicatedhq/pvmigrate).

Here is something more representative:

"What alternatives to Gusto would you recommend? Create a table showing the payroll provider in a column, the base monthly subscription price, the monthly price per employee, and the total cost for 3 full time employees, considering that the employees live in two different states" This and Claude do a good job, but do not correctly retrieve all the prices. Claude omitted Square Payroll, which is really the "right answer" to this query. Google would never be able to answer this "correctly."

Openshift last I looked used Velero under the covers for the functionality, which works fine in standard kubernetes. Most if not all that Openshift does is Open source.

Valero

velero is also a popular solution to for k8s backup that is 3rd party you might check out.

Logical backups using pre and post hooks thanks to this suggestion https://github.com/vmware-tanzu/velero/issues/2763 working way better than kanister blueprints.

While not discounting OP or the work in this repo (seems like a fun k8s/go project), folks might check out Velero for this purpose if they're looking to rely on this kind of export in prod: https://github.com/vmware-tanzu/velero

Hyper-V itself does not directly support backing up container-based platforms like Kubernetes clusters. To back up a Kubernetes cluster, you would typically use tools that interact with the Kubernetes API to capture the necessary data and metadata for backup purposes. Some of those tools are Velero https://velero.io/ (formerly Heptio Ark), Kasten K10, and Stash.

For Kubernetes-land, https://velero.io/ is awesome - but I haven't used it for online-database backups yet. If you're exploring, I'd checkout Velero - if you just need something to work reliably, I'd checkout Percona.

If you're looking for a backup solution for managed kubernetes, check out Velero. It is great for non-managed kube as well (but you've got other options like etcd backups)

You can also leverage https://velero.io/ to backup both cluster state and pvc state to s3