You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2019. It is now read-only.
Kubernetes allows different resource types to be named the same, even within the same namespace. If the operator is watching multiple resource types and there is an instance of each resource type with the same name, they will resolve to the same release name, which tiller does not support.
An obvious option is to include the resource type in the release name, but that is problematic due to a 53-character limit on the release name imposed by helm.
This would pull the release name from the object's actual release, and if that doesn't exist, an empty string would result in Tiller generating a unique release name during release installation. This approach would require the use of a finalizer (provided by #48) to be able to lookup the release name during uninstallation.
We could also consider supporting an annotation or two that allows a user to override the default provided by tiller. For example:
This issue manifests itself only after #48 is merged, once multiple resource types are supported.
The release name lookup for an object returns a value that is not sufficiently unique:
helm-app-operator-kit/helm-app-operator/pkg/helm/helm.go
Lines 224 to 226 in 0a420ad
Kubernetes allows different resource types to be named the same, even within the same namespace. If the operator is watching multiple resource types and there is an instance of each resource type with the same name, they will resolve to the same release name, which tiller does not support.
An obvious option is to include the resource type in the release name, but that is problematic due to a 53-character limit on the release name imposed by helm.
A better solution may be something like:
This would pull the release name from the object's actual release, and if that doesn't exist, an empty string would result in Tiller generating a unique release name during release installation. This approach would require the use of a finalizer (provided by #48) to be able to lookup the release name during uninstallation.
We could also consider supporting an annotation or two that allows a user to override the default provided by tiller. For example:
<resource_string>/resource-name-as-helm-release-name
:"true"|"false"
<resource_string>/helm-release-name
:<release_name>
Thoughts?
The text was updated successfully, but these errors were encountered: