However, I'm using mesos, marathon and chronos to manage a production environment with service discovery glue based on Route53.
Using Docker to ship an application to a well configured environment is just a delight, the amount of configuration needed is absolutely minimal.
However, I think people need to realize that it's "easy" if your services are not talking to each other and dependent on one another in a way. If service X is using service Y directly (via HTTP), it gets a bit more challenging.
The way I like to configure micro-service is based on messaging so you send a message to a queue and multiple satellite services can consume that message and do stuff with it.
If your services are dependent on one another, the configuration gets trickier and the maintenance gets a bit harder.
Good job by Box also contributing back to the core of Kube based on what they needed, based on it getting merged I am guessing other people will find it useful as well.