Kasten DR backup fails on brand new installation

I ran into the same issue on a fresh Kasten K10 install when trying to export metadata to an S3 bucket. Even though multicluster wasn't enabled, the export process failed with an error like:

error when collecting data: error when retrieving instances of type dist.kio.kasten.io/v1alpha1, Resource=bootstraps: the server could not find the requested resource


Although multicluster isn’t configured, Kasten still expects the multicluster CRDs to exist when exporting metadata. To resolve this, you need to apply the CRDs manually, no need to actually enable multicluster.

After applying, I was able to run the export again successfully. Thats works for me. 

Kasten attempts to retrieve all known resource types during export, like bootstraps, policies, profiles. If the CRDs aren’t present, even if unused, it throws an error. This is common in new environments where multicluster support hasn’t been initialized.

Hope this helps

Hey Matheus - thanks for replying.

Where do I get these multicluster CRDs from, and why on Earth would they not be installed by default? I’ve searched the Helm values file but can’t see any option to install them by default.

To have to manually update a cluster that was deployed using automation… is not great!

 

-Mark

Wait… this cannot be right.

So basically EVERY kasten customer who uses DR must be failing if they’re not using Multicluster/customer doesn’t manually install the CRDs.

That just doesn’t seem right. That must generate thousands of support requests. Or no-one is using DR.

Either way this seems bonkers.

Yes this is not the case there is absolutely no way you need to have multi cluster configured. 
 

please share case number and I will get some more details. 

This doesn’t seem the correct mode to get things working at all. 

Support icket is # 07757320