Skip to content
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

Merged
merged 2 commits into from
Oct 18, 2024

Conversation

howardjohn
Copy link
Member

@howardjohn howardjohn added the release-notes-none Indicates a PR that does not require release notes. label Oct 9, 2024
@howardjohn howardjohn requested a review from a team as a code owner October 9, 2024 15:25
@istio-testing istio-testing added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 9, 2024
annotation/annotations.yaml Outdated Show resolved Hide resolved
howardjohn added a commit to howardjohn/istio that referenced this pull request Oct 9, 2024
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
Copy link
Contributor

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?

Copy link
Member

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

Copy link
Member

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.

Copy link
Member Author

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)

Copy link
Contributor

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.

Copy link
Member Author

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

Copy link
Member

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

annotation/annotations.yaml Outdated Show resolved Hide resolved
annotation/annotations.yaml Outdated Show resolved Hide resolved
@@ -581,3 +581,23 @@ annotations:
hidden: true
resources:
- Gateway

- name: networking.istio.io/traffic-distribution
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

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.

Copy link
Member

@linsun linsun left a 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.

@istio-testing istio-testing merged commit 585d68d into istio:master Oct 18, 2024
5 checks passed
howardjohn added a commit to howardjohn/istio that referenced this pull request Oct 18, 2024
Also, the chart accidentally made it a label -- its an annotation,
though.

Fails until istio/api#3328
howardjohn added a commit to howardjohn/istio that referenced this pull request Oct 21, 2024
Also, the chart accidentally made it a label -- its an annotation,
though.

Fails until istio/api#3328
istio-testing pushed a commit to istio/istio that referenced this pull request Oct 21, 2024
* traffic distribution: move to API repo

Also, the chart accidentally made it a label -- its an annotation,
though.

Fails until istio/api#3328

* Rebase
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes-none Indicates a PR that does not require release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants