Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

Define machines deletion policies. #625

Closed
p0lyn0mial opened this issue Feb 28, 2018 · 3 comments
Closed

Define machines deletion policies. #625

p0lyn0mial opened this issue Feb 28, 2018 · 3 comments

Comments

@p0lyn0mial
Copy link
Contributor

The current implementation of MachineSet chooses the first machine from the list to delete. As this doesn't provide any guarantees of consistency regarding the order of the items. It is random. We would like to identify some strategies that would provide better approaches for deletion.

@p0lyn0mial
Copy link
Contributor Author

/cc @rsdcastro

@rsdcastro rsdcastro added this to the cluster-api-beta milestone Mar 1, 2018
@mvladev
Copy link
Contributor

mvladev commented Mar 7, 2018

If I would manually remove one Machine from a set of machines I would use the order bellow to determine which to remove:

  1. Machine needs to be preferably removed - marked with annotation or some other means by human / cluster autoscaler (down-sizing scenario) / other controller
  2. Health of the Machine - unhealthy machines first
  3. If all else fails: select one at random

@rsdcastro
Copy link

This issue was moved to kubernetes-sigs/cluster-api#45

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants