philipcristiano

When I tried this I was hoping there was some reduction in packaging associated. At least for me, it was just all the same boxes on the same day, instead of one big box, or something reusable/returnable like Fresh.

What would you use to provide a single endpoint to multiple instances of an app server?

The article claims "Without its internal heaters turned up to-the-max, a shrew would leak out all of its heat and freeze. And this explains its furious appetite."

Dairy and eggs both involve the death of animals. Dairy cows produce milk for their offspring. In order for us to get milk the offspring must be removed. Typically males are sold for veal, females continue as dairy cows. The production of laying hens results in roughly 50/50 male vs female chickens. Most of the males are killed shortly after hatching as they are not the variety kept for meat.

The autoscaler will add minions when there is a pod that cannot be scheduled. It doesn't help in balancing existing things, but at least the new pod should be able to go there.

kops creates an autoscaling group for the worker nodes as part of the cluster creation process. Adding the cluster autoscaler is simple as deploying the autoscaler (as mentioned in your linked docs) pointing to the correct ASG. The IAM permissions for the autoscaler can be added with `kops edit cluster $CLUSTER`.

What is the concern with using bigger nodes then planned?

I agree the basic networking has a lot of limitations. Compared with added more layers with networking, I'd rather have a simpler setup with fewer nodes, even if they are larger.

That's the case if you were going to deploy this on Linux. The packages provided are for SmartOS.

I'm surprised you found that, I'm working on etsdb on hack days when I get the chance. It sort of works but shouldn't be trusted with production data.