f505c4da75
## What this PR does The `backupstrategy-controller` chart declared a `Role` and `RoleBinding` scoped to the `cozy-velero` namespace (for managing `ResourceModifier` ConfigMaps consumed by Velero Restore). Because `cozystack.velero` is an optional package, that namespace does not exist in bundles that do not enable velero — and `backupstrategy-controller` is a **default** package. Helm install aborted with: ``` namespaces "cozy-velero" not found ``` which blocked the entire `cozy-backup-controller/backupstrategy-controller` HelmRelease on any cluster where velero was not explicitly enabled (including the E2E environment). This PR moves that Role/RoleBinding into the velero chart (`packages/system/velero/templates/backupstrategy-controller-rbac.yaml`), so the permission grant only exists when velero is actually installed — where it is useful. The RoleBinding subject points to the stable `backupstrategy-controller` ServiceAccount in `cozy-backup-controller`. ### Release note ```release-note fix(backups): moved the velero-namespaced ResourceModifier ConfigMap Role and RoleBinding from the backupstrategy-controller chart into the velero chart. This unblocks installs of backupstrategy-controller on bundles that do not enable velero (previously the HelmRelease failed with `namespaces "cozy-velero" not found`). ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Reorganized RBAC configuration for the backup strategy controller by consolidating namespace-scoped role definitions in the Velero chart template * Updated role bindings and permissions structure across system packages <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| definitions | ||
| images/backupstrategy-controller | ||
| templates | ||
| Chart.yaml | ||
| Makefile | ||
| values.yaml | ||