feat: auto-migrate on low capacity#184
Draft
ctrox wants to merge 3 commits into
Draft
Conversation
This allows to configure the activator to connect to any provided address instead of localhost.
ctrox
force-pushed
the
auto-migrate
branch
2 times, most recently
from
a436e54 to
8112249
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before restoring a container with migration enabled, the shim will ask the manager if the node has enough capacity available. If not, the pod will be auto-migrated to another node while the incoming traffic is held and eventually forwarded to the new pod.