KEP-2433: Removing traffic policy interoperability as beta graduation requirement #3043
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One-line PR description: Removes traffic policy interoperability as beta graduation requirement
Issue link: Topology Aware Routing #2433
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