-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Should all Skaffold labels be prefixed with skaffold-
?
#2002
Comments
seems like a good idea to me. |
+1 |
Does that count as a breaking change? If so, we would need to label with old and new label name for a transition period, right? |
@corneliusweig good point, unfortunately we don't really have insight into who is using these labels currently or what they're being used for. it would be pretty trivial to keep the old labels around for a while though, so I'd say being safe here doesn't really cost us anything. we could document it in the release notes, and then give a deprecation period (maybe two releases) after which the old labels would disappear. |
except for this one #2045 |
This issue was fixed with #2062. |
Skaffold applies custom labels to every resource that it deploys.
I think that every label that it applies should be prefixed with
skaffold-
to avoid conflicts with user labels.The text was updated successfully, but these errors were encountered: