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

Open
therc opened this Issue Apr 25, 2017 · 15 comments

Comments

Projects
@therc
Copy link

therc commented Apr 25, 2017

Feature Description

  • One-line feature description (can be used as a release note): Allow clients to talk only to a service's pods running on the same node/rack/AZ/region/label, etc.
  • Primary contact (assignee): therc
  • Responsible SIGs: sig-network
  • Design proposal link (community repo): kubernetes/kubernetes#28637 (can be recreated in the community repo if needed)
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @thockin @smarterclayton
  • Approver (likely from SIG/area to which feature belongs): @thockin
  • Initial target stage (alpha/beta/stable) and release (x.y): alpha 1.7
@therc

This comment has been minimized.

Copy link

therc commented Apr 25, 2017

Also see other existing discussion at kubernetes/kubernetes#28610

@cmluciano

This comment has been minimized.

Copy link
Member

cmluciano commented May 4, 2017

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.

@kargakis

This comment has been minimized.

Copy link
Member

kargakis commented May 5, 2017

@cmluciano what issues are you talking about? I can't find any description linking issues in any of the links above.

@cmluciano

This comment has been minimized.

Copy link
Member

cmluciano commented May 7, 2017

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Dec 24, 2017

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@craigbox

This comment has been minimized.

Copy link
Contributor

craigbox commented Jan 2, 2018

/remove-lifecycle stale

@m1093782566

This comment has been minimized.

Copy link
Member

m1093782566 commented Jan 3, 2018

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!

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Apr 3, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@craigbox

This comment has been minimized.

Copy link
Contributor

craigbox commented Apr 3, 2018

/remove-lifecycle stale

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Apr 17, 2018

@therc
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:
    • stage/{alpha,beta,stable}
    • sig/*
    • kind/feature

cc @idvoretskyi

@justaugustus justaugustus removed this from the next-milestone milestone Jul 2, 2018

@justaugustus

This comment has been minimized.

Copy link
Member

justaugustus commented Jul 30, 2018

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:

  • One-line feature description (can be used as a release note):
  • Primary contact (assignee):
  • Responsible SIGs:
  • Design proposal link (community repo):
  • Link to e2e and/or unit tests:
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
  • Approver (likely from SIG/area to which feature belongs):
  • Feature target (which target equals to which milestone):
    • Alpha release target (x.y)
    • Beta release target (x.y)
    • Stable release target (x.y)

Set the following:

  • Description
  • Assignee(s)
  • Labels:
    • stage/{alpha,beta,stable}
    • sig/*
    • kind/feature

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:

  • Docs deadline (open placeholder PRs): 8/21
  • Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

P.S. This was sent via automation

@kacole2

This comment has been minimized.

Copy link
Contributor

kacole2 commented Oct 8, 2018

Hi
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:

  • Docs (open placeholder PRs): 11/8
  • Code Slush: 11/9
  • Code Freeze Begins: 11/15
  • Docs Complete and Reviewed: 11/27

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!

@fejta-bot

This comment has been minimized.

Copy link

fejta-bot commented Jan 6, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@cmluciano

This comment has been minimized.

Copy link
Member

cmluciano commented Jan 8, 2019

I believe this has been supplanted by #640

This can probably be closed but confirming with others @caseydavenport @thockin @m1093782566

@caseydavenport

This comment has been minimized.

Copy link
Member

caseydavenport commented Jan 9, 2019

@cmluciano yes that's my understanding as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment