The CoreOS Multinode Cluster guide appears to have a problem. When I create a cluster and configure connectivity, everything appears fine -- however, I'm unable to create an ELB through service exposing:

$ kubectl expose rc my-nginx --port 80 --type=LoadBalancer
service "my-nginx" exposed

$ kubectl describe services
Name:           my-nginx
Namespace:      temp
Labels:         run=my-nginx
Selector:       run=my-nginx
Type:           LoadBalancer
IP:         10.100.6.247
Port:           <unnamed>   80/TCP
NodePort:       <unnamed>   32224/TCP
Endpoints:      10.244.37.2:80,10.244.73.2:80
Session Affinity:   None
No events.

The IP line that says 10.100.6.247 looks promising, but no ELB is actually created in my account. I can otherwise interact with the cluster just fine, so it seems bizarre. A "kubectl get services" listing is similar -- it shows the private IP (same as above) but the EXTERNAL_IP column is empty.

Ultimately, my goal is a solution that allows me to easily configure my VPC (ie. private subnets with NAT instances) and if I can get this working, it'd be easy enough to drop into CloudFormation since it's based on user-data. The official method of kube-up doesn't leave room for VPC-level customization in a repeatable way.