-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
static names for container-name #265
Comments
Isn't the dynamic naming by design @klml? With every Helm install, the application is given a name. This should be reflected in the objects to make it possible that instances of the same application can coexist, which would not work with static names. Or did I miss something here? I agree about the inconsistency and the bug in ingress, we should definitely improve that. |
Yes, the k8s resources itself should take over at least parts of the name of the release name, so the same chart can be installed multiple times in the same namespace. The names inside the resources, like containernames, could be static. |
@mgruner you are right
I moved this to #268 and .... @monotek you are also right ;)
so I redescribed this issue as only "container-name" and optional |
* Fix ingress configuration and use static container names. * Consistently prefer 'include' over 'template'. Fixes: #265 - static names for container-name Fixes: #268 - inconsistency static ingress and dynamic svc Co-authored-by: André Bauer <[email protected]>
Currently we are using dynamic container-name (eg name: {{ .Chart.Name }}-nginx This is sometimes confusing.
Version of Helm and Kubernetes:
zammad-12.0.0
What you expected to happen:
static container names
Anything else we need to know:
@monotek
The text was updated successfully, but these errors were encountered: