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
Is your feature request related to a problem? Please describe.
Not quite, but it's around consistency of how we label things. For examples I noticed that we have been using v prefixed labels when we tagged projects on Github but not prefixed when we published packages on the container registry.
Describe the solution you'd like
Our projects use SemVer, and everyone is closely aligned with how that works. We should write out a guide that outlines our policy of prefixing tags on:
Container registry
Version control systems (e.g Github)
Describe alternatives you've considered
NA
Additional context
I published a package on a repository with a prefix and the charts don't reference the prefix and hence had installation issues on EKS.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Not quite, but it's around consistency of how we label things. For examples I noticed that we have been using
v
prefixed labels when we tagged projects on Github but not prefixed when we published packages on the container registry.Describe the solution you'd like
Our projects use SemVer, and everyone is closely aligned with how that works. We should write out a guide that outlines our policy of prefixing tags on:
Describe alternatives you've considered
NA
Additional context
I published a package on a repository with a prefix and the charts don't reference the prefix and hence had installation issues on EKS.
The text was updated successfully, but these errors were encountered: