-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Pod locality for services (node-local, etc.) #274
Comments
Also see other existing discussion at kubernetes/kubernetes#28610 |
As discussed in SIG-Network meeting, the proposal has not been finalized according to the issues linked in the description. These issues should be addressed prior to an official milestone assignment. |
@cmluciano what issues are you talking about? I can't find any description linking issues in any of the links above. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/remove-lifecycle stale |
There is a proposal trying to figure out a more generic way for local-only service, say "topology aware routing of services", please check kubernetes/community#1551 We need more user cases to refine the API, please feel free to populate your comments there :) Thanks! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
@therc If so, can you please ensure the feature is up-to-date with the appropriate:
cc @idvoretskyi |
This feature current has no milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12. If so, please ensure that this issue is up-to-date with ALL of the following information:
Set the following:
Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12. Please note that Features Freeze is tomorrow, July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.In addition, please be aware of the following relevant deadlines:
Please make sure all PRs for features have relevant release notes included as well. Happy shipping! P.S. This was sent via automation |
Hi
Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet Thanks! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I believe this has been supplanted by #640 This can probably be closed but confirming with others @caseydavenport @thockin @m1093782566 |
@cmluciano yes that's my understanding as well. |
/close |
@cmluciano: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Feature Description
The text was updated successfully, but these errors were encountered: