Skip to content

Resource naming changes in Rancher Prime v2.13.1 Helm installation

Article Number: 000022266

Environment

  • Rancher Prime v2.13.1 Helm installation

Situation

Starting with Rancher Prime v2.13.1, the Helm chart name has been updated from rancher to rancher-prime. Due to the internal logic of the Helm chart, this change causes deployed resources (such as the Deployment, Service, and Ingress) to be named rancher-rancher-prime by default, rather than the legacy rancher name.

Cause

This behavior is driven by the rancher.fullname logic within the Rancher Helm chart.

  • Previous Versions: Both the Release Name (rancher) and the Chart Name (rancher) matched. The rancher.fullname template simplifies the name to just rancher when these two strings are identical.
  • v2.13.1: The Release Name (rancher) no longer matches the new Chart Name (rancher-prime), the template concatenates them, resulting in rancher-rancher-prime.

Resolution

To maintain the legacy naming convention (rancher) and avoid resource name changes during an upgrade, you can explicitly set a nameOverride in your Helm command or values.yaml file.

Option 1: Via Helm CLI Add the following flag to your helm upgrade command:

--set nameOverride=rancher

Option 2: Via values.yaml Add the following line to your configuration file:

nameOverride: rancher