Incompatibility introduced by v0.27

What happened?

The upgrade guide for Upgrading to 0.27 mention

This release removes nameOverride field from values.yaml in favor of fullnameOverride. If you were using nameOverride field, please update your values file to use the new field.

Which seems to indicate that no manual action need to be done for those who were not using nameOverride.

But this is not the case, since the output of "timescaledb.fullname" change from {{ .Release.Name }}-timescaledb to {{ .Release.Name }}. Which makes the upgrade open to data lost, since new PVC will be scheduled to be created with the new name.

Did you expect to see something different?

The resolved "timescaledb.fullname" should not changed. This can be done by changing the default value for fullnameOverride from {{ .Release.Name }} to {{ .Release.Name }}-timescaledb. and clusterName to {{ .Release.Name }}.

Alternatively, update the "Upgrading to 0.27" guide to mention that the following configuration MUST be provided to allow seamless upgrade with no data lost.

clusterName: '{{ .Release.Name }}'
fullnameOverride: '{{ .Release.Name }}-timescaledb'

How to reproduce it (as minimally and precisely as possible):

Deploy timescaledb-single of any version before 0.27
Upgrade to 0.27

Environment

Which helm chart and what version are you using?
What is in your values.yaml ?

before the upgrade (v0.13.1):

timescaledb-single:
enabled: true
image:
  tag: pg14.2-ts2.6.1-latest
  repository: timescale/timescaledb-ha
replicaCount: 1
loadBalancer:
  enabled: false
postInit:
  - secret:
      name: timescaledb-post-init
secretNames:
  credentials: timescaledb-credentials
  certificate: timescaledb-certificate

after the upgrade (v0.33.1):

timescaledb-single:
enabled: true
image:
  tag: pg14.2-ts2.6.1-latest
  repository: timescale/timescaledb-ha
replicaCount: 1
postInit:
  - secret:
      name: timescaledb-post-init
secrets:
  credentialsSecretName: timescaledb-credentials

Kubernetes version information:

kubectl version
Kubernetes cluster kind:

insert how you created your cluster: kops, bootkube, etc.

Anything else we need to know?:

timescale / helm-charts

Incompatibility introduced by v0.27 #576