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.

Sign up for GitHub

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

Aggregated used ports at the NodeInfo level. #42523

Closed
k82cn opened this issue Mar 4, 2017 · 0 comments · Fixed by #42524
Closed

Aggregated used ports at the NodeInfo level. #42523

k82cn opened this issue Mar 4, 2017 · 0 comments · Fixed by #42524

Comments

@k82cn
Copy link
Member

k82cn commented Mar 4, 2017

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Enhancement.

Kubernetes version (use kubectl version):
master

What happened:
In scheduler's PodFitsHostPorts predicates, it collect used ports every times. It's better to aggregate used ports into NodeInfo.
@k82cn k82cn mentioned this issue Mar 4, 2017
Merged
k8s-github-robot pushed a commit that referenced this issue Apr 8, 2017
Merge pull request #42524 from k82cn/used_ports_per_node
fed535e 
Automatic merge from submit-queue (batch tested with PRs 41775, 39678, 42629, 42524, 43028)

Aggregated used ports at the NodeInfo level.

fixes #42523

```release-note
Aggregated used ports at the NodeInfo level for `PodFitsHostPorts` predicate.
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Aggregated used ports at the NodeInfo level. k82cn/kubernetes
1 participant
@k82cn