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

React to failure by growing the remaining clusters #7614

Merged
1 commit merged into from May 5, 2015

Conversation

tamsky
Copy link
Contributor

@tamsky tamsky commented May 1, 2015

@ghost
Copy link

ghost commented May 1, 2015

LGTM

1. I manually specify "additional resources to be provisioned" per
remaining cluster, possibly proportional to both the remaining functioning resources
and the unavailable resources in the failed cluster(s).
(All the benefits of over-provisioning, without expensive idle resources.)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The drawback here is that you might not be able to acquire the resources.
If everyone is planning to do this, and a large IaaS provider/zone has a large outage, it isn't assured that everyone can instantly scale up on other IaaS providers/zones.

@j3ffml j3ffml added the kind/design Categorizes issue or PR as related to design. label May 1, 2015
@roberthbailey roberthbailey assigned ghost May 4, 2015
ghost pushed a commit that referenced this pull request May 5, 2015
React to failure by growing the remaining clusters
@ghost ghost merged commit 868df86 into kubernetes:master May 5, 2015
@tamsky tamsky unassigned ghost Aug 12, 2015
xingzhou pushed a commit to xingzhou/kubernetes that referenced this pull request Dec 15, 2016
React to failure by growing the remaining clusters
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/design Categorizes issue or PR as related to design.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants