Kubernetes: Deleting cluster node should delete non working node in priority

[olblak]

Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes - 1.6.6

What happened:

1. I setup a new ACS cluster (kubernetes) with two nodes
2. I drained the first agent node.
3. I update ACS cluster to only have one node
4. It removed the latest created node which wasn't the drained node.
5. Only pods run on master were working.

What you expected to happen:
I expect to keep working nodes in priority

How to reproduce it (as minimally and precisely as possible):

1. Create a new cluster with two nodes
2. Drain the first node 'XXXXX-0'
3. Via UI, set node to 1

Anything else we need to know:

[JackQuincy]

Currently the ACS service has no access to the details from the orchestrator to make this decision. If/When we decide to start doing more inside the vanilla orchestrators, then we will want to do something like this where we would actually cordon then drain a node before we delete it, and possibly look for non working nodes first.
But for now this is out of scope as we actually can't make a call to the orchestrator to find none working nodes.

[olblak]

Explained like that, it totally makes sense to me.
Thank for your response.