-
Notifications
You must be signed in to change notification settings - Fork 562
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
Add traffic distribution annotation #3328
Add traffic distribution annotation #3328
Conversation
Also, the chart accidentally made it a label -- its an annotation, though. Fails until istio/api#3328
@@ -581,3 +581,21 @@ annotations: | |||
hidden: true | |||
resources: | |||
- Gateway | |||
|
|||
- name: networking.istio.io/traffic-distribution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If users are setting this, should it be a label?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make some sense, labels can be used to fiter by user
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have labels that start with networking.istio.io (for example gatewayPort); we also have annotations that start with networking.istio.io, for example exportTo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a design to set a guidance for this: https://docs.google.com/document/d/1q27KAgIzkmqDMWI1nTMOdlBvY-dRyGTldxe9Yu3pVq0/edit.
(the doc suggests this should be an annotation)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added an alternate proposal to that doc, because I prefer a criteria that's based on end-user usage and not development internals. I would suggest everyone look at that and add anything that's been missed.
This isn't a technical question at all really. It's a simple type. It could quite comfortably be either a label or an annotation, even under the proposal doc in its current state. If you think the tiebreak should be annotations, it's an annotation. If you think the tiebreak should be labels, it's a label.
Which is kinda why I'd rather go with what is maximally logical and simple to the end user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the TOC meeting on monday there was some agreement to go with the proposal in the doc which would make this an annotation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for that context, i caught up with the meeting mins and doc, SGTM
@@ -581,3 +581,23 @@ annotations: | |||
hidden: true | |||
resources: | |||
- Gateway | |||
|
|||
- name: networking.istio.io/traffic-distribution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we use same naming parttern like others, use networking.istio.io/trafficDistribution
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems we are split on which we use, with most new ones using -
instead of the casing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should make a clear rule on this, we just introuduce some new casing annotations IIRC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, don't see outstanding issue after the TOC discussion on Monday.
Also, the chart accidentally made it a label -- its an annotation, though. Fails until istio/api#3328
Also, the chart accidentally made it a label -- its an annotation, though. Fails until istio/api#3328
* traffic distribution: move to API repo Also, the chart accidentally made it a label -- its an annotation, though. Fails until istio/api#3328 * Rebase
Added in istio/istio#53435