-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Enable per-endpoint routes by default #14955
Comments
Just linking in issue #16717 here, seemed like a case where if we had a mix of endpoints with endpoint-routes enabled + endpoint-routes disabled, it could cause forwarding issues between the endpoints. One longer-term approach to solving that issue is to support endpoints in different modes concurrently. An alternative approach would be to support endpoint routes with all other configurations (per the goal of this issue) and switch to this by default. |
are there any plans to have this in 1.13 milestone? |
Hi @m-yosefpor 👋 You should already be able to enable endpoint routes in your cluster if you need it. Or is there a reason you need it to be enabled by default? |
Ok 👍 As far as I know, there are no plans to address #14240 for v1.12 or v1.13. It's something we'd like to address but it's not prioritized right now. |
This issue has been automatically marked as stale because it has not |
Another discrepancy: #28812 |
Per-endpoint routes (
enable-endpoint-routes
) are currently disabled by default. We want to enable them by default for 1.10, mostly as a workaround for #10645. This is a meta issue to track progress on that work item.The text was updated successfully, but these errors were encountered: