The scheduler is just best effort at the moment there's some ways around it. You could indeed create seperate replication-controllers against labels, such as y

The scheduler is just best effort at the moment there's some ways around it. You could indeed create seperate replication-controllers against labels, such as your aws-zone, and run them seperatly. This flies in the face of having replication-controllers and sucks in my opinion. The other option is a single replication-controller and have your containers use a resouce that can't be reused, thus ensuring you're scheduled elsewhere. This is hacky. I suspect it'll be another year before kubernetes is all singing and dancing, but I do like using it.