Summary: 34 instances, 29 unique

Text	Count
// TODO: Continue?  Tolerate non-attached error from the AWS DetachVolume call?	1
// TODO: revisit these values	1
// TODO: add additional tags from users	1
// TODO: Move to instanceCache	1
// TODO: use ClientToken for idempotency?	1
// TODO: Is there any use for this?  We can get it from the instance metadata service	1
// TODO: revise the logic	1
// TODO: should we support ExternalIP by default?	1
// TODO: This is pretty arbitrary	1
// TODO: Wait for creation?	1
// TODO: Check if the volume was concurrently attached?	1
// TODO: Caching / expose v1.Nodes to the cloud provider?	1
// TODO: All clouds should be cluster-aware by default	1
// TODO: replace DefaultLoadBalancerName to generate more meaningful loadbalancer names.	1
// TODO: Remove when user/admin can configure volume types and thus we don't	1
// TODO: What happens if we have more than one subnet per AZ?	2
//TODO: It would be nice to be able to determine the reason for the failure,	3
// TODO: Clean up double-API query	1
// TODO: Sync internal vs non-internal	2
//  TODO: support node name policy other than private DNS names	1
// TODO: Allow other clouds to implement this	2
// TODO: We could also query for subnets, I think	1
// TODO: implement ONLY for external cloud provider	1
// TODO: Should we rename this to AWS (EBS & ELB are not technically part of EC2)	1
// TODO: Check if error was because load balancer was concurrently deleted	1
// TODO: Other IP addresses (multiple ips)?	1
// TODO: There is a limit in VPC of 100 rules per security group, so we	1
// TODO: Get rid of this field, send all calls through the instanceCache	1
// TODO: Wait for creation?	1