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

Automatic pod rescheduling #47965

Closed
rochdev opened this issue Jun 23, 2017 · 2 comments
Closed

Automatic pod rescheduling #47965

rochdev opened this issue Jun 23, 2017 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@rochdev
Copy link

rochdev commented Jun 23, 2017

/kind feature

Right now if a node is terminated, its pods are rescheduled on any other available node. However, once a new node is created to replace the failed node, pods are not rescheduled on this node, so in case of a failure of the other node will result in a temporary outage.

For example:

Node N1 has pod P1
Node N2 has pod P2
Node N1 fails
Node N2 has pod P1 and P2
Node N3 is created to replace Node N1
Node N2 has pod P1 and P2
Node N3 has no pods

If N2 fails, there will be an outage until pods are rescheduled on N3. If one of the pods would have been rescheduled automatically when N3 became healthy, each node would have had a pod and a failure of any node would not result in an outage.
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 23, 2017
@k8s-github-robot
Copy link

@rochdev There are no sig labels on this issue. Please add a sig label by:
(1) mentioning a sig: @kubernetes/sig-<team-name>-misc
e.g., @kubernetes/sig-api-machinery-misc for API Machinery
(2) specifying the label manually: /sig <label>
e.g., /sig scalability for sig/scalability

Note: method (1) will trigger a notification to the team. You can find the team list here and label list here

@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 23, 2017
@k8s-ci-robot k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Jun 23, 2017
@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 23, 2017
@krmayankk krmayankk mentioned this issue Jun 26, 2017
Closed
@davidopp
Copy link
Member

I agree with @krmayankk , this is a dupe of #12140. I'm going to close it, please reopen if you think the use case is not covered by that issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rochdev @davidopp @k8s-github-robot @k8s-ci-robot