How to Migrate Built-In Blueprints to User-Managed Blueprints

Alternatively, open the Blueprints page in the Veeam Kasten for Kubernetes dashboard. Click Add Blueprint, paste the blueprint YAML and click Validate and Save.

4. Bind the blueprint to the application.

   1. For K8ssandra or Crunchy PGO, create a Blueprint Binding that selects the CassandraDatacenter or PostgresCluster resource type. A Blueprint Binding covers every matching resource, including ones created later, so you do not need to annotate each instance. See the Blueprint Binding API reference for the full resource selector syntax.

      Alternatively, add the kanister.kasten.io/blueprint: <blueprint-name> annotation directly to a single CassandraDatacenter or PostgresCluster resource. In the Veeam Kasten for Kubernetes dashboard, do this from the Applications page. Select the resource, open its ellipsis menu and choose Configure Blueprints. Then select the blueprint from the Blueprint Annotation dropdown. See Managing Blueprint Resources for the full walkthrough.

   2. For RDS PostgreSQL, create a Blueprint Binding that selects ConfigMaps by resource type and a label or annotation you control. A Blueprint Binding matches every ConfigMap that carries your chosen label or annotation, in any namespace. You do not need to repeat the step for each namespace. Do not select on the kanister.kasten.io/rds: rds-postgres annotation itself. Step 5b removes that annotation, which would also stop the Blueprint Binding from matching.

      Alternatively, add the kanister.kasten.io/blueprint: <blueprint-name> annotation directly to each ConfigMap. Unlike a Blueprint Binding, this requires a separate step for every ConfigMap. In the Veeam Kasten for Kubernetes dashboard, do this from the Applications page. Select the ConfigMap, open its ellipsis menu and choose Configure Blueprints. Then select the blueprint from the Blueprint Annotation dropdown. See Managing Blueprint Resources for the full walkthrough.

5. Disable the built-in blueprint.

   1. For K8ssandra or Crunchy PGO, set the Helm value kanister.managedDataServicesBlueprintsEnabled to false, and upgrade the Veeam Kasten for Kubernetes release. This value applies to every K8ssandra and Crunchy PGO application in the cluster. Before you change it, confirm that each application has a user-managed blueprint.

      Note: This setting stops Veeam Kasten for Kubernetes from using the built-in blueprint. It does not delete the built-in Blueprint CR that Veeam Kasten for Kubernetes already created. That CR is named k10-k8ssandra-bp-<version> or k10-pgo-bp-<version>, in the kasten-io namespace, and it is now unused. You can delete it manually once you confirm the new blueprint works.

   2. For RDS PostgreSQL, remove the kanister.kasten.io/rds: rds-postgres annotation from the ConfigMap. Veeam Kasten for Kubernetes uses this annotation to trigger the built-in blueprint, independently of any Blueprint Binding or kanister.kasten.io/blueprint annotation. The built-in blueprint stops running once you remove it. You do not need a Helm change.
6. Run a manual backup to confirm Veeam Kasten for Kubernetes uses the new blueprint. In the dashboard, go to the Policies page and click Run Once on the application's policy. Alternatively, open the Policy View page and click the Run Once button there. See Manual Policy Runs for details.