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

Jump to bottom

How to consider the impact of network quality on POD scheduling? #87968

Closed
limx59 opened this issue Feb 10, 2020 · 3 comments
Closed

How to consider the impact of network quality on POD scheduling? #87968

limx59 opened this issue Feb 10, 2020 · 3 comments
Labels
kind/support Categorizes issue or PR as a support question. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@limx59
Copy link

limx59 commented Feb 10, 2020

For remote nodes, when a kubernetes distributed cluster deploys POD, how to combine factors such as network transmission delay and network transmission quality to pull up relevant PODs
@limx59 limx59 added the kind/support Categorizes issue or PR as a support question. label Feb 10, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 10, 2020
@athenabot
Copy link

/sig network

These SIGs are my best guesses for this issue. Please comment /remove-sig <name> if I am incorrect about one.

🤖 I am a bot run by vllry. 👩‍🔬

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 10, 2020
@athenabot
Copy link

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

@k8s-ci-robot k8s-ci-robot added the triage/unresolved Indicates an issue that can not or will not be resolved. label Feb 10, 2020
@thockin
Copy link
Member

thockin commented Mar 19, 2020

This is a great topic. I think the best forum for this would be the sig-network mailing-list rather than an issue here, at least until we can start to describe what we want to happen.

@thockin thockin closed this as completed Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/support Categorizes issue or PR as a support question. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@limx59 @thockin @k8s-ci-robot @athenabot