11---
2- sidebar_position : 41
2+ sidebar_position : 90
33---
44
5- # Resource Name Migration Guide
5+ # Resource name migration guide
66
77<!-- SPDX-License-Identifier: CC-BY-4.0 -->
88
@@ -64,7 +64,7 @@ Please refer to the [Installation](installation.mdx) section to deploy the new p
6464:::danger Verify Resources Before Deletion
6565** IMPORTANT** : The old resource names are generic and could potentially belong to other components in your cluster.
6666
67- ** Before deleting each resource, verify it belongs to the barman plugin by checking:**
67+ ** Before deleting each resource, verify it belongs to the Barman Cloud plugin by checking:**
6868- For ` objectstore-* ` roles: Look for ` barmancloud.cnpg.io ` in the API groups
6969- For ` metrics-* ` roles: Check if they reference the ` plugin-barman-cloud ` ServiceAccount in ` cnpg-system ` namespace
7070- For other roles: Look for labels like ` app.kubernetes.io/name: plugin-barman-cloud `
@@ -79,7 +79,8 @@ You can add `--dry-run=client` to any `kubectl delete` command to preview what w
7979removing anything.
8080:::
8181
82- ** Only proceed if you've verified these resources belong to the barman plugin (see warning above).**
82+ ** Only proceed if you've verified these resources belong to the Barman Cloud
83+ plugin (see warning above).**
8384
8485For each resource below, first verify it belongs to barman, then delete it:
8586
@@ -124,7 +125,7 @@ kubectl delete clusterrole metrics-reader
124125The ` metrics-reader ` role is particularly dangerous to delete blindly. Many monitoring systems use this exact name. Only delete it if:
1251261 . You've verified it ONLY grants access to ` /metrics `
1261272 . No other rolebindings reference it (checked with the jq command above)
127- 3 . You're certain it was created by the barman plugin
128+ 3 . You're certain it was created by the Barman Cloud plugin
128129
129130If you're unsure, it's safer to leave it and let the new ` barman-plugin-metrics-reader ` role coexist with it.
130131:::
0 commit comments