Use unique names -- include release name

[remram44]

This is the first Helm Chart I've encountered that don't include the release name in the names of created object. If I helm install mycloud ocis/ocis, I expect deployments/services/... objects to be named mycloud-web, mycloud-proxy, ... so they don't conflict with other installed charts.

This is even the default in the helm create chart. Why did you get rid of the fullname macro? This is dangerous.

[wkloucek]

I will have a look into this. It's most likely not there because this chart was not bootstrapped by helm create.

[remram44]

helm create does use unique names, via the ocis.fullname template.

It was present in the first commit and was immediately removed:

ocis-charts/templates/deployment.yaml

Lines 3 to 6 in 7f91f94

	metadata:
	name: {{ include "ocis.fullname" . }}
	labels:
	{{- include "ocis.labels" . | nindent 4 }}

[d7oc]

Yes was removed without further notice in ec848c1. I will try to add this again.

[d7oc]

Had a first look. There is a dependency to #50 which needs to be addressed first. If the app/service names change, the certificate as generated in our docs at https://doc.owncloud.com/ocis/next/deployment/container/orchestration/orchestration.html#built-in-user-management-secrets won't match anymore, as the name will not be fixed to idm each time. So there needs to be a dynamic process.

[dnrce]

@d7oc and @wkloucek, I see that #50 is resolved. Are you aware of anything else that would still block this change?

[wkloucek]

@d7oc and @wkloucek, I see that #50 is resolved. Are you aware of anything else that would still block this change?

The release name would needed to be included in every objects' name. Also we would need to touch all selector labels. Also the secret auto-generation would need to be touched.

I guess it's still a lot of work (especially when considering a path for backwards compatibility). To be honest, from my side this is more a low priority right now, but I'm just a developer and no product manager.