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

KEP-2433: Removing traffic policy interoperability as beta graduation requirement #3043

Merged
merged 1 commit into from
Nov 16, 2021

Conversation

robscott
Copy link
Member

The interoperability between InternalTrafficPolicy, ExternalTrafficPolicy, and Topology are actively being worked on by @danwinship (thanks!!). I think this is an important thing to get right, but I'm not sure it needs to block beta graduation. I expect the vast majority of users will want to user at most one of these features per Service. Open to other input here. This may all be a non-issue if all the kube-proxy updates and fixes manage to make it into 1.23, but I just wanted to start this conversation a bit earlier in case they don't.

/sig network
/cc @aojea @danwinship
/assign @thockin

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Nov 10, 2021
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory labels Nov 10, 2021
@thockin
Copy link
Member

thockin commented Nov 15, 2021

I don't understand "the vast majority of users will want to user at most one of these features per Service". Once beta, isn't topology on by default?

@robscott
Copy link
Member Author

I don't understand "the vast majority of users will want to user at most one of these features per Service". Once beta, isn't topology on by default?

Clarified on Slack but also responding here.

Beta just means the opt-in annotation is available by default, not that it is on for all services by default. I don’t think it will be very common for users to want to combine InternalTrafficPolicy and Topology on the same Service. With the current logic, if that is configured, traffic policy wins and topology hints are ignored. There is an argument that ExternalTrafficPolicy=Local + Topology for internal traffic could be useful, but I’m not sure that’s sufficient to block this graduating.

@thockin
Copy link
Member

thockin commented Nov 16, 2021

This makes me uncomfortable (seems mildly surprising) but I think topology feedback is really useful.

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: robscott, thockin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 16, 2021
@k8s-ci-robot k8s-ci-robot merged commit b309b70 into kubernetes:master Nov 16, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Nov 16, 2021
@pacoxu pacoxu mentioned this pull request Jan 22, 2025
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/network Categorizes an issue or PR as relevant to SIG Network. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants