Caution
If you are upgrading from v6.x or earlier, apply v7.0.0 first. That release contains its own breaking changes (service account binding, part-of label removal, envFrom format, pod security context) that must be addressed before upgrading to v8.
This release contains breaking changes that standardize resource naming across all templates.
Breaking Changes
1. Resource names now use the release name as default prefix (#466)
The application.name helper now defaults to .Release.Name instead of .Chart.Name when applicationName is not set. All resource names are generated using a consistent printf | trunc 63 | trimSuffix "-" pattern.
If you were relying on the chart name as the default, set applicationName explicitly:
applicationName: application2. PVC name change — risk of data loss
If applicationName was not set, the PVC name changes from <chartName>-data to <releaseName>-data. This will create a new PVC and orphan the existing one, causing data loss.
To prevent drift, set persistence.name to your current PVC name before upgrading:
persistence:
name: <your-current-pvc-name>3. Resources now prefixed with release/application name
Resources that previously used standalone or value-only names are now prefixed:
| Resource | Before | After |
|---|---|---|
| CronJob | <jobKey>
| <name>-<jobKey>
|
| Job | <jobKey>
| <name>-<jobKey>
|
| GrafanaDashboard | <dashboardKey>
| <name>-<dashboardKey>
|
| SecretProviderClass | <spcName>
| <name>-<spcName>
|
| Backup | <applicationName>-backup
| <name>-backup
|
4. Redundant type suffixes removed
| Resource | Before | After |
|---|---|---|
| ClusterRole | <name>-cr-<role>
| <name>-<role>
|
| ClusterRoleBinding | <name>-crb-<role>
| <name>-<role>
|
| Role | <name>-role-<role>
| <name>-<role>
|
| RoleBinding | <name>-rolebinding-<role>
| <name>-<role>
|
| ServiceMonitor | <name>-svc-monitor
| <name>
|
What's Changed
Full Changelog: v7.0.0...v8.0.0