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
If i have a subchart named subchart-name, I will violate the naming convention with these values.yaml in my umbrella chart:
subchart-name:
name: nginx
This is a design flaw that seems like we're stuck with but all users using sub charts will face this problem if they use the conventions you've laid out. The closing statement in helm/helm#2192 says that documentation was updated, but I see nothing that warns users of this problem and users are forced to do an internet search on how to work around this problem. I think you should update the documentation correctly. Either by stating that all sub charts should be aliased to a name without hyphens or that if you don't use alias than the workaround using index is required. And that workaround should be clearly documented.
The text was updated successfully, but these errors were encountered:
In addition using aliases is not ideal because there are a whole list of problems you can run into when using them, a good summary in: helm/helm#9150 (comment)
Hello, the naming convention says that helm chart name can contain dashes, but variable name not:
If i have a subchart named subchart-name, I will violate the naming convention with these values.yaml in my umbrella chart:
This is a design flaw that seems like we're stuck with but all users using sub charts will face this problem if they use the conventions you've laid out. The closing statement in helm/helm#2192 says that documentation was updated, but I see nothing that warns users of this problem and users are forced to do an internet search on how to work around this problem. I think you should update the documentation correctly. Either by stating that all sub charts should be aliased to a name without hyphens or that if you don't use alias than the workaround using index is required. And that workaround should be clearly documented.
The text was updated successfully, but these errors were encountered: