Charts should be prefixed with an identifier

[carpenterm]

Is your feature request related to a problem? Please describe.
The fact the chart is called "operator" is confusing as when you upload it to a repository with a bunch of other charts you have no idea what it is. Same for the "tenant" chart.

Describe the solution you'd like
The charts should be prefixed with an identifier e.g. "minio-operator" and "minio-tenant"

Describe alternatives you've considered
Hacky renaming of Chart.yaml and folders after downloading which need reapplying on every release and are error prone.

Additional context
None

[jdonzallaz]

Hi,

I would add that this also cause conflicts making installing charts dependencies with the same name impossible.

Because the name "operator" is so generic and also used by others (e.g. redpanda), it causes errors on installation: Error: can't get a valid version for repositories operator. Try changing the version constraint in Chart.yaml].

Note: It should also be noted that Helm developers are not willing to fix the underlying cause (see issue).

[cesnietor]

@cniackz could you please take a look at this one and verify if it'd make sense to add the prefix and not cause issues with existing deployments? 🙏

[ramondeklein]

When you add a Helm repository, then you typicall add it like this:

helm repo add minio https://operator.min.io

So, the name of the repository will be called minio. Then when you install it, you run

helm install minio-operator minio/operator --namespace minio-operator --create-namespace

So the actual chart is referenced using minio/operator that references the operator chart in the https://operator.min.io repository. Also the name of the installed instance can be named by the user, so I don't understand the actual problem. I don't see a real issue here.

We can change the Helm charts, but that would render all old documentation, blogs, StackOverflow answers useless. I don't see a good reason why to do this.

[dke]

The other issue with this naming is in the context of embedding the chart in a meta chart. Then by definition / by current helm behavior, the dependency would be listed at

- name: operator
  repository: https://operator.min.io
  version: 7.0.0
- name: tenant
  repository: https://operator.min.io
  version: 7.0.1

... and on helm dep up, they would be downloaded into

operator-7.0.0.tgz
tenant-7.0.1.tgz

... and then we don't have the prefixes mentioned above (like, our custom repo names).

Using an alias on the dependency doesn't change anything here, as it does not affect the downloaded filename.

You might argue that realistically no one might want to put the operator in a chart dependency, but for the tenant this should be a common usecase.

[ramondeklein]

We won't be renaming the charts. It will cause a lot more trouble, then our current naming does. We also need to consider compatibility.